Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread Mark Sapiro 
On 11/01/2017 12:35 PM, Nick Wyman wrote:
> Emailing mailman-ow...@mydomain.com has not worked.  The mailman list has 
> valid owner config, but has no members.


What happens to this mail. Can you see it in mail logs? It should be
delivered via a pipe to '/path/to/mail/mailman owner mailman' and then
Mailman should resend it to the list owner address(es).

How is mail to Mailman delivered? If via aliases, are there aliases for
the 'mailman' list?


> Unfortunately, the original spam email has cleared from the mail spool.  
> However, I feel certain that the To: address was mail...@mydomain.com.  There 
> were several CC: addresses which are stuck in the queue.  This was truly a 
> spam email.


Spam or not, it shouldn't result in Mailman sending mail with envelope
from mailman-bounces@com.

What is the content of mm_cfg.py? In particular, is there an entry like

add_virtualhost('mydomain.com')

or some entry like

add_virtualhost('DEFAULT_EMAIL_HOST')

If so, these are probably wrong and the underlying cause. I.e. the
arguments for add_virtual_host are 'web host' and 'email host' but if
only one is provided, the email host becomes the web host with the
leftmost subdomain removed. I.e.

add_virtualhost('mydomain.com')

is equivalent to

add_virtualhost('mydomain.com', 'com')

which is never what you want. If both domains are the same, you want

add_virtualhost('mydomain.com', 'mydomain.com')

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread Nick Wyman 
Emailing mailman-ow...@mydomain.com has not worked.  The mailman list has valid 
owner config, but has no members.

Unfortunately, the original spam email has cleared from the mail spool.  
However, I feel certain that the To: address was mail...@mydomain.com.  There 
were several CC: addresses which are stuck in the queue.  This was truly a spam 
email.



