Re: allow some senders, but block everyone else

2013-07-25 Thread Florin Andrei
I solved my routing problem... by switching to Exim. :) Arbitrary routing decisions can be implemented by simply daisy-chaining routers in a config file. It's actually surprising how easy it is to read the whole logic at once just by glancing at one file. Almost like pseudo-code. Their

Re: allow some senders, but block everyone else

2013-07-23 Thread Florin Andrei
I apologize for not being more specific at the beginning. I appreciate the fact that support is offered here freely for everyone, it's a great help. I am getting the impression that it's not possible to make routing decisions based on sender *before* making decisions based on recipient.

Re: allow some senders, but block everyone else

2013-07-23 Thread DTNX Postmaster
On Jul 23, 2013, at 22:25, Florin Andrei flo...@andrei.myip.org wrote: I apologize for not being more specific at the beginning. I appreciate the fact that support is offered here freely for everyone, it's a great help. I am getting the impression that it's not possible to make routing

Re: allow some senders, but block everyone else

2013-07-23 Thread Wietse Venema
Florin Andrei: I apologize for not being more specific at the beginning. I appreciate the fact that support is offered here freely for everyone, it's a great help. I am getting the impression that it's not possible to make routing decisions based on sender *before* making decisions based

allow some senders, but block everyone else

2013-07-22 Thread Florin Andrei
This is a clone of the production site, for QA and testing. This being QA, whenever we run a test of our software, we don't want our test suite to go ahead and blast the Internet with lots of random email messages. OTOH, we need to keep the configuration of the QA site as close to production

Re: allow some senders, but block everyone else

2013-07-22 Thread Wietse Venema
Florin Andrei: This is a clone of the production site, for QA and testing. This being QA, whenever we run a test of our software, we don't want our test suite to go ahead and blast the Internet with lots of random email messages. OTOH, we need to keep the configuration of the QA site as

Re: allow some senders, but block everyone else

2013-07-22 Thread Florin Andrei
Okay, let's try this: The goal is to send most emails to local, send most mydomain.com recipients to a relay nearby, and let foobardomain.com senders go out on the Internet freely. In main.cf I have: sender_dependent_default_transport_maps = regexp:/etc/postfix/sender_transport In

Re: allow some senders, but block everyone else

2013-07-22 Thread Wietse Venema
Florin Andrei: Okay, let's try this: The goal is to send most emails to local, send most mydomain.com recipients to a relay nearby, and let foobardomain.com senders go out on the Internet freely. Presumably, if foobardomain.com senders send mail to local or mydomain.com recipients, then

Re: allow some senders, but block everyone else

2013-07-22 Thread Florin Andrei
On 07/22/2013 05:30 PM, Wietse Venema wrote: Florin Andrei: The goal is to send most emails to local, send most mydomain.com recipients to a relay nearby, and let foobardomain.com senders go out on the Internet freely. Presumably, if foobardomain.com senders send mail to local or

Re: allow some senders, but block everyone else

2013-07-22 Thread Wietse Venema
Florin Andrei: On 07/22/2013 05:30 PM, Wietse Venema wrote: Florin Andrei: The goal is to send most emails to local, send most mydomain.com recipients to a relay nearby, and let foobardomain.com senders go out on the Internet freely. Presumably, if foobardomain.com senders send mail