Re: [Mailman-Users] Digest not working on Mac 10.3.6 running mailman2.1.4
On 6/11/10 6:51 AM, Mark Sapiro m...@msapiro.net wrote: Bob Bader wrote: I still have a Macintosh 10.3.9 server running the default mailman (version 2.1.4) for mail lists. We have noticed digests have stopped working, I can send them manually, or if I set the trigger size to 0 they go. If I run the command /usr/bin/python -S /usr/share/mailman/cron/senddigests That also works. I suspect it has something to do with cron. I look in the file /usr/share/mailman/cron/crontab.in and it all looks good. Is there is setting for mailman in the Mac's crontab? No. crond normally looks at the system crontab /etc/crontab and all the user crontabs in /var/spool/cron/* (or in Mac OS X 10.6 at least, /usr/lib/cron/tabs/*). It doesn't look at /usr/share/mailman/cron/crontab.in which is the input intended to be installed in /usr/lib/cron/tabs/ by a command like crontab -u _mailman /usr/share/mailman/cron/crontab.in (assuming the Mailman user is _mailman). See 'man crontab' and 'man cron'. Since Mailman's cron jobs used to run, I suspect the issue is that crond is not running on your server. It's either that or Mailman's crontab has gone missing. If crontab -u_mailman -l shows Mailman's crontab, then crond is not running. How to fix that is a Mac OS X question. On my Mac OS X 10.6.3 system, crond is not running, but cron is. The man page for cron makes it look like crond by the shorter name. This is 10.6.3 client, not server (and I don't run Mailman on it). A quick test suggests that cron acts like crond. * * * * * /bin/date /tmp/dates (Which I think I'll turn off now.) It produced: cat /tmp/dates Sun Jun 13 09:10:00 PDT 2010 Sun Jun 13 09:11:00 PDT 2010 --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Approved: password header!
On 8/6/09 9:08 PM, Mark Sapiro m...@msapiro.net wrote: Thus, the idea of allowing [Approved: password] in the subject header and removing only that text from the subject has appeal because it doesn't depend on any characteristics of the message body. Won't work in an environment in which the message arrives with a DKIM signature including the Subject: header and when enforces valid DKIM headers inbound. (Or for a list going to outside subscribers, if any of them insist on DKIM validation.) Of course, it's very unlikely that approved header as first line of first text part works in that environment either. But Mailman already (by common configuration) munges Subject: headers. When Office 2010 public beta arrives (or before if someone here has earlier access) it would be nice to check whether Outlook 2010 has learned a rational way to add custom headers. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Can one use EC2 for bandwidth spikes?
On 11/4/07 12:29 PM, Chuck Peters [EMAIL PROTECTED] wrote: We have a newsletter with 1500+ subscribers which is currently hosted on my friends house. He has DSL and the connection goes to crap for 5-15 minutes every time we send one out, other than that it works fine. When I looked at some of the low cost hosting options none of them seem to be good because of various limitations like 500 messages per hour. We send out 1 or 2 newsletters a week at most so it has been hard to justify spending the $40-$100 or more a month for better hosting. I have been wanting to try out Amazon's Elastic Compute Cloud, http://aws.amazon.com/ec2, and I think it would be really cool to fire up the EC2 instance (basically a linux server) for an hour and fire off the newsletter. Has anyone done this sort of thing? I doubt it could it be as simple as making a temporary exim smarthost with some configuration tweaks. What is required to make this work properly? Brad points out disk performance issues and others. In addition, each time you fire up your EC2 server, it gets a dynamically assigned IP which is virtually certain to differ from the last time. And that includes restarts after crashes (but of course they don't crash). So you have to deal with the usual problems of running mail servers on dynamic IPs. Both incoming and outgoing servers in this case...the incoming problem can be solved by routing through the home server--that leaves the list members who won't get their copies because the mail comes from a dynamic pool space--but the list may already have that problem. So nice as the idea sounds, it likely isn't practical. Unfortunately, I can't help with specific configurations. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Reject *to* non-subscriber
On 10/11/07 2:33 PM, glen martin [EMAIL PROTECTED] wrote: I've seen several posts about restricting non-subscribers from posting. This is a little different. I run a private list where the list-members have decided they don't want non-subscribers on the threads at all. But occasionally one will forget and cross-post. I'd like to bounce subscriber messages where a non-subscriber is anywhere on the receiver list. Is there anything like this currently available or contemplated? It can't be fully done because of Bcc. (Except in a very specific scenario which likely isn't achievable.) It could be done with respect to To: and Cc:, but that might well just give a false sense of privateness. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Looping Moderator Approval Requests / MailmanExim
On 7/27/07 8:51 AM, Mark Sapiro [EMAIL PROTECTED] wrote: mailman_router should be the first router. Also, you might check your exim-main-log to see how these messages are routed and delivered. The command line command exim -bt [EMAIL PROTECTED] may provide some insight. The -bt flag tells exim to explain its routing of the address. For example $ /usr/sbin/exim -bt [EMAIL PROTECTED] [EMAIL PROTECTED] router = mailman_router, transport = mailman_transport First line shows the routed address; second shows the router and transport. Multiple levels are reported similarly. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing
On 6/29/07 7:44 AM, Rich Kulawiec [EMAIL PROTECTED] wrote: Two related suggestions. (1) LHS (left-hand-side) rules Any incoming mail message whose putative sender matches: do-not-reply@ do.not.reply@ donotreply@ no-reply@ no.reply@ noreply@ and which is directed to any of the Mailman standard aliases can be rejected (not bounced [1]) with SMTP status 550 (extended status 5.7.1) since either: (a) it's a forgery, therefore there's no point in letting Mailman attempt to emit a reply -- or even in accepting the message to begin with. (a) it's not a forgery, therefore there's no point in trying to reply to it. (Nor is there any point in permitting it to subscribe to a list or send any traffic to one.) Arguably, this could be done in some MTAs by configuring rejection of those LHS patterns on a per-local-user basis; but I'll argue that doing this in Mailman itself would be more useful, since many (perhaps most) sites don't use per-local-user configuration (and perhaps don't know how). Moreover, any site running multiple mailing lists would need to set this up for every Mailman alias for every mailing list -- so it seems simpler to handle it inside Mailman itself. My guess is that this should be a switchable feature, named something like reject-noreplies. (Not that I can envision a need to switch it off, but I think it'd be more conversative to have that option.) At least here, this good idea would have to be implemented in the MTA which receives the message, as the message is not presented to Mailman until after the receiving MTA has accepted the message (in fact, here, it's not even presented to Mailman by the same MTA or on the same machine). Thus rejection is not possible based on what Mailman does. (Further, in the present Mailman, the presentation is by pipe, so doing something like Exim's recipient verification callout doesn't work.) There have indeed been discussions about making the MTA able to get information from Mailman in time to do SMTP-time rejection. It's not simple to do in the general case. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing
On 6/29/07 11:23 AM, Rich Kulawiec [EMAIL PROTECTED] wrote: p.s. As as aside, I strongly recommend against callbacks/SAV. It's inherently abusive, it's a deliberate attempt to bypass site security policies [and thus illegal in some jurisdictions, but ask your attorney for clarification 'cause IANAL], I wasn't referring to sender verification callbacks (which we do not use). I was referring to recipient verification callforwards, where the edge MTA doesn't know valid recipients but some internal (or even customer) MTA does. Exim can configure these easily (but that doesn't help because Mailman doesn't act like an MTA). I don't know about any other MTAs in this regard. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Subject Lines Wrapped After Commas, (LikeThis?)
On 5/21/07 4:54 PM, Mark Sapiro [EMAIL PROTECTED] wrote: I would argue that Eudora is much more at fault here Eudora was also the primary source of resistance to the List-* headers, with its interesting habit of displaying all headers except those in its list of boring headers. Manipulating that list, in the time frame in which the List-* headers appeared, was not easy for the users on any platform (less hard on Mac than on Windows). On the screen size I had at the time they appeared, the List-* headers caused me to have to scroll to see the useful part of any mailing list message longer than a couple of lines. (My usage of Eudora is down to sending test messages and sending some template-based messages. And searching messages older than a half decade or so.) --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Slow delivery
On 3/8/07 10:44 PM, Herman Privyhum [EMAIL PROTECTED] wrote: --- Brad Knowles [EMAIL PROTECTED] wrote: I'd be willing to bet you're waiting on DNS timeouts at the remote end for one or more of your users -- their MTA is slowing you down, maybe as a result of trying to do a reverse DNS lookup on your IP address. Thanks to all for the thorough replies. It appears that the solution actually lies in disabling ident. In Exim, this is achieved by setting the timeout to 0. #rfc1413_query_timeout = 30s rfc1413_query_timeout = 0s I may go back and turn it on again with a smaller timeout (suggestions as to how long is reasonable?). Just a note: The default value of rfc1413_query_timeout was reduced in recent versions of Exim to, I think, 5s. That was in preference to changing it to 0s, as a change to 0s would impact sites which don't change that default, something Philip doesn't like to do except when the major version changes. Philip will be retired (late September) before Exim 5 is out--the Exim community is well along in setting up a structure to deal with that. His retirement is, IMHO, much scarier with respect to the PCRE library than is is with respect to Exim. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman an sendmail receiveing mails
On 3/8/07 1:52 AM, TRON478 [EMAIL PROTECTED] wrote: i have set up mailman on a suse machine with sendmail. when i open the administration site and subscribe i get mails (), but when i sent to the list, the mail never arrives. You sent the message to which I'm replying from Gmail. If you sent the test message that way, and it was intended to go back to the Gmail account, it won't. Google is being helpful, and hiding the message that comes back from the list since it thinks you already have a copy. I'm pretty sure this is in the Mailman FAQ, but I seem to be too dumb to find it. (This morning, anyhow.) Of course, if you didn't send the test message from Gmail, then the above isn't the problem. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] OT: Firefox Crashing on Admin Pages
On 1/16/07 6:57 AM, Kenneth Jacker [EMAIL PROTECTED] wrote: I appreciate both Mark and Barry's informative and prompt replies. Let me do a little more investigating ... maybe there's some conflict with one of my FF plugins ... Did you install a new plugin (or update one) about the time the problem started? A nice thing about Firefox is the wealth of available extensions. The problem with that is that just saying Firefox version doesn't identify what is running. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mail delivery notification
On 12/15/06 6:45 PM, Brad Knowles [EMAIL PROTECTED] wrote: At 10:48 AM -0300 12/15/06, Andres Tarallo wrote: We need to receive a notification that the suscribers had received the mail. We where thinking in adding a header that makes the mail client return an automatic answer. You can put in a header that some mail clients will recognize, and which may be configured to allow a return receipt to be generated. However, not all clients understand that concept at all, there have been multiple different attempts and standards to try to achieve this goal, and some of those multiple attempts are mutually incompatible. Not to mention that it could be the visiting 8 year old grandson who sees the message, tells the MUA to return the receipt (or the MUA options are set so that is implicit), then deletes the message. Not only does the sender not control the automated parts of the path, the sender doesn't control the human element at the receiving end. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman and (really) large lists
On 11/27/06 11:48 PM, Brad Knowles [EMAIL PROTECTED] wrote: The easiest way is to configure your MTA so that it has a different and customized configuration that it uses for listening to a particular numbered port on the loopback interface (a.k.a., 127.0.0.1), and then you configure Mailman to use only that port/interface for all outbound mail. And avoid 127.0.0.2 That IP is included--for testing purposes--in many DNS-based blocking lists. So sites which check all Received: headers in messages are likely to see 127.0.0.2 as a Bad Thing[tm] and reject/discard/mark as spam messages containing it. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] subscription only via email?
On 11/22/06 12:03 AM, Zbigniew Szalbot [EMAIL PROTECTED] wrote: Because I cannot offer http access to the machine where mailman is installed, I wonder if I can set the subscription process so that it is available only through email. I understand I will have to edit some templates with email texts (suggestions which would be welcome though hopefully I will find them) but should I take anything else into considertaion? In your situation, it may make more sense to use a mailing list manager written to be driven from email, such as Majordomo. Mailman--as a reaction to the problems some people found with the Majordomo way--was designed to be driven from the web, with a few email commands tossed in to make former Majordomo users feel more at home. After we switched our lists from Majordomo to Mailman, I stopped following progress--if any--on Majordomo. There could well be better choices around. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Freepbx querries
On 11/21/06 8:54 PM, vyom asterisk [EMAIL PROTECTED] wrote: I have resently joined this mailing list , Plz suggest mailig list if you can , It will be a great help thnks Suggest you look at the left side of http://www.freepbx.org/. Near the top is FreePBX Forums which looks promising. Near the bottom (just above the long skinny ad) is a blog. And under Useful Links there is Asterisk Tutorials. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] spam, spamcop and mailman moderation
On 11/10/06 9:07 AM, Dragon [EMAIL PROTECTED] wrote: You really should use the power of MTA filtering, it will save you a lot of frustration. At the very least, use gray-listing because the vast majority of spam simply won't be resent when a deferral response is sent from your MTA to the sender. Unfortunately, the spam engines sending image spam (or at least some of them) are indeed retrying and successfully getting through greylisting. [I can't say how much image spam might not be getting through greylisting.] So the end of greylisting as a useful tool is approaching (I'm surprised it has survived this long). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] debian/exim4/mailman
On 11/3/06 3:23 PM, Mark Sapiro [EMAIL PROTECTED] wrote: 1) I have a website that I want to maintain a list for but my host provider charges me if I run a list through that hosts. So I figured I could run a list from my own personal machine and use remote smtp to just mail to the list. ( its going to be an announcement list only). Well, I am running debian and home and I was able to finally get exim4 talking with gmail and use googles smtp servers. Why not just let Exim connect directly to the recipients' smtp servers? A. Terms of service. B. Filters of two kinds (the first of which has two sub-kinds): 1. List operator's ISP (a) blocks port 25 except to its own servers or (b) diverts the traffic to its own servers 2. Recipient's ISP does not accept incoming port 25 connections from the list operator's IP block. If list operator has static IP AND suitable reverse lookup for his domain, and his ISP doesn't do static IP out of the same subnets that it does dynamic, then #2 is much less likely--and so is the TOS problem. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Unexpected Listname When Creating New List
On 10/27/06 6:17 PM, Jon Forrest [EMAIL PROTECTED] wrote: Are you sure your postfix aliases for Mailman are case sensitive. I doubt it. Try mailing to [EMAIL PROTECTED] and [EMAIL PROTECTED] I suspect both messages will get posted to the list. You are 100% right. I did NOT know this!! All these years of misinformation... The current situation is that the local parts are not case sensitive almost everywhere, but CAN be. (Exim, for example, has a little-used option to create case-sensitivity. I don't speak Postfix, but a quick look at Postfix, The Definitive Guide didn't show me an equivalent option.) So (most) MTAs are stuck preserving case, particularly on messages relayed to other MTAs, but comparing all lower case. This seemingly was a political thing in the mail standards meetings--there were still enough case-sensitive sites to keep the status quo. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Auto-deleting mail from outside .no?
On 10/17/06 9:00 AM, Thomas Gramstad [EMAIL PROTECTED] wrote: I have many small lists in Norwegian and they're all being hit by a lot of spam. Yes, the spam filter holds them back -- but then I get a /lot/ of mail about new messages waiting, and it's a big job moderating them. What I really want is the option to set that anything mailed from an address that does not end with .no is automatically deleted and I never see it. Is that possible, per list or even per domain/for all lists? As has been said, the MTA is likely the better venue for doing this, as SMTP 5xx rejections can be arranged. That aside, are there *no* .com, .org, .edu etc within Norway (without the trailing .no), which contain potential list subscribers? For example, no one at hydro.com would want to be a list member. (Domain obtained on my first attempt, a Google search for Norsk Hydro.) --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] where is creator.py?
On 10/11/06 4:52 AM, Peter Soccar [EMAIL PROTECTED] wrote: I'm using mailman 2.1.7 installed from rpm on fedora 5, as I understand the default path of adm.py and creator.py should be /etc/mailman I found adm.py but not creator.py, could it be in any other location? Aside from what Brad and Mark said, the locate command should find these files for you. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] importing an archive in such a way as to populatethe associated newsgroup.
On 9/24/06 8:19 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Assuming the experiment above works, you could probably create a simple script in Python (or perl or even a shell script) that would extract the messages one by one from the mailbox and pipe them to bin/inject --listname=listname --queue=news (bin/inject reads stdin if no filename arg is given). formail can probably be used for this job. The man page is a must, and caution is advised (formail will do what it's told, as will the commands it is told to send the output to--it can happen that it's told the wrong thing for an input mbox file with lots of messages). The formail program typically rides in with the procmail package in package-based distributions. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Question about Debian/Ubuntu Mailman Package
On 9/12/06 11:26 AM, Dragon [EMAIL PROTECTED] wrote: Version 2.1.5 is rather old. I believe there are some security issues that have been fixed since that release. IMO it is a good idea to use the latest version to preclude as many potential issues as possible. The security fixes are very likely backported by the major distributions. Beyond that, they don't tend to do version upgrades of components until their next major release. (This was a major nuisance a while back the Debian and Exim, as Debian had such a long wait for a major release that nearly everyone on the Exim-users list had forgotten how to drive the Exim version found in the stable Debian release.) Mailman 2.1.5 remains old, but if the distributions' updates are applied, the security fixes are likely close to current if not current. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] a few details
On 9/11/06 10:35 AM, Brad Knowles [EMAIL PROTECTED] wrote: At 1:20 PM -0400 2006-09-11, Matt Herzog wrote: Not exactly. I have MTA = Postfix in mm_cfg.py. Do the spaces matter? In this case, I don't think that the spaces will be a problem (although Python does normally care a great deal about spacing), but the double versus single quotes may be something that Python cares about. The spaces (or lack thereof) around the = do not matter in Python. (My habit is to use them; which conflicts with my (necessary) habit not to use them in shell scripts.) There is no difference in Python between a string in double quotes and one in 'single' quotes, except that the former can easily contain ' characters and the latter can easily contain characters. (Got that one by the grammar checker. ;-)) As in This doesn't cause problems. In this area, Python is quite different from, for example, Perl and Ruby. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] HTML Newsletter Setup
On 9/8/06 4:43 AM, David Ellsworth [EMAIL PROTECTED] wrote: Uh, thanks for that Brad, I got it, it's complicated. All I need is a simple way to get a formatted html email with Approved through the system. You're telling me that that isn't going to be the case? I'm using an applescript with Entourage on OS 10.47 to send the file to mailman. Perhaps another email client that allows me to put the Approved comment in the email file header? I see two fairly obvious ways to proceed. 1. Create an Account in Entourage, and insert the needed Approved: header manually into that account's additional headers area. Then send messages to the list using that account (in your scripting). 2. Using Applescript to modify a single account, you may be able to set the Exchange account object's additional headers property early in the sending script to contain the needed header, then prepare and send the message, then restore the additional headers property to normal (probably empty). I haven't tried this. The Entourage version I'm looking at is 11.2.5. Note that if someone manually sends a message at an inconvenient moment, the header would be part of it. Suggest debugging the script using a bogus password in the Approved: header. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] query re message has implicit destination(devils advocate!)
On 8/31/06 4:09 PM, Brad Knowles [EMAIL PROTECTED] wrote: Actually, I think either unapproved or unauthorized are the most appropriate terms. After all, the code is released under the GPL, and anyone who is making modifications to that code and then making their modified version available to their customers (or otherwise benefiting from those modifications) are supposed to contribute the source to their changes back to the community. But CPanel has not done this, neither has Plesk, nor Apple. Now, in a way, Apple gives back to the project more than they probably realize, but that's not the same thing. So, while we don't make that big a deal of this issue, I think I'm actually being reasonably lenient on these companies. I continue to think that un-vetted is closer. GPL doesn't give Mailman's copyright holders control over what changes are made, which unapproved or unauthorized would seem to imply. I think. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Why Not Upgrade to 2.1.8?
On 8/25/06 8:07 AM, Dragon [EMAIL PROTECTED] wrote: Security for one. Much of the impetus for releasing later versions in the 2.1.X branch was for that reason. I don't know what, if anything, RedHat is doing about backporting the security changes. For things in general, they are pretty good about backporting upstream security fixes. Some, at least, of the ones present in 2.1.8 may be present in RedHat's current 2.1.5. Or not, of course. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Sender address..
On 8/24/06 6:48 AM, Mark Sapiro [EMAIL PROTECTED] wrote:
See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq02.003.htp.
Unfortunately, both domains used in the examples at the top of that FAQ
entry exist (although the FQDNs of the hosts mailman and poster within those
domains do not, so having the FAQ as is isn't TOO bad).
Is there any interest in sanitizing the FAQ by adjusting examples to follow
RFC 2606 as closely as possible? I'm reasonably sure that 2.003 isn't the
only entry which could use adjustment.
As closely as possible because we wouldn't want to confuse things by
putting the mailman server AND the poster both into the
example.{com,org,net} domains. But we could use mailman.example or
mailman.something.example for the server and poster.example.com for the
poster without TOO much confusion.
--John
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Sender address..
On 8/24/06 11:11 AM, Brad Knowles [EMAIL PROTECTED] wrote: At 10:41 AM -0700 2006-08-24, John W. Baxter wrote: Is there any interest in sanitizing the FAQ by adjusting examples to follow RFC 2606 as closely as possible? I'm reasonably sure that 2.003 isn't the only entry which could use adjustment. Sure, that's a great idea. The Mailman FAQ Wizard is a community-supported facility, and all the information you need for making updates or creating entire new entries is provided on the page. In a way, this is kind of like a wiki, although it has a much simpler syntax, and is a lot easier than most wikis that I've encountered. If you're up for it, please go ahead and make the appropriate changes. OK, thanks. I was volunteering, but didn't want to forge ahead without letting the idea be visible for a while. I'll wait a while longer for a possible veto. (More to do during my off duty hours. Say I, who got nine pages around 03:15 yesterday (local time, unfortunately) from our monitors.) --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Spam avoidance, revisited: best practices?
On 8/23/06 1:18 PM, Dragon [EMAIL PROTECTED] wrote: Matt England sent the message below at 12:14 8/23/2006: At 8/23/2006 11:52 AM, Patrick Bogen wrote: I think he meant: auto-moderate new users, and unmoderate them after some amount of time has passed (e.g., after a day or after a week) Yes, that's correct. Can Mailman do the above (auto-moderate new users, and then automatically un-moderate them after a certain duration)? End original message. - It can do the first part but not the second. What you need is a script that will check the moderation setting, check the time since subscription, and reset the setting if the threshold is reached. You would then run that script as a cron job. I don't know if there is a way to find the time somebody subscribed, I don't think it is stored in the config.pck for the list but it may be in a log somewhere. Or, one could take the position that if a new subscriber turns out to be a lurker only, it doesn't matter whether she is still marked as moderated in a few months, or not. On the other hand, if she does post properly, some moderator will decide to remove the moderation. I'm not sure automation is in order here in the general case. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Need help for small non-profit
On 7/30/06 6:32 PM, William Yardley [EMAIL PROTECTED] wrote, answering Marty Beilin: There are some third party providers who might do a good job for you (listbox comes to mind), or there are providers with free or discounted services for non-profits who provide Mailman. Electric Embers is one such (although they may use something other than Mailman for lists) http://electricembers.net/ I know of one organization satisfied with their services (out of one I know who has tried them). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Quick spam regex question
On 7/17/06 12:31 PM, Jason LaMar [EMAIL PROTECTED] wrote: from [EMAIL PROTECTED] (for example) Mark has answered your question well. I'm just jumping in as I sometimes do to point out that any likely example domain name one comes up with is likely taken. This one is relatively new in that context, only going back to 1997. This particular fubar is Films Unlimited Blizzards Avalanches and Rainstorms (not what we thought at all ;-) ) example.com is guaranteed never to exist, and is useful for purposes of examples. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails?
On 6/22/06 9:51 AM, Chris Northwood [EMAIL PROTECTED] wrote: I'm at a total loss as to what's going wrong, especially as the logs are showing nothing, but Exim is saying completed. You've solved the problem, and the completed wasn't related to the problem, so this is just a note. Exim's completed doesn't necessarily mean I've delivered this. It means I've done everything I'm ever going to do with this. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman and fault tolerance
On 6/22/06 11:11 AM, Mark Sapiro [EMAIL PROTECTED] wrote: It depends on how the server died and whether Mailman (specifically OutgoingRunner) was sent a SIGTERM and given a chance to wrapup. The outgoing message (containing a recipient list in its metadata) is placed in Mailman's 'out' queue where it is picked up by OutgoingRunner. At this point it is deleted from the out queue and exists only in memory. OutgoingRunner calls the DELIVERY_MODULE (normally SMTPDirect) to actually pass the message to the outgoing MTA. If the 'plug is pulled' on this process, the current SMTP transaction is lost as are the subsequent transactions on behalf of 'the rest' of the recipients. Hmmm. That processing is contrary to the spirit of RFC 822 and 2822, which require MTAs (which Mailman is not, so it doesn't apply) to always have a message copy on non-volatile storage (usually disk) until the next step in the chain has signaled OK going out, and to not signal OK until the message is in non-volatile storage coming in. This seems to be a hole which shouldn't and needn't exist. (That RFC requirement is one of the main reasons that MTA performance is so often disk limited, not processor limited, although the need for incessant filtering caused by spammers and virus folks and phishers is changing that--but even so processors are gaining faster than disks are.) --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] new users get welcome e-mails but posts aren'tgoing out
On 6/15/06 1:03 PM, Rabinowitz, Ari (Exchange) [EMAIL PROTECTED] wrote: Try checking to see if postfix is configured to only listen on the loop-back interface (localhost 127.0.0.1). You should check the inet_interfaces value in main.cf. If it says inet_interfaces = localhost then that is probably your problem. Change it to inet_interfaces = all (or just comment out the line since the default is all) and do a postfix reload. Then try the port scan again. netstat -ln -p tcp works in Mac OS X. One should expect to see either 0.0.0.0.25 (Postfix listening on all active addresses), or 127.0.0.1.25 (which the experiment using localhost showed is working) plus at least one other suitable IP address.25 If Postfix is listening, then either its logs will have useful information or more likely the firewall needs attention. (My usual netstat -ln produced between 2 and 3 screens of output in my 44-line window, hence the -p to reduce output. Apple passes LOTS of stuff around via sockets.) --John (who no longer has Postfix active on his Mac OS X machines) -- 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] Web based interface not working
On 6/13/06 12:24 AM, jon lanclos [EMAIL PROTECTED] wrote: When I click on the link to go to the web interface - I get the following message ... Safari can¹t open the page ³http://mail.corporates.com/mailman/admindb/everyone² because it could not connect to the server ³mail.corporates.com². In Terminal, type the command host mail.corporates.com Do you get back a sensible address? From here, I get # host mail.corporates.com mail.corporates.com has address 216.61.158.217 but things might be set up so that you get a different, LAN-based address. From here, port 80 connections to 216.61.158.217 are immediately refused, but that might very well make sense if use of that server is restricted. # telnet 216.61.158.217 80 Trying 216.61.158.217... telnet: connect to address 216.61.158.217: Connection refused telnet: Unable to connect to remote host: Connection refused If Safari gets the same sort of response from its connection attempt (also a telnet, although that's hidden from you), you are seeing the proper display of the error by Safari. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Some Subscribers Receiving 2 Copies of Each Message
On 6/12/06 10:57 AM, David Andrews [EMAIL PROTECTED] wrote: Others on the list do not have this problem, but he forwarded two copies of a message to me, so I know it is true for him. The messages looked identical to me. Start by examining the Received: headers on the two copies of a duplicated message. The point where they diverge, reading bottom up, (if they do) is the point at which the duplication happens. If they don't diverge at all, then the problem happens after the last recorded Received: header, meaning as the messages go into his mailbox or after he retrieves them. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Members list settings
On 6/9/06 5:10 PM, Mark Sapiro [EMAIL PROTECTED] wrote: I like the latter idea which would allow, in the example of chunk size = 30, for a list of 31 to 60 members to be displayed in two pages rather than 20 or more. This can make it more difficult to find a particular member in a large list, but the 'Find member' function is probably better for this anyway. Other thoughts? I just put a supporting comment into the related RFE (782436). However, we need to remember that we got to where we are because people didn't like the old (1.0.x) way of doing this. The page size choice might have been the better way to fix that. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Members list settings
On 6/8/06 6:50 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Eli Tuber [EMAIL PROTECTED] Date: Thu, 8 Jun 2006 21:38:08 -0400 To: mailman-users@python.org Is there a way to not change over to alphabetical view of the members list once it has over N number of users? I have about 25 emails and would rather see them all in one page then broken down by letters. It makes it easier when I have to disable a couple of users from receiving an email and then turning them back on. No, but you can increase the value of N for a list. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.030.htp I always worry about changing default values, but in this case the world has changed. Is 25 still the right default in this age when few list owner/admin folks are on dialup? Just one more thing to contemplate. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Second request - Code edit question.
On 6/5/06 1:44 AM, 7D [EMAIL PROTECTED] wrote: Can someone PLEASE help me with editing the canned standard confirmation emails for subscribing and unsubscribing to lists? basically a customer wnats to remove the reference to the web inteface method of confirming the requested action. Any help in getting this takenb care of would greatly be apprecaited. Brad and Mark have provided the answer. If one is part of an organization which tries to train its people not to click on links in email--a reasonable training goal in today's malware world, it seems wrong for that organization's mailing lists to send out email which strongly encourages clicking on such links. Having not found that idea in the Feature Requests section on SourceForge, I have added item 1501086 there covering it. --John (who normally discards list messages with subjects containing Second request and the like, but didn't this time) -- 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] password reminders, subscribers with [EMAIL PROTECTED]
On 6/1/06 7:51 AM, Dewhirst, Rob [EMAIL PROTECTED] wrote: I have a mailing list set up to send monthly password reminders. Today, two of these reminder messages ended up in the Administrative requests for the list as being posted to the list from non-members. Coincidentally, the subscriber's email addresses are [EMAIL PROTECTED] Their email address usernames are the same as the name of the problematic list sending out the password reminders, but their complete email address is in another domain. I am running Mailman 2.1.8 on RHEL4 with Exim. Any ideas? I suppose I could post headers if this is not clear. Exim is seeing just the local part of the addresses when it processes aliases. I don't know how RedHat is packaging Mailman--assuming that's how you installed Mailman. I see that our installation would have the same problem, now that I look at our Exim configuration on the Mailman machine: mailman_router: driver = accept require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm+* : -join : -leave : \ -owner : -request : -admin transport = mailman_transport In other words, if the local part of an address matches a list name, exim will treat the address as something to send to the list. Now that you've pointed out the problem, it would appear that the school solution for Exim configuration for lists is flawed. (And has worked at many sites for many years.) I think there should probably be something like domains = +mailman_domains as a condition in the router. Where that list would be defined in the early part of the configuration as something like domainlist mailman_domains = mailman.example.com : lists.example.com as needed (the above would be right for us were we example.com). An Exim macro could also be used, as was done with MAILMAN_HOME in the above. The above is top-of-the-head, and untested. I wonder whether the published solution ought to be changed. Note that if one is doing virtual domains--in the limited way Mailman does it now, it would be better to fill the mailman_domains list by reading a file, which could be managed by whatever software establishes lists in domains. When Mailman begins allowing real virtual hosting, the Exim solution will need to be changed, perhaps using a series of routers imported from a file managed by the management software (Exim does handle import statements in its configuration file--a feature which the stock Debian configuration for Exim exercises heavily). -- 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] Can't run mm_cfg.py
On 6/1/06 9:30 AM, Carl Fink [EMAIL PROTECTED] wrote: On Thu, Jun 01, 2006 at 11:18:04AM -0500, Brad Knowles wrote: When the configuration is done in the Python language in a Python script, you can let Python do all the parsing, and do the equivalent of #include in order to pull in all your configuration details. Fair enough. A downside is that there is no proper place for Defaults.py and mm_cfg.py They are configuration, so they go into /etc somewhere. They are executable, so they DON'T go into /etc. Not a problem with the stock Mailman layout, but it does cause problems for one trying to match the file system standard (such as the Red Hat packaging of Mailman, which shotguns Mailman into several different places--and is well done). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can't run mm_cfg.py
On 6/1/06 1:10 PM, Carl Zwanzig [EMAIL PROTECTED] wrote: In general, I agree, but I question a language that relies on indent level for blocking and don't let you include blank lines for readability. I guess it's ok when you get used to it. But then again, I mostly work in tcl at this point... :-) Of course, YMMV And if braces for structure move into Python as a required thing (unlikely, as long as the BDFL is around, and he's much younger than I am), I stop with the version upgrades. The clearly visible structure was one of the first things that attracted me. As you say, YMMV. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] follow up: help request: new 1300 member list results inmostly bounces
On 5/25/06 11:13 PM, Brad Knowles [EMAIL PROTECTED] wrote: Mailman does intentionally add a header for Precedence: Bulk to all outgoing messages, as is appropriate for the function that it is performing. Actually, Precedence: list (As copied from the message I'm replying to.) This doesn't change the argument (much), and I agree with Brad's points. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Missing headers of postings
On 5/26/06 7:43 AM, Roland Studer [EMAIL PROTECTED] wrote: Suddenly postings on our Mailman (2.1.5) list are missing headers, the mails sometimes arrive without any Information about the sender or the subject. The headers From and Reply-to and Subject are missing. In addition I wanted to send a HTML-Email with an attachment: It wasn't displayed correctly, the display of the mail began with the following. --===0751753693== Content-Type: multipart/alternative; boundary=Apple-Mail-1-691538562 What could cause this, what can I do about it? My best guess is that the outgoing mail processing at devzone.ch has gone insane, based on what arrived at GMail. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Newbie questions
On 5/26/06 6:54 PM, Mark Sapiro [EMAIL PROTECTED] wrote: You don't have to send email commands in the subject. The body is processed too, but to answer your question, I don't feel uneasy about sending a list member password. They are mailed in reminders and we say not to use a valuable password. Although password reminders are going away in Mailman 2.2 in favor of a reset scheme. I am less cavalier about the list admin password. I am not bothered by the idea of sending it, but whenever I do send it in an email command or an Approved: header, I am extra careful about how the mail is addressed. I've mentioned before that part (only part) of the problem is that we call the thing a password. So people see password and plain text, and rightly respond with security anguish. So it's not a password it's a mumble token. (I don't know what mumble should be.) A lot less frightening. And as a side benefit, if it isn't a password some people will be less likely to use the same password they've used 10 other places, endangering their accounts at those places. --John (at least if you think I haven't forged myself) -- 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 do I make 'username' appear in the 'from' field instead of email addy?
On 5/24/06 5:57 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'd like it to display From: Teresa Some MTAs can be--and frequently are--configured to reject such a From: header, as it violates the email RFCs. Other mail systems may accept such a From: header but increase the message's spamishness because of the header. Users who are sensitive about their addresses should be trained to use throw-away addresses for mailing lists. (As I am, although this one is fresh, and I threw away the last one because of a change of direction at my ISP, not because it was getting spammed much yet.) My original address for mailing lists is now a nice honeypot--at least as much because I used it for Usenet as for mailing lists. Another approach which may (or may not) take off is to use something like --John http://xri.net/=johnbaxter -- 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] Messages discarded by ISP
On 5/20/06 4:46 PM, Antonio Dragone [EMAIL PROTECTED] wrote: Hi! I have configured a mail server with Sendmail on my office and mails are sent fine. I'm using MailMan to send a newsletter to a test list of five people, one from hotmail, one from gmail, one from yahoo and two from my ISP (including my address). The newsletter is sent fine to all of the recipients (I've checked sendmail queue) but for some reason my ISP is discarding the message for their addresses (hotmail, gmail and yahoo are working fine). I suspect the problem is related to the headers sent by MailMan because when I send the newsletter directly from my mail client trough my office server, it is received without problems (the only difference between the one sent by MailMan and the one sent by my mail client is the headers). Is there some special header sent by MailMan that is well known as some kind of SPAM header? The obvious one is Precedence: list But that's a silly thing to filter on, and it is correct for Mailman to insert it. They might not like From: your address with them coming with the envelope sender. Or they might be running a silly challenge-response system All of those would essentially mean that one can't receive messages from mailing lists at that ISP (or that you have to configure something related to your account to allow it). Anyone else? --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman + exim, no mail to owners
On 5/18/06 9:26 AM, Anne Ramey [EMAIL PROTECTED] wrote: I've just switched over from sendmail to exim because of how well it (supposedly) works with mailman, but now none of my owner posts are going through...thus owners are not getting their notifications of pending posts, etc. It's happening for all my lists. This is what's in the mailman logs: May 18 11:43:51 2006 (1956) post to escml.field.all from [EMAIL PROTECTED], size=5185, message-id=[EMAIL PROTECTED], 2 failures And there is nothing in the exim log. Since the message are getting to mailman, I don't think it's a problem with exim delivering the message to mailman, but there seems to be some error in processing the data. They just keep sitting in the retry queue. I'm not sure what to try next, please advise. If you mean there is nothing in the Exim log literally, then either you've turned off all logging in Exim--I'm not sure that's possible--or you're looking in the wrong place for the Exim log. At the least, there should be evidence of the message being delivered to Mailman. If you mean there is nothing in the Exim log related to the messages Mailman should be sending, then my best guess would be that Exim is not accepting port 25 connections from localhost (assuming Exim on the same machine). You could try, on the Mailman machine, telnet localhost 25 That should be rejected, timed out, or responded to with Exim's banner. If you get a banner, next issue the quit command. Let us on the list know what happens, and we'll have a chance to work through this further. --John (whose list address will shortly change to [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] mailman + exim, no mail to owners
On 5/18/06 10:24 AM, Anne Ramey [EMAIL PROTECTED] wrote: Anne Ramey wrote: I've just switched over from sendmail to exim because of how well it (supposedly) works with mailman, but now none of my owner posts are going through...thus owners are not getting their notifications of pending posts, etc. It's happening for all my lists. This is what's in the mailman logs: May 18 11:43:51 2006 (1956) post to escml.field.all from [EMAIL PROTECTED], size=5185, message-id=[EMAIL PROTECTED], 2 failures And there is nothing in the exim log. Since the message are getting to mailman, I don't think it's a problem with exim delivering the message to mailman, but there seems to be some error in processing the data. They just keep sitting in the retry queue. I'm not sure what to try next, please advise. Let me add that the main mailman messages are going through fine, and I see those sent in the exim logs, it is just these owner posts that don't show up in the logs. Yes, it appears that exim is configured correctly, and like I said, the mail is getting to mailman to be posted to the owner fine, it's mailman that doesn't seem to be able to handle it. OK (I really think I should have read that last part into what you wrote first--sorry). At this point, I'm having trouble imagining what is going wrong. I can see a failure if the The list administrator email addresses. box on the General page contains a bare local part, with sendmail having been configured to qualify that and Exim not so configured, but I have trouble coming up with customized Exim logging settings which would totally suppress the logging of the unqualified address error that would result, while letting Exim logging for proper messages happen. And Mailman wouldn't know the difference--it would do what it's always done. The same logging argument would apply to Exim believing it isn't allowed to relay the message to owner to whatever machine that would be a relay to. It's someone else's turn. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Announce-list only.
On 5/18/06 11:13 AM, Fabiano Breves [EMAIL PROTECTED] wrote: Thanks Todd, I tested the method of using the first line with Approved: password. I would like to know how can I use the Header way. I don't know how insert it on the header of the message... I don't see a way to add a header to outgoing mail in Gmail (from which you sent your question). I checked the Settings area and Help. I can understand why it isn't allowed. (Of course, I might have missed something.) If you tell us what other mail programs you could use to send, we would have a chance to help further. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman vs yahoogroups
On 5/2/06 10:00 PM, Brad Knowles [EMAIL PROTECTED] wrote: From the Mailman side, the canonical answer is FAQ 1.26 at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.026.htp. I *think* that the m2f discussion in the above article is stale. The m2f stable release seems to be at 1.01. (Their web site and my habits for reading web sites do not correspond well.) I'm not sure enough to try to make a change. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Getting duplicates when people CC list
On 4/30/06 1:28 AM, Tony G [EMAIL PROTECTED] wrote: It seems I am getting duplicate messages from mailman v2.1.5 when senders send both TO and CC to the list. For some reason no one else in the list is acknowledging this issue so I look like an idiot complaining about it, but I'm seeing several instances of it per day. I'm seeing duplicates too, reading in Microsoft Entourage (which differs greatly from Outlook). I haven't taken the time to analyze them (delete works fine). Since some of them are in threads crossposted to users and developers lists, I see four copies of those. Two copies of a message with this Message-Id: Message-Id: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] reached me through the developers list (based on the List-xx headers) This is the one in which Barry started out I agree that we need a lot more data And two more copies came via the users list. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Getting duplicates when people CC list
On 5/1/06 7:47 AM, John W. Baxter [EMAIL PROTECTED] wrote: On 4/30/06 1:28 AM, Tony G [EMAIL PROTECTED] wrote: It seems I am getting duplicate messages from mailman v2.1.5 when senders send both TO and CC to the list. For some reason no one else in the list is acknowledging this issue so I look like an idiot complaining about it, but I'm seeing several instances of it per day. I'm seeing duplicates too, reading in Microsoft Entourage (which differs greatly from Outlook). I haven't taken the time to analyze them (delete works fine). Since some of them are in threads crossposted to users and developers lists, I see four copies of those. Two copies of a message with this Message-Id: Message-Id: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] reached me through the developers list (based on the List-xx headers) This is the one in which Barry started out I agree that we need a lot more data And two more copies came via the users list. Tony, I think you need to review your Outlook rules. My duplications are produced in our mail server's mail sorting process, and the key is the presence of prefixes for both -users and -developers in the Subject: lines of the problem messages. Considering only the two copies from the Developers list, the divergence appears to be in our mail processing. The messages arrived our our world-facing machine with the same Exim Id: Received: from smtp-vbr8.xs4all.nl ([194.109.24.28]:3979) by entiat.olympus.net with esmtp (Exim 4.42) id 1FaYCW-0006pK-O1 for [EMAIL PROTECTED]; Mon, 01 May 2006 06:12:33 -0700 and Received: from smtp-vbr8.xs4all.nl ([194.109.24.28]:3979) by entiat.olympus.net with esmtp (Exim 4.42) id 1FaYCW-0006pK-O1 for [EMAIL PROTECTED]; Mon, 01 May 2006 06:12:33 -0700 (ie, the same). And having looked at the server logs, I now know what is happening in my case. I have our mail processing sort list mail into IMAP folders based on--in the case of these lists--the presence of the subject prefix, and these messages have prefixes for both lists in the Subject: header. So my copy for -users gets sorted into my folders for -users and for -developers, and my copy for -developers gets sorted into -users and into -developers. Note: the next revision of our mail processing will allow sorting based on arbitrary headers--the List- headers for example. -- 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-Developers] Sender field
On 4/29/06 8:00 AM, Stephen J. Turnbull [EMAIL PROTECTED] wrote: Sender doesn't instruct *conformant* MTAs at all, does it? AFAIK the only thing that a RFC 2821-conforming MTA looks at is the Return-Path header, and it's supposed to remove that. There is no Return-Path: header during transmission of a message. The Return-Path header is added in the process of delivery. There is a return path, stated in the MAIL FROM:[EMAIL PROTECTED] SMTP command. (That command *can* have more stuff related to authentication.) The return path is what should be used as the address of a bounce if a mail system foolishly accepts a message and then creates a bounce. Notice that if an MTA rejects a message (or one or more of the recipients of the message), it is not bouncing or creating a bounce. It is issuing an error response...the MTA (or MUA in the case of message submission) that was trying to send creates a bounce message if appropriate (for message submission, the MUA notifies the user--or pretends to: Microsoft by default hides the notification remarkably well). While multi-line text associated with the rejection code is provided for, MUAs are very poor about showing it if a submission is rejected--some show only the first line; some only the last line. Even some MTAs improve the text of the rejection. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Message HTML/Plain text. Wish client display HTML when possible
On 4/29/06 7:50 AM, Thomas Carpentier [EMAIL PROTECTED] wrote: Sending a message in both Plain Text and HTML doesn't seem to be a solution. Apple mail displays the Plain Text only (as immediate alternative). Eudora displays the two parts, plain text and HTML. No idea about others programs. Apple Mail as shipped prefers the HTML part. Using defaults write blah, blah in Terminal one can (and I have) set Mail to prefer plain text. Either way, the other form can be displaying using Command-] (short for View--Message--Next Alternative). However, in this case, you control the sending (you are the one who sends to the newsletter). You could split the list into two lists, one preferring plain text and the other preferring HTML, and then send messages with only the right form to each list. The Mac-related TidBITS newsletter works that way (with a third alternative of HTML with article headlines linked to the stories on the web site). It appears that, using Thunderbird, you would prepare the HTML version of the newsletter, and send it to the address of the HTML-preferring list, whose address would be marked in the Thunderbird address book as preferring HTML mail. Then you would select the message in the sending account's Sent folder, and use the Message--Edit Message as New command. Change the address to that of the plain text list. In Thunderbird's Preferences in the Composition tab, on the Configure text format behavior line, click the Send Options... button. In the upper box, set the popup to Convert the message to plain text. Suggestion: if you go this route, tune up your Thunderbird settings by sending to a couple of addresses which are NOT lists, until you get it right. With luck, that will help you avoid annoying the list members with failed tests. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] [Mailman-Developers] Sender field
On 4/28/06 6:06 AM, Barry Warsaw [EMAIL PROTECTED] wrote: On Thu, 2006-04-27 at 22:46 -0500, Brad Knowles wrote: If the previous value of the Sender: field is being lost, then that should be corrected. At the very least, the value should be saved in an Old-Sender: or Previous-Sender: or some other suitable renamed sender field. Probably Original-Sender: Probably, indeed. But what happens if that header was already taken in the process that brought the message to mailman for distribution to the list? (As usual, I have only questions, not answers.) --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] error install MM on MAC OS x
On 4/25/06 8:43 PM, Mark Sapiro [EMAIL PROTECTED] wrote: You need to install the Apple Developer Tools package that is on the Mac OS X CDs/DVDs that came with the computer or contained the OS upgrade you have installed. If you don't have the CDs/DVDs, you can download the Developer tools from Apple, but you should have the disks. The Developer Tools version on the Tiger DVD (the DVDs I have, at any rate) is not the current version, but that shouldn't matter for compiling Mailman (a task I've never attempted since I don't want to run Mailman on my Macs). The upgrade download is smaller than the full download, if I remember correctly (I usually set the machine to the task of downloading and go away). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can someone refresh my memory?
On 4/26/06 12:30 PM, Tom Ray [EMAIL PROTECTED] wrote: Our mail server crashed and we didn't have a back up of the Exim configuration file. We had some mailman lists running and I remember there was a command I put up at the top on the configuration file but I can't remember what is was. Can someone refresh my memory? I believe it was something along the lines of MM_LISTS=lists.list1.tld:lists.list2.tld Am I right? I already have the MAILMAN_HOME and MAILMAN_WRAP already set. We don't have (or need) a list of the lists in the Exim configuration. Exim learns that a local part refers to a list by asking the file system (with the require_files doing the file system query and the two local_part_suffix things doing the work of turning, say listname-join, into listname for the lookup): mailman_router: driver = accept require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm+* : -join : -leave : \ -owner : -request : -admin transport = mailman_transport --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can this be done with Mailman?
On 4/24/06 2:28 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Then my questions are what would the purpose of this archive be? and in what way would members find it useful? A crutch for users who don't archive their own outgoing mail is the only thing which comes quickly to mind. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] get members list
On 4/8/06 7:35 PM, Ed [EMAIL PROTECTED] wrote: so it doesn't tend to get a chance to annoy me more than occasionally. :) YOU are lucky -:) !! The continuing outcry against the old way was the reason the alphabetic way was tried. The old way produced pages of 30--I think--addresses (count was modifiable), with an index of available address ranges presented on each such page. For small lists, the two ways are equivalent (except for the odd-looking one-entry index if the old way showed that--I forget). For huge lists, the larger alphabetic pages get broken into parts anyhow, but at least there are fewer parts to consider. For in-between sizes, the amount of complaining seems to vary with the connection speed of the person(s) using the member list. Various ways to improve matters have been discussed. I tend to favor gathering initial characters (not always letters) together to make up one (configurable-max size) page. Even fairly large lists might have just one page devoted to addresses starting with digits, that way. The modern way would probably be to publish a web service which sends out the list in XML, and a couple of working sample programs which display according to different tastes, with the XML described clearly enough that more display programs would be written (and contributed, one hopes). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Protecting Administrators
On 2/22/06 9:23 PM, Mark Sapiro [EMAIL PROTECTED] wrote: If you look at the Received: headers in your incoming mail, the one at the top (last one added) will give the name of the server that your mail was finally delivered to. Just use that host name in your email address to completely bypass Postini. Maybe. But not if the ISP has configured that MTA to reject port 25 connections from any sending machines except Postini's . So the method needs to be tested from an outside address (Gmail accounts are handy for this sort of thing, in addition to being handy generally). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Displaying message sender
On 2/21/06 3:27 PM, Matthew Thompson [EMAIL PROTECTED] wrote: I have a mailing list with users subscribed from two particular domains, call them nice.com and naughty.com. The security czars are naughty.com have decided that inbound email with naughty.com in the From address cannot possibly be legitimate so they silently drop the mail. The result of this is when users from nice.com send email to the list, everyone gets the message just fine. However, when someone from naughty.com sends a message, only users at nice.com get the message. One way around this is to make the list anonymous but that creates the problem that we don't know who sent the message unless everyone always remembers to mark the messages either in the subject line or at the end of the message. You know your institutional requirements and I don't. However, I don't think I would do anything to accommodate naughty.com's users. Let them use an address elsewhere for dealing with your mailing list. --John the Churl -- 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] Displaying message sender
On 2/21/06 3:27 PM, Matthew Thompson [EMAIL PROTECTED] wrote: I have a mailing list with users subscribed from two particular domains, call them nice.com and naughty.com. By the way, almost any domain whose name one invents for purposes like this exists. nice.com has existed since 1992 (or earlier), and naughty.com since 1996 (or earlier). --John [Not to mention at.com since 1993 and atdot.com since 1998.] -- 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] Is there a workaround to this?
On 1/29/06 11:18 AM, Jp Possenti [EMAIL PROTECTED] wrote: So basically there is none yet. Hopefully in the future there will be. I don't want to hack anything really, just don't feel comfortable enough, and it maybe breaking something else in the long run after an upgrade or update. The fix will come from Microsoft, when they decide to make Outlook behave sensibly. (It's quite possible that they view the behavior as making sense for mail passed from one Outlook user to another via a single in-house Exchange server (or even a nest of in-house Exchange servers.) --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman stagger script?
On 1/25/06 7:21 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I was told by my hosting company that I need to pick a mailing list manager for my 14,000+ subscriber e-mail list that would stagger the sending of the email to something like 300 e-mails per hour to lower the impact on the server. I already have Mailman installed, and the entire list currently sits there. Is there any way to do this with Mailman? If you expect more than four messages per week to be sent to the list, then you can't do this with any mailing list manager. (If I can still do arithmetic, it would take about 44 hours to send 14,000 messages at 300 per hour.) I think you need a different hosting company. Aside from that little detail, this general question has come up several times recently, and as far as I know the answer remains no. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman stagger script?
On 1/25/06 7:40 AM, John W. Baxter [EMAIL PROTECTED] wrote: On 1/25/06 7:21 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I was told by my hosting company that I need to pick a mailing list manager for my 14,000+ subscriber e-mail list that would stagger the sending of the email to something like 300 e-mails per hour to lower the impact on the server. I already have Mailman installed, and the entire list currently sits there. Is there any way to do this with Mailman? If you expect more than four messages per week to be sent to the list, then you can't do this with any mailing list manager. (If I can still do arithmetic, it would take about 44 hours to send 14,000 messages at 300 per hour.) I think you need a different hosting company. Aside from that little detail, this general question has come up several times recently, and as far as I know the answer remains no. Oops. That was a little too strong, if the hosting company means 300 messages, not 300 recipients. You would need to NOT turn on personalization, or VERP, and you would probably need to turn off the monthly password reminders. Given that, you would still run into the answer that no, Mailman doesn't throttle. But some other list management software might work. Go to the Mailman FAQ (link in the footer to this message) and search for throttle for more information. Rather than a whole new hosting company, you may want to look for a separate host for your list, one that specializes in lists. You would then need list mailing addresses like list.example.com rather than example.com, so the world can direct the mail properly, and the same for the web interface. Such a hosting company might prefer software other than Mailman, or might prefer Mailman. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] virtual domains problem
On 1/3/06 9:29 AM, Sean Roe [EMAIL PROTECTED] wrote:
The macro
MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
is later used in a list context
require_files = MM_LISTCHK
So I to would expect the : in $(lc:$local_part) to have to be doubled. But
what seems to be happening is that the second of the pair of colons is being
picked up as part of the string to be lower-cased.
You could make certain that the colon *doesn't* need to be doubled by
changing the list separator character in the require_files option:
require_files = ; MM_LISTCHK
If you do that, then for sure you only need a single : in the MM_LISTCHK
macro. (You need to do the same magic other places the macro is used in
list context.)
--John
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Released: Mailman 2.1.7b1
On 12/25/05 11:57 PM, Ralf Hildebrandt [EMAIL PROTECTED] wrote: * John W. Baxter [EMAIL PROTECTED]: It doesn't look folded correctly in Ralf's message as received here. I don't see whitespace after the CR LF. Thus the second part isn't a proper continuation of the header. Oh, correct. I didn't notice this either. Good point!! This lack of white space could, of course, be an artifact of the tortured path the header has traveled to reach my screen. Ralf, it would be useful to know what version of Python you are using with Mailman. As I read CookHeaders.py, the relevant code there looks right with respect to folding headers, but it is subject to correct behavior in the str() operation applied to an email.Header object. That is, the email.Header.encode() function. This code has greatly changed between Python 2.3 and 2.4, and I'd rather not work on understanding both forms. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Released: Mailman 2.1.7b1
On 12/29/05 11:11 AM, Ralf Hildebrandt [EMAIL PROTECTED] wrote: * Ralf Hildebrandt [EMAIL PROTECTED]: So I should go for python 2.4? I installed python2.4, stopped the queuerunner and linked /usr/bin/python2.4 - /usr/bin/python and restarted the queuerunner. The problem seems to remain. So, I had a closer look: 1) mutt displays the Subject: header OK. 2) Postfix still shows: warning: header Subject: [webKess] webKess Stations- / Abteilungsregistrierung??Elisabeth_KH.1049 in it's log, as before - but that's normal. When I saved the mail and opened in a hex editor, I found the two ? to be 0A (LF) 09 (TAB) Mark said: So Mailman has folded a long subject according to RFC 2822 section 2.2.3 This section says: The general rule is that wherever this standard allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP. But it's only a LF, not a CR LF -- and the space that used to be in the Subject: has been transformed into a TAB character instead. So I'm not sure if that's correct folding (even when if mutt displays it correctly!) Ah. There is a difference between the line endings on the wire, which the RFC is discussing, and the line endings on some particular machine. On the wire, the LFTAB sequence will (almost certainly) become CRLFTAB and then (probably) switch back upon arrival on a Unix machine. (Or stay as is on Windows or become CRTAB on Mac OS 9 and below.) The line-endingTAB sequence is good as it provides the whitespace needed to make the second part a continuation. As I recall, there was a mail program involved which didn't like the folded header? It appears that Mailman is doing the right thing. (At least the designed thing...the TAB rather than space bothers some, and the current code uses space if a header comes in folded by a space. That's what the little dance in CookHeaders.py is working out. TAB is used if an unfolded Subject: expands enough due to the prefix being added that it now needs to be folded.) John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Released: Mailman 2.1.7b1
On 12/24/05 8:23 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Ralf Hildebrandt wrote: As you can see, = Subject: webKess Stations- / Abteilungsregistrierung Elisabeth_KH.1049 was transformed into Subject: [webKess] webKess Stations- / Abteilungsregistrierung??Elisabeth_KH.1049 (?? denotes a non-8-bit character). I wonder why a mere space sign needs to be transformed... and ?? denotes 2 non-printable characters. I'd need to check which ones EXACTLY. Found out: It's a CR LF. So Mailman has folded a long subject according to RFC 2822 section 2.2.3, and it is not being properly unfolded by Postfix for logging. Or is there some other problem that I'm not seeing? It doesn't look folded correctly in Ralf's message as received here. I don't see whitespace after the CR LF. Thus the second part isn't a proper continuation of the header. This lack of white space could, of course, be an artifact of the tortured path the header has traveled to reach my screen. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] How to stop sendmail from spewing messages one itstarts?
On 12/8/05 6:12 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Paul Williams wrote: 1). A user added a large number of subscribers by uploading an Excel spreadsheet. Mailman accepted the file and addresses appeared reasonable when viewed with IE but not so good with mozilla (each alpha char was followed by a box). I was able to remove the names using the remove_members command by removing all members. It seems that it might be a good check when importing a list of users, for mailman to make sure it is a text file so users don't mess things up inadvertantly. What Mailman version is this? Current Mailman (2.1.6) is pretty good about weeding out addresses with non-printable ascii characters. In particular, it won't accept whatever characters were displaying as a 'box'. Is Excel perhaps producing UTF-16? 2). The second problem that developed is that the user has set notification on subscribing to yes and so she and her boss bere getting several thousand emails. I finally had to completely delete the list. Is there a better way to tell mailman to stop sending email from a specific list? If that is possible, I have not bumped into an explanation how mailman works so I would be able to stop it sending emails. Mass subscribe allows subscribing with or without notifications regardless of list settings. This is very much repairing the barn door after the horse is stolen, but for such mass subscribes from previously-untested data, sending through a sample of 10 or so addresses first isn't a bad idea. --John (cheering from the sidelines) -- 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 lists on a replacement list server w/different name
On 11/18/05 6:58 AM, Greg Earle [EMAIL PROTECTED] wrote: The old machine is running Majordomo and Sendmail, not Mailman and Postfix. Sorry if that wasn't clearer. So it's not a matter of just bringing lists/archives/etc. across, alas. It was very clear in your original post, but that detail quickly got left out in the process of quote-trimming. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Admin Password
On 11/10/05 5:55 AM, Bryan Carbonnell [EMAIL PROTECTED] wrote: On 10/11/05, Thomas Spuhler [EMAIL PROTECTED] wrote: On Thursday 10 November 2005 01:42 am, Stefan Henrico wrote: Hi guys Is there any way for me to retrieve my admin password? I was under the impression that I do know the password as I created a list not too long ago, but alas.. :) mmsitepass would give you the ste password. Actually mmsitepass SETS the site password. So Stefan, if you have command line access, you can use the mmsitepass command to set a new site password. And if history | grep mmsitepass shows you the site password, you should consider using the parameterless form of mmsitepass instead. I had forgotten that it could be used either with password in the command line (nice for scripting) or without (prompting for the password), until I checked just now. (It's a somewhat nasty exception to the fact that *most* things in ~mailman/bin give their usage if called with no parameters.) --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] HELP, using WIN XP Pro, Admin panel problems#2
On 11/10/05 9:12 AM, Bob Bales [EMAIL PROTECTED] wrote: - Original Message - From: Mark Sapiro [EMAIL PROTECTED] Subject: Re: [Mailman-Users] HELP, using WIN XP Pro, Admin panel problems#2 Your web browser is not accepting cookies. Mark, I have cookies turned on in both IE6 and in Firefox. Or at least they say they are on. Or the failing machine's clock is way off. Did it forget about the end of daylight time, perhaps? --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Posting problems to all users of our mailing list...
On 10/25/05 8:09 PM, Mark Sapiro [EMAIL PROTECTED] wrote: ISPs do lots of things with mail besides delivering it or rejecting it. Some ISPs will just silently discard mail they don't like. Thus in these cases, you won't see a bounce and the recipient won't see the mail and the ISP may not admit that this has happened. ISPs tend to think that it's to their advantage to protect their users from spam even if it means discarding some desired mail. The above is part of the destruction of email that the spammers have accomplished. Note that it's not just the ISP. We regularly get support calls about mail not being received, when the logs clearly show that the message was deposited into the user's mailbox and later picked up by the user's machine. Something on the user's machine (our users primarily run Windows of some vintage) has filed, dropped, or done whatever to the message. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Who can view subscription list?
On 10/20/05 7:19 PM, David [EMAIL PROTECTED] wrote: I have this checked as admin only but it showing to anyone whos subscribed? Any thoughts on this? Try with a different web browser (or after restart your browser, or you use the Logout command). Start the test sequence with a different browser, as that is the most like an ordinary user. I suspect you were simply using a browser which still knew (session cookie) that it had logged in as administrator. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Strange errors
On 10/19/05 11:14 AM, Dan Szkola [EMAIL PROTECTED] wrote: Mark Sapiro wrote: Dan Szkola wrote: Patched the admin script as suggested. When I saw the error this morning, I emailed to the admin address of our test list. Here is what I got: - Transcript of session follows - PYTHONPATH /usr/local/mailman I wouldn't have expected this, but I don't think it should matter. What do you get if you add to the patch as follows --- admin 2005-10-14 16:31:42.078125000 -0700 +++ admin_patched 2005-10-19 10:21:51.328125000 -0700 @@ -25,8 +25,16 @@ import sys +from os import environ +for env_var in environ: +print env_var, environ[env_var] +for s_path in sys.path: +print 'before =', s_path import paths +for s_path in sys.path: +print 'after =', s_path + from Mailman import mm_cfg from Mailman import Utils from Mailman.i18n import _ - Transcript of session follows - PYTHONPATH /usr/local/mailman AGENT sendmail before = /usr/local/mailman/scripts before = /usr/local/mailman before = /usr/local/lib/python24.zip before = /usr/local/lib/python2.4/ before = /usr/local/lib/python2.4/plat-sunos5 before = /usr/local/lib/python2.4/lib-tk before = /usr/local/lib/python2.4/lib-dynload after = /usr/local/mailman/pythonlib after = /usr/local/mailman after = /usr/local/mailman/scripts after = /usr/local/mailman after = /usr/local/lib/python24.zip after = /usr/local/lib/python2.4/ after = /usr/local/lib/python2.4/plat-sunos5 after = /usr/local/lib/python2.4/lib-tk after = /usr/local/lib/python2.4/lib-dynload after = /usr/local/lib/python2.4/site-packages Traceback (most recent call last): File /usr/local/mailman/scripts/admin, line 42, in ? from Mailman.Queue.sbcache import get_switchboard File /usr/local/mailman/Mailman/Queue/sbcache.py, line 19, in ? from Mailman.Queue.Switchboard import Switchboard File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 47, in ? from Mailman.Logging.Syslog import syslog File /usr/local/mailman/Mailman/Logging/Syslog.py, line 22, in ? from Mailman.Logging.StampedLogger import StampedLogger File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 20, in ? from Mailman.Logging.Logger import Logger File /usr/local/mailman/Mailman/Logging/Logger.py, line 25, in ? from Mailman.Logging.Utils import _logexc File /usr/local/mailman/Mailman/Logging/Utils.py, line 18, in ? import traceback ImportError: No module named traceback 554 5.3.0 unknown mailer error 1 Oddly, the correct path statement is the only one with a trailing slash. Have we eliminated the possibility that--due to some unfortunate event--there really is no traceback module (or it can't be read)? What do you get from ls -l /usr/local/lib/python2.4/traceback.py If it is there, does that file have world read permission? Do you have multiple Python versions installed? --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] attachements question
On 9/28/05 1:30 AM, Brad Knowles [EMAIL PROTECTED] wrote: Why archivers don't use Message-Id for the URL, I don't know. Because some MUAs generate message-ids that are likely to collide. In addition, the Message-Id values would have to be filtered, if used as is, for URL-unfriendly characters (eg, Outlook Express tosses in a couple of $ characters). Just another example of not trusting input from untrusted sources. The hash of Message-Id:, Date:, and Received: (all of the Received: headers) would do, except for the case of an insane MTA--the one generating the top Received: header--feeding the same message into Mailman multiple times. Perhaps a representation of the computer's clock would help there. There's also the small point that the presence of Message-Id: is a SHOULD, not a MUST (some compromise in the musty past of the IETF, no doubt). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman 2.1.2 and Python 2.4.1
Sorry, I haven't fully searched the FAQ and archives--I'm also guessing I wouldn't find the answer if I did. Does someone know without research whether Mailman 2.1.2 will run under Python 2.4.1. (Due to a disk failure, we're having to replace the build of a server, while mailman is running happily on the other machine. If we just let [most of] mailman get set up by our synchronization process, we'll end up with this combination of Mailman 2.1.2 and Python 2.4.1 on the restored machine.) Thanks. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] config.pck, apache, permissions and Errno 13
On 9/14/05 10:46 AM, Sam Gamgee [EMAIL PROTECTED] wrote: yes yes yes. I know that. but the results are not permanent. My problem is trying to find out why. If the fixes are not permanent, then something is fixing them. My memory of the thread says that this happens periodically. I've now forgotten what aspect of the fix isn't permanent in your case. If it is the setgid bit, then perhaps there is a periodic nanny process which removes dangerous setgid bits. If so, there probably is a these are OK list associated with the process. Traditionally, one looked carefully at what is run by cron...in some cases that no longer suffices...for example Apple has moved much of the periodic stuff out of cron into their launchd thing. (Which probably isn't really theirs, but Mac OS X is where I encounter the beast.) --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman stopped working after upgrade
On 9/12/05 7:58 PM, Mark Sapiro [EMAIL PROTECTED] wrote: The wrapper is telling you that it expects to be executed as group 'mailman', and it looks from what you've presented that it was in fact built that way. It also seems you can't change it in your update package. The wrapper also complains that it is not being executed as group 'mailman', but rather as group 'mail'. This is the confusing part because it seems from the above that you are telling Exim to invoke the wrapper as group 'mailman' yet the wrapper is telling you it is being invoked as group 'mail'. I would look carefully at the Exim configuration to be sure that MM_UID=mailman MM_GID=mailman are in the right place and are not being overridden somewhere else. Has Exim lost its setuid bit (and/or its root ownership) in the upgrade? --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Enabling personalization with Digest Mode?
On 9/2/05 2:53 PM, Mark Sapiro [EMAIL PROTECTED] wrote: David Morris wrote: I have a subscriber to digest mode whose ISP is mandating her email address be in the To or CC header. The only way I can see to do this is through personalization. I have seen where I can do that with non-digest messages, but I can't find where I can do that with Digests. I would prefer (for performance reasons) to not enable personalization for the larger list, and turn it on just for the digest list. Can it be done? If not, how can I work around it (running mailman on Debian Linux with exim4) Personalized digests are not supported in Mailman 2.1. I'm not aware of any work around for your issue. GMail, Yahoo Mail, etc. As I've said before, the spammers have broken email. This kind of requirement is just another example. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] max_num_recipients variable question
On 8/31/05 7:00 PM, Stephen J. Turnbull [EMAIL PROTECTED] wrote: John == John W Baxter [EMAIL PROTECTED] writes: John But yes, 10 recipients known to Mailman is the limit as set John up by the default value. Personally, I prefer a setting of John 1 (I hate broadcasting addresses into a mailing list). Does that actually work? Although 10 is too many (I don't think I've ever seen a non-spam/troll with more than 5 including the list on the lists I manage), most of the lists I manage have occasional valid reasons for cross-posting or adding non-member recipients. I would think the inconvenience would be greater with restriction to 1. I probably should have said I would prefer. As to cross-posting, for a list where that is natural, a setting of 1 would not work well. As to non-member recipients, that's why I would prefer a setting of 1. I don't think--in most cases--the addresses of such people should be broadcast to lists. If their spam filtering doesn't let Bcc-addressed messages through, then a separate send seems in order. [For the address I use for this and other work-related lists, it wouldn't matter...this morning Google shows 3600 hits on the address: it was ruined years ago, before the spammers destroyed email. The address does make a nice honeypot, though.] --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] max_num_recipients variable question
On 8/31/05 7:46 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Does max_num_recipients = 10 in the default configuration of the list, means that when I'm posting to the list I can additionaly write only 9 e-mails along with the list address and no more? If I'm writing more than 10 e-mail addresses along with the list address it goes to list admin approval? Is it for To Cc and Bcc alltogether? Generally, mailman won't learn of Bcc recipients (except itself). [Some mailers may still include the full Bcc header on Bcc copies of the message, as the RFCs still allow, but Mailman quite possibly doesn't bother looking, since that is rare.] But yes, 10 recipients known to Mailman is the limit as set up by the default value. Personally, I prefer a setting of 1 (I hate broadcasting addresses into a mailing list). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Some users do not get emails
On 8/26/05 4:04 AM, Tim Howes [EMAIL PROTECTED] wrote: Hi I am reasonably new to using mailman and I have a problem that I cannot trace. I have setup a list which is essentially private. I have managed to test the list by subscribing myself - however the main users of this list at Company A do not get any emails i.e. the initial confirmation email hence are not able to use the list. I have made sure that the different types of emails are in their spam program to be by passed i.e. listname-owner or listname-request@ I have also test by using hotmail accounts and gmail accounts and they seem to be fine. The only clue I have at present is that the log /var/log/mailman/bounce appears to have entries for this failed attempts. But I cannot be sure if it my setup that is preventing the emails are their system. Example log entry Aug 25 12:00:35 2005 (32397) bounce message with non-members of listname: [EMAIL PROTECTED] My mailman version is mailman-2.1.1-5 on RHE3 Thanks in advance for any pointers on this. If your message to the list came from the same host which sends the mailing list mail to the list, it is quite likely that companyA.com's mail server is refusing the messages. You list message entered the Mailman-users mailing list system here: Received: from dns0.ssi.uk.net (unknown [62.89.146.20]) by bag.python.org (Postfix) with ESMTP for mailman-users@python.org; Fri, 26 Aug 2005 13:05:30 +0200 (CEST) host 62.89.146.20 20.146.89.62.in-addr.arpa domain name pointer 62-89-146-20.pool.free.th.hotchilli.net. (Line broken by email client.) That IP is on the Spamhaus list, and likely many others. Check the log entries your MTA creates when you try to send a list message. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Reply to all with original destination and list destination
On 8/10/05 7:36 AM, Tiago Cruz [EMAIL PROTECTED] wrote: Stephen J. Turnbull escreveu: So the best solution is to configure the list server to leave the Reply-To header alone and you get a good mail agent. If you're stuck with a mail agent that has no reply to list command, then you're also stuck with the inability to implement the options you prefer. That's good enough and your letter solved my doubts, thanks! So, now I'm' going to spam the list of mozilla-thunderbird-devel asking for the button: I want a 'reply to list' button :-) Thanks again, have a nice day! Note that with Thunderbird, there could well be a plugin available that does what you want. Or not, of course. But it would be worth checking. --John (who has other reasons for not using Thunderbird) -- 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] Incorrect mail being received on mailman list
On 8/9/05 7:37 AM, Richard Hobbs [EMAIL PROTECTED] wrote: Hello, We have routers setup in exim, in the following order: - mailman_router: - dnslookup: - system_aliases: - userforward: - spam_router: - localuser: Lets say our domain is domain.com and we have one mailing list named fred. When emails are sent through exim to the address [EMAIL PROTECTED], they are actually accepted by mailman and delivered to [EMAIL PROTECTED]. This is obviously incorrect. Should mailman be reconfigured to only accept mail for particular domains, or do I have the routers in a non-perfect order? Any advice is very much appreciated :-) You have the routers out of order. You don't want to be doing local aliasing while messages for the world are still being considered by the routers. mailman_router after dnslookup should do the trick, given your router list above. --John (just bitten by a much more obscure version of the problem on one of our non-public machines) -- 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] Is this a mailman or postfix error?
On 7/28/05 4:13 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Does this setting change whether or not postfix runs chrooted or not? Well, the option probably doesn't change, but the locations of lots of things do change. For starters, if chrooted, Postfix couldn't find the wrapped CGI unless it were at the proper path inside the jail. Same may/should be true for what the CGI tries to reference, and so on. I'll leave the rest for someone who knows what he or she is talking about. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Setting Sender Name
On 7/18/05 5:09 PM, Jim Tittsler [EMAIL PROTECTED] wrote: On Jul 19, 2005, at 09:00, Tim Arney wrote: For my mailing list, I have it set so that the senders email address is masked with the list address. So for example, I presume if you receive a digest of this list then it would come from mailman- [EMAIL PROTECTED], not something like Mailman Users mailman-users@python.org. Does that clear up my problem? If you update to Mailman 2.1.6 (or at least replace your old Mailman/ Handlers/Cleanse.py with the current one (which you could fetch from CVS)), Mailman will use the 'description' field (of the General Options page) as the name associated with the list. Which I find to be a great nuisance, since the Description tends to be a bit longer than makes sense as the name portion of the address. I don't think a field should be used in two such disjoint places. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] REQ: member list with nomail
On 7/9/05 11:31 AM, Daevid Vincent [EMAIL PROTECTED] wrote: There should be a way under the Membership Management... section in the web UI to show all members who are set to 'no mail'. This way I can weed out users that are basically useless on the list. But no mail users aren't necessarily useless *to the subscriber*. They are, for example, a way to read the list at home but occasionally post from a work account (assuming a list to which only subscribers can post). I've been known to set some up behind the subscribers' backs, to cut down moderation delays and workloads, when I see a pattern. Nonetheless, I agree the GUI would be better with the option. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] SMTPDirect issues (Name or service not known)
On 6/11/05 9:39 PM, Mark Sapiro [EMAIL PROTECTED] wrote: I don't understand why SMTPDirect.pyc is not recreated. It should be created when OutgoingRunner.py is initialized. It does The typical--of Python generally--reason is that the process which does the import doesn't have permissions (on the directory) to create or replace the .pyc file. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Migration from Linux to MacOSX
On 6/6/05 10:06 AM, Carfield Yim [EMAIL PROTECTED] wrote: Thx for the information, however I get problem from the starting... where can I download the binary of mailman? I just have a mac mini which don't come with make and gcc. Besides, as I don't have other software need to compile, I would like prevent this process, do you know anywhere can download the binary? The Mini's DVD Mac OS X Install Disk 1 includes at the top level a folder Xcode Tools make, gcc etc are in there, but you'll need to run the installer inside the folder and install most of XCode (I think there may be a few things you can leave out...I don't, so I'm not sure). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Migration from Linux to MacOSX
On 6/5/05 1:41 PM, Heather Madrone [EMAIL PROTECTED] wrote: I'm running Mailman on OSX 10.2.8. The setup was straightforward Installation varies depending on which version of OSX you're running, and your preferred MTA. For some reason, a lot of versions of OSX come with sendmail preinstalled while others have postfix or nothing. sendmail was in the earlier versions of Mac OS X. Postfix--instead--showed up in either Jaguar or Panther (I ignored it in Jaguar). A positive change, IMHO. I haven't gone beyond the setup produced for me by the third party Postfix Enabler. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] What is the problem when...
On 6/4/05 4:51 AM, PeteBell [EMAIL PROTECTED] wrote: And is there any reason why emails to a mailman list from Gmail accounts should not get sent out? Well, Gmail inserts the very very long--and with few whitespace interludes--domain keys header. When I read one of those headers in Eudora (Macintosh, of course), Eudora breaks it on screen in such a way that it *appears* to break the header sequence. That isn't so, as I found by widening the Eudora window across a screen and a half...the header really is just one long line of--to be kind--stuff. Mailman (probably the Python Email module) may be having trouble with that. If the domain keys header is the problem, and it relates to the email module, poor Barry...he just tuned that up. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] how can moderators automatically subscribe users?
On 6/2/05 8:39 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Ricardo Kleemann wrote: I know that via the web interface this is quite easy. However, I have a need to be able to subscribe users via email commands, without the user being subscribed getting a confirmation email. In other words, someone asks to be inserted into the list, and then an email is sent with the subscribe command in it. Is this possible? I think that as long as subscribe_policy includes confirm, the subscribee will always receive a confirm e-mail from a subscribe (or join) e-mail command. This is at least in part because it's so easy to send a subscribe command for someone else. I've looked at the code, and I don't see that Approved: headers are handled in e-mail command processing. It's generally assumed that the list admin will use the web interface. As an RFE, allowing Approved: headers in this context would be a good thing to ask for. Adjusting the Python code to do so and offering a patch against Mailman 2.1.6 would also be feasible, if it matches Ricardo's talents or those of someone he enlists. It may also be that Mailman in the 2.x form isn't the right tool to use for solving Ricardo's problem. Mailman was built to be web-interface driven in part because lots of MajorDomo, LISTSERV, and others were tired of having to do things by email command (including me). And tired of waiting for the ever-receding MajorDomo 2. The email commands which are there are there basically so that list users could keep doing things the familiar way when their list was moved to Mailman. [I wasn't around during Mailman's early days--we first installed 2.0.6--I'm reading between the lines in writing this paragraph.] --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] how can moderators automatically subscribe users?
On 6/2/05 8:39 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Ricardo Kleemann wrote: I know that via the web interface this is quite easy. However, I have a need to be able to subscribe users via email commands, without the user being subscribed getting a confirmation email. In other words, someone asks to be inserted into the list, and then an email is sent with the subscribe command in it. Is this possible? I think that as long as subscribe_policy includes confirm, the subscribee will always receive a confirm e-mail from a subscribe (or join) e-mail command. Hmmm...another thought. A possibility would be to write a program (in whatever language is convenient and safe) which receives the email commands at some address not related to mailman, validates them for authenticity by whatever means (I'd be tempted to use PGP or GPG signatures here, and a sufficiently paranoid* person would add encryption), and then drives the Mailman command line tool which can add addresses without confirmation. There remains nothing in as-shipped Mailman through 2.1.6 which will do what Ricardo wants. --John * It's not paranoia if they really are out to get you. -- 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] short question, probably an FAQ that I've overlooked.
On 6/2/05 5:50 PM, Larry Stone [EMAIL PROTECTED] wrote: On 6/2/05 2:27 PM, Brad Knowles at [EMAIL PROTECTED] wrote: Proper mailing list management systems don't use blind-carbon-copies. The equivalent that they do use is to list multiple envelope recipients, whose addresses are not necessarily referred to on the To: or Cc: headers. Brad, I realize this is getting a little off of Mailman but how is that different from what a BCC does? A BCC header is local to the originating MUA - it doesn't appear in the transmitted message but the BCC recipients do become envelope recipients. So from the view of the MTA, isn't what you say Mailman does exactly the same as what the MUA does with a BCC? Not really. Some MUAs preserve the full Bcc header for anyone in that header, but removed it for the To: and Cc: recipients. Others set up a Bcc: header with just the individual recipient's address (clearly these talk to the MTA separately for each Bcc: recipient). And most remove it. All these behaviors are sanctioned by the RFCs (clearly a compromise in the RFC development process). Also, there are more knobs--outside Mailman--that can be messed with. I don't know how in Postfix; I never will know how in sendmail (I'm 66--I won't live long enough to learn sendmail). In Exim, it's a matter of settings in a transport, with routers feeding appropriate domains to the transport. So you could arrange to send large batches most places, batches of one to AOL, and batches of 5 to xyz.example.com, for example. Also, I don't believe that the original posting's 5xx response meant that the receiving site thought that your machine is an open relay--it guessed it might be because of too many invalid recipient addresses in one connection, which is typical of spamming through open relays (and spamming generally). --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] short question, probably an FAQ that I've overlooked.
On 6/2/05 6:07 PM, John W. Baxter [EMAIL PROTECTED] wrote: Not really. Some MUAs preserve the full Bcc header for anyone in that header, but removed it for the To: and Cc: recipients. Others set up a Bcc: header with just the individual recipient's address (clearly these talk to the MTA separately for each Bcc: recipient). And most remove it. All these behaviors are sanctioned by the RFCs (clearly a compromise in the RFC development process). What I didn't say and should have is that the MTA used for submission may also play a role in this process. There's a lively discussion in the exim-users list archives (sorry, no URL handy). That discussion included a rehash of the issue on the appropriate IETF list (requested by Exim's developer, Philip Hazel--also the father of the PCRE code). The essential result was that MTAs when not acting in submission form as part of the MUA should leave any Bcc: headers alone. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailman simply *stops* sending messages
On 5/20/05 3:23 PM, Rob Scott [EMAIL PROTECTED] wrote: moral of the story: Python hates the French almost as much as Dubya does.. Or perhaps Python's code likes the RFCs. From RFC 2183: NOTE ON PARAMETER VALUE LENGHTS: A short (length = 78 characters) parameter value containing only non-`tspecials' characters SHOULD be represented as a single `token'. A short parameter value containing only ASCII characters, but including `tspecials' characters, SHOULD be represented as `quoted-string'. Parameter values longer than 78 characters, or which contain non-ASCII characters, MUST be encoded as specified in [RFC 2184]. an accented e is a not-ASCII character. If the sending MUA didn't encode it, it's an MUA error (this is NOT a new RFC)--dated in 1997. If the MUA did encode the name, and Mailman decoded it and then choked on the result later, that would be a clear Mailman error. --John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Setting sitewide defaults that can't be changed?
On 5/18/05 2:09 PM, Mark Sapiro [EMAIL PROTECTED] wrote:
Mark Sapiro wrote:
Alternatively, I *think* (Warning! I don't know what I'm talking about)
you can just remove the Mailman/Gui/Archive.py* files alltogether AND
put
ARCHIVE_CATEGORIES.remove('archive')
DEFAULT_ARCHIVE = Off
in mm_cfg.py to remove the Archiving Options completely and default
'archive' to Off for new lists.
Oooops. That should be
ADMIN_CATEGORIES.remove('archive')
I really thought the Original Poster enquired about maximum message size,
not archiving. Perhaps I missed a transition.
--John
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
