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

[Barry Warsaw]

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

On Sep 27, 2006, at 12:51 AM, Dale Newfield wrote:

> This of course begs the questions of how mailman distinguishes between
> the lists (what's the appropriate argument to the mailman binary, and
> whether there are any characters besides "." that are disallowed in
> domain names (what is a good encoding to use as a valid local  
> address)?

I've just read the Postfix documentation again to see if there are  
any new features since the last time we implemented integration with  
Postfix virtual domains.  Here's the man page:

http://www.postfix.org/VIRTUAL_README.html

What looks interesting is the section entitled:

Postfix virtual MAILBOX example: separate domains, non-UNIX accounts

This appears to allow us to set up true virtual domains without  
having to encode destination aliases.  The trick though is that we  
would use Maildir delivery for all incoming messages, something I'm  
keen on switching to for Mailman 2.2 anyway.  Maildir is way more  
efficient than invoking a mail program per incoming message, Mailman  
already supports Maildir (although it isn't the default), and AFAIK  
all major MTAs support Maildir.

I'd like to know what you think about updating our Postfix virtual  
delivery hooks to use this technique, and about making Maildir  
delivery the default.  We'd keep the old way around for MTAs that  
don't support Maildir (which would be...?) but we'd deprecate that  
delivery mechanism.

One thing I'm not sure of is the minimum version of Postfix this  
would tie us to.  On OS X 10.4 it looks like I've got Postfix 2.1.5  
and according to postconf, it supports the  necessary variables.

Thoughts?
- -Barry

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

iQCVAwUBRRrLK3EjvBPtnXfVAQK4sAQAkkFgWXxxdk1TxLVYxbb3CEO2y59XJtb5
dRcCT8qg0LyxTkFNGEqAQTi9iRIs2/RVuK1KUBVXpSpQbt7zrGfs0s/ukfPVlVbO
/h45S+cQ8d9cF2s77PHSqiUgdGckMy7W6v15qJ9zrrMC+M38yqV5oAzpxNc660y8
UtXNleCdeGM=
=dgKK
-----END PGP SIGNATURE-----