> -Original Message-
> From: Mailman-Users [mailto:mailman-users-
> bounces+nwyman=viablecomputing@python.org] On Behalf Of Mark
> Sapiro
> Sent: Wednesday, November 01, 2017 2:05 PM
> To: mailman-users@python.org
> Subject: Re: [Mailman-Users] New list's SMTP failures
> 
> On 11/01/2017 09:19 AM, Nick Wyman wrote:
> >
> > I now think this is due to a spam email which was sent to
> mail...@mydomain.com  (it's stuck in my mail queue) which is somehow
> erroneously being processed by mailman and routed to this particular list's
> owners, but with a bad sender address.
> 
> 
> Do you have a copy of this spam email including all headers? That might
> be helpful.
> 
> Also, what happens if you send a message to mailman-owner@... ?
> 
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> 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/nwyman%40viablecomputing.com

--
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

Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread Mark Sapiro 
On 11/01/2017 09:19 AM, Nick Wyman wrote:
> 
> I now think this is due to a spam email which was sent to 
> mail...@mydomain.com  (it's stuck in my mail queue) which is somehow 
> erroneously being processed by mailman and routed to this particular list's 
> owners, but with a bad sender address.  


Do you have a copy of this spam email including all headers? That might
be helpful.

Also, what happens if you send a message to mailman-owner@... ?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread Mark Sapiro 
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 mail...@mydomain.com should be processed?  
> Is this an address which must be functional for receiving incoming email?


Mail to mail...@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 The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread Nick Wyman 
Well, I was hopeful, but the owner and hostname config for the mailman list are 
valid.

Can you tell me how mail sent to mail...@mydomain.com should be processed?  Is 
this an address which must be functional for receiving incoming email?

> -Original Message-
> From: Mark Sapiro [mailto:m...@msapiro.net]
> Sent: Wednesday, November 01, 2017 1:26 PM
> To: Nick Wyman ; Mailman Users  us...@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 mail...@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 The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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

Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread 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 mail...@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 The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread Mark Sapiro 
On 11/01/2017 09:19 AM, Nick Wyman wrote:
> 
> I now think this is due to a spam email which was sent to 
> mail...@mydomain.com  (it's stuck in my mail queue) which is somehow 
> erroneously being processed by mailman and routed to this particular list's 
> owners, but with a bad sender address.  
> 
> Does this seem plausible?  


Perhaps.


> I see a "mailman" list in /etc/aliases and ../mailman/lists, but there isn't 
> a "mailman" list in my web config.  I did dump the configuration for the 
> "mailman" list via config_list and hostname is set correctly.


Is this cPanel? If so, see the thread beginning at
.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread Nick Wyman 
Mark, thank you for your reply.

Yes, the hostname variable for the list is correct.  The posting emails from 
the list are delivered correctly.

I now think this is due to a spam email which was sent to mail...@mydomain.com  
(it's stuck in my mail queue) which is somehow erroneously being processed by 
mailman and routed to this particular list's owners, but with a bad sender 
address.  

Does this seem plausible?  

I see a "mailman" list in /etc/aliases and ../mailman/lists, but there isn't a 
"mailman" list in my web config.  I did dump the configuration for the 
"mailman" list via config_list and hostname is set correctly.


> -Original Message-
> From: Mailman-Users [mailto:mailman-users-
> bounces+nwyman=viablecomputing@python.org] On Behalf Of Mark
> Sapiro
> Sent: Wednesday, November 01, 2017 10:34 AM
> To: mailman-users@python.org
> Subject: Re: [Mailman-Users] New list's SMTP failures
> 
> On 11/01/2017 07:41 AM, Nick Wyman wrote:
> >
> > On a server which hosts several mailman lists, a new list is exhibiting odd
> behavior for owner email addresses.  There are two owners, and both are
> receiving post emails, but are also bouncing what I assume are administrative
> emails.
> >
> > The smtp-failure log looks like:
> >
> > Nov 01 09:37:09 2017 (1387) delivery to  failed with code 553:
> 5.1.8 ... Domain of sender address mailman-bounces@com does not
> exist
> 
> 
> If it actually says "mailman-bounces@com", go to the list's web admin UI
> and look at the setting for host_name near the bottom of the General
> Options page. It will be "com". Set it to the actual correct email
> domain name for this list.
> 
> 
> > Note that the sender address is incorrect (default value?).  Regular posting
> emails are delivered with the correct sender address (foo-
> boun...@domain.com).
> >
> > Using config_list to inspect the non-working list against a working list
> produces only the expected differences.
> 
> 
> It doesn't show a difference in the host_name setting?
> 
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> 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/nwyman%40viablecomputing.com

--
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

Re: [Mailman-Users] New list's SMTP failures

2017-11-01 Thread Mark Sapiro 
On 11/01/2017 07:41 AM, Nick Wyman wrote:
> 
> On a server which hosts several mailman lists, a new list is exhibiting odd 
> behavior for owner email addresses.  There are two owners, and both are 
> receiving post emails, but are also bouncing what I assume are administrative 
> emails.
> 
> The smtp-failure log looks like:
> 
> Nov 01 09:37:09 2017 (1387) delivery to  failed with code 553: 
> 5.1.8 ... Domain of sender address mailman-bounces@com does not 
> exist


If it actually says "mailman-bounces@com", go to the list's web admin UI
and look at the setting for host_name near the bottom of the General
Options page. It will be "com". Set it to the actual correct email
domain name for this list.


> Note that the sender address is incorrect (default value?).  Regular posting 
> emails are delivered with the correct sender address (foo-boun...@domain.com).
> 
> Using config_list to inspect the non-working list against a working list 
> produces only the expected differences.


It doesn't show a difference in the host_name setting?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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

[Mailman-Users] New list's SMTP failures

2017-11-01 Thread Nick Wyman 
Hello, 

On a server which hosts several mailman lists, a new list is exhibiting odd 
behavior for owner email addresses.  There are two owners, and both are 
receiving post emails, but are also bouncing what I assume are administrative 
emails.

The smtp-failure log looks like:

Nov 01 09:37:09 2017 (1387) delivery to  failed with code 553: 5.1.8 
... Domain of sender address mailman-bounces@com does not exist

Note that the sender address is incorrect (default value?).  Regular posting 
emails are delivered with the correct sender address (foo-boun...@domain.com).

Using config_list to inspect the non-working list against a working list 
produces only the expected differences.

Where should I look next?

Thank you.

--
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