Re: [Mailman-Users] List not archiving, not sending mail, mischief log shows 'Hostile listname: "

[Mark Sapiro]

On 05/17/2015 10:14 PM, Bill Christensen wrote:
> On Sun, May 17, 2015 at 6:26 PM, Mark Sapiro  wrote:
> 
>> On 05/17/2015 01:58 PM, Bill Christensen wrote:
>>> In the smtp-failure log I'm seeing
>>>
>>> Message size exceeds fixed limit
>>>
>>> In General Options => Maximum length in kilobytes (KB) of a message body.
>>> Use 0 for no limit.  I have '0'.
>>
>>
>> These two things are unrelated. The message in smtp-failure says Mailman
>> attempted to send a message which was larger than the MTA would accept.
>> In Postfix for example, this is the main.cf parameter message_size_limit.
>>
> 
> Ok.
> 
> I checked the messages waiting in Gmail.  They're all small enough, no
> worrisome attachments or anything.  I tried marking the oldest as read just
> in case it was jamming up the works, but the others are still in a logjam.


The Message size exceeds fixed limit errors have nothing to do with the
list messages that are not getting posted. They are messages being sent
from Mailman to the MTA (Postfix ?) that are bigger than Postfix's
message_size_limit.

You'll have to look at the Postfix log for more info.

-- 
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] help with error on start

[Mark Sapiro]

On 05/18/2015 05:32 AM, Ricardo Santos wrote:
> Thanks Mark for you answer. I installed from a tutorial with this command
> (Centos 6.6)
> 
>> yum --enablerepo=remi install mailman  (Ver 3:2.1.12-18.el6 )


OK, but the /usr/lib/mailman/Mailman/i18n.py file in your installed
Mailman doesn't look like the one distributed by GNU Mailman nor does it
look like the one from RHEL 5 that I happen to have.

So either something went wrong with your package install, or you will
have to pursue this with Red Hat/Centos.

Or, you could try downliading i18n.py from

and replacing yours with that. That will probably get you past the
current issue, but there may be other things wrong.

-- 
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] List not archiving, not sending mail, mischief log shows 'Hostile listname: "

[Mark Sapiro]

On 05/17/2015 10:14 PM, Bill Christensen wrote:
> On Sun, May 17, 2015 at 6:26 PM, Mark Sapiro  wrote:
> 

>> If this is a one-time occurrence, It was just a glitch. Maybe someone
>> manually ran cron/gate_news as a user not in Mailman's group. If you get
>> these every 5 minutes, there is a permissions issue, probably with the
>> user running this cron not being mailman, because if the locks directory
>> were not group mailman and group writable, lots more would be broken.
>>
> 
> Yes, definitely every 5 minutes.


There is a permissions issue on the locks directory. If you do

ls -la /opt/local/var/mailman/locks/

you should see something similar to

drwxrwsr-x 2 rootmailman 4096 May 18 20:11 .
drwxrwsr-x 9 rootmailman 4096 May 10  2008 ..
-rw-rw-r-- 2 mailman mailman   62 May 19  2015 master-qrunner
-rw-rw-r-- 2 mailman mailman   62 May 19  2015 master-qrunner.host.pid

There may or may not be other files, but the two master-qrunner files
should be there and everything should be mailman's group (owner is not
important) and both . and .. should have permissions as shown.

