Mailman 3 May 2009 - Mailman-Users

Auto confirmation
by Infokeep - Mario Sergio 28 May '09

28 May '09

Hi list, When I send a message for my list, I'd like to receive the an email with reading confirmation. I marked this options in my outlook. In menu Tools, Options: Request reading confirmation All people of my list receive my email but no confirmation was send to me. Is this possible? Regards, MSC

2 4

migrating from sendmail site to postfix site
by admin2 28 May '09

28 May '09

Hi there, I am migrating mailman from a freebsd server running sendmail to an ubuntu server running postfix. Could somebody please send me a decent link that explains the postfix/mailman configuration? I am getting relaying denied messages on the postfix side. Cheers, Noah

2 3

Odd Behavior
by Dennis Putnam 28 May '09

28 May '09

I'm not sure this is really a Mailman issue but at this point, I don't know where else to start. The problem stems from email to the root user. I have an alias set (postfix) to send mail for root to my administrator address. If it matters this address is in a different domain so the form of the alias is administrator(a)myotherdomain.com. Also, FWIW, this seems to have started when I upgraded from Mandriva 2007 to 2008.2. What is happening, is that mail to root is somehow being routed through Mailman. Each time something is sent to root, the following error email is generated: --------------------------------------------------------------------------------------------------------------- This is the mail system at host home.mydomain.com. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <"mailman-loop:/var/lib/mailman/data/owner-bounces.mbox"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-loop:/var/lib/mailman/data/owner-bounces.mbox" <"mailman:|/usr/lib/mailman/mail/mailman post mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman:|/usr/lib/mailman/mail/mailman post mailman" <"mailman-admin:|/usr/lib/mailman/mail/mailman admin mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-admin:|/usr/lib/mailman/mail/mailman admin mailman" <"mailman-bounces:|/usr/lib/mailman/mail/mailman bounces mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-bounces:|/usr/lib/mailman/mail/mailman bounces mailman" <"mailman-confirm:|/usr/lib/mailman/mail/mailman confirm mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-confirm:|/usr/lib/mailman/mail/mailman confirm mailman" <"mailman-join:|/usr/lib/mailman/mail/mailman join mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-join:|/usr/lib/mailman/mail/mailman join mailman" <"mailman-leave:|/usr/lib/mailman/mail/mailman leave mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-leave:|/usr/lib/mailman/mail/mailman leave mailman" <"mailman-owner:|/usr/lib/mailman/mail/mailman owner mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-owner:|/usr/lib/mailman/mail/mailman owner mailman" <"mailman-request:|/usr/lib/mailman/mail/mailman request mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-request:|/usr/lib/mailman/mail/mailman request mailman" <"mailman-subscribe:|/usr/lib/mailman/mail/mailman subscribe mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-subscribe:|/usr/lib/mailman/mail/mailman subscribe mailman" <"mailman-unsubscribe:|/usr/lib/mailman/mail/mailman unsubscribe mailman"@home.mydomain.com> (expanded from <root>): unknown user: "mailman-unsubscribe:|/usr/lib/mailman/mail/mailman unsubscribe mailman" . . . Reporting-MTA: dns; home.mydomain.com X-Postfix-Queue-ID: C0B9C85073 X-Postfix-Sender: rfc822; root(a)home.mydomain.com Arrival-Date: Mon, 25 May 2009 04:11:19 -0400 (EDT) Final-Recipient: rfc822; "mailman-loop:/var/lib/mailman/data/owner-bounces.mbox"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-loop:/var/lib/mailman/data/owner-bounces.mbox" Final-Recipient: rfc822; "mailman:|/usr/lib/mailman/mail/mailman post mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman:|/usr/lib/mailman/mail/mailman post mailman" Final-Recipient: rfc822; "mailman-admin:|/usr/lib/mailman/mail/mailman admin mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-admin:|/usr/lib/mailman/mail/mailman admin mailman" Final-Recipient: rfc822; "mailman-bounces:|/usr/lib/mailman/mail/mailman bounces mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-bounces:|/usr/lib/mailman/mail/mailman bounces mailman" Final-Recipient: rfc822; "mailman-confirm:|/usr/lib/mailman/mail/mailman confirm mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-confirm:|/usr/lib/mailman/mail/mailman confirm mailman" Final-Recipient: rfc822; "mailman-join:|/usr/lib/mailman/mail/mailman join mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-join:|/usr/lib/mailman/mail/mailman join mailman" Final-Recipient: rfc822; "mailman-leave:|/usr/lib/mailman/mail/mailman leave mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-leave:|/usr/lib/mailman/mail/mailman leave mailman" Final-Recipient: rfc822; "mailman-owner:|/usr/lib/mailman/mail/mailman owner mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-owner:|/usr/lib/mailman/mail/mailman owner mailman" Final-Recipient: rfc822; "mailman-request:|/usr/lib/mailman/mail/mailman request mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-request:|/usr/lib/mailman/mail/mailman request mailman" Final-Recipient: rfc822; "mailman-subscribe:|/usr/lib/mailman/mail/mailman subscribe mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-subscribe:|/usr/lib/mailman/mail/mailman subscribe mailman" Final-Recipient: rfc822; "mailman-unsubscribe:|/usr/lib/mailman/mail/mailman unsubscribe mailman"@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: "mailman-unsubscribe:|/usr/lib/mailman/mail/mailman unsubscribe mailman" . . . Subject: Cron <root@dap002> nice -n 19 run-parts --report /etc/cron.daily From: root(a)home.mydomain.com (Cron Daemon) Date: Mon, 25 May 2009 04:02:01 -0400 (EDT) To: root(a)home.mydomain.com /etc/cron.daily/msec: diff: /var/log/security/chkrootkit.today: No such file or directory -------------------------------------------------------------------------------------------------------------- This continues for every mailing list on the host. I should note that all the mailing lists seem to otherwise be functioning properly. Is there something in my Mailman configuration that can intercept all mail (outgoing?) and try to process it or is something else going on? Any help trying to figure this out would be greatly appreciated.

2 1

Re: [Mailman-Users] Help! "Stuck Messages"
by Aaron Marcavitch 28 May '09

28 May '09

And that - ladies and gentlemen - did it. Nothing like a quick hit to the side of a machine to make it act right. Aaron -------- http://www.marcavitch.com --- On Wed, 5/27/09, John <mailman-owner(a)rx7-world.net> wrote: > From: John <mailman-owner(a)rx7-world.net> > Subject: Re: [Mailman-Users] Help! "Stuck Messages" > To: mailman-users(a)python.org > Date: Wednesday, May 27, 2009, 12:07 PM > I have a similar problem... I use a > Virtual Dedicated server to host several > domains with a number of Mailman lists on them. Every so > often the traffic on > the Mailman lists drops to a trickle or stops. Bounce > volume and regular email > is usually unaffected. I've given up trying to debug it, I > just reboot the > server and the flood-gates open. Sometimes the easiest > solution/work-around is > brute force... :-/ > > John > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users(a)python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: http://mail.python.org/mailman/options/mailman-users/acornhp%40yahoo.com > > Security Policy: http://wiki.list.org/x/QIA9 >

1 0

Non-Member filter Notations
by Ferdinand Escudero 28 May '09

28 May '09

In Mailman 2.1.5 Under Privacy Options|Senders Filters non-member filters.. are regular expressions case sensitive ? -- Ferdinand Escudero Systems Administrator University of California San Diego Computer Science and Engineering Phone:858 822-6561 email:ferdie@ucsd.edu

2 1

Re: [Mailman-Users] my mailman has been hacked !!
by Russell Clemings 28 May '09

28 May '09

