Re: [Mailman-Users] New list's SMTP failures
On 11/01/2017 11:00 AM, Nick Wyman wrote:
This is not cpanel. This is a virtual host running Ubuntu 14.04 and mailman 2.1.23.
OK.
Things have been running smooth for 1+ year but seem to have been tripped up by spam to mailman@mydomain.com.
It's possible that it's the 'mailman' list that has the 'com' host name. That might be it.
Perhaps the "mailman" list is misconfigured?
I don't have a mailman user account, the Ubuntu mailman setup created a "list" user. So I'm not sure how the above mail should be routed.
Yes, in Debian/Ubuntu the Mailman user is 'list'. The "site list" which every Mailman 2.1 installation must have is normally named 'mailman' and is 'mailman' in the Debian/Ubuntu package.
You can access the web UI for the 'mailman' list at the same URL you use for other lists' admin UI but with 'mailman' as the list name. You can set a site password for your installation via Mailman's bin/mmsitepass and use that password to log in to the list.
Do that and check the host_name for that list. Also make sure the 'owner' address is good. Or you can do it with 'withlist'.
$ bin/withlist -l mailman Loading list mailman (locked) The variable `m' is the mailman MailList instance
m.host_name 'com'
Assuming that's the result, set it as in
m.host_name = 'mydomain.com'
also look at
m.owner
and set that if needed, and finally after making changes
m.Save() <- enter control-D here to exit Unlocking (but not saving) list: mailman Finalizing
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Well, I was hopeful, but the owner and hostname config for the mailman list are valid.
Can you tell me how mail sent to mailman@mydomain.com should be processed? Is this an address which must be functional for receiving incoming email?
-----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: Wednesday, November 01, 2017 1:26 PM To: Nick Wyman <nwyman@viablecomputing.com>; Mailman Users <mailman- users@python.org> Subject: Re: [Mailman-Users] New list's SMTP failures
On 11/01/2017 11:00 AM, Nick Wyman wrote:
This is not cpanel. This is a virtual host running Ubuntu 14.04 and mailman
2.1.23.
OK.
Things have been running smooth for 1+ year but seem to have been tripped up by spam to mailman@mydomain.com.
It's possible that it's the 'mailman' list that has the 'com' host name. That might be it.
Perhaps the "mailman" list is misconfigured?
I don't have a mailman user account, the Ubuntu mailman setup created a "list" user. So I'm not sure how the above mail should be routed.
Yes, in Debian/Ubuntu the Mailman user is 'list'. The "site list" which every Mailman 2.1 installation must have is normally named 'mailman' and is 'mailman' in the Debian/Ubuntu package.
You can access the web UI for the 'mailman' list at the same URL you use for other lists' admin UI but with 'mailman' as the list name. You can set a site password for your installation via Mailman's bin/mmsitepass and use that password to log in to the list.
Do that and check the host_name for that list. Also make sure the 'owner' address is good. Or you can do it with 'withlist'.
$ bin/withlist -l mailman Loading list mailman (locked) The variable `m' is the mailman MailList instance
m.host_name 'com'
Assuming that's the result, set it as in
m.host_name = 'mydomain.com'
also look at
m.owner
and set that if needed, and finally after making changes
m.Save() <- enter control-D here to exit Unlocking (but not saving) list: mailman Finalizing
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/01/2017 11:34 AM, Nick Wyman wrote:
Well, I was hopeful, but the owner and hostname config for the mailman list are valid.
I was hopeful too :(
Can you tell me how mail sent to mailman@mydomain.com should be processed? Is this an address which must be functional for receiving incoming email?
Mail to mailman@mydomain.com should be processed as a post to the 'mailman' list. How it is handled depends on list configuration. There is a suggested config for the list in Mailman's data/ directory, but I don't recommend that. In particular, I recommend that the members of the list and the owners of the list be the mailman site admin(s) and the following specific settings.
Privacy options... -> Subscription rules advertised = No subscribe_policy = Require approval unsubscribe_policy = No private_roster = List admin only Privacy options... -> Sender filters dmarc_moderation_action = Munge From dmarc_quarantine_moderation_action = Yes generic_nonmember_action = Accept
The reason for accepting messages from nonmembers is this address is exposed on listinfo and admin overview pages as a "help" address.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro
-
Nick Wyman