[Mailman-Users] New list's SMTP failures

[Mark Sapiro]

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 at 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 at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan