Hi folks,
We're (finally) in the early stages of upgrading from Mailman2 to Mailman3.
Our Mailman2 setup uses Fetchmail to retrieve list mail from our accounts on Gmail.
Is there a similar setup for Mailman3?
I admit that I've only done a light scan of the docs so far, but haven't found anything addressing such a scenario.
Thanks in advance!
-- Bill Christensen http://SustainableSources.com http://LinkedIn.com/in/billc108
Dance like nobody's watching. Encrypt like everyone is. --Adrián Lamo
On 06/23/2018 02:48 PM, Bill Christensen wrote:
Our Mailman2 setup uses Fetchmail to retrieve list mail from our accounts on Gmail.
Is there a similar setup for Mailman3?
Delivery to Mailman is different in Mailman 3. What are you currently doing with Fetchmail?
If you are doing something like getting the mail from google and delivering it via SMTP to an MTA on the Mailman server, that should still work for MM 3.
If Fetchmail is piping it to a command like
"| /path/to/mail/mailman post listname"
that won't work in Mailman 3. Mailman 3 gets mail via its own LMTP server (which it calls a runner). Mail is normally delivered to an MTA which is configured to relay the mail via LMTP to the localhost port that Mailman is listening on. So Fetchmail can eithr deliver to the MTA and let the MTA relay to Mailman or deliver directly to Mailman's LMTP port.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 06/23/2018 02:48 PM, Bill Christensen wrote:
Our Mailman2 setup uses Fetchmail to retrieve list mail from our accounts on Gmail.
Is there a similar setup for Mailman3?
Delivery to Mailman is different in Mailman 3. What are you currently doing with Fetchmail?
On 6/23/18 5:01 PM, Mark Sapiro wrote: the general syntax we're using is:
poll imap.gmail.com protocol IMAP username "<list address>" there with password "<password>" is "mailman" here nofetchall keep ssl sslcertck sslcertpath /path/to/share/ssl/certs mda "/path/to/mail/mailman post <listname>" set daemon 900
If you are doing something like getting the mail from google and delivering it via SMTP to an MTA on the Mailman server, that should still work for MM 3.
I think that's what the above is doing. Right?
If Fetchmail is piping it to a command like
"| /path/to/mail/mailman post listname"
that won't work in Mailman 3. Mailman 3 gets mail via its own LMTP server (which it calls a runner). Mail is normally delivered to an MTA which is configured to relay the mail via LMTP to the localhost port that Mailman is listening on. So Fetchmail can eithr deliver to the MTA and let the MTA relay to Mailman or deliver directly to Mailman's LMTP port.
-- Bill Christensen http://SustainableSources.com http://LinkedIn.com/in/billc108
Dance like nobody's watching. Encrypt like everyone is. --Adrián Lamo
On 06/23/2018 10:49 PM, Bill Christensen wrote:
On 6/23/18 5:01 PM, Mark Sapiro wrote:
Delivery to Mailman is different in Mailman 3. What are you currently doing with Fetchmail?
the general syntax we're using is:
poll imap.gmail.com protocol IMAP username "<list address>" there with password "<password>" is "mailman" here nofetchall keep ssl sslcertck sslcertpath /path/to/share/ssl/certs mda "/path/to/mail/mailman post <listname>" set daemon 900
If you are doing something like getting the mail from google and delivering it via SMTP to an MTA on the Mailman server, that should still work for MM 3.
I think that's what the above is doing. Right?
No. what the above is doing is piping the mail to
"/path/to/mail/mailman post <listname>"
That is what won't work for Mailman 3. I am not familiar with Fetchmail configuration, but what you need to do is forward the mail via LMTP to localhost:8024 with recipient listname@domain.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Bill Christensen -
Mark Sapiro