Asking here because I saw the note to keep 3.0 discussion off -users.
One of the features that would be nice for my site, and I'm sure others, would be support for alternate addresses for users. For example, users here have the mailAlternateAddress field in LDAP populated with all their firstname.lastname, initial.lastname and nickname email aliases, and sometimes set their mail clients to identify as these, causing their posts to be held or rejected. It would be nice if mailman could either query a specified location for alternate identities, or accept a generated list of them for the current membership list.
It seems problematic to wedge a list of alternate addresses into accept_these_nonmembers, as we would never be entirely sure if someone had unsubscribed from the list but been administratively allowed to post to it, and I'm sure it will confuse the list administrators who have to keep both alternate addresses and non-members in the same text box.
I see 3.0 has support for LDAP and other forms of back-end database, so I was wondering if support for mailAlternateAddress would be part of that new feature-set? If not, may I request it?
-- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Nov 11, 2008, at 4:52 AM, Simon Fraser wrote:
I see 3.0 has support for LDAP and other forms of back-end database,
so I was wondering if support for mailAlternateAddress would be part of that new feature-set? If not, may I request it?
Actually, there's no LDAP backend implemented yet (or at least,
integrated into the core). I'd love to see someone tackle an LDAP
backend as a plugin.
Having said that, MM3's model fully supports multiple email addresses
per user. The idea is that a mailing list should be able to accept a
message from any of a person's linked addresses, but deliver only to
those (usually one) that they want delivery on.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkkZ4LwACgkQ2YZpQepbvXFH2QCeM4CeEaJy5X16TvdfhXsnhaSA fmMAoIyoLPFPG5ZMw8uLKACOgnG8U57k =oTGY -----END PGP SIGNATURE-----