[Mailman-Users] Subscribe command doesn't check for spam?
Hi, I'm using Mailman v. 2.1.9 on a Debian Linux platform. I'm running Exim4 as the MTA with spamassassin doing spam checking when messages are recived in Exim (Exiscan-acl). I've set up spam filtering rules in Mailman that will throw away messages that match ^X-Spam: YES in the headers. This works fine with most of the spam but messages that are sent to the *-subscribe address are accepted and not rejected. This means that mailman sends out confirmation requests to the spammers mail address, which most often is not valid or goes to some bogus address. I'm also adding to the flow of unwanted mail messages on the net... Is this a bug or a feature or have I gotten the things backwards? Shouldn't postings to the subscribe address be checked in the spam filter? Regards, /Martin -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Alternatives to having a list own itself
On 2/22/07, Brad Knowles [EMAIL PROTECTED] wrote: At 6:43 PM -0700 2/22/07, Kelly Jones wrote: My question: what's the best way to handle a situation like this? Have a list owned by itself or effectively owned by itself. What I've done in situations similar to this, is to make the listowner list itself owned by an alias that is directly resolvable out of /etc/aliases. So, there is no loop -- owner mail for other lists goes to the listowner list, owner mail for the listowner list goes to the listmaster alias, and that's that. Thanks, Brad. My problem here is that the 'sysops' list changes frequently, and I don't want to maintain it in two places (/etc/mail/aliases and the list membership). I suppose I could have a script update /etc/mail/aliases using the output of list_members sysops, but this seems kludgey. I'd also like members of 'sysops' to decide whether they want message to 'sysops' awaiting approval or not. If I make it an alias, everyone will get these emails. If I send it to a mailing list, I can setup a topic so that only people who want those messages will receive them. -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Subscribe command doesn't check for spam?
Martin Hagelin wrote: I've set up spam filtering rules in Mailman that will throw away messages that match ^X-Spam: YES in the headers. This works fine with most of the spam but messages that are sent to the *-subscribe address are accepted and not rejected. This means that mailman sends out confirmation requests to the spammers mail address, which most often is not valid or goes to some bogus address. I'm also adding to the flow of unwanted mail messages on the net... Is this a bug or a feature or have I gotten the things backwards? It is a problem. Shouldn't postings to the subscribe address be checked in the spam filter? Mailman's spam filters are designed to prevent unwanted mail from being delivered to the list or the list owner (i.e. humans). Thus only mail to the posting address and the -owner address is processed through Mailman's SpamDetect module. As you note above and I acknowledge, sending autoresponses and/or subscription confirmation requests to spoofed addresses is a problem. We intend to mitigate this somewhat in Mailman 2.1.10 by optionally not including the original message in autoresponses, thus not relaying the spam itself, but this doesn't affect subscription confirmations. The real question here is why aren't you just rejecting the spam at the MTA level instead of flagging and forwarding it, and then wanting to discard it in Mailman? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Alternatives to having a list own itself
At 6:43 AM -0700 2/27/07, Kelly Jones wrote: I'd also like members of 'sysops' to decide whether they want message to 'sysops' awaiting approval or not. If I make it an alias, everyone will get these emails. If I send it to a mailing list, I can setup a topic so that only people who want those messages will receive them. But you get into loop issues. That's why I do things the way I do -- I don't get loops. You've got to decide which is more important to you: 1) Avoiding loops and things working right virtually all the time? Or: 2) Convenience? -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Alternatives to having a list own itself
Where can I find more information concerning the uses of aliases and some examples? Dan Good On Feb 27, 2007, at 7:43 AM, Kelly Jones wrote: On 2/22/07, Brad Knowles [EMAIL PROTECTED] wrote: At 6:43 PM -0700 2/22/07, Kelly Jones wrote: My question: what's the best way to handle a situation like this? Have a list owned by itself or effectively owned by itself. What I've done in situations similar to this, is to make the listowner list itself owned by an alias that is directly resolvable out of /etc/aliases. So, there is no loop -- owner mail for other lists goes to the listowner list, owner mail for the listowner list goes to the listmaster alias, and that's that. Thanks, Brad. My problem here is that the 'sysops' list changes frequently, and I don't want to maintain it in two places (/etc/mail/aliases and the list membership). I suppose I could have a script update /etc/mail/aliases using the output of list_members sysops, but this seems kludgey. I'd also like members of 'sysops' to decide whether they want message to 'sysops' awaiting approval or not. If I make it an alias, everyone will get these emails. If I send it to a mailing list, I can setup a topic so that only people who want those messages will receive them. -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users% 40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/ dgood%40independence.k12.ia.us Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Alternatives to having a list own itself
At 2:16 PM -0600 2/27/07, Dan Good wrote: Where can I find more information concerning the uses of aliases and some examples? That's going to depend on your MTA. We have a little information in the Mailman documentation, the FAQ Wizard, etc... but most of the useful information will probably be found within the documentation that is specific to your MTA. If you use sendmail, then try sendmail.org. If you use postfix, then try postfix.org. Or whatever is appropriate for your MTA. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] sendmail and solaris stuff
The esteemed Barry Warsaw has said: Thanks Hank. I haven't used Sendmail in 20 years, so if there is some specific text you'd like to see added (or preferably a patch to the latex file), please feel free to send it directly to me and I'll push up a doc update. Barry (and Mark) Just to acknowledge your note. I am installing Mailman on a Solaris 10 cold O/S install, and am right at the point in the install manual where I have to configure sendmail to work with Mailman. This is the fourth or fifth time I've gone through the process, so as they say in the automotive trades, I'm able to make flat rate. Since you guys aren't working with either Sendmail or Solaris, I think it would be best for me to walk through and record the entire process, and give that to you as a basis for inclusion where and however you want to use it. I'll note that the sendmail.org faq on setting up virtual domains is broken, and while the bat book covers doing it, the discussion is not complete. I think that including the relevant part of the main.mc file, as well as the configuration of the local-domain-name file (known as the cw file), to give the novice admin. all of what is needed to set up a virtual domain system might be wise. That would save you guys from having to answer FAQ questions constantly. Mark, I still owe you a how-to on moving an existing list to a new host. Your notes on my first stab at it made clear that I was overcomplicating things. Hank -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] sendmail and solaris stuff
At 8:44 PM -0700 2/27/07, [EMAIL PROTECTED] wrote: Since you guys aren't working with either Sendmail or Solaris, I think it would be best for me to walk through and record the entire process, and give that to you as a basis for inclusion where and however you want to use it. The ironic thing is that I was the comp.mail.sendmail FAQ maintainer for a couple of years -- but that was ten years ago. It's been so long since that I really don't have the recent experience necessary to be able to comment usefully on the sendmail-related documentation that we have. That would save you guys from having to answer FAQ questions constantly. Yeah, we need to get all this in one place. Mark, I still owe you a how-to on moving an existing list to a new host. Your notes on my first stab at it made clear that I was overcomplicating things. That would also be appreciated. Thanks! -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] No mail and no posts from mailman
I am befuddled. mailman-2.1.8-0.FC4.1 (from RPM) Fedora Core 4 (kept up to date with nightly yum) postfix-2.2.2-2 (from RPM) This is an established list server that has had one functioning list (albeit very low volume, so I can't swear that it is still working). I added a new list, put myself and one other person as the administrator, set it to send notifications of new subscribers, and subscribed both of us to the list. Then I sent two test emails to the list, but they seem to have gone into a black hole. My workstation mail server sent them: Feb 26 18:07:33 bobcat postfix/smtp[1119]: 5B3EF42C8: to=[EMAIL PROTECTED], relay=bubba.bobcatos.com[192.168.3.2], delay=0, status=sent (250 Ok: queued as AC98C2057) Feb 26 22:08:54 bobcat postfix/smtp[11974]: DFFA742C8: to=[EMAIL PROTECTED], relay=bubba.bobcatos.com[192.168.3.2], delay=1, status=sent (250 Ok: queued as 429CA2056) My list server got it: Feb 26 18:07:41 bubba postfix/local[17421]: AC98C2057: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post foobarlist) Feb 26 22:09:03 bubba postfix/local[20514]: 429CA2056: to=[EMAIL PROTECTED], relay=local, delay=1, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post foobarlist) But nothing came out. Nothing held for moderation. Nothing in the /var/log/mailman/* logs about them. Nothing in the archives. Following FAQ 3.14: 0) Did it. 1) # ps auxww| grep mailmanctl |grep -v grep mailman 7087 0.0 0.3 13048 1672 ?Ss2006 0:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q start # ps auxww | egrep 'p[y]thon' mailman 7087 0.0 0.3 13048 1672 ?Ss2006 0:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q start mailman 7097 0.0 0.5 12912 2508 ?S 2006 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s 2) My /etc/mailman/aliases contains (among other things) # STANZA START: foobarlist # CREATED: Sat Feb 24 18:33:52 2007 foobarlist: |/usr/lib/mailman/mail/mailman post foobarlist foobarlist-admin: |/usr/lib/mailman/mail/mailman admin foobarlist foobarlist-bounces: |/usr/lib/mailman/mail/mailman bounces foobarlist foobarlist-confirm: |/usr/lib/mailman/mail/mailman confirm foobarlist foobarlist-join:|/usr/lib/mailman/mail/mailman join foobarlist foobarlist-leave: |/usr/lib/mailman/mail/mailman leave foobarlist foobarlist-owner: |/usr/lib/mailman/mail/mailman owner foobarlist foobarlist-request: |/usr/lib/mailman/mail/mailman request foobarlist foobarlist-subscribe: |/usr/lib/mailman/mail/mailman subscribe foobarlist foobarlist-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe foobarlist # STANZA END: foobarlist And the aliases.db file was updated. But then we knew that from the maillog entries. Also, my postfix main.cf contains alias_maps = hash:/etc/postfix/aliases, hash:/etc/mailman/aliases But then we knew that from the maillog entries, too. 3) Smrsh (not applicable) 4) Interface: This is a full-bore company mail server and has serviced the other list just fine, not to mention Squirrelmail and several daemons and cron jobs that send mail. 5) qrunner: Mailman is started by /etc/rc.d/init.d/mailman, and # service mailman status mailman (pid 7087) is running... 6) Locks: # ls -l ~mailman/locks ls: /usr/lib/mailman/locks: No such file or directory 7) Logs: The only things in the logs are the subscriptions: [EMAIL PROTECTED] mailman]# cat qrunner Feb 25 04:08:42 2007 (7087) Master watcher caught SIGHUP. Re-opening log files. Feb 25 04:08:44 2007 (7097) RetryRunner qrunner caught SIGHUP. Reopening logs. [EMAIL PROTECTED] mailman]# cat subscribe Feb 26 17:42:35 2007 (10359) foobarlist: new [EMAIL PROTECTED], admin mass sub Feb 26 17:42:35 2007 (10359) foobarlist: new [EMAIL PROTECTED], admin mass sub The only thing in error is the result of running mailmanctl with no arguments. /var/log/mailman/smtp is zero-length. 8) Qfiles: # ls -l ~mailman/qfiles ls: /usr/lib/mailman/qfiles: No such file or directory # locate qfiles /usr/lib/mailman/bin/show_qfiles Okay, with this and (6), I'm wondering if some directories are missing. But if so, why is (or was) the other list functioning, and why is there nothing in the logs about it? Also, the server has been up for 216 days, and the other list was created since the last boot, so there's been no system crash to take something out. 9) SMTPHOST: /var/log/mailman/smtp shows no signs of distress, in fact, it is zero-length (and owned by mailman). 10) Sendmail + mm-handler (not applicable) For FAQ 1.7: a) N/A since this is v2.1.8. b, c, and d) Aliases are ok by inspection and log entries, above. e) qrunner is running. f) No messages for moderation. g) /etc/mailman/mm_cfg.py contains DEFAULT_URL_HOST = www.bobcatos.com DEFAULT_EMAIL_HOST = lists.bobcatos.com
