On Sun, Nov 30, 2008 at 3:50 PM, Wietse Venema <[EMAIL PROTECTED]> wrote:
> john mickler:
>> I have one other question about BCP for mailing infrastructure.
>>
>> In our current setup we have:
>>
>> INBOUND
>> a.mx --
>> b.mx ---- mail
>> c.mx --
>>
>> OUTBOUND
>> {local servers} -->
>> remote-smtp-auth --> smtp --> {INTERNET}
>
> Makes sense to me, but then it's been a while since I set up email
> infrastructure myself. The drawing doesn't show mailbox access,
> but this is not part of the questions that you're asking.
>
> The only thing you might add at some point is a safety to prevent
> a corrupted client from sending out massive amounts of email and
> getting your servers blacklisted. Something like policyd to enforce
> generous safety limits on local submissions.
>
> Wietse
>
I never thought about that circumstance, and the more I do think about it
the more it sounds like a must. Grey listing at the MX machines is something
I'm planning in implementing; I'll configure policyd as you suggest at the same
time.
For mailbox access, I have Cyrus IMAP in place allowing clients access to
their spools either by POPS or IMAPS (also webmail access using a
modified version of @Mail). That being the case, the following set
from main.cf
control my delivery:
fallback_transport = lmtp:unix:/var/imap/socket/lmtp
local_transport = cyrus
transport_maps = mysql:/usr/local/etc/postfix/transport.sql
Thanks for the suggestion Wietse. As previously mentioned any comments or
suggestions are more than welcome.
