 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] domain alias with...| From | Sent On | Attachments |
|---|---|---|
| charles uchu | Apr 19, 2006 8:01 pm | |
| Sam Varshavchik | Apr 19, 2006 8:26 pm | |
| charles uchu | Apr 19, 2006 9:18 pm | |
| Sam Varshavchik | Apr 20, 2006 3:49 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [courier-users] domain alias with email alias issues | Actions... |
|---|---|---|
| From: | charles uchu (onl...@gaiahost.coop) | |
| Date: | Apr 19, 2006 9:18:38 pm | |
| List: | net.sourceforge.lists.courier-users | |
Sam Varshavchik wrote:
charles uchu writes:
what happened:
1) sent a message to username1@aliaseddomain, when username1@primarydomain is a mailbox, it arrives just fine in username1@primarydomain mailbox.
2) sent a message to username2@aliaseddomain, when there is only an alias for username2@primarydomain. bounce back occurred with "user unknown". 3) added an alias for username2@aliaseddomain to match the forwarding addresses listed for username2@primarydomain alias. sending again and the email got delivered fine with this extra layer of aliasing aliases... seems like a redundant work-around. any suggestions?
Sorry. This is too confusing to figure out. If you're going to ask questions that use randomly-generated E-mail addresses, pulled out of thin air, then you should also employ a random number generator to find your answer.
Otherwise, you should post the actual contents of your configuration files (locals, hosteddomains, aliases, and so on), as well as the actual portions of your maillog/syslog files, that show what the problem is. Reading the repetitive occurences of "username1", "username2", "domain1", "domain2", "fooX", just makes one's eyes glaze over.
sam,
sorry about that. was trying to protect the innocent. hopefully this clarifies settings while still being non-specific about domains and address involved in testing.
DOMAIN ALIAS SETUP (common for all scenarios): [hosteddomains] bigelephant.com bigelephant.net bigelephant.com
[esmtpacceptmailfor] bigelephant.com bigelephant.net
SCENARIO 1: (successful)
mailbox created: john...@bigelephant.com
Action Success: email sent to john...@bigelephant.net properly arrives at john...@bigelephant.com (a good confirmation that the domain aliasing was working, at least somewhat)
Log Result: Expected logs written in mail.log for processing and delivery of message.
SCENARIO 2: (unsuccessful)
mailbox created: john...@bigelephant.com
alias created (makealiases) jo...@bigelephant.com: john...@bigelephant.com
Action Failure: email sent to jo...@bigelephant.net gets returned "user unknown"
Log Result: Expected log written in mail.log for "user unknown"
SCENARIO 3: (successful)
mailbox created: john...@bigelephant.com
two aliases created (makealiases) jo...@bigelephant.com: john...@bigelephant.com jo...@bigelephant.net: john...@bigelephant.com
Action Success: email sent to jo...@bigelephant.net arrives at john...@bigelephant.com
Log Result: No logs about transaction written to mail.log (even though it got scanned by SpamAssasin and delivered to maildir)
*Scenario 3 is a solution to the user unknown error, but seems problematic to have to specify this extra alias explicitly when domain itself was already aliased in hosteddomains. Maybe its supposed to work this way?
thanks,
charles