Subject: Sender based relayhost (was: Sender based routing)
- msg#00020

Previous Message by Date:

Re: Proposal: Sender based routing

Bernd Paysan: > On Sunday 14 August 2005 23:18, mouss wrote: > > > I suggest that you look at the SUBJECT line of this thread. > > > > It seems I did, but my understanding is that this means something > > like: nexthop = f(sender, recipient) > > not > > nexthop = domain(sender) > > That's a good summery ;-). In fact, if you send From: user@xxxxxx To: > user@localhost, someone@xxxxxx, others@xxxxxxxxx, you should deliver > user@localhost without going through GMX. > > The current unusable sender_based_routing = yes setting follows the > second rule only, making it impossible to deliver reliable to > localhost. You're looking for a per-sender relayhost table. Mail that isn't local or virtual is delivered via a relayhost when one is specified. Wietse

Next Message by Date:

Re: Sender based relayhost (was: Sender based routing)

On Monday 15 August 2005 00:08, Wietse Venema wrote: > > You're looking for a per-sender relayhost table. Mail that isn't > > local or virtual is delivered via a relayhost when one is > > specified. > > See also: > http://taschenorakel.de/mathias/archive/patches/postfix-2.2.3-sender_ >relay.patch Yes, this patch works as desired. The remaining issue is per-sender authentication (so it's useful for a single-user environment). Room for improvement: The new RESOLVE_CLASS_OFFHOST is set when there's a relayhost, instead of checking for relayhost_map (use case). -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/

Previous Message by Thread:

Proposal: Sender based routing

Hi, I looked at the sender_based_routing option, which at the moment is utterly useless (unless you want a send-only mail server ;-). I thought about how to fix it, and that's what I've come up with: Purpose: You want sender based routing when you have several users which really use a freemailer or other central mail infrastructure, and you want to forward their mail to the correct relay. This includes authentication with the relay. If directly delivered, these mails quite likely end up in some spam folders (especially if the recipient uses SPF). The responsible service is the "relay" service. It's used for outgoing services, at the boundary to the rest of the world. No other part of the chain should route depending on the sender. The relay service still may route depending on the recipient, so the table should contain four fields: recipient-pattern :transport [sender-pattern] [auth] The transport may need authentication, so there's either an optional authentication or user/password field, or the authentication is encoded in the transport itself, e.g. like in user:pass@host. Example: sub.mydomain.tld :[mail.sub.mydomain.tld] * :[mail.gmx.de] user@xxxxxx user-id:pass This would first route everything that's going to sub.mydomain.tld to the specific mail-server for this sub-domain (without authentication), and then try to match the freemailer user, and use the freemailer outgoing SMTP server with authentication as relay. It's necessary to use a sender-specific authentication, because more than one user might have a freemail account at the same freemailer, so the sasl_passwd file also is not good enough (only one password per destination). What do you think? -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/ pgpBpPw31sn5H.pgp Description: PGP signature

Next Message by Thread:

Re: Sender based relayhost (was: Sender based routing)

On Monday 15 August 2005 00:08, Wietse Venema wrote: > > You're looking for a per-sender relayhost table. Mail that isn't > > local or virtual is delivered via a relayhost when one is > > specified. > > See also: > http://taschenorakel.de/mathias/archive/patches/postfix-2.2.3-sender_ >relay.patch Yes, this patch works as desired. The remaining issue is per-sender authentication (so it's useful for a single-user environment). Room for improvement: The new RESOLVE_CLASS_OFFHOST is set when there's a relayhost, instead of checking for relayhost_map (use case). -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/