[Mailman-Users] HELP!!!
Dear sir/miss, When using your software I keep having the same problem and I really cannot figure out how to solve it! How do I sent a emailmessage to all the people in my mailing list that I have put in it manually. I have tried many things but nothing works. What is the problem? I have a mailing list called t...@slimmer-denken.nl and I have a emailaccount called slimm...@slimmer-denken.nl So when i send a emailmessage using slimm...@slimmer-denken.nl to t...@slimmer-denken.nl it suppose to send a email to all my subscribers right? But it doesn't. I have also tried serveral other things, but nothing works! So how do I fix this? How does this work? I have looked on your website and read the FAQ but still nothing works. So please help me out with this. with kind regards, Atma Ramsaran _ Haal meer uit je leven met Windows Live http://www.microsoft.com/netherlands/windowslive/Views/index.aspx -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Customizing Special Addresses -request, -bounce, etc.
Mark Sapiro wrote: Lawrence Chan wrote: How can I customize Mailman's special addresses? It seems like it uses listname-request, listname-bounce, etc.. I'd like to use my own. For example, if my listname is list_domain.tld and my virtual and alias mappings are list-requ...@domain.tld to list-request_domain.tld to |/usr/lib/mailman/mail/mailman request list-request_domain.tld, I want Do you mean |/usr/lib/mailman/mail/mailman request list_domain.tld Yes. Mailman to respond with list-requ...@domain.tld instead of list_domain@domain.tld. Is this cPanel? If so, see http://wiki.list.org/x/sYA9. This is not cPanel. I'd like to have certain functionality (mainly 1-3) in the FAQ. For 1 in the FAQ, I use virtual aliases. For 2 and 3, I can just follow the listname_domain.tld convention. In any case, I don't understand what you mean by I want Mailman to respond with Please clarify. When Mailman replies, for example to listname-requ...@domain.tld and subject help, it uses listname_domain.tld-boun...@domain.tld as From. It uses listname_domain.tld-[request, owner, etc.] in the links in the body. How can I make Mailman reply without the _domain.tld in its headers and links in the reply messages? -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Customizing Special Addresses -request, -bounce, etc.
Mark Sapiro wrote: Lawrence Chan wrote: Mark Sapiro wrote: Is this cPanel? If so, see http://wiki.list.org/x/sYA9. This is not cPanel. I'd like to have certain functionality (mainly 1-3) in the FAQ. For 1 in the FAQ, I use virtual aliases. For 2 and 3, I can just follow the listname_domain.tld convention. What FAQ? The Mailman FAQs I know (http://www.list.org/faq.html and http://wiki.list.org/x/AgA3%22) don't have a '1-3' relating to virtual domain hosting. 1-3 in http://wiki.list.org/x/sYA9. Anyways... In any case, I don't understand what you mean by I want Mailman to respond with Please clarify. When Mailman replies, for example to listname-requ...@domain.tld and subject help, it uses listname_domain.tld-boun...@domain.tld as From. It uses listname_domain.tld-[request, owner, etc.] in the links in the body. How can I make Mailman reply without the _domain.tld in its headers and links in the reply messages? It appears that you are adopting a convention, perhaps enforced by list creation, that list names are of the form LISTNAME_HOSTNAME and are using aliases to direct mail addressed to listn...@hostname and listname-...@hostname to the proper list. The short answer to your question is to find the places in the code where these addresses are generated and change them to strip the _HOSTNAME part. This may or may not be as simple as modifying just the getListAddress() method in Mailman/MailList.py. That's it. I'll check out getListAddress() in Mailman/MailList.py. Thanks for your direction. -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Non-subscribers defeating the generic non-member action
Mark: Thank you for this info. I'll see if I have access to archives/private/LIST.mbox/List.mbox. To answer your question, I made a mistake in the regex (it's been years since messing with those little darlings). I actually blocked the spoofed email by putting t...@mydomain.org in the discard these non-members list. Since I have also been getting emails from t...@otherdomain.com I thought I would just discard everything with a username the same as my (pretty unique) listname. But I see now that I got that regex wrong. I don't understand how non-alphanumeric characters made a difference, either, but they did. Emails containing such characters were not in general a problem, but if they started with a '_' or a '-' or something of the sort, mailman would simply let them through. When I put the following regexes into the spam filter rule 1, the problem stopped: from: _...@.* from: -...@.* and then, later, just in case, I added from: \...@.* Skipper Mark Sapiro wrote: Robert Boyd Skipper wrote: I've been running lists for years, and the filtering has been pretty good at blocking posts from non-members. But recently, there have been some leaks, allowing non-member spammers to slip a message onto the list. The first time this happened, it turned out to be due to non-alphanumeric characters at the beginning of email addresses in the From: field. I don't know why non-alphanumeric characters in the address would by themselves cause a non-member post to be accepted. So, I made a regex filter that put a stop to that. But now, it has happened again, and I can't see anything unusual about the emails. Has anyone else noticed this happening? One of those emails that say Can't see images? Click here! got through. The subject line reads, [test] Dear t...@mydomain.org Shopping just got a loteasier! (I've substituted dummy names for real ones.) Where you see four spaces in the Subject line, there instead appeared a small circle. The Subject: header has nothing to do with whether or not the post is accepted. The From: field had the name Doctor Joe Smith, but on mouseover, it said t...@mydomain.org. Now I've had many hundreds of emails that spoofed the name of my list in the past. And the program always caught them. This one got through. Doctor Joe Smith is not a subscriber and his name does not appear in any of the non-member filters. The real name in the From: header also has nothing to do with it. I've blocked anything that claims to come from te...@.* and that seems to have stopped it, but I don't think the spoofing explains the problem, since mailman had previously blocked about ten posts per day that spoofed the listname. It could be that I've never seen the combination of a person's name and the listname in the From: field. I just don't remember. By default (this can be changed in mm_cfg.py but normally isn't), Mailman looks at the addresses in From:, Reply-To: and Sender: headers and the envelope sender address to determine if the post is from a list member. Any thought? I saved the email. The mail received from the list will not reflect the original envelope sender or Sender: header and may not reflect the original Reply-To:. Thus it is not completely useful in diagnosing this. If you have access to the archives/private/LIST.mbox/List.mbox file, the message archived there will have the original Sender: if any and may have a Return-Path: header indicating the original envelope sender. How are you blocking mail from te...@.*? What if anything is in the list's accept_these_nonmembers? -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Unicode in daily digest
Hi, I am an administrator for a mailing list that uses unicode extensively. Mails containing unicode are garbled in daily digest mode. The same mail with unicode is faithfully transmitted in individual email mode (i.e., when a list member signs up to receive mails directly instead of digest mode). Any info would be appreciated. Thanks, Naresh -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Non-subscribers defeating the generic non-member action
Mark: About the list's accept_these_non-members, I have ten email address that I put there for people who want to send from multiple emails but only want to receive posts at one of those addresses. None of them resemble the problem address. I'll do the testing you suggest and report what I find. Skipper Mark Sapiro wrote: Robert Boyd Skipper wrote: Thank you for this info. I'll see if I have access to archives/private/LIST.mbox/List.mbox. If you don't have direct access to the file on host, you can get it via the web with a URL like http://www.example.com/Mailman/private/LIST.mbox/LIST.mbox. This works whether the archive is private or public. To answer your question, I made a mistake in the regex (it's been years since messing with those little darlings). I actually blocked the spoofed email by putting t...@mydomain.org in the discard these non-members list. The ONLY thing that will be accomplished by putting an address or regexp in discard_these_nonmembers is that mail from matching non-member addresses will be discarded instead of applying generic_nonmember_action. If generic_nonmember_action is other than Accept, this should have no effect on whether a particular message goes to the list without moderator action. Since I have also been getting emails from t...@otherdomain.com I thought I would just discard everything with a username the same as my (pretty unique) listname. But I see now that I got that regex wrong. I don't understand how non-alphanumeric characters made a difference, either, but they did. Emails containing such characters were not in general a problem, but if they started with a '_' or a '-' or something of the sort, mailman would simply let them through. When I put the following regexes into the spam filter rule 1, the problem stopped: from: _...@.* from: -...@.* and then, later, just in case, I added from: \...@.* Did you ever test with your own message with a From: beginning with '_' or '-' to see if that was really letting messages through or if it was just a coincidence? Again, What if anything is in the list's accept_these_nonmembers? -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] help with bug in mailman version 2.1.12
Hi - hope you can help me with a bug I encountered when trying to open one of my lists - here is the error message: Bug in Mailman version 2.1.12 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Any idea what's going on and how to fix? Thank you Lisa Lisa McClear Marketing Director Advanced Learning Institute 8600 W. Bryn Mawr Avenue Suite 920-N Chicago, IL 60631 T: 773-695-9400, x12 F: 773-695-9403 -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] help with bug in mailman version 2.1.12
Unfortunately, that error message doesn't contain enough information for us to help you. As it says, you'll need to find this information in the mailman logs (specifically, the error log, which is probably stored in something like ~mailman/logs/error or /var/log/mailman/error, but the exact path will depend on your installation). It would also help if you could explain exactly what you mean by trying to open one of my lists -- were you trying to use the web interface? Was it the listinfo page or one of the admin pages or something else? Lisa McClear wrote: Hi - hope you can help me with a bug I encountered when trying to open one of my lists - here is the error message: Bug in Mailman version 2.1.12 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Any idea what's going on and how to fix? Thank you Lisa Lisa McClear Marketing Director Advanced Learning Institute 8600 W. Bryn Mawr Avenue Suite 920-N Chicago, IL 60631 T: 773-695-9400, x12 F: 773-695-9403 -- Mailman-Users mailing list Mailman-Users@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/terri%40zone12.com Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] HELP!!!
See the FAQ at http://wiki.list.org/x/MIA9 for a list of potential reasons for this, and links to other FAQ entries that might help solve your problem. Atma R wrote: Dear sir/miss, When using your software I keep having the same problem and I really cannot figure out how to solve it! How do I sent a emailmessage to all the people in my mailing list that I have put in it manually. I have tried many things but nothing works. What is the problem? I have a mailing list called t...@slimmer-denken.nl and I have a emailaccount called slimm...@slimmer-denken.nl So when i send a emailmessage using slimm...@slimmer-denken.nl to t...@slimmer-denken.nl it suppose to send a email to all my subscribers right? But it doesn't. I have also tried serveral other things, but nothing works! So how do I fix this? How does this work? I have looked on your website and read the FAQ but still nothing works. So please help me out with this. with kind regards, Atma Ramsaran _ Haal meer uit je leven met Windows Live http://www.microsoft.com/netherlands/windowslive/Views/index.aspx -- Mailman-Users mailing list Mailman-Users@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/terri%40zone12.com Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Unicode in daily digest
Naresh Cuntoor wrote: I am an administrator for a mailing list that uses unicode extensively. Mails containing unicode are garbled in daily digest mode. The same mail with unicode is faithfully transmitted in individual email mode (i.e., when a list member signs up to receive mails directly instead of digest mode). MIME format digests should contain the individual messages in their original character sets and should not be a problem. Plain format digests are converted to the character set of the list's preferred language (us-ascii for English language). Thus, unicodes in the original message which are not representable in the character set of the list's preferred language will be replaced by the 'unknown' character. If this is the issue in your case, your users can get MIME digests, or if your list's preferred language is English, you can change its character set to utf-8. -- Mark Sapiro m...@msapiro.netThe 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://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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] [mm] HELP!!!
Is that address properly aliased to mailman in /etc/aliases? -C When using your software I keep having the same problem and I really cannot figure out how to solve it! How do I sent a emailmessage to all the people in my mailing list that I have put in it manually. I have tried many things but nothing works. What is the problem? I have a mailing list called t...@slimmer-denken.nl and I have a emailaccount called slimm...@slimmer-denken.nl So when i send a emailmessage using slimm...@slimmer-denken.nl to t...@slimmer-denken.nl it suppose to send a email to all my subscribers right? But it doesn't. I have also tried serveral other things, but nothing works! So how do I fix this? How does this work? I have looked on your website and read the FAQ but still nothing works. So please help me out with this. with kind regards, Atma Ramsaran _ Haal meer uit je leven met Windows Live http://www.microsoft.com/netherlands/windowslive/Views/index.aspx -- Mailman-Users mailing list Mailman-Users@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/cgregory%40hwcn.org Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
* Mark Sapiro m...@msapiro.net wrote: Stefan Förster wrote: generated by recipi...@intern.example.com mailbox is full: retry timeout exceeded Is there any way to rewrite those addresses or to help Mailman identify those bounces correctly? And yes, this a pretty stupid thing to do on their ISPs part... Mailman has a whole host of heuristic recognizers for non-compliant DSNs, but it doesn't try to guess if a non-member bouncing address might be a munged version of a member address. Because it's a pretty stupid thing to do - at least the fact that addresses are not rewritten twice. The 'best' solution for recognizing original recipients of bounced messages is Mailman's VERP like capability. This puts the original recipient's address in the envelope sender address so the envelope in this case is from invalidlist-bounces+recipient=example@lists.incertum.net. When the bounce is returned to that address, the MTA delivers it to the list-bounces address and Mailman recognizes the original recipient as recipi...@example.com from the envelope recipient of the DSN. The cost of this approach is that Mailman has to send an individual message to the outgoing MTA for each recipient. Bummer. There is no way to implement that, our mailing list server is already suffering from too much traffic, it's quite old hardware, after all. Thanks anyways Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #283: whoami - Whoami ist nur was für Leute mit Alzheimer! (Begründung von Microsoft Deutschland für das Entfernen des Befehls aus Windows NT) -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
on 7/8/09 11:56 AM, Stefan Förster said: Bummer. There is no way to implement that, our mailing list server is already suffering from too much traffic, it's quite old hardware, after all. Take a look at the stuff on performance tuning in the FAQ. Even really old hardware can perform amazingly well, if it's tuned correctly. I guarantee that you would be astonished at what I can achieve with an ancient Compaq Pentium-133 laptop with 64MB of RAM and a 10GB hard drive (upgraded from 1GB). If you've already done as much performance tuning as you can do, then obviously you're not going to squeeze any more blood out of that turnip. But I would suggest that you familiarize yourself with these sections to make sure that you're actually doing as much as you can. -- Brad Knowles b...@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
* Brad Knowles b...@shub-internet.org wrote: on 7/8/09 11:56 AM, Stefan Förster said: Bummer. There is no way to implement that, our mailing list server is already suffering from too much traffic, it's quite old hardware, after all. Take a look at the stuff on performance tuning in the FAQ. Even really old hardware can perform amazingly well, if it's tuned correctly. I guarantee that you would be astonished at what I can achieve with an ancient Compaq Pentium-133 laptop with 64MB of RAM and a 10GB hard drive (upgraded from 1GB). If you've already done as much performance tuning as you can do, then obviously you're not going to squeeze any more blood out of that turnip. But I would suggest that you familiarize yourself with these sections to make sure that you're actually doing as much as you can. Thanks for your advice, Brad. The problem is that, due to policy reasons, outgoing mail has to pass a content filter, running locally on the Mailman box. With VERP... I guess I will simply move the list server to another computer (and a different network). Cheers Stefan -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
on 7/8/09 6:12 PM, Stefan Förster said: Thanks for your advice, Brad. The problem is that, due to policy reasons, outgoing mail has to pass a content filter, running locally on the Mailman box. With VERP... Chuq von Rospach wrote some stuff in the FAQ detailing his experience with how VERP impacted performance on the systems he was managing. Of course, this doesn't necessarily apply directly to your case, but it is instructive to read. My recollection is that, in his case, he found that without VERP he got about two recipients per copy of each message transmitted -- due to the fact that some recipients are all on the same system and only one copy is sent to that system for multiple recipients, while others get unique copies because no one else is subscribed from that system. That meant that enabling VERP roughly doubled the number of copies of messages that had to be sent (so that each person is guaranteed to get their own personal unique copy), but that this didn't actually affect the overall performance very much (since so much of e-mail is I/O bound and waiting for the system at the other end to respond). However, enabling VERP also meant that it was now much, much easier for the system to automatically manage bounces (a.k.a., Non-Delivery Notices, or NDNs), delivery status notices (DSNs), etc This made overall management of the system much easier, and greatly reduced the amount of work that the system had to try to do to parse the bounces to try to figure out which recipient(s) it was in relation to. If you throw a content scanning system into that mix, most of the content of each of those mailing list messages will be the same, so depending on how that content scanning system is configured, it shouldn't be that much more expensive to process 100 virtually identical messages as it is to process the first message in that group. I guess I will simply move the list server to another computer (and a different network). OTOH, moving the mailing list function to a different server and separating that from the content scanning system is also a good idea, including lots of other reasons. Good luck, and I hope that this works out for you. -- Brad Knowles b...@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@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/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
