Re: [Mailman-Users] X-SPAM-FILTER problems
Excellent thanks, I'll upgrade and check it out. Mark Sapiro wrote: martin moriarty wrote: We run Mailman Version 2.1.5. Ive added in spam filter rules/expression: X-SPAM-FLAG:YES . Seems to work for a while, then stops working. This is a bug in 2.1.5, partially fixed in 2.1.6 and completely fixed in 2.1.7. See http://sourceforge.net/tracker/index.php?func=detailaid=1230865group_id=103atid=100103. The problem is updating any of the other Privacy options... pages, loses header_filter_rules. -- 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] Re-enabling users who exceed the bouncethreshold
At 9:05 AM -0700 10/4/06, Mark Sapiro wrote: Now this may well be a coincidence, but it is also possible that att.net had a DNS reverse lookup error at the beginning and blocked the IP. Then each subsequent mail found a 'cached' block and was itself blocked and also updated the cache expiration. When I stopped sending for over a week, the cached entry finally expired. This is conjecture and may not be correct, but I think it is not necessarily a good idea to keep reenabling bounces like this. There are plenty of places out there that run seriously screwed-up nameservers, and cache data in direct violation of the TTLs specified on the records, or do various other strange things. It's also possible that you were running afoul of a firewall/network abuse rule, and by continually re-enabling those users you kept tripping that rule -- and resetting whatever auto-timeout they may have put on it. By letting those users sit for a while, the rule ended up getting dropped and then when you re-enabled them later, you no longer had this problem. I've seen automated network intrusion detection systems do this sort of thing. One thing in common with both of these explanations is that the larger the recipient site, the more likely they are to be doing strange and bizarre things behind the scenes in order to deal with a wide variety of problems that you will probably never even have heard of, and when they do those kinds of things they are much more likely to have strange and bizarre side-effects -- which they frequently won't even know about themselves, and even if they do know about them they will almost certainly never discuss them with any outside party. Cisco PIX firewalls used to break the SMTP protocol by default, when you enabled their SMTP proxy implementation. People would do this to try to gain a measure of security-through-obscurity, but all that would really do is tell the whole world that their clueless mail/firewall administrators don't care about breaking SMTP e-mail to the world, and that they're using piss-poor Cisco PIX firewall crap to do it. But they would never admit anything about what they were doing, and would violently refuse to accept any blame for any mail breakage problems that they caused. Strangely enough, once someone pointed them at the specific piece of the Cisco documentation that showed precisely what they were doing wrong with precisely which stupid piece of equipment and then how to fix that damn configuration problem, things would mysteriously start working again -- but again without any kind of acknowledgement as to what idiot had broken the thing or why it had taken them so long to fix the thing that we all knew that they had broken (and how they had broken it). Cisco PIX firewalls can still break SMTP e-mail in this way, but at least they're not configured to do so by default, out-of-the-box. And you still get plenty of idiots in this world that set things up and then refuse to accept blame or even acknowledge that they could possibly have caused any portion of the problem they are experiencing. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- 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] Threading for integration with message board
At 6:41 PM -0500 10/4/06, Robert Hsiung wrote: #1 could be addressed by embedding, as I described, the message number in the original Reply-To: header, because then you could count on it being included in the To: header of replies. No, because the Reply-to: header has to contain an e-mail address and not a message number, so you can't go off and just change the format of that header without breaking every other mail program on the planet. Moreover, when the mailing list is sending out the cooked version of the message, it has no idea what message number will have been assigned to that message by the archiving system. It would know the value of the message-id header, but as we've said before, this doesn't always do us any good. #4 seems like it would be easy to fix, since you know the posts belong together and which came first. That would require potentially re-parsing and modifying every single message in the archive, every time a new message comes into the list. The ramifications of having to go back and re-parse and modify a potentially never-ending string of previous messages in the list just because some new message came in on a thread three years after the previous message, is just ... mind boggling. You can't properly fix #4 until the entire archive is implemented exclusively as a real database, and the display of the archive is always generated on-the-fly. This is what mail and news clients effectively do when they use Jamie's algorithm, and this is what the archive server would also have to do. In particular, this would mean that you could not pre-generate the cooked HTML version of an archive message, and message numbers in an archive could change whenever some new message comes into the archive in an earlier thread. Not having persistent message numbers would break the ability to post links to specific archive messages on the list, because tomorrow there might be a different message with that number. You can resolve the latter issue by getting away from message numbers entirely and going with a scheme based on the originating message-id header, but you'd have to add some additional intelligence to handle the potential problem of message-id collisions, etc So, there's lots of work here that needs to be done to fix the archiving system, yes. Is it possible to get Mailman to insert a variable +detail in the Reply-To headers? If so, I could use my threading system and Mailman both... I'm sure you could write such a module, yes. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- 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] Re-enabling users who exceed the bouncethreshold
At 11:06 AM +0900 10/5/06, [EMAIL PROTECTED] wrote: Then each subsequent mail found a 'cached' block and was itself blocked and also updated the cache expiration. When I stopped sending for over a week, the cached entry finally expired. This would be a serious violation of cache semantics, though. If the bug occurred at the DNS level, ATT would have been in a world of pain. Yeah, but during the years I was working at AOL, I frequently saw all sorts of really bizarre stuff that ATT was doing, and I would not be at all surprised if they actually did exactly what Mark suggested. There are other ways to explain the same kind of behaviour, but I certainly wouldn't put it past them. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- 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] Mailman and qmail confuse
Hello, I am running Mailman and qmail on a RH9 server. Both are running quite good. But in one condition, one of them confuses and mails are not delivered. I have a user account with name 'ccc' on the server. The mails, which are sent to [EMAIL PROTECTED] can be delivered. But at the same time, I have a Mailman list with name 'ccc-submit' . After openning the 'ccc' account, mail delivery stopped to ccc-submit and I began to receive 'no such mailbox' error. When I remove user 'ccc' mails to 'ccc-submit' can be delivered. What can cause this confusion, and what can be a possible solution? Best regards, Onur. -- 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] Threading for integration with message board
At 12:17 AM -0700 10/5/06, Brad Knowles wrote: #1 could be addressed by embedding, as I described, the message number in the original Reply-To: header, because then you could count on it being included in the To: header of replies. No, because the Reply-to: header has to contain an e-mail address and not a message number Sorry, embed was short for: My other idea is to do it myself, by using the post number of the post being replied to as the +detail part of the reply-to address. The message board script gives each post a post number. If it emails out post 123, for example, with a reply-to address of: [EMAIL PROTECTED] and a user replies to that, the sendmail aliases file can pipe it to the message board script: list+*: |path-to-script which can then extract the 123 from the [to] header and thread it after post 123. So it would be an address containing the number, not just the number. #4 seems like it would be easy to fix, since you know the posts belong together and which came first. That would require potentially re-parsing and modifying every single message in the archive, every time a new message comes into the list. Why would it imply that? The message comes in, you determine which thread it belongs to, and all you have to do is (1) go back in that thread until you reach the point where it belongs, which would just involve re-parsing those messages, and (2) insert it there, which would involve linking the previous message to it and linking it to the next message, or modifying two messages. In particular, this would mean that ... message numbers in an archive could change whenever some new message comes into the archive in an earlier thread. Not having persistent message numbers would break the ability to post links to specific archive messages on the list, because tomorrow there might be a different message with that number. No, the message numbers could stay the same, they might just not stay in the same order. If you start with 1 - 2 - 3 and 4 comes in late, it would become 1 - 4 - 2 - 3. Or whatever. Or am I missing something? Bob -- 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] Customizing message to large moderation email
We are going to start limiting the size some of our internal mailing lists and would like to customize the message that is sent to the poster to include the number of our helpdesk if their message is to large. Where is this text stored? -- 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] How to subscribe an user without his/her confirmation?
On 10/5/06, Simona [EMAIL PROTECTED] wrote: Hi all, I'm developing an unified system using PHP that I would like to use to manage users' subscriptions to my website, forums and newsletters. So, I'm asking you if there is a method to subscribe an user account to my Mailman lists without his/her confirmation via e-mail (I need to manage all confirmation procedures via PHP code...). Hi, The only way I have ever found to do this is to use the mailman command line command add_members. This usually isn't really an option from a web script because of permissions issues. If you don't have access to the mailman bin directory on the server, I don't know of a way to subscribe addresses without their confirmation, other than using the mass subscribe form in the list admin interface (but that would be difficult to use from php). Kristina -- 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] How to subscribe an user without his/herconfirmation?
Simona wrote: I'm developing an unified system using PHP that I would like to use to manage users' subscriptions to my website, forums and newsletters. So, I'm asking you if there is a method to subscribe an user account to my Mailman lists without his/her confirmation via e-mail (I need to manage all confirmation procedures via PHP code...). If you have access to the Mailman configuration, you can put ALLOW_OPEN_SUBSCRIBE = Yes in mm_cfg.py. Then each list will have an additional choice of 'None' for subscribe_policy (the default will still be 'Confirm' unless you change that too). This may work for you, but 'None' allows all subscription requests to be effective immediately whether from your PHP code or not. Otherwise, your PHP code could post the admin mass subscribe form data via the web, but the drawback here is the list's admin password has to be available to the PHP code. See http://mail.python.org/pipermail/mailman-users/2004-December/041210.html and possibly other posts in the archive. -- 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] Mailman and qmail confuse
M. Onur ERGiN wrote: What can cause this confusion, Qmail and what can be a possible solution? You would probably be more likely to get a good answer to this from a list or other support resource devoted to Qmail. -- 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] Customizing message to large moderation email
Knight, Eric Sean wrote: We are going to start limiting the size some of our internal mailing lists and would like to customize the message that is sent to the poster to include the number of our helpdesk if their message is to large. Where is this text stored? The English language text is in the definition of the MessageTooBig class in Mailman/Handlers/Hold.py. Other languages are in the translations in the messages/ directory. -- 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] Mailman and Postfix on different hosts?
Anders Norrbring skrev: Eric Howland skrev: On 8/30/06, Mark Sapiro [EMAIL PROTECTED] wrote: Anders Norrbring wrote: Simple question, would it be possible to run mailman on one host, and the Postfix MTA on another host? The reason is that I'm configuring a new in/outgoing server that eventually should take over the old one, the old should keep the web server functionality, so I'd like to split things up. If it can be done, any hints on how? Using a different host for outgoing mail is simple. Just set SMTPHOST in mm_cfg.py. Incoming mail to Mailman is more difficult. This has been discussed before on this list. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.018.htp for searching information. I'm having troubles finding info on this matter.. Probably because English isn't my native language, so I guess I just don't get the search terms right to get relevant results. Anyway, more info would be really useful. Thanks, Anders. -- 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] automatically subscribe
I need to write a script to add users to a Mailman list. The trick is that the script will not be running on the same machine that Mailman is running on. When I add a user to our system, I need to kick off this script so that if the new user is in the faculty group, their email address is automatically added to the faculty Mailman list. I am thinking that I could do this via the email interface. Ie. Generate a mail message to faculty-request. That sort of works. The only problem is that I need to do it as the list administrator or moderator so that the user doesn't get a confirmation message. Essentially, I need it to work as if I used add_members. With add_members, the user just gets a message that he has been subscribed. Can I authenticate as list administrator and then subscribe some other email address? This doesn't seem to work: To: [EMAIL PROTECTED] set authenticate password [EMAIL PROTECTED] subscribe [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
[Mailman-Users] Sporadic, fractional non-delivery
We have an on-campus list with about 1,900 student subscribers that has been functioning properly for months. Recently, however, an extremely small percentage of students -- about 1% that we're aware of -- have stopped getting messages from the list. Here are some of the specifics ... 1. Mailman and the MTA (Sendmail) both reside on the same well-configured Red Hat Linux ES server, which serves as our primary on-campus e-mail server, too. 2. Doing grep on specific account names through all the Mailman logs hasn't turned up any issues. 3. All impacted students are receiving normal (non-Mailman) messages just fine from the same on-campus domain, which (again) is driven by the same Sendmail instance. 4. No differences can be found at the Linux account level -- directory permissions, user configuration, etc. -- between those who are receiving the messages and those who aren't. 5. The impacted account names have been confirmed to reside in the Mailman config.pck file and via the Web GUI Membership Management screen with typical (non-digest) delivery preferences set. I should note that some of these students are automatically forwarding their University e-mail to an off-campus account -- like Gmail or Hotmail -- and obviously that introduces another layer of message filtering. But many of these students are using on-campus IMAP or POP e-mail resources only, and a spot check immediately after a message is distributed via Mailman reveals that they still aren't getting anything from the list. Any ideas to help our investigation on the Mailman and/or Sendmail side? Is there some extra verbose logging that could be turned on? Thanks, Jason _ Jason LaMar Director of Information Services Ohio Wesleyan University | Delaware, OH 43015 AIM/Yahoo IM: jasonrlamar | MSN/Google Talk: [EMAIL PROTECTED] Tel: 740-368-3131 | Fax: 740-368-3272 | Web: http://www.owu.edu/ -- 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] Cron gate_news
For some reason, the gate_news cron starting giving this error every 5 minutes: IOError: [Errno 13] Permission denied: '/usr/local/mailman/lists/testlist/config.pck' To the best of my knowledge, this list does not have a mail/news gateway. Can someone let me know how I can get rid of this error? -- 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] Cron gate_news
For some reason, the gate_news cron starting giving this error every 5 minutes: IOError: [Errno 13] Permission denied: '/usr/local/mailman/lists/testlist/config.pck' To the best of my knowledge, this list does not have a mail/news gateway. Can someone let me know how I can get rid of this error? Found out what the problem was. The permissions were incorrect. Did a chown on the config.pck file and it worked! -- 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] Sporadic, fractional non-delivery
Jason LaMar wrote: We have an on-campus list with about 1,900 student subscribers that has been functioning properly for months. Recently, however, an extremely small percentage of students -- about 1% that we're aware of -- have stopped getting messages from the list. The same students for each message? 5. The impacted account names have been confirmed to reside in the Mailman config.pck file and via the Web GUI Membership Management screen with typical (non-digest) delivery preferences set. I should note that some of these students are automatically forwarding their University e-mail to an off-campus account -- like Gmail or Hotmail -- and obviously that introduces another layer of message filtering. But many of these students are using on-campus IMAP or POP e-mail resources only, and a spot check immediately after a message is distributed via Mailman reveals that they still aren't getting anything from the list. How is this 'spot check' being done? Any ideas to help our investigation on the Mailman and/or Sendmail side? Is there some extra verbose logging that could be turned on? It's pretty unlikely that this is a Mailman issue, but you can check this by looking at Mailman's 'smtp' log. It will have an entry like Oct 05 10:33:45 2006 (1570) message-id smtp for 170 recips, completed in 4.645 seconds The message should be delivered to nnn recips (170 in the above example) where nnn is the number of message mode members with delivery enabled less the poster if the poster doesn't receive her own posts and less the number of members explicitly mentioned in To: or Cc: that have the 'avoid dups' option. If this number is as expected, then SMTPDirect delivered the message to the MTA for all the expected recipients. You can also check Mailman's 'smtp-failure' log to see if any problems were reported to Mailman during SMTP. If the number of recips is short the number of missing deliveries, it is a Mailman issue and we need to figure why Mailman is dropping these, but I suspect from your analysis so far, that this isn't it. If Mailman delivered to the expected number, then check the MTA's logs because the problem is almost certainly in the MTA or outbound from there. -- 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] Threading for integration with message board
At 7:56 AM -0500 10/5/06, Robert Hsiung wrote: That would require potentially re-parsing and modifying every single message in the archive, every time a new message comes into the list. Why would it imply that? The message comes in, you determine which thread it belongs to, and all you have to do is (1) go back in that thread until you reach the point where it belongs, Right, but a new message can come into a thread at any time in the future, potentially years in the future. You'll have to change the next and previous links in the affected pre-generated HTML files (for each of the different types of sorting, including date, thread, and subject), plus the associated indexes. And then all links which people have put into their messages will break, if the archives ever have to be re-generated. which would just involve re-parsing those messages, and (2) insert it there, which would involve linking the previous message to it and linking it to the next message, or modifying two messages. Take a look at the code. Understand what it actually does. This process is not nearly so straightforward as you think. Yes, in theory everything is trivially simple. I mean, Jamie's algorithm has a pretty short description, right? In practice, things get a lot thornier. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 Founding Individual Sponsor of LOPSA. See http://www.lopsa.org/. -- 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] automatically subscribe
John Heim wrote: I am thinking that I could do this via the email interface. Ie. Generate a mail message to faculty-request. That sort of works. The only problem is that I need to do it as the list administrator or moderator so that the user doesn't get a confirmation message. Essentially, I need it to work as if I used add_members. With add_members, the user just gets a message that he has been subscribed. Can I authenticate as list administrator and then subscribe some other email address? There are two reasons why this doesn't work. 1) 'set authenticate' is only effective for subsequent 'set' commands. 2) even if you use the list admin password and the list owners email address in address=, you are still authenticating the 'member', not the 'owner' (in fact, you'll get an error if the owner isn't a member). For a different approach see http://mail.python.org/pipermail/mailman-users/2006-October/053679.html and the other post to which it refers. -- 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] Making Archives password protected
On Thu, 2006-10-05 at 15:49 -0300, Douglas Denny wrote: Hello, I am list administrator on a Mailman list. Users have asked me to password protect the archives. I cannot find this option in my list interface. This option does not seem to do anything: I s archive file source for public or private archival? * private That option works for me and my lists. I am using version 2.1.7. Can someone tell me how to make the archives only viewable by list subscribers? I was using v2.1.7, now on v2.1.9, archive_private worked then and works now. What does your apache config look like, wrt your paths/redirects associated with the mailman archive directory structure? -Jim P. -- 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] Threading for integration with message board
At 11:05 AM -0700 10/5/06, Brad Knowles wrote: That would require potentially re-parsing and modifying every single message in the archive, every time a new message comes into the list. Why would it imply that? The message comes in, you determine which thread it belongs to, and all you have to do is (1) go back in that thread until you reach the point where it belongs, Right, but a new message can come into a thread at any time in the future, potentially years in the future. You'll have to change the next and previous links in the affected pre-generated HTML files (for each of the different types of sorting, including date, thread, and subject), plus the associated indexes. OK, that's 6 changed messages for every out-of-order one (+ 3 index files). That's still a lot less than every single message in the archive, every time. And then all links which people have put into their messages will break, if the archives ever have to be re-generated. Wouldn't that depend on how and why they're regenerated? If it's just to add messages, then the same process could be followed, 6 old files would be changed for each new file, and all the old files could keep their message numbers. which would just involve re-parsing those messages, and (2) insert it there, which would involve linking the previous message to it and linking it to the next message, or modifying two messages. Take a look at the code. Understand what it actually does. This process is not nearly so straightforward as you think. What code? I didn't have any specific code, or algorithm, in mind. It just seemed to me that inserting a message earlier in a thread shouldn't be so much more trouble than adding it at the end. As I said before, it's just: 1 - 4 - 2 - 3 instead of: 1 - 2 - 3 - 4 If it's more complicated than that, then there's something I'm not understanding, and I'd appreciate it if you'd explain. Thanks, Bob -- 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] Making Archives password protected
Douglas Denny wrote: I am list administrator on a Mailman list. Users have asked me to password protect the archives. I cannot find this option in my list interface. This option does not seem to do anything: I s archive file source for public or private archival? * private This setting should do it. It should cause the archives/public/listname symlink to be removed so the 'pipermail' URL no longer works and access is through the private CGI only. If you 'tested' by visiting the archive immediately after changeing the option, you were already logged in as the admin so you didn't have to log in again. -- 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] Mailman vs. Email Aliases
I'm a new Mailman user. So far things are working OK. I just discovered a wrinkle that I suspect that other mailmen and mailwomen have faced. I follow good Sendmail/Postfix practice by breaking my email aliases file into two sections - one where I define a canonical email name for each person, and the other where I define my email lists (which will be replaced by Mailman-managed lists). In my lists I only use the canonical name so that if somebody's email address changes, I only have to change one thing and then everything else works. To show what I mean, I'll have something like this: smith: [EMAIL PROTECTED] list1: smith list2: smith list3: smith So when smith moves to yahoo.com, I only have to change the first line. However, I'm deliberately setting up each Mailman list to only allow posting from members of the list. This means that the technique above won't work because if I put the canonical name in as the list member, any mail send to the list by [EMAIL PROTECTED] will be rejected. Using [EMAIL PROTECTED] in all the lists goes against the teachings of Sendmail/Postfix, which are righteous. I don't currently see any way around this. What would be nice would be if there were a way to point Mailman to the Sendmail/Postfix aliases file and then change the Mailman check for list membership to do alias expansion. I checked the FAQ but didn't see any mention of this. What am I missing? Cordially, -- Jon Forrest [EMAIL PROTECTED] Computer Resources Manager Civil and Environmental Engineering Dept. 305 Davis Hall Univ. of Calif., Berkeley Berkeley, CA 94720-1710 510-642-0904 -- 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] %variable for fullname in verify.txt
Hi all, We are trying to customize the verify.txt which is used in the Email subscription confirmation to the user. We would like to personalize it by adding the user's fullname when they registered. What is the %variable for the user's fullname we can use in the verify.txt file? Since the user's fullname is optional on the registration form so may be blank, does the verify.txt file support some type of conditional code so only display the user's fullname when it is not blank? Thank you in advance for any suggestion. Sincerly, Jimmy -- 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] Another puzzler
Martin Dennett wrote: Brad Knowles wrote: At 7:23 AM +0100 10/4/06, Martin Dennett wrote: There is no other information in the bounce message, so how do I find out who the message is really trying to be delivered to? This kind of problem is what VERP was designed to make much easier to detect. Check the relevant FAQ entries on this subject, and keep in mind that this may require a level of access to your Mailman server that you may not have. Will check the FAQ's, but you're correct about my server access :-( I'm sorry to say that if as you seem to say above, no part of the original message is quoted in the bounce message and you don't have the ability to alter the Mailman configuration on the server, the only thing I can think to do is to directly mail your list members and see who bounces. You could do a kind of binary search by sending a brief, apologetic note with Bcc: to half the list. If you get a bounce, the offending address is in that half. If not, it's in the other half (be sure you wait long enough). Keep repeating this process until you narrow it down to one address. Of course, this is tedious for you and for your non-bouncing members who will receive a number of these probes, but I don't think there's another way. You could examine the Received: headers in the bounce message, but I think these will originate with the unknown server and thus, won't help you understand how (from where) the message got to that server. -- 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] Mailman vs. Email Aliases
Jon Forrest wrote:
snip
To show what I mean, I'll have something like this:
smith: [EMAIL PROTECTED]
list1: smith
list2: smith
list3: smith
So when smith moves to yahoo.com, I only have to
change the first line.
However, I'm deliberately setting up each Mailman list
to only allow posting from members of the list. This means
that the technique above won't work because if I put
the canonical name in as the list member, any mail send
to the list by [EMAIL PROTECTED] will be rejected.
You have a more serious issue to contend with first and that is that
Mailman does not accept email addresses consisting of only a
local-part ('smith' in your above example).
However, I'm deliberately setting up each Mailman list
to only allow posting from members of the list. This means
that the technique above won't work because if I put
the canonical name in as the list member, any mail send
to the list by [EMAIL PROTECTED] will be rejected. Using
[EMAIL PROTECTED] in all the lists goes against the teachings
of Sendmail/Postfix, which are righteous. I don't currently
see any way around this.
Stop thinking in terms of using MTA aliases to manage your list members
and let Mailman do its job.
Smith can subscribe her gmail address to a number of your Mailman lists
and when she moves to yahoo, she can change her address globally on
all your lists to which she is subscribed by visiting her options page
for a single list and changing her address globally.
--
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] Mailman vs. Email Aliases
Mark Sapiro wrote:
You have a more serious issue to contend with first and that is that
Mailman does not accept email addresses consisting of only a
local-part ('smith' in your above example).
I didn't know that. I had read the following:
# The host_name is the preferred name for email to mailman-related
# addresses on this host, and generally should be the mail host's
# exchanger address, if any. This setting can be useful for selecting
# among alternative names of a host that has multiple addresses.
host_name = 'ce.berkeley.edu'
so I was expecting this to be used when only a local part appears.
Stop thinking in terms of using MTA aliases to manage your list members
and let Mailman do its job.
Smith can subscribe her gmail address to a number of your Mailman lists
and when she moves to yahoo, she can change her address globally on
all your lists to which she is subscribed by visiting her options page
for a single list and changing her address globally.
Our list members don't use Mailman's web interface. All our lists are
created by administrative staff. Could a list administrator also
change an address globally?
Jon
--
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] Mailman vs. Email Aliases
Jon Forrest wrote: I didn't know that. I had read the following: # The host_name is the preferred name for email to mailman-related # addresses on this host, and generally should be the mail host's # exchanger address, if any. This setting can be useful for selecting # among alternative names of a host that has multiple addresses. host_name = 'ce.berkeley.edu' so I was expecting this to be used when only a local part appears. host_name is used for constructing the list posting address and the various listname-* addresses from the list name. Our list members don't use Mailman's web interface. All our lists are created by administrative staff. Could a list administrator also change an address globally? No. Only the Mailman site admin (anyone who has logged on with the site password) and the individual user can request a global address change. In addition, regardless of who requests the change and whether or not it is global, a confirmation request is sent to the new address and the change must be confirmed. Individual list owners (logged in with a list admin password) generally can't request/change information for other lists. -- 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
