On 11/14/19 11:31 AM, Zinski, Steve wrote:
We are migrating from sendmail (virtuser) mail routing to LDAP routing. Setting up routing for users is pretty straightforward using the inetLocalMailRecipient class and the mail/mailLocalAddress/mailRoutingAddress attributes. But I was wondering what would be the best (correct) way to represent the mailman alias addresses in LDAP (i.e., list-admin, list-bounces, list-confirm, etc.). Would each get its own entry in LDAP or is there a better way? Any help would be appreciated.
Are your mailing lists mixed in a dedicated (sub)domain name? Or are they mixed in with other non-mailing list addresses?
The former probably doesn't need much other than something akin to a mailertable entry. (Is that also migrating to LDAP?) If it's the former, you're going to need /something/ to cause Sendmail to recognize the mailing list addresses. This probably means that you're going to need LDAP entries.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
