[Mailman-Users] Help
Please can someone help me? I have set a distribution list using mailman and my isp. I have set the replies to poster, but the whole list is receiving the replies, and it is annoying members of the list. Please people have discussed the confidentially issue. Kind Regards Mark -- 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] Help
Hello! On Fri, Oct 28, 2005 at 08:53:03AM +0100, Mark.A.Lombardo wrote: Please can someone help me? I have set a distribution list using mailman and my isp. I have set the replies to poster, but the whole list is receiving the replies, and it is annoying members of the list. Please people have discussed the confidentially issue. Two words: User education. And set the reply-to header setting appropriately (i.e. do *not* set reply-to to the list), if you usually want direct replies to poster. Oh I read you have already done that. Then... User education (they should use the reply to sender function, not group reply or list reply in their MUA if they want their replies to be private). If they aren't supposed at all to send to the list, deny them the right to do so (possible on the web interface). Or set the list to moderated. Kind Regards Mark Kind regards, Hannah. -- 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] Help
MUA = ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] n.org] On Behalf Of Hannah Schroeter Sent: 28 October 2005 10:39 To: mailman-users@python.org Subject: Re: [Mailman-Users] Help Hello! On Fri, Oct 28, 2005 at 08:53:03AM +0100, Mark.A.Lombardo wrote: Please can someone help me? I have set a distribution list using mailman and my isp. I have set the replies to poster, but the whole list is receiving the replies, and it is annoying members of the list. Please people have discussed the confidentially issue. Two words: User education. And set the reply-to header setting appropriately (i.e. do *not* set reply-to to the list), if you usually want direct replies to poster. Oh I read you have already done that. Then... User education (they should use the reply to sender function, not group reply or list reply in their MUA if they want their replies to be private). If they aren't supposed at all to send to the list, deny them the right to do so (possible on the web interface). Or set the list to moderated. Kind Regards Mark Kind regards, Hannah. -- 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/mark.a.lombardo%40olney -scout-group.org.uk 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] Help
Hello! On Fri, Oct 28, 2005 at 12:40:14PM +0100, Mark.A.Lombardo wrote: MUA = ? Mail user agent. Kind regards, Hannah. -- 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] Help
Hello! On Fri, Oct 28, 2005 at 12:39:27PM +0100, Mark.A.Lombardo wrote: It they hit reply, it is redirecting the email to the list, this should not be the case. I have set the option to poster, so why does it post to the list. Perhaps the original poster set reply-to to the list address. The setting poster does just not add an own reply to, but it leaves original reply-to headers alone, AFAIK. Kind regards, Hannah. -- 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] Help
Hello, Please for novices around her don't use jargon. I sent the original message, and the message stating reply to poster. Kind Regards Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] n.org] On Behalf Of Hannah Schroeter Sent: 28 October 2005 12:51 To: mailman-users@python.org Subject: Re: [Mailman-Users] Help Hello! On Fri, Oct 28, 2005 at 12:39:27PM +0100, Mark.A.Lombardo wrote: It they hit reply, it is redirecting the email to the list, this should not be the case. I have set the option to poster, so why does it post to the list. Perhaps the original poster set reply-to to the list address. The setting poster does just not add an own reply to, but it leaves original reply-to headers alone, AFAIK. Kind regards, Hannah. -- 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/mark.a.lombardo%40olney -scout-group.org.uk 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] Help
Hi Hannah, I apologise for my comments earlier on. I am getting very little support from my service provider on this issue. I am getting complaints from users of the list. As far as I was aware I had set it up, so what ever reply they hit it will direct the reply to the poster, and not to the list. Kind Regards Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] n.org] On Behalf Of Hannah Schroeter Sent: 28 October 2005 13:24 To: Mark.A.Lombardo Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Help Hello! On Fri, Oct 28, 2005 at 01:11:34PM +0100, Mark.A.Lombardo wrote: Hello, Please for novices around her don't use jargon. You get what you pay for. And I think one can expect for people to educate themselves. [...] Kind regards, Hannah - slightly annoyed by that attitude of entitlement. -- 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/mark.a.lombardo%40olney -scout-group.org.uk 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] Having mailman treat two domains as equal during migration...
On Fri, 2005-10-28 at 09:30 -0600, Mike Cisar wrote: At this point the mail server is configured to respond to both domains, and treat them as the same. Mailman itself is configured to use the new domain both on the web side, and all the lists have been changed to use that as their preferred domain. However the problem arises with the list subscribers themselves. We can't simply export the membership for the lists and change everyone to the new domain because everyone won't be sending with the new addresses at once. In the worst case scenario we could export the list make the changes and reimport with nomail set so that everyone has a duplicate membership, and then remove the old domain accounts once the conversion is complete. I'd prefer to save this as a last resort at this point as it is kind of messy. What I would like to do is do a one-shot conversion of all the users to the new domain name and then internally to mailman, when the message is first submitted into the mailman process simply have a regex replacement of the sender's domain name so even though the message might actually be coming from [EMAIL PROTECTED] mailman would read that in, do a quick replace in its mind and for the rest of the process treat the message as if it had come from [EMAIL PROTECTED] Why involve mailman? Why not use either the alias feature or the address rewriting feature of your MTA? But don't you have a larger problem? If the user is still using his old address and thus receiving mail at his old address and you change his address to the new domain when mailman sends the mail to the list then how is somebody going to respond to that user? It's going to go to the new address right where he won't see it (or were you planning on aliasing these as well?). -- John Dennis [EMAIL PROTECTED] -- 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] Having mailman treat two domains as equal duringmigration...
Mike Cisar wrote: What I would like to do is do a one-shot conversion of all the users to the new domain name and then internally to mailman, when the message is first submitted into the mailman process simply have a regex replacement of the sender's domain name so even though the message might actually be coming from [EMAIL PROTECTED] mailman would read that in, do a quick replace in its mind and for the rest of the process treat the message as if it had come from [EMAIL PROTECTED] I am assuming that this should pretty much be a 'one-liner' code modification to mailman. Pardon my Perl (I'm not a native Pythoner so that doesn't help matters :-) but the equivalent of sender =~ s/olddomain/newdomain/ immediately after mailman parses 'sender' from the incoming message. I don't really grok how the message flows through the internals of Mailman... so the couple of places I've tried putting the 'one-liner' don't seem to have any effect. I'm assuming that this should be done literally as soon as possible after Mailman has received the message from the MTA to ensure that the substitution is used in all possible processes? I'm hoping someone on the list may be able to tell me if this a) is really a one-liner and b) roughly where to look at inserting the 'one-liner' in order to acchieve the required result. Well, maybe a two liner :) Aside -- Actually, John Dennis' reply suggesting rewriting the address in the MTA is a good one. The way I read your original, his concern about replies is not relevant as I think you said the users already receive mail addressed to either domain. In spite of my agreement that John's suggestion is probably best, there is one small caveat. If you have USE_ENVELOPE_SENDER = Yes in mm_cfg.py, you'll have to rewrite the envelope sender too, and I don't know if you can do that. In any case, I'd already written most of the following before I saw John's reply, so rather than let it go to waste ... :) End aside --- It depends on what the desired result is. I'm not clear on whether you want to actually change the domain in the From: and maybe elsewhere in the message so when the message from [EMAIL PROTECTED] goes out, it is From: [EMAIL PROTECTED], or if you just want [EMAIL PROTECTED] to be considered equivalent to [EMAIL PROTECTED] for the purpose of validating list membership for posting. The easy one is the latter, so for that I would look at Mailman/Message.py in the get_sender() and get_senders() methods. In get_sender(), I would do the replacement in 'address' just before if not preserve_case: return address.lower() return address In get_senders(), I would again do it to 'address' in this loop where the dots are for pair in pairs: address = pair[1] ... if address is not None and not preserve_case: address = address.lower() authors.append(address) This will also cause other messages (e.g. auotoresponses and your message awaits approval) to go to the new domain, but I gather that is not a problem. If you want to do the former (rewrite the headers), I suggest one of two things. Do it in the first handler in the pipeline which is Mailman/Handlers/SpamDetect.py, or make a new handler (e.g. Mailman/Handlers/MungDomain.py) to do it and insert the new handler at the beginning of the pipeline with something like GLOBAL_PIPELINE.insert(0, 'MungDomain') in mm_cfg.py. This won't work for any list which has a 'pipeline' attribute, but that is rare. -- 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] Help
Mark.A.Lombardo wrote: As far as I was aware I had set it up, so what ever reply they hit it will direct the reply to the poster, and not to the list. The only way to do this is to enable Full Personalization for the list which you may not be able to do (It requires that the Mailman installation have OWNERS_CAN_ENABLE_PERSONALIZATION set to Yes), or to post with the list address as a Bcc:. Otherwise, the list posting address will be in the To: or Cc: of the received post and 'reply all' will include it. To post with the list in Bcc: you need to turn off require_explicit_destination on Privacy options...-Recipient filters or post with an Approved: header, or the post will be held for approval. -- 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] Help
Hi Mark, I am totally confused, can you explain this please? Where are replies to list messages directed? Poster is strongly recommended for most mailing lists. Poster This list Explicit address Please can you explain this bit, for me, if this is set to poster, why does everyone get the reply. Mark -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: 28 October 2005 18:04 To: Mark.A.Lombardo; 'Hannah Schroeter' Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Help Mark.A.Lombardo wrote: As far as I was aware I had set it up, so what ever reply they hit it will direct the reply to the poster, and not to the list. The only way to do this is to enable Full Personalization for the list which you may not be able to do (It requires that the Mailman installation have OWNERS_CAN_ENABLE_PERSONALIZATION set to Yes), or to post with the list address as a Bcc:. Otherwise, the list posting address will be in the To: or Cc: of the received post and 'reply all' will include it. To post with the list in Bcc: you need to turn off require_explicit_destination on Privacy options...-Recipient filters or post with an Approved: header, or the post will be held for approval. -- 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] Help
Mark.A.Lombardo wrote: I am totally confused, can you explain this please? Where are replies to list messages directed? Poster is strongly recommended for most mailing lists. Poster This list Explicit address Please can you explain this bit, for me, if this is set to poster, why does everyone get the reply. When a user tells his/her MUA (mail reader, email client) to 'reply' to the current message, the MUA is supposed to direct the reply to the address(es) in the Reply-To: header if any or to the address in From: if there is no Reply-To:. If the above is set to 'poster', Mailman makes no change to the From: or Reply-To: header of the message. If the above is set to 'this list' Mailman adds the list posting address to the addresses in the existing Reply-To: header if any and if first_strip_reply_to is No. Otherwise it just makes a Reply-To: with the list posting address. If the above is set to 'explicit address', it works like 'this list' except the address used is the address in reply_to_address instead of the list posting address. So, if the user tells the MUA to 'reply', it will generally work as you expect for any of the three cases. However, if the user tells the MUA to 'reply all', the MUA normally directs the reply as in the 'reply' case, but also adds every address in the To: and Cc: headers of the current message to the recipients of the 'reply all' Thus, if a user does 'reply all' to a post and the list posting address is in the To: or Cc: of the post, the reply will be sent to the list posting address as well as the poster and other addressees of the original message. If you don't want this, and you DO want to allow list members in general to post, then you have to arrange for the list posting address to NOT appear in the To: or Cc: headers of the posts which you CAN NOT do. I said in a prior post that Full Personalization, if you can enable it, can do this by replacing the To: address with the recipient's address, BUT this won't do for you because it also puts the list posting address in Cc: in order to falicate the ability to reply to the list if the user wants to. If you really do not want users to have the ability to reply to the list at all, as opposed to just when they do a simple 'reply' you have to set up the list as a one-way/announcement/newsletter list as described in the FAQ. You basically have two choices: 1) set reply_goes_to_list to Poster and teach your list members to use 'reply' to reply to the poster and 'reply all' to reply to the poster and the list. 2) prevent your list members from posting at all by setting up the list as described in the FAQ. At the risk of flogging a dead horse, you can't PREVENT your users from addressing replies to the list, you can only try to teach them not to or set up the list to not accept any posts from general list members. -- 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
[Mailman-Users] Google and other search engines
Other than setting the archives to private are the any other recommended methods of preventing these Bots from accessing the list archives? Jack -- 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] Help
Mark Sapiro wrote: If you don't want this, and you DO want to allow list members in general to post, then you have to arrange for the list posting address to NOT appear in the To: or Cc: headers of the posts which you CAN NOT do. Not quite correct. You can post by addressing the list in Bcc:, but if you're allowing general list members to post, they won't do it. -- 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] Having mailman treat two domains as equal duringmigration...
Hi Mark, I'm hoping someone on the list may be able to tell me if this a) is really a one-liner and b) roughly where to look at inserting the 'one-liner' in order to acchieve the required result. Well, maybe a two liner :) Aside -- Actually, John Dennis' reply suggesting rewriting the address in the MTA is a good one. The way I read your original, his concern about replies is not relevant as I think you said the users already receive mail addressed to either domain. Yes it's a sendmail configuration and it has actually been reconfigured completely as the new domain with an alias for the old domain, so if users are receiving mail to either address it ends up in the same mailbox. Rewriting in the MTA is definitely something I had not thought of, but your two-liner looks much easier ;-) Rule #1 in configuring sendmail... if it's working don't touch it :-) From: [EMAIL PROTECTED], or if you just want [EMAIL PROTECTED] to be considered equivalent to [EMAIL PROTECTED] for the purpose of validating list membership for posting. That's it, that's the one :-) Basically all of the user memberships will be converted for the new domain, and we just don't want posts to get held for the people who are 'less than prompt' in reconfiguring their email clients during the transition. The easy one is the latter, so for that I would look at Mailman/Message.py in the get_sender() and get_senders() methods. In get_sender(), I would do the replacement in 'address' just before snip This will also cause other messages (e.g. auotoresponses and your message awaits approval) to go to the new domain, but I gather that is not a problem. Will give this a try and see how it goes :-) Cheers, Mike -- 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] Help
I must be coming across as really thick and stupid. If I have set the tag to reply to poster, and I hit reply, then there is no way of mailman knowing which email address that came from So in simple terms, if I put up a subject on the mailing list and I don't want people to reply, it is better to put the email address in the bcc field. How do I set that the reply only comes to the person that posted the mail, and not the list, I thought setting the reply to poster it would only send the mal to the person who posted, and not the rest of the list. Is this not correct? If this is not correct, then I am confused, because that is the way it reads. If I set reply is sent to an explicit email address (ie mine), then if someone replies to an email I have sent to the list, it will send the reply to me. So what happens if someone wants to reply to the whole list, and not just me, and I have the explicit email address set. It must seems as though I am totally thick. Mark -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: 28 October 2005 19:07 To: Mark.A.Lombardo Cc: mailman-users@python.org Subject: RE: [Mailman-Users] Help Mark.A.Lombardo wrote: I am totally confused, can you explain this please? Where are replies to list messages directed? Poster is strongly recommended for most mailing lists. Poster This list Explicit address Please can you explain this bit, for me, if this is set to poster, why does everyone get the reply. When a user tells his/her MUA (mail reader, email client) to 'reply' to the current message, the MUA is supposed to direct the reply to the address(es) in the Reply-To: header if any or to the address in From: if there is no Reply-To:. If the above is set to 'poster', Mailman makes no change to the From: or Reply-To: header of the message. If the above is set to 'this list' Mailman adds the list posting address to the addresses in the existing Reply-To: header if any and if first_strip_reply_to is No. Otherwise it just makes a Reply-To: with the list posting address. If the above is set to 'explicit address', it works like 'this list' except the address used is the address in reply_to_address instead of the list posting address. So, if the user tells the MUA to 'reply', it will generally work as you expect for any of the three cases. However, if the user tells the MUA to 'reply all', the MUA normally directs the reply as in the 'reply' case, but also adds every address in the To: and Cc: headers of the current message to the recipients of the 'reply all' Thus, if a user does 'reply all' to a post and the list posting address is in the To: or Cc: of the post, the reply will be sent to the list posting address as well as the poster and other addressees of the original message. If you don't want this, and you DO want to allow list members in general to post, then you have to arrange for the list posting address to NOT appear in the To: or Cc: headers of the posts which you CAN NOT do. I said in a prior post that Full Personalization, if you can enable it, can do this by replacing the To: address with the recipient's address, BUT this won't do for you because it also puts the list posting address in Cc: in order to falicate the ability to reply to the list if the user wants to. If you really do not want users to have the ability to reply to the list at all, as opposed to just when they do a simple 'reply' you have to set up the list as a one-way/announcement/newsletter list as described in the FAQ. You basically have two choices: 1) set reply_goes_to_list to Poster and teach your list members to use 'reply' to reply to the poster and 'reply all' to reply to the poster and the list. 2) prevent your list members from posting at all by setting up the list as described in the FAQ. At the risk of flogging a dead horse, you can't PREVENT your users from addressing replies to the list, you can only try to teach them not to or set up the list to not accept any posts from general list members. -- 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] Google and other search engines
Mark Sapiro wrote: 2)You can configure your web server to add a Robots: noindex,nofollow header when it delivers the pages. 3)You can edit the various arch*.html and article.html templates to add a META NAME=ROBOTS CONTENT=NOINDEX,NOFOLLOW tag. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.048.htp for editing instructions. 2) is better than 3), if you do 2) you don't need 3). 1) never hurts. Actually, I googled a bit and now it is not clear to me that 2) is better than 3) or even if 2) works at all. Maybe someone else knows. In any case, except for the additional effort to set it up, it won't hurt to do both. -- 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] A non-text attachment was scrubbed... -- URL break
On Fri, Sep 02, 2005 at 16:39:01, Mark Sapiro wrote:
Hi,
I'm seeing the same thing. It works OK as long as the body of the
message is us-ascii, but if it contains characters like æøå
(iso-8859-1) the message is printed in the archive as quoted printables
(litteraly) and the link is mangled like reported by the OP.
The message is sent fine to the list, _unless_ msg_footer is empty. If
it is empty the message mailed to list also contains quoted printables.
(If scrub_nondigest is set to no, archiving works perfectly fine with
iso-8559-1 characters)
Anyone else seen this?
Lars
Tim Willson wrote:
If I set Non-digest options/Scrub attachments of regular delivery message?
to Yes my archived messages URL's have an extra = in the URL string at the
end of line one and a line break making the URL 2 lines and non-clickable.
snip
-- next part --
A non-text attachment was scrubbed...
Name: Official notice Spam Filtering Implementation Update 09030.pdf Type:
application/octet-stream Size: 76382 bytes
Desc: not available
Url : http://www.mn.us/pipermail/listname/attachments/20050901/2d8=
eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
This was at some point a quoted-printable encoding. I don't know where
the '' at the end of the first line came from, but in
quoted-printable speak the '=' at the end of the first line of
Url : http://www.mn.us/pipermail/listname/attachments/20050901/2d8=
eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
means there is really no line-break here - join this line to the next.
I've looked at Mailman/Handlers/Scrubber.py, and it doesn't put angle
brackets ('', '') around the urls. I don't know where they are
coming from, but I don't think Mailman is doing it.
Likewise, Scrubber.py does not produce a quoted-printable encoded
message. It produces a message with Content-Transfer-Encoding: 8bit.
So it looks like somewhere in the outgoing MTA path, an MTA is
converting 8bit to quoted-printable which is changing
Url :
http://www.mn.us/pipermail/listname/attachments/20050901/2d8eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
to
Url : http://www.mn.us/pipermail/listname/attachments/20050901/2d8=
eb35e/OfficialnoticeSpamFilteringUpdate09030.pdf
and then somewhere further along, something is not correctly
interpreting the quoted-printable encoding - perhaps the thing which
is putting the angle brackets around the
http://www.mn.us/pipermail/listname/attachments/20050901/2d8= part.
--
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/lsa%40business.auc.dk
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Lars Anderson E-mail: [EMAIL PROTECTED]
Faculty of Social Sciences Jabber: [EMAIL PROTECTED]
Aalborg University Voice: +45 96358225, Fax: +45 98153505
DenmarkOffice: Fib4-117
--
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] add_members and email confirmation
Thanks very much to John for his advice on this. I've implemented it, and am now facing a slightly different problem. For those just tuning in, I'm using MM 2.1.5 and trying to add new list subscribers via the command line (so users don't see the default MM templates and I have control over the UI). I started off by using PHP to call add_members, which successfully subscribes a user. It goes like this: [EMAIL PROTECTED] echo [EMAIL PROTECTED] | add_members -r - LISTNAME I have to use echo because add_members only reads from files or standard input, but otherwise it works wonderfully. The trouble is that no confirmation is sent to the subscriber. John Dennis pointed out that add_members could be copied and hacked so that instead of calling ApprovedAddMember (which doesn't send a confirmation), I could call AddMember (which should generate a confirmation). So I created a modified add_members and swapped this line: mlist.ApprovedAddMember(userdesc, ack, 0) with this one: mlist.AddMember(userdesc, remote=Webpage) Running the new script on the command line generates this: [EMAIL PROTECTED] echo [EMAIL PROTECTED] | MODIFIED_add_members -r - LISTNAME Traceback (most recent call last): File /usr/lib/mailman/bin/MODIFIED_add_members, line 255, in ? main() File /usr/lib/mailman/bin/MODIFIED_add_members, line 235, in main addall(mlist, nmembers, 0, send_welcome_msg, s) File /usr/lib/mailman/bin/MODIFIED_add_members, line 135, in addall mlist.AddMember(userdesc, remote=Webpage) File /usr/lib/mailman/Mailman/MailList.py, line 888, in AddMember raise Errors.MMSubscribeNeedsConfirmation MMSubscribeNeedsConfirmation Strangest of all, a confirmation message *is* generated and sent to the email address, but clicking on the confirmation link just sends me to a MM error page. I'm at a loss as to what the problem might be. Thanks to anyone who made it this far. And quadruple thanks to anyone who can help. I appreciate it! -Ren On Oct 21, 2005, at 2:41 PM, John Dennis wrote: On Fri, 2005-10-21 at 14:23 -0400, Ren Bucholz wrote: Hello, I have a signup sheet that subscribes people to a Mailman list by using PHP to call add_members (the PHP is below, FYI). My problem is that add_members seems to ignore the email confirmation settings from the admin interface. Even though my list is configured to send a confirmation message, subscribers only get the Thanks for signing up! email. Does anyone know of a way to use add_members in a confirmed-opt-in list? Thanks very much! Not is its current manifestation. The reason is that manual adding of members assumes this is an approved action. You have two choices: 1) redirect them to the signup page for the list (this has the advantage of allowing the user to set some preferences and see some basic info). 2) Copy the add_members script to a new name and edit it so that it calls AddMember instead of AddApprovedMember. See Mailman/Cgi subscribe.py for an example of how to do this and the various exceptions you'll have to catch and handle. -- John Dennis [EMAIL PROTECTED] -- 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] Help
Mark.A.Lombardo wrote: I must be coming across as really thick and stupid. If I have set the tag to reply to poster, and I hit reply, then there is no way of mailman knowing which email address that came from I'm not sure what you mean by this, but Mailman is not really involved here other than perhaps setting a Reply-To: address. It's you and your MUA (Outlook in your case) that decides where the reply/reply-all goes. Consider this post of yours to the Mailman-Users list. The Mailman-Users list is set up with 'reply to poster'. I think you generated your post by some kind of 'reply-all' to my post. I think this because your post has an In-Reply-To: header with the message id of my post. It is addressed to me with a Cc: to the list, so unless you just 'replied' to me and manually added the Cc: to the list, the Cc: was added by the 'reply all'. Further evidence of your use of 'reply-all' is the fact that Hannah was addressed explicitly in your initial reply to a message from me, presumably because she was explicitly addressed in my message and you did 'reply-all'. So anyway, I think you did 'reply-all' to my post, and the reply came to me with Cc: to the list because my previous post had Cc: to the list. So in simple terms, if I put up a subject on the mailing list and I don't want people to reply, it is better to put the email address in the bcc field. Do you want people to be able to reply to the list in general, and just not to this post, or do you want them to never reply to the list? The answer really depends on that and you've never said. How do I set that the reply only comes to the person that posted the mail, and not the list, I thought setting the reply to poster it would only send the mal to the person who posted, and not the rest of the list. Is this not correct? This depends on how the person replying does the actual replying. If the actual reply somehow reaches the list posting address, Mailman doesn't care how it got there or whether it was a reply to some prior post; it treats the post as any other from that sender. If this is not correct, then I am confused, because that is the way it reads. The configuration option only governs where a simple reply to sender only will go - nothing else - and it does this through the content of headers in the message only, not through any enforcement on a received reply. If I set reply is sent to an explicit email address (ie mine), then if someone replies to an email I have sent to the list, it will send the reply to me. It will actually be exactly the same as the reply to poster case if you are the original poster. It's only different if someone else sent the original post. So what happens if someone wants to reply to the whole list, and not just me, and I have the explicit email address set. They do reply all, and the reply is addressed to the list and to the explicit reply-to address and to any other addresses that were in the To: an Cc: of the received post (except perhaps their own). -- 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] Having mailman treat two domains as equal duringmigration...
It's Friday afternoon so forgive me a little tongue-n-cheek humor :-) On Fri, 2005-10-28 at 12:54 -0600, Mike Cisar wrote: Rule #1 in configuring sendmail... if it's working don't touch it :-) Corollary #1 follows from Rule #1: sendmail configuration is so painful it can't be changed readily. Thus Rule #2 follows from Corollary #1: Don't use sendmail :-) -- John Dennis [EMAIL PROTECTED] -- 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] add_members and email confirmation
Ren Bucholz wrote:
So I created a
modified add_members and swapped this line:
mlist.ApprovedAddMember(userdesc, ack, 0)
with this one:
mlist.AddMember(userdesc, remote=Webpage)
Running the new script on the command line generates this:
[EMAIL PROTECTED] echo [EMAIL PROTECTED] | MODIFIED_add_members -r - LISTNAME
Traceback (most recent call last):
File /usr/lib/mailman/bin/MODIFIED_add_members, line 255, in ?
main()
File /usr/lib/mailman/bin/MODIFIED_add_members, line 235, in main
addall(mlist, nmembers, 0, send_welcome_msg, s)
File /usr/lib/mailman/bin/MODIFIED_add_members, line 135, in addall
mlist.AddMember(userdesc, remote=Webpage)
File /usr/lib/mailman/Mailman/MailList.py, line 888, in AddMember
raise Errors.MMSubscribeNeedsConfirmation
MMSubscribeNeedsConfirmation
Strangest of all, a confirmation message *is* generated and sent to the
email address, but clicking on the confirmation link just sends me to a
MM error page. I'm at a loss as to what the problem might be.
The problem is that AddMember generates the pending subscription, the
cookie and the confirmation email and then raises
Errors.MMSubscribeNeedsConfirmation so the caller (generally,
Mailman/Cgi/subscribe.py) can catch the exception and generate the
appropriate response text. The add_members script doesn't catch this
exception, so you get the above error. You can just add
except Errors.MMSubscribeNeedsConfirmation:
print tee, _('Sent Confirmation: %(member)s')
or maybe, if you don't actually see this output, just
except Errors.MMSubscribeNeedsConfirmation:
pass
to the excepts following the try: of the AddMember call. You probably
want to also handle the Errors.MMNeedApproval exception in case you do
this on a list where subscription requires approval.
As to why the confirmation link returned an error, I don't know why
this happened. What does Mailman's error log say?
--
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] Help
One other thing that hasn't been mentioned, but all the answers in this thread apply to replies to non-digest messages. Digests always have Reply-To: the list posting address. -- 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] Help!
Change the length in KB a message is before posting in general to 0 for no limit. If I remember the setting. At 10:55 10/26/2005, you wrote: Hi, We use this software and continue to get the following error message (see below). Is there anything that can be adjusted in order to send larger messages? Also, we can not send messages with attached files. What can we do to rectify this situation? Sincerely, Marlowe Futrell ___ Your mail to 'NAPHAstaff' with the subject FW: [Naphastaff] RE: San Filippo event Is being held until the list moderator can review it for approval. The reason it is being held: Message body is too big: 50802 bytes with a limit of 40 KB Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://napha.org/mailman/confirm/naphastaff_napha.org/72586148b76afd1cdd2af6 ba8e6e4ea8e77e377e Outgoing mail is Virus Scanned byNorman Data Defense.Inbound Spam reduced 98.2% byVircom Sieve. -- 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/jrimer%40tagline.cc Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp Jared Rimer Business website: http://www.superior-software.com/support Personal Website: http://www.asmodean.net/jrimer Music Education Network for the Visually Impaired http://menvi.org a service done through Superior Software level one WBBY Internet Radio and All In Play team up. Learn more http://www.menvi.org/allinplay WBBY Internet Radio: www.wbby.us -- 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] name of my mailing-list adress ...
Hallo, I installed Mailman on my computer. (+ Apache and Postfix) My domain is : rezoperso.net My hostname is : aw.rezoperso.net Everything works fine when I create my mailing-list named : starinux. But how to create the name of The Email adress of the ML starinux ? When I register a new member, all works fine and the Email adress of the ML is : [EMAIL PROTECTED]@aw.rezoperso.net So I send an Email (test) from the new member TO [EMAIL PROTECTED]@aw.rezoperso.net and I receive a error message : undelivered message : [EMAIL PROTECTED]@aw.rezoperso.net error [EMAIL PROTECTED] (expanded from @aw.rezoperso.net): [antoine.rezoperso.net]: Name or service not known So my two questions : 1) How to create a valid Mailing List Email Adress, 2) Does it comme from postfix = /etc/postfix/main.cf file bad configured or from mailman Many thanks for a help and see you. Antoine (i'm not far to succeed ..) -- 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] Attach Pics
Mark Sapiro wrote: David wrote: One more thing. If people are on moderation is there some place to set it that they dont get notification of being moderated and their message is just held without them knowing it. No. If member_moderation_action is hold or reject, the member is notified. Only if member_moderation_action is discard is there no notice. It turns out, I was wrong here. Also, the documentation appears wrong in a different way. The setting is on the list's General Options page and is respond_to_post_requests. The help for this option says Approval notices are sent when mail triggers certain of the limits _except_ routine list moderation and spam filters, for which notices are not sent. This option overrides ever sending the notice. The phrase _except_ routine list moderation and spam filters, for which notices are not sent is not correct in that the only notices that aren't sent are when a message is 'discarded' including for a match on mm_cfg.KNOWN_SPAMMERS or when a message is held because emergency is Yes. Submitters of all held posts regardless of reason except emergency moderation are notified or not depending on the setting of respond_to_post_requests. This includes posts held for routine moderation and posts that match header_filter_rules with a hold action and posts that match bounce_matching_headers. Thus, you can turn off notices to moderated users by setting respond_to_post_requests to No, but you also turn off all other held post notices as well. -- 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] name of my mailing-list adress ...
[EMAIL PROTECTED] wrote: I installed Mailman on my computer. (+ Apache and Postfix) My domain is : rezoperso.net My hostname is : aw.rezoperso.net Everything works fine when I create my mailing-list named : starinux. But how to create the name of The Email adress of the ML starinux ? When I register a new member, all works fine and the Email adress of the ML is : [EMAIL PROTECTED]@aw.rezoperso.net If you look at the General Options page for the list, I think you'll find host_name is '[EMAIL PROTECTED]'. It should not be this. It should probably be just 'aw.rezoperso.net'. If you set this to '[EMAIL PROTECTED]', that is not correct. If it was set that way in the list creation process, your settings for DEFAULT_EMAIL_HOST and maybe DEFAULT_URL_HOST are wrong. So my two questions : 1) How to create a valid Mailing List Email Adress, See above. 2) Does it comme from postfix = /etc/postfix/main.cf file bad configured or from mailman 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] Bounce messages
Ashley M. Kirchner wrote: We'd like to set one of our lists up so that permanent/fatal errors (such as invalid mailbox, unknown user, unknown host) would immediately get unsubscribed, while temp fails (such as mailbox full, try again later, etc.) will simply go through the normal motions. With that, we have a few questions: a) Does mailman discern between a temp fail and a permanent fail on a subscriber's address? Obviously this would be the way to figure out who gets unsubscribed right away and who doesn't. Yes, but not really well. Hard bounces increment the score by 1.0 while soft bounces increment the score by 0.5 b) How do we configure mailman to do this immediate unsub of the permanent/fatal errors? See below: b) in logs/bounce, I see various different bounce scores. Can anyone tell me what those numbers actually mean? Jul 16 23:14:54 2005 (1835) [EMAIL PROTECTED]: list current bounce score: 3.0 Jul 17 05:10:59 2005 (1835) [EMAIL PROTECTED]: list current bounce score: 4.0 Jul 22 10:21:11 2005 (1835) [EMAIL PROTECTED]: list current bounce score: 5.0 Jul 27 12:00:49 2005 (1868) [EMAIL PROTECTED]: list current bounce score: 2.0 Aug 17 06:17:18 2005 (1868) [EMAIL PROTECTED] list current bounce score: 1.0 It is a report of that user's current bounce score. Read the material on the Bounce processing page in the list's admin interface. For configuration try the following bounce processing settings: bounce_processing Yes bounce_score_threshold 1.0 i.e. the first hard bounce hits the threshold, but it takes soft bounces on two days. bounce_info_stale_after 0 but see below. This is the part that may not work well for soft bounces. bounce_you_are_disabled_warnings 0 These settings will cause a member who hard bounces to be unsubscribed immediately (or sent a probe which will cause the unsubscribe if it bounces). The problem is with soft bounces. If you set bounce_info_stale_after to 1 or more, then anyone with soft bounces on two consecutive days (or any two days with less than bounce_info_stale_after days in between) will be immediatly unsubscribed. This seems a little harsh. OTOH, if you set bounce_info_stale_after to 0, soft bounces will never disable/unsubscribe a member because only one bounce is scored per day and yesterday's bounce is always stale. This seems a little lenient, but may in fact be OK -- 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
[Mailman-Users] Setting up an archive list
Hi All This is my first post to the list but I've been lurking for a while. I'm running Mailman 2.1.5 on a debian sarge box with exim 4, apache 1.3 etc. at home. I also have an account with a hosting company which provides mailman 2.1.5 lists and a fairly standard mailman control interface. My home setup runs fine and so far I've had no problems with the couple of test lists set up on the host. What I want to do is to set up a list with the host and forward emails received there to a list on my home system purely to provide a backup archive. For test purposes I'm only using my home setup at the moment. I've created a main list ([EMAIL PROTECTED]) and an archive list ([EMAIL PROTECTED]) and added [EMAIL PROTECTED] to [EMAIL PROTECTED] member list. [EMAIL PROTECTED] has no members but in the privacy options /senderfilters I've added [EMAIL PROTECTED] to the List of non-member addresses whose postings should be automatically accepted section. So far so good. I post to [EMAIL PROTECTED] and the post goes out to all members including [EMAIL PROTECTED] but there it gets held for approval by the list admin (i.e. me). The reason given is: Blind carbon copies or other implicit destinations are not allowed. Try reposting your message by explicitly including the list address in the To: or Cc: fields. I can pass it through to the list manually but would prefer it to go through automatically as I intend to do this several lists. Does anyone have any ideas as to how I can do this. I have access to the python source on my machine so I can modify if need be. Apologies if the detail above is a bit excessive. Cheers Horse -- 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] Bouncing admins
Nark and all, This is all we have. From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Tue, 11 Oct 2005 11:46:54 -0500 X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.6 Sender: [EMAIL PROTECTED] X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - idea5.anoeticconcepts.com X-AntiAbuse: Original Domain - codeamber.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - idea5.anoeticconcepts.com X-Source: X-Source-Args: X-Source-Dir: This is a Mailman mailing list bounce action notice: List: Woodlake_el_school Member: [EMAIL PROTECTED] Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Woodlake_el_school subscription notification From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Date: Tue, 11 Oct 2005 11:46:52 -0500 Precedence: bulk X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.6 Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] bhavsar [EMAIL PROTECTED] has been successfully subscribed to Woodlake_el_school. The address isn't even bouncing on the list. At 16:31 10/28/2005, you wrote: Jared Rimer wrote: I'm running on a domain of mine that has Mailman installed. The hosting provider moved the account to another server he runs. Ever since, the notify when subscribers added has not worked correctly. We've received bounce notifications disabling the one admin because of too many bounces, but the subscription is not disabled. How does mailman handle this? The fact that a bouncing address happens to be the address of an Owner or Moderator is not relevant to Mailman's bounce processing. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.060.htp As far as the notices of new subscribers and the disabling is concerned, it seems that mailman can't successfully mail to the owner address or to the matching member address. What does the copy of the bounce in the disable notification say? And where do you receive it? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Jared Rimer Business website: http://www.superior-software.com/support Personal Website: http://www.asmodean.net/jrimer Music Education Network for the Visually Impaired http://menvi.org a service done through Superior Software level one WBBY Internet Radio and All In Play team up. Learn more http://www.menvi.org/allinplay WBBY Internet Radio: www.wbby.us -- 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] Setting up an archive list
Horse wrote: I post to [EMAIL PROTECTED] and the post goes out to all members including [EMAIL PROTECTED] but there it gets held for approval by the list admin (i.e. me). The reason given is: Blind carbon copies or other implicit destinations are not allowed. Try reposting your message by explicitly including the list address in the To: or Cc: fields. In the list configuration for the archive list on, Privacy options...-Recipient filters, put [EMAIL PROTECTED] in acceptable_aliases. You could also just set require_explicit_destination Off, but the alias is better. Also, on the subscription options for the [EMAIL PROTECTED] subscription to the main list, be sure to set Get password reminder email for this list? to No. -- 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] Setting up an archive list
Horse, Go to privacy, I don't remember if its sender or recipient and turn off implicit destination. At 17:08 10/28/2005, you wrote: Hi All This is my first post to the list but I've been lurking for a while. I'm running Mailman 2.1.5 on a debian sarge box with exim 4, apache 1.3 etc. at home. I also have an account with a hosting company which provides mailman 2.1.5 lists and a fairly standard mailman control interface. My home setup runs fine and so far I've had no problems with the couple of test lists set up on the host. What I want to do is to set up a list with the host and forward emails received there to a list on my home system purely to provide a backup archive. For test purposes I'm only using my home setup at the moment. I've created a main list ([EMAIL PROTECTED]) and an archive list ([EMAIL PROTECTED]) and added [EMAIL PROTECTED] to [EMAIL PROTECTED] member list. [EMAIL PROTECTED] has no members but in the privacy options /senderfilters I've added [EMAIL PROTECTED] to the List of non-member addresses whose postings should be automatically accepted section. So far so good. I post to [EMAIL PROTECTED] and the post goes out to all members including [EMAIL PROTECTED] but there it gets held for approval by the list admin (i.e. me). The reason given is: Blind carbon copies or other implicit destinations are not allowed. Try reposting your message by explicitly including the list address in the To: or Cc: fields. I can pass it through to the list manually but would prefer it to go through automatically as I intend to do this several lists. Does anyone have any ideas as to how I can do this. I have access to the python source on my machine so I can modify if need be. Apologies if the detail above is a bit excessive. Cheers Horse -- 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/jrimer%40tagline.cc Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp Jared Rimer Business website: http://www.superior-software.com/support Personal Website: http://www.asmodean.net/jrimer Music Education Network for the Visually Impaired http://menvi.org a service done through Superior Software level one WBBY Internet Radio and All In Play team up. Learn more http://www.menvi.org/allinplay WBBY Internet Radio: www.wbby.us -- 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] Bouncing admins
Jared Rimer wrote: Nark and all, This is all we have. From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Tue, 11 Oct 2005 11:46:54 -0500 X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.6 Sender: [EMAIL PROTECTED] X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - idea5.anoeticconcepts.com X-AntiAbuse: Original Domain - codeamber.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - idea5.anoeticconcepts.com X-Source: X-Source-Args: X-Source-Dir: This is a Mailman mailing list bounce action notice: List: Woodlake_el_school Member: [EMAIL PROTECTED] Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Woodlake_el_school subscription notification From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Date: Tue, 11 Oct 2005 11:46:52 -0500 Precedence: bulk X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.6 Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] bhavsar [EMAIL PROTECTED] has been successfully subscribed to Woodlake_el_school. This message looks very suspicious (i.e.faked). What do you see in Eudora if you open the message and click 'Blah Blah Blah' to see ALL the headers. The alleged triggering bounce is not a bounce at all, but a copy of a subscribe notification. The address isn't even bouncing on the list. All the more reason to think the message is a fake since the subscription wasn't disabled. -- 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] Bouncing admins
I don't have my copy any more, but this has been the problem since we've moved. Shall I re-enable the option to send notifications and when I get another one send it to the list? At 17:51 10/28/2005, you wrote: Jared Rimer wrote: Nark and all, This is all we have. From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Tue, 11 Oct 2005 11:46:54 -0500 X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.6 Sender: [EMAIL PROTECTED] X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - idea5.anoeticconcepts.com X-AntiAbuse: Original Domain - codeamber.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - idea5.anoeticconcepts.com X-Source: X-Source-Args: X-Source-Dir: This is a Mailman mailing list bounce action notice: List: Woodlake_el_school Member: [EMAIL PROTECTED] Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Woodlake_el_school subscription notification From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Date: Tue, 11 Oct 2005 11:46:52 -0500 Precedence: bulk X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.6 Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] bhavsar [EMAIL PROTECTED] has been successfully subscribed to Woodlake_el_school. This message looks very suspicious (i.e.faked). What do you see in Eudora if you open the message and click 'Blah Blah Blah' to see ALL the headers. The alleged triggering bounce is not a bounce at all, but a copy of a subscribe notification. The address isn't even bouncing on the list. All the more reason to think the message is a fake since the subscription wasn't disabled. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Jared Rimer Business website: http://www.superior-software.com/support Personal Website: http://www.asmodean.net/jrimer Music Education Network for the Visually Impaired http://menvi.org a service done through Superior Software level one WBBY Internet Radio and All In Play team up. Learn more http://www.menvi.org/allinplay WBBY Internet Radio: www.wbby.us -- 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] Bouncing admins
Jared Rimer wrote: I don't have my copy any more, but this has been the problem since we've moved. Shall I re-enable the option to send notifications and when I get another one send it to the list? You can do that. If you're willing to experiment, answers to the following questions would be interesting and helpful. What does the full 'bounce action notice' look like, complete with all headers and attached parts? How often does this occur? Is the subscription really disabled (I think you said no)? What happens if bounce processing is turned off for the list? If you have access to Mailman's bounce log, what's there associated with this address? I guess it is possible that there is some wierd alias loop causing this, but I can't think how. I only say that because the member's user name is apparently the same as the list name although the domains are different. -- 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] Bouncing admins
At 18:23 10/28/2005, you wrote: Jared Rimer wrote: I don't have my copy any more, but this has been the problem since we've moved. Shall I re-enable the option to send notifications and when I get another one send it to the list? You can do that. If you're willing to experiment, answers to the following questions would be interesting and helpful. What does the full 'bounce action notice' look like, complete with all headers and attached parts? That's all there is, I'll have to get a copy to show you anything else new. How often does this occur? Maybe once a week or two since this occurred. Is the subscription really disabled (I think you said no)? No, the subscription is not disabled. What happens if bounce processing is turned off for the list? I don't think we'd get bounces that were lidigament if address were inactive or something no? If you have access to Mailman's bounce log, what's there associated with this address? That I don't we're running under Cpannel. I guess it is possible that there is some wierd alias loop causing this, but I can't think how. I only say that because the member's user name is apparently the same as the list name although the domains are different. Then why isn't my address bounce? We have changed addresses in the past, the hotmail address bounced with the same as before. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Jared Rimer Business website: http://www.superior-software.com/support Personal Website: http://www.asmodean.net/jrimer Music Education Network for the Visually Impaired http://menvi.org a service done through Superior Software level one WBBY Internet Radio and All In Play team up. Learn more http://www.menvi.org/allinplay WBBY Internet Radio: www.wbby.us -- 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] A non-text attachment was scrubbed... -- URLbreak
Lars Anderson wrote: I'm seeing the same thing. It works OK as long as the body of the message is us-ascii, but if it contains characters like æøå (iso-8859-1) the message is printed in the archive as quoted printables (litteraly) and the link is mangled like reported by the OP. The message is sent fine to the list, _unless_ msg_footer is empty. If it is empty the message mailed to list also contains quoted printables. (If scrub_nondigest is set to no, archiving works perfectly fine with iso-8559-1 characters) I see it too on a test system with Mailman 2.1.6. Thanks to your description of the triggering conditions, I can duplicate the problem. It will be a few days before I have time to look at this further, but I'll report what I find to the list. -- 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
