Re: [Mailman-Users] [SOLVED] Re: Mailman won't send messages?
Dennis Carr wrote: > >The problem, as I discovered completely by accident, is that the list >owner also needs to be subscribed to the list - this is not >automatically done in 2.1.5, which is what is current in Debian Sarge. I don't know why that would be a problem unless the problem was that the list owner's posts were held because they were from a non-member. Or maybe you're saying that the only problem was that the list owner thought that posts weren't delivered because he/she wasn't receiving them. In general, there is no requirement that the owner be a member of the list which is why the owner is not automatically a member. -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] delivery to Prodigy
Jeff Donsbach wrote: >Has anyone out there had any problems with their lists where messages >were not being delivered to subscribers on Prodigy? My prodigy users receive list posts OK. >I have one user >on Prodigy (small lists) that says he hasn't received any list emails >for a while now. I checked my Postfix logs and I can see that Prodigy >accepted the messages successfully (return code 250). I'm at a loss of >what to do next. Yes, I have told him to check any Spam filters & >folders on his end to see if messages were getting caught somewhere. >No luck. No messages found. > >Suggestions? Could Prodigy be silently dropping messages from my lists? Absolutely, but if they are, it is unlikely that the fact that they come from Mailman or have Precedence: list is the reason unless the user has somehow elected not to receive Precedence: list mail. The next step is for the user to complain to Prodigy that he is not receiving mail that he wants to receive, and to keep beating on them until they stop censoring his mail or satisfactorily explain what the problem is. You can help by providing the log messages that show the mail was sent and 'accepted' at their end. You could try contacting Prodigy too, but I think this kind of complaint is more likely to produce a successful result if it coms from their customer. -- 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=show&file=faq01.027.htp
[Mailman-Users] Can't Delete Corrupt Subscriber Address
We are using Mailman v 2.1.4 on a Linux box with postfix and I am site admin. We have a subscriber address that has /t on the end of it ([EMAIL PROTECTED]/t) which can only be seen when dumping the lists config file. The subscriber address looks normal [EMAIL PROTECTED]) when looking for it using any other method (list members, etc). I've tried to use reg exps using remove member with no luck and tried using the method described in the FAQ (3.13. How do I remove a user name or email address with an illegal character in it?) with no luck either. Does anyone have any other suggestions? Thanks Tim -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] installation problems - newlist-issues
> "Mark" == Mark Sapiro <[EMAIL PROTECTED]> writes: Mark> Henrik wrote: >> On 2/24/06, Mark Sapiro <[EMAIL PROTECTED]> wrote: >>> Then maybe someone put it in Defaults.py. Let's hope Mandrake >>> is not distributing its package this way. >> They are, I'm afraid. Mark> :-( With all due respect to Henrik, if I were you, unless you find something obvious pretty quickly, I'd send him right back to Mandriva. Then add Mandriva to the cPanel FAQ. I've been around this loop with Mandriva, and they claim to see nothing wrong with such hacks as a matter of policy. :-( -- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software. -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Integrating Mailman with Spamassassin
> On Thursday 23 February 2006 16:36, Jon D. Slater wrote: >> I've been using Mailman for some time, and just recently installed >> SpamAssassin on my Fedora Core 4, Linux machine. > > Spam-assassin would normally be used with the MTA (i.e. exim, qmail, etc.) > and > not Mailman. Basically, you should be using it to stop spam from getting > to > Mailman alltogther and not after the message has already been accepted by > your SMTP daemon. > > So this is likely not the place to be asking that question, try looking > through the Spam-Assassin site for intergration how-tos for your SMTP > daemon. Oh, I disagree, it's not that bad a place to ask - How about Mailman FAQ #4.23? http://www.python.org/cgi-bin/faqw-mm.py?req=all#4.23 Three methods - #1 is MTA integration #2 uses patches - This is what I do, and it works great. Unfortunately, the link http://jamesh.id.au is no longer good, so you will have to get the patches elsewhere. Google spamassassin.py or see http://sourceforge.net/tracker/index.php?func=detail&aid=640518&group_id=103&atid=300103 You will need to add the following to your mm_cfg.py: # GLOBAL_PIPELINE.insert(1, 'SpamAssassin') SPAMASSASSIN_HOST = 'localhost' SPAMASSASSIN_DISCARD_SCORE = 500 SPAMASSASSIN_HOLD_SCORE = 3 SPAMASSASSIN_MEMBER_BONUS = 0 # You can also do a similar thing for Clam if you get that patch # Scan messages for viruses using Clam AntiVirus GLOBAL_PIPELINE.insert(1, 'ClamScan') CLAMAV_DISCARD = 0 CLAMAV_CLAMDSCANPATH = '/usr/bin/clamdscan' #3 Procmail also works, of course. John -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Can't Delete Corrupt Subscriber Address
Tim wrote: > >We have a subscriber address that has /t on the end of it ([EMAIL >PROTECTED]/t) which can only be seen when dumping the lists config file. The >subscriber address looks normal [EMAIL PROTECTED]) when looking for it using >any other method (list members, etc). Do you mean '\t', i.e. a tab character? Is the difference between '\t' and '/t' a typo here or does it have something to do with your lack of success? If you try the '-f' option with list_members, you might actually see the between 'xxx.com' and the terminating '>'. >I've tried to use reg exps using remove member with no luck Do you mean bin/remove_members? It doesn't accept regexps, only literal addresses, and it won't accept a '\t' escape - you'd need to give it an actual tab character. You could try bin/remove_members listname '[EMAIL PROTECTED]' where represents an actual tab character >and tried using the method described in the FAQ (3.13. How do I remove a user >name or email address with an illegal character in it?) with no luck either. Try bin/withlist -l listname and then at the '>>>' prompts type adr = '[EMAIL PROTECTED]'(this should be the actual address of course) m.removeMember(adr) If that throws an exception, try del m.members[adr] Then in any case type m.Save() in order to save the changed list, and finally type control-D to a prompt to end the interactive session. -- 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=show&file=faq01.027.htp
