Great Circle Associates Majordomo-Users
(May 2001)
 

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

Subject: Re: Problems with invalid return addresses
From: Dan Liston <dliston @ netscape . com>
Organization: iPlanet eCommerce Solutions, A Sun|Netscape Alliance
Date: Tue, 15 May 2001 13:59:12 -0500
To: "Dean J. Pompilio" <dean_j_pompilio @ yahoo . com>
Cc: majordomo-users @ GreatCircle . COM
References: <20010515135707.77744.qmail@web10406.mail.yahoo.com>

Majordomo 1.94.5 requires fully qualified email addresses in the From: header.
Using echo and mail from the command line does not add @your.domain.tld to the 
root (or any other users) address.

There are two ways I have gotten around the
"
MAJORDOMO ABORT (mj_majordomo)!!

Majordomo@your.domain.tld: First Last <login> is not a valid return address.
"
error message.  

Using Sendmail, use the "FEATURE(always_add_domain)dnl" in your m4
sendmail.mc file.  This will tag @your.domain.tld onto any local user or
alias that sends mail from the local machine.

OR

Edit majordomo.pl (thanks Mike O.).
Line 605 in Version 1.94.5 from;
                if (!(/\@/ && /\./)) {
to what Line 590 in Version 1.94.4 used to be;
                if (/\@/ && !/\./) {

In my opinion, the 1.94.4 version is more correct as login names and
aliases do not need to be fully qualified when they are on the same host
as the mail server or list server.  login@host is even a valid mail
address in relation to the local network, which is what the 1.94.4
version was trying to catch (if the address has an at sign but no dot). 
Neither the "@" nor the "." should be mandatory to the list server if
the MTA does not require them.  While it is easier to manage a
subscriber list by requiring the "@" and "." for a human, it makes no
difference to sendmail.

On the other hand, "if (!(/.+\@.+\..+/)) {" as Mike suggests is a much
better test if you DO wish to force "@" and "." in the correct sequence
in an email (or from) address.  This expression says the address must
have at least one or more of any character followed by an at sign, one
or more characters followed by a dot, and one or more characters. 

Considering no TLD has numerics, dashes, underscores or other
mathematical or punctuation characters, the final "." in the expression
could easily be replaced with "[a-z]" assuming all lower casing has 
already happened, or "[a-zA-Z]" if lower casing has not happened yet.  
With the exception of .arpa, .nato, .firm, and .store, no TLD has less 
than 2 or more than 3 characters.  While these TLDs are probably valid 
for web browsing, I doubt their validity for useful email addressing, 
bringing us back to a 2 or 3 letter TLD.  A tighter narrowing of valid 
addressing could be a regex of 

"if (!(/[a-z0-9][-a-z0-9_+.]*\@([a-z][-a-z0-9]*\.)+[a-z][a-z][a-z]?/)) {" 

which forces an alpha-numeric as the first character of an email address, 
followed by another alpha-numeric or dash, underscore, plus, or period
zero or more times followed by an at sign to signify the end of the LHS
of the address.  The first section in parenthesis after the at sign 
allows for one or more instances of a host or domain name beginning with
a letter followed by one or more alpha-numerics (or dash) and a period.
Lastly, the regex above requires 2 and allows an optional 3rd alphabetic
character as the top level domain.

Even with this, majordomo should only test validity of an email address 
on subscribe commands.  Unsubscribe only has to find and exact match for
addresses that have already been successfully added to the distribution
list during the subscribe process.

Dan Liston

(final note: I am not sure if the period in the second character class
above needs to be escaped with a back-slash, and potentially, the same
character class could be expanded to include other RFC compliant 
characters.)

"Dean J. Pompilio" wrote:
> 
> I am reasonably confident that I have set up Majordomo correctly.  When I issue
> the 'lists' command as root, (echo 'lists' | mail majordomo), I get the
> following error message in root's email.
> --------------------------------------------------------------------
> From Majordomo-Owner@dpompilio.kdc.capitalone.com Tue May 15 09:36:39 2001
> Date: Tue, 15 May 2001 09:36:39 -0400 (EDT)
> Message-Id: <200105151336.JAA07546@dpompilio.kdc.capitalone.com>
> To: Majordomo-Owner@dpompilio.kdc.capitalone.com
> From: Majordomo@dpompilio.kdc.capitalone.com
> Subject: MAJORDOMO ABORT (mj_majordomo)
> Content-Length: 130
> 
> --
> 
> MAJORDOMO ABORT (mj_majordomo)!!
> 
> Majordomo@dpompilio.kdc.capitalone.com: Super-User <root> is not a valid return
> address.
> --------------------------------------------------------------
> 
> My aliases file is below:
> --------------------------------------------------------------
> majordomo:      "|/usr/local/majordomo-1.94.5/wrapper majordomo"
> majordomo-owner: root
> owner-majordomo: root
> 
> test:           "|/usr/local/majordomo-1.94.5/wrapper resend -l test test-list"
> test-list:      :include:/usr/local/majordomo-1.94.5/lists/test
> owner-test:     root
> test-owner:     root
> test-request:   "|/usr/local/majordomo-1.94.5/wrapper majordomo -l test"
> --------------------------------------------------------------
> 
> This is the first time I am trying to get this working on my Sparc 10
> workstation, so I may be doing something really stupid here...
> 
> One last thing!  I can't seem to download the 'majorcool' web front end for
> majordomo.  Does anyone know of an alternate location for this software
> besides:
> 
> http://www.conveyanced.com/MajorCool/
> 
> Thanks a million!



References:
Indexed By Date Previous: Majordomo+Postfix..
From: Ish Rattan <ishwar@pali.cps.cmich.edu>
Next: Re: HowDoI Prevent 'vacation' function from echo/replying to the list?
From: Dan Liston <dliston@netscape.com>
Indexed By Thread Previous: Re: Problems with invalid return addresses
From: CB <todd@mrball.net>
Next: HowDoI Prevent 'vacation' function from echo/replying to the list?
From: Stewart Dean <sdean@bard.edu>

Google
 
Search Internet Search www.greatcircle.com