Great Circle Associates Majordomo-Workers
(April 2000)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: majordomo.pl address matching
From: Dave Wolfe <dwolfe @ lists . linuxppc . org>
Date: Mon, 24 Apr 2000 12:09:37 -0500
To: relph @ sgi . com
Cc: majordomo-workers @ greatcircle . com, majordomo-patches @ cloud . ccsf . cc . ca . us
In-reply-to: <10004232053.ZM97064@mando.engr.sgi.com>; from John Relph on Sun, Apr 23, 2000 at 08:53:14PM -0700
References: <200004231953.MAA87125@mando.engr.sgi.com> <20000423223132.C30799@lists.linuxppc.org> <dwolfe@lists.linuxppc.org> <10004232053.ZM97064@mando.engr.sgi.com>

[ John Relph writes: ]
> On Apr 23, 22:31, Dave Wolfe wrote:
> >I can't tell if your changes even do the same thing, but it appears that
> >they attempt to deal w/ unqualified addresses (no domain). Don't know
> >about stock 1.94.5, but other patches disallow unqualified addresses.
> >Your best bet is to fix your MTA so that you never get unqualified
> >addresses. It prevents a lot of other problems that way.
> 
> Actually, I am comparing the addresses to "majordomo@where.am.i".  To
> make sure that neither of the addresses is the address of majordomo.
> I think.  You know, it's been so long since I hacked this that I don't
> even remember what it was I was trying to do.  But I do know that this
> change fixed some problems I was having.  (I hope it wasn't the unQ'ed
> address problem.)  I guess I'll have to look at it once more.  (I wish
> I had emacs on my majordomo machine.)  You may be right about the
> unQ'ed address hack, though.
[...]
>     if ($addr1[0] eq $addr2[0]) {
>       if ($#addr1 == 0 && $#addr2 == 1 && $addr2[1] eq $main'whereami) { #'
>           return(1);
>       }
>       if ($#addr2 == 0 && $#addr1 == 1 && $addr1[1] eq $main'whereami) { #'
>           return(1);
>       }
>     }

Nope, $whereami is the local FQDN, $whoami is Majordomo@$whereami.
Annotated:

    # if user names are the same...
    if ($addr1[0] eq $addr2[0]) {
      # if addr1 has no domain and addr2 does and addr2's domain is my
      # domain, then return true.
      if ($#addr1 == 0 && $#addr2 == 1 && $addr2[1] eq $main'whereami) { #'
          return(1);
      }
      # if addr2 has no domain and addr1 does and addr1's domain is my
      # domain, then return true.
      if ($#addr2 == 0 && $#addr1 == 1 && $addr1[1] eq $main'whereami) { #'
          return(1);
      }
    }

In other words, you expect to receive unqualified local addresses and
want to detect them. Unfortunately, unqualified remote addresses that
match local users will be matched too.

Understand that I have no intention of telling you what you can or
can't do w/ your Mj installation. If it works for you, it's served its
purpose. But I think the real problem is w/ the MTA configuration and
that makes the changes unsuitable for general use. Same story for the
LookOut!...er, OutLook users; those folks definitely need a lot of help,
probably more than a help file or instructions in a mail message can
offer. You might want to look into Majordomo2 instead, which simplifies
the authentication exchange somewhat.

-- 
 Dave Wolfe



References:
Indexed By Date Previous: Re: Change between Majordomo-1.94.4 and 1.94.5
From: Dave Wolfe <dwolfe@lists.linuxppc.org>
Next: majordomo config-test suggested patch
From: Jerry Sweet <jsweet@undoo.com>
Indexed By Thread Previous: Re: majordomo.pl address matching
From: relph@mando.engr.sgi.com (John Relph)
Next: Change between Majordomo-1.94.4 and 1.94.5
From: "Eric M. Sisson" <ems@mdacc.tmc.edu>

Google
 
Search Internet Search www.greatcircle.com