I hope that someone here can help me (or point me in the right direction).
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.
Steve
[University of Richmond] Steven C. Zinski Sr. Network Programmer Network Services, Jepson Hall 221 Richmond Way University of Richmond, Virginia, 23173 804-289-8773 • szinski@richmond.edu<mailto:szinski@richmond.edu> • https://is.richmond.edu
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
We're actually migrating to Proofpoint (no more sendmail). Proofpoint will use our LDAP server for routing mail, so I'm trying to determine the best way to represent our mailman aliases in LDAP.
On 11/15/19, 2:03 PM, "Mailman-Users on behalf of Grant Taylor via Mailman-Users" <mailman-users-bounces+szinski=richmond.edu@python.org on behalf of mailman-users@python.org> wrote:
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
On 11/15/19 11:12 AM, Zinski, Steve wrote:
We're actually migrating to Proofpoint (no more sendmail). Proofpoint will use our LDAP server for routing mail, so I'm trying to determine the best way to represent our mailman aliases in LDAP.
I know nothing about Proofpoint and not much about LDAP, but every list
address has a target which is a pipe to Mailman's mail wrapper with
unique arguments depending on the address. E.g., list@example.com
pipes to mailman/mail/mailman post list and list-suffix@example.com
pipes to mailman/mail/mailman suffix list for the various suffixes.
If you can do this programmatically, you may be able to do it similarly to the way Exim does it (see <http://www.exim.org/howto/mailman21.html>).
Otherwise, you will probably need 10 individual entries per list for the list name and the nine suffixes.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Grant Taylor -
Mark Sapiro -
Zinski, Steve