Mailman 3 July 2016 - Mailman-Users

mailman and yahoo
by Manuel Goepfert 09 Jul '16

09 Jul '16

Hi All, I’m facing since a few weeks if not even more some issue when a registered user using yahoo.com email address sends an email to one of the list that mailman manages. As the list is configured to send emails on behalf of the user to the members of the list, this triggers some anti spam mecanism that puts the message in the spam folders of the different recipients even worth, the email is rejected by some mail servers. The consequence is that the email addresses get at the end removed from the list because of bounces as the origin email address @yahoo.com is not legitimately sent from a yahoo email server. Looking at some documentation I found out that this was a known problem and that it was addressed in on e of the mailman version. So I upgraded to 2.1.18 that included that fix but I?m still facing this problem. Do you guys have the same issue and if yes are you able to mitigate it in any way ? I do have spf,dkim and dmark in place for the domain used to send emails. Thanks for your feedback. Kind regards, Manu

2 2

Re: [Mailman-Users] Message discarded without reason logged in vette
by Mark Sapiro 09 Jul '16

09 Jul '16

On 7/8/16 9:33 AM, Hirayama, Pat wrote: > > This is the message (from just a few minutes ago, in fact): > > Jul 08 09:17:51 2016 (3892) Message discarded, msgid: <...> > > I am stumped. The sender is a non-moderated member. She is in fact, listed as a moderator. filter_content is set to no. ARCHIVE_HTML_SANITIZER does not appear to be set. dmarc_moderation_action is set to ACCEPT. header_filter_rules = []. The fact that she is listed as a moderator is irrelevant to this. Just to be sure, do 'ps -fww 3892' and verify that the process is IncomingRunner. Also note that starting with Mailman 2.1.19, the log message includes the name of the handler that raised the discard. See <https://bugs.launchpad.net/mailman/+bug/558096> and <http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1502>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 4

Re: [Mailman-Users] Message discarded without reason logged in vette
by Mark Sapiro 08 Jul '16

08 Jul '16

On 7/8/16 9:00 AM, Hirayama, Pat wrote: > > WRT Content filtering -- if filter_content is set to NO, then nothing else in that section should apply, right? That is, even if there is stuff defined for pass_mime_types and filter_filename_extensions? That's correct. Note that what I wrote below applies only to the exact log entry "Message discarded, msgid: <...>". It seems that's the one you've seen, but there can be other messages such as "No command, message discarded, msgid: <...>" which is logged for messages sent to the -request address with no command or to -confirm with incorrect format. > > -----Original Message----- ... > If the message in the vette log is "Message discarded, msgid: <...>", > that message is only produced in standard Mailman by IncomingRunner when > a handler raises DiscardMessage. Again in standard Mailman, the only > Handlers that do that are: > > MimeDel > - content filtering removes the entire message and filter_action is > other than Reject > > Moderate > - a post is from a moderated member with member_moderation_action Discard > - a post is from a non-member in discard_these_nonmembers or with > generic_nonmember_action Discard > > Scrubber > - if the top level MIME type is text/html and ARCHIVE_HTML_SANITIZER = > 0 (not the default, and this only applies if scrub_nondigest is Yes) > > SpamDetect > - when a message matches KNOWN_SPAMMERS > - A post is From: a domain with DMARC p=reject (or maybe quarantine) > and dmarc_moderation_action is Discard > - a message matches header_filter_rules with Discard action or with > Reject action and the message is to -owner -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Message discarded without reason logged in vette
by Hirayama, Pat 08 Jul '16

08 Jul '16

So, I found a 10 year old post where Mark Sapiro described some of the reasons why "Message discarded" with only a message id and no reason happens: Examples are when nothing is left after content filtering, a post from a moderated user when action is discard, a post from a non-member in discard_these_nonmembers, a post from a non-member with generic action discard, some cases of a text/html post when ARCHIVE_HTML_SANITIZER = 0 and a post matching a header_filter_rule with discard action. I was wondering if there was a more complete list someplace? Mostly because I had this happen to one of my users 3 weeks ago, and I think that I've managed to rule out everything that Mark wrote back then. Thanks, -p -- Pat Hirayama Systems Engineer / 206.667.4856 / phirayam(a)fredhutch.org / Fred Hutch / Cures Start Here CIT | Enterprise IT Services / Advancing IT and Data Services to Accelerate the Elimination of Disease

2 2

Mailman installation does not work
by Bob Lydiate 07 Jul '16

07 Jul '16

I am reinstalling Mailman after having to change servers. I am using Ubuntu 16.04, Apache, Postfix, Mailman. I have apache and postfix both working and serving mail and web. I have installed and re-installed Mailman a couple of times to try and get it working right and now have no idea what is creating the problem that stops it from working. I have several issues that I can identify, and I am sure there are several that I have missed. Problem 1 When I run 'check_perms -f' it tells me that the permissions on /var/lib/mailman/cron bad group (has:root, expected list) (fixing) this problem is repeated with 9 other scripts. When I check the actual directory '/var/lib/mailman' I find that these files are all links to '/usr/lib/*; where the correct group is set. When I try to access the web interface, I am asked if I want to open a file called 'admin' instead of opening a webpage called admin. when I run '/etc/init.d/mailman start' or the equivalent for postfix or apache, I get no errors. I did alter the config setup to have mydomain.ca rather than lists.mydomain.ca, but that is the only change I made to the config as it came through. I have checked the archives and have searched out the issues that I suspect, but have found nothing that worked to fix these issues. Bob

3 3