| |||||||||||||||||||||||||||||||
|
> Example (simplified, prop. not correct syntax) Simplified to the the point of being incomprehensible to anyone (including yourself I suspect). > sender_based_map > internal-with-check.com:[next_hop_will_do_mx_lookup] > internal.com: use mx > *:all other use mx What on earth does this mean. The sender table specifies a mapping between a sender address and a relayhost, not a transport. Are you trying to say that for senders in the domain on the LHS of the table entry below the nexthop should be the RHS gateway when the recipient is delivered using SMTP (rather than local)? internal-with-check.com [next_hop_will_do_mx_lookup] Does this system do *any* local delivery? Do any users submit mail directly via sendmail(1) rather than via SMTP? If not, there is not much difference betwen sender-dependent routing and a "FILTER smtp:[next_hop...]" access check on the sender domain. > recipient_map > internal-with-check.com:[mymailserver.internal.com] > internal.com:[mymailserver.internal.com] > *:all other use mx There is no "recipient map" there a transport table, whose syntax is to select a transport and nexthop. Do make your examples more realistic. > Mails : > > sender user to user > should go to next_hop_will_do_mx_lookup, no recipient map applies Is this because the domain in question is hosted on the gateway in question, and all email from the domain should originate there, or because you are considering misusing sender based routing to solve a different problem that you have not explained? Sender based routing is a SOHO feature, intended for machines with perhaps a few local accounts and most user mailboxes hosted by an ESP. > sender user to user > should go to destination via mx, no recipient map applies The documentation adequately describes this case. The transport table is always checked, but there is certainly no requirement to least every destination there. > sender user to user > should go to mymailserver.internal.com, no sender map applies The documentation adequately covers this case. > sender user to user > should go to mymailserver.internal.com, no sender map applies The documentation adequately covers this case. There are likely more cases to consider. And your real motivation for sender based routing left to describe. -- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: <mailto:majordomo?body=unsubscribe%20postfix-users> If my response solves your problem, the best way to thank me is to not send an "it worked, thanks" follow-up. If you must respond, please put "It worked, thanks" in the "Subject" so I can delete these quickly.
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com