In addition to the earlier suggestions: 1. Turn on content filtering -- the default settings should remove most if not all dangerous attachments. 2. Under general settings, set the maximum message size as small as possible. This not only blocks a lot of viruses but on a discussion list it prevents people from quoting an entire digest when replaying. But for broadcast lists, the suggestion about moderating everybody should do the trick. I just keep emergency moderation (also on general options page) on at all times for those lists. rac > ---------- Forwarded message ---------- > From: Rob MacGregor <rob.macgregor(a)gmail.com> > To: mailman-users(a)python.org > Date: Wed, 27 May 2009 19:41:15 +0100 > Subject: Re: [Mailman-Users] my mailman has been hacked !! > On Wed, May 27, 2009 at 19:23, Khalil Abbas <khillo100(a)hotmail.com> wrote: > > > > HELP!! > > > > one of my lists has been hacked.. all members are moderated, except my > own email address (my(a)email.com) which I use to post to the list .. > > > > someone sent from my address to the list and all my subscribers has > recieved a damn virus as an attachment!! but the 'From' name is not me, > which means that the sender didn't use my email to send but used a kind of > open-relayed server or something .. > > > > please help what should I do ??? > > Look at the headers and work out what really happened. > > Forging email addresses is trivial. It is the work of a few seconds > to send an email with somebody else's email address. You can mitigate > somewhat by using SPF and DKIM, but it does require that everybody > checks your SPF and DKIM records - not everybody does. > > -- > Please keep list traffic on the list. > > Rob MacGregor > Whoever fights monsters should see to it that in the process he > doesn't become a monster. Friedrich Nietzsche > > >

1 0

Repeating calendar entries
by John Colbert 28 May '09

28 May '09

I want to sending emails with repeating calendar entries into a mailman text-only community list. Any suggestions or experience with this idea? Seems like an obvious thing but Yahoo and Google calendars produce messages with loads of extra stuff and I just want text that I have more control over. thanks in advance, John

1 0

Mailman Sibling lists
by Damion Theobald 27 May '09

27 May '09

Hi, Could anyone be of help in the setting up of mailman sibling lists. I currently have the below setup Parent list Sibling list Staff staff-info All-info Non-staff non-staff-info All-info This all works correctly except when a e-mail is sent to both the staff and non-staff parent lists. It results in the people on 'All-info' list receiving duplicate e-mails. I have tried adding the staff list into the regular_exclude_lists in the 'non-staff' list but this does not work Any help would be most appreciated. Regards Damion

2 1

Re: [Mailman-Users] Help! "Stuck Messages"
by John 27 May '09

27 May '09

I have a similar problem... I use a Virtual Dedicated server to host several domains with a number of Mailman lists on them. Every so often the traffic on the Mailman lists drops to a trickle or stops. Bounce volume and regular email is usually unaffected. I've given up trying to debug it, I just reboot the server and the flood-gates open. Sometimes the easiest solution/work-around is brute force... :-/ John

1 0

Dealing with spam
by Henry Hartley 27 May '09

27 May '09

I have a few small, private lists managed with Mailman. For the most part, I don't have problems with spam, probably aided by the fact that they are both small and private. Lately, however, on one list (about two dozen addresses) I'm getting spam that has valid users as the From: address. My first thought was that the users' machines were being used as spam bots but at least one uses my server as it's mail server and these messages are coming from other servers. So, it seems that their address is being spoofed and being used to sent mail to the list (even though it isn't advertised). For the most part, messages are coming with implicit destination so I can simply discard them but occasionally they come directly to the list and are not filtered. I have two questions: 1) What is the best practice approach to dealing with these messages? I have simply been discarding them. If I reject them, will that send a response back that might make an automated sender drop my list address from their list as a non-working address? Or is that wishful thinking? 2) Is there some way to automatically reject or discard mail with implicit destination rather than holding it for moderation? The users of this particular list do not (ever) intentionally use an implicit destination so I wouldn't mind just automating that. There doesn't seem to be a setting on the Recipient Filters page of Privacy options. Thanks. -- Henry

3 2