If all this is correct, then either cron/gate_news is not running as the
Mailman user (where is its crontab and what's in it?) or there may be
some SELinux, apparmor or other security policy issue.



>>>  post(12068): post script, list not found: 
>>
>> The post script invoked by
>>
>>  /path/to/mailman/mail/mailman post 
>>
>> in your fetchmail script says  doesn't exist.
>>
>>> Mailman mischief log says:
>>>
>>>   Hostile listname: 
>>
>> This is consistent with the 'post script' report and says that
>>  contains one or more characters not in the
>> Defaults.py/mm_cfg.py setting ACCEPTABLE_LISTNAME_CHARACTERS. The
>> default setting only allows letters, digits, '-', '+', '_', '.' and '='.
>>
>> Does  contain characters outside this set or whatever set
>> you've specified?
>>
> 
> Nope, it's four uppercase letters.  No spaces, no punctuation.


List names are always all lower-case. The list may have a real_name
attribute which is mixed case but it must differ only in case from the
list's internal name.

The name in the pipe to 'mailman/mail/mailman post ' command
MUST be all lower case.


> I checked the messages waiting in Gmail.  They're all small enough, no
> worrisome attachments or anything.  I tried marking the oldest as read just
> in case it was jamming up the works, but the others are still in a logjam.


Because fetchmail can't deliver to the list until you fix the listname
you pass to the 'mailman' wrapper if that's the issue.


> Yes, there are still 5 messages waiting in Gmail. Fetchmail apparently
> hasn't marked them as read as it can't put them anywhere.


Yes.



> As far as I can tell, the list name is correct.  I checked
> 
> bin/list_lists
> 
>  /etc/aliases
>  /etc/postfix/virtual
>  /etc/fetchmailrc
> and ran sudo newaliases
> 
> it was lower case in a few places, so I changed those to upper case to
> match, just in case.


That was the reverse of what you should have done. Hopefilly, the name
of the list's directory in the /opt/local/var/mailman/lists/ directory
is all lower case.

It must also be all lower case in fetchmailrc and in the commands in
/etc/aliases.

I.e. an alias could be

LISTNAME: '|/path/to/mailman/mail/mailman post listname'
LISTNAME-admin: '|/path/to/mailman/mail/mailman admin listname'

But it should match /etc/postfix/virtual, but it's best if it's all
lower case.

But then if fetchmail is delivering directly to
/path/to/mailman/mail/mailman, none of the postfix stuff matters as it
isn't used.


> then stopped/started Mailman.  No change.
> 
> I decided to take a chance and used your clone_list script to make a copy,
> moved the original archives to a backup location, then removed the original
> list and cloned back from the copy to the original name.
> 
> Ran check_perms -f and checked them manually as well.  All looks correct.
> 
> And yet, it's still throwing the same errors.
> 
> One improvement - after correcting permissions manually on
> .mbox/.mbox I can get to the archives again.  They were
>-rw-rw-r--  1 root  staff
> and I set them to
>-rwxrwxr-x  1 root  staff
> to match other working lists with public archives.

It's a file. +x is not necessary on files.
archives/private/.mbox should be drwxrwsr-x (note the SETGID),
but no x of the file is needed (it's not executable). And I hope
 is all lower case.

Also, it appears that Mailman's group is 'staff', not 'mailman' so
everywhere I refer to it as 'mailman', read 'staff'

> 
> Then I looked at mailman/lists/.  The list in question was owned by my
> user, not root like the rest of them (possibly a result of clone list?  the
> only two with that user were this list and the clone I had made earlier).
> Changed that to match the rest.
> 
> Ownership of the enclosed files has me confused.  All have the following
> files
> 
> config.pck
> 
> config.pck.last
> 
> pending.pck
> 
> request.pck
> 
> some lists have som

Re: [Mailman-Users] Could Mailman cope with extra Mime sections intended for Apple Watches?

[Peter Shute]

Thanks to you both for your input on this. It'll be interesting to see whether 
they persist with this mail format.

Peter Shute 

> -Original Message-
> From: Mailman-Users 
> [mailto:mailman-users-bounces+pshute=nuw.org...@python.org] 
> On Behalf Of Mark Sapiro
> Sent: Monday, 18 May 2015 9:59 AM
> To: mailman-users@python.org
> Subject: Re: [Mailman-Users] Could Mailman cope with extra 
> Mime sections intended for Apple Watches?

> This is arguably non-conformant. multipart/alternative parts 
> are supposed to contain sub-parts which are alternative 
> representations of the message arranged in increasing order 
> of complexity, and MUAs are supposed to render the most 
> complex (supposedly closest to the original) that they 
> understand. The summary part is not a more faithful 
> representation of the complete message than even the 
> text/plain part, so it doesn't belong there.
--
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] Mail delivered locally but not to remote domains

[Dean Collins]

Sorry for not changing the subject last time. This is a server using the
Plesk 12 control panel.

The answer was:

"Ensure that 'localhost' IP addresses is white listed in Plesk. Go to Tools
& Settings > Mail Server Settings > White list To verity it open Tools &
Settings > Mail Settings > White List and check whether it contain the
following addresses: '::1/128' and '127.0.0.1'."

Their knowledgebase article is at http://kb.odin.com/en/123649.

Thank you!

Dean


-Original Message-
From: Mailman-Users
[mailto:mailman-users-bounces+dean.collins=insightplanners@python.org]
On Behalf Of Mark Sapiro
Sent: Friday, May 15, 2015 12:59 PM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] Importing from 2.1.12-18.el6 to 2.1.15-17.el7

