[Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8041] trunk/mailman/Mailman

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sep 28, 2006, at 12:25 AM, Brad Knowles wrote:

> At 11:54 PM -0400 9/27/06, Barry Warsaw wrote:
>
>>  Looking at Postfix, what other options are readily available?  I
>>  suppose you could try to hook into the transport maps, but if I
>>  understand them correctly, you're still talking about forking a
>>  process per message.
>
> Use LMTP instead.  This will allow you to completely avoid an  
> intermediate (and unnecessary) queue-to-disk stage.

The only problem I see is that I'm not sure Postfix can be configured  
to deliver via LMTP on a per-recipient basis.  It looks like you have  
to specify LTMP via transports and so must deliver all mail for a  
particular domain to that transport.  That's not good because of  
course we want Mailman to only receive messages for the aliases  
corresponding to mailing lists, while other things like local  
recipients or non-list aliases get delivered in the "normal way".

Or is there some way I'm missing that would allow us to segregate  
some domain traffic to Mailman's LMTP server and other traffic to  
Postfix's standard transports?  What about Sendmail?

Other than that, we'd need a reliable standards-compliant LMTP server  
written in Python (and no, smtpd.py- or Twisted-based versions are  
not acceptable ;).

- -Barry


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iQCVAwUBRRtYj3EjvBPtnXfVAQKIowP/anqUQekOOQO8v18sE9PuDtqfeIt8gamF
r+AUEyLFQJ9D2RiCcrJm74mXbGGoVVOxsTaMpIzLdfLL20K+MtX8UtgAcEYT40+C
TzrT34p3I8pVriplpsLIXMb539If3/CR00I3XRhlHhYGbMt14PC/KlpAQ0TCkzqH
uRRDtEWXDlk=
=HwLP
-----END PGP SIGNATURE-----