# Configure X400 parsing here. This is functional, but not well tested
# and rather a hack.
# By default all addresses that look x400-ish will be checked for a
# @ sign (meaning that it's headed to an smtp->x400 gateway, as well
# as the 'c=' and 'a[dm]=' parts, which mean something as well.
# If you will be receiving x400 style return addresses that do not have
# an @ sign in them indicating an smtp->x400 gateway, set $no_x400at to 1.
# Otherwise, leave $no_x400 at 0.
$no_x400at = 0;
Anything that munges an address by adding spaces before the majordomo server
sees the message is outside majordomo's control and can not be managed or
corrected by majordomo. Space or Tab characters are not valid characters in
an email address. A list address IS an email address. If you have spaces
in the subscriber list that are not part of an email "comment" field, the
membership file needs to be cleaned up. Keep in mind, that I am defining
address separately from comment for each line of the subscriber file.
What is the OS being used? What MTA and version? What version of majordomo?
Ralph Manak wrote:
> I've set up some lists for a non-profit organization. When they try to post
> messages, they bounce with this notification:
> The e-mail account does not exist at the organization this message was sent
> to. Check the e-mail address, or contact the recipient directly to find out
> the correct address.
> <theirMAILSERVER.theirDOMAIN.theirname.ORG #5.1.1>
> Their (x400, I think) mailer seems to add ' ' s to the list address, and
> therefore the address is not recognized. Is anyone familiar with this
> situation, and have a way to resolve it?
> They can send messages from their home ISP accounts.
> I also have this set up with restricted-send (these are announcement-only
> ... ... ... ...
> Ralph Manak
> Oakland CA
> email@example.com | http://rmanak.home.mindspring.com/