On 05/15/2015 12:28 PM, Dean Collins wrote:
> 
> Subscribers include m...@mydomain.com (the same domain the list is on) 
> and various addresses from other domains/servers (a couple of servers 
> I run, plus Gmail and AT&T.)
> 
> Mail sent to myl...@mydomain.com from any subscriber gets archived -- 
> and distributed to m...@mydomain.com. But none of the other subscribers 
> receive the list mail.


In order to be sure about anything, I'd need to see some logs like Mailman's
smtp-failure log and the MTA logs, except I don't know anything about qmail.

However, based on past experience I can say the following.

1) Mailman is delivering to the local MTA (qmail) and the mail is being
delivered to local addresses but not being sent to remote domains.

2) Other locally generated mail is being sent to remote domains.

When this happens it is probably an IPv4 vs. IPv6 issue. Here's one
scenario. It may not be exactly this in your case, but you should be able to
translate.

The MTA has an idea of what addresses constitute the local network and will
relay mail from those addresses to the outside. This includes say the IPv4
local host, something like 127.0.0.1, but not the IPv6 local host ::1.

Mailman, by default, delivers to 'localhost'. 'localhost' in turn is defined
as the IPv6 ::1 address. Thus Mailman's mail comes to the MTA from ::1 which
is not in the MTA's notion of the local network, so the MTA refuses to relay
the mail.

This can be fixed in multiple ways. You can add the IPv6 local host to the
MTA's local network. You can change /etc/hosts to associate
127.0.0.1 rather than ::1 with 'localhost'. You can set SMTPHOST in
mm_cfg.py to something that will work. E.g.,

SMTPHOST = '127.0.0.1'

Note that since I haven't seen your logs, the above scenario may be off.
Perhaps it would be that Mailman is sending via the IPv4 loopback and qmail
wants IPv6, but the idea is the same.

-- 
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/dean.collins%40insight
planners.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] help with error on start

[Ricardo Santos]

Thanks Mark for you answer. I installed from a tutorial with this command
(Centos 6.6)

> yum --enablerepo=remi install mailman  (Ver 3:2.1.12-18.el6 )



2015-05-17 11:54 GMT-04:00 Mark Sapiro :

> On 05/16/2015 06:55 PM, Ricardo Santos wrote:
> > I installed mailman and have those message:
> >
> > /usr/lib/mailman/bin/check_db --all --verbose
> >
> > Traceback (most recent call last):
> ...
> >   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 37, in
> 
> >
> > from Mailman.i18n import _
> >
> >   File "/usr/lib/mailman/Mailman/i18n.py", line 36, in 
> >
> > _ctype_charset = _get_ctype_charset()
>
>
> Something is wrong here. The Mailman/i18n.py distributed by the GNU
> Mailman project does not anything like the above line.
>
> How did you install Mailman? Where did /usr/lib/mailman/Mailman/i18n.py
> come from? If this is a 'package', see .
>
> --
> 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/ericardosantos%40gmail.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