Zhigang Chen wrote:
>>Since majordomo was able to reply by sending the confirmation
>>request to you successfully, I can only assume that your reply
>>message was sent back to the wrong place, which was why it
>>bounced back to you. Perhaps you sent your request to umich.edu
>>rather than apple.umich.edu?
>apple and banana are in the same subnet. When I send email from a
>different email account to email@example.com.
>I can receive the message at banana, but not apple. zhigangc is the
>account that both apple and banana have. If a message is sent to
>firstname.lastname@example.org, the message is bounced back because there is no majordomo at banana.
If you do not have a .forward or an entry in the /etc/aliases file on
apple that redirects your mail from apple to banana, this tells me that
you have MTA (sendmail) issues that need to be worked out. I am curious
about how majordomo was able to reply from apple in the first place, if
mail to apple ends up on banana. How did you get your original
subscription request to majordomo? It sounds like something somewhere
upstream needs to be informed of the addresses on apple, so that email
actually routes to apple for the addresses that live on that server.
This is "not" a funtionality of majordomo, but your MTA and/or your
Ignoring majordomo for the moment, and focussing on your email flow
between servers, do apple and banana talk to each other directly, or is
there a higher authority (smarthost) that both must talk to in order to
send email out? Can you send a message for example from apple to me at
my domain, and another from banana, so that I can compare headers of
each message? If I reply to either message or both, will those messages
be delivered at the host the original message was sent from? Without
this basic funtionality, your email service is broken and must be fixed.
What tests have you performed to determine email works (to and from)
apple.unich.edu? Have you examined the /var/log/maillog* files on apple
to see if sendmail is receiving?
Getting back to majordomo, only after the above funtionality is working,
can we diagnose potential issues with majordomo. Right now, your
problem does not appear to be a majordomo problem.