10 msgheader check question
12 msgverify parameters
4 msgConfigure postfix in big env
2 msgenvelope sender '<>' via uucp gets rewrit...
2 msgSpam filtering only for specific email accounts
3 msgPostfix 2.4 to 2.5: smtp(d)_tls_session_cache_d...
15 msgQuestion about 'standards' WRT BATV and SAV
7 msgmy solution to fight backscatter email
2 msgAUTO: Joe Grastara is out of the office (return...

Q about sender_dependent_relayhost_maps inbound...
\ Harakiri (8 May 2008)
. \ Victor Duchovni (8 May 2008)
. . \ Harakiri (8 May 2008)
. . \ Harakiri (8 May 2008)
. . . \ Victor Duchovni (8 May 2008)
. . . . \ Harakiri (8 May 2008)
. . . . \ Harakiri (8 May 2008)
. . . . . \ (Wietse Venema) (9 May 2008)
. . . . . \ Victor Duchovni (9 May 2008)
. . . . . . \ Harakiri (9 May 2008)
. . . . . . . \ (Wietse Venema) (9 May 2008)
. . . . . . . \ Victor Duchovni (9 May 2008)

16 msgMilter Suggestions
9 msgTransport table and postmap
3 msgArchiving e-mail?
8 msgError 550: unable to relay
1 msgFW: new subject
13 msgTLS handshake error
6 msgSeperating SMTP and POP/IMAP services
3 msgTest 2
1 msgTesting
12 msg[Fwd: ldap users & aliases config]
Subject:Re: Q about sender_dependent_relayhost_maps inbound vs outbound traffic
Group:Postfix-users
From:Victor Duchovni
Date:9 May 2008


 
On Fri, May 09, 2008 at 02:02:24AM -0700, Harakiri wrote:

> 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