[Mailman-Users] disabling delivery of emails and yet be able to post
Hi, I did not find an answer to this question in the FAQ. It beats me as to why this feature has been ignored all this while. I am an infrequent poster to many mailing lists powered by mailman. In most cases, I am not interested in receiving neither digests nor individual emails from the list, but yet on an occasional day I would like to post to list. I check the archives on an irregular basis. Turning off the delivery of emails unfortunately disables posting. So I will have enable/disable each time before/after I want to post. Is there a better way? thanks, Krishna. -- 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] Load-balancing mailman between two servers
At 3:03 PM +1100 11/27/06, Guy Waugh quoted Kim Hawtin: How/where do you share the incoming mail list aliases that sendmail checks? Also when you create a new list, how to you update the other hosts aliases? On each server, in the sendmail aliases file. So, when adding or removing a list, I have to do the alias changes on each of the two servers. Hmm. With postfix, you can specify multiple alias files, some of which will get auto-rebuilt as necessary by postfix, others which can get manually rebuilt by other processes (like by Mailman, with the standard tools it provides). It's been a while since I mucked around with sendmail, but I have to believe that the same is possible there. Indeed, I believe that the technique that is currently used to completely automate this process with postfix was adapted from the technique that previously worked only with sendmail. You could put that second set of aliases in the NFS shared space, so that you shouldn't have to rebuild that separately on the two boxes. One thing I am a bit concerned about is contention on the shared files between the two servers. If, for example, both servers wanted to update the same .pck file at the same time, I'm not sure what would happen... would one server lock the file and the other server wait for the lock to be released, does anyone know? Or would chaos ensue? The developers of Mailman have gone to great lengths to make the system as NFS-proof as possible. That is to say, it should be possible to share the entire /usr/local/mailman structure via NFS (or wherever you put all the Mailman files, including archives, queue directories, etc...). It should just work. That said, file locking on NFS is problematic during the very best of times, and I believe that the Mailman developers have gone to great lengths to try to work around that. But, by putting that stuff on NFS, you are increasing the chances that you'll run into a situation where you get lock contention, or maybe stale locks that will need to be cleared out. You will increase the amount of system maintenance that you have to do -- that's simply unavoidable. And a very great deal depends on your NFS server. Putting all this stuff on NFS can cut your throughput that you can handle by a great deal -- orders of magnitude or more, and that's if you've got a high-end mega-expensive dedicated NFS fileserver from the likes of EMC, Auspex, or Network Appliance. Just keep this in mind as you program for redundancy. I'm not saying that you can't put things on NFS, or that it's even unwise. I am saying that everything is a set of trade-offs, and you've got to understand what it is that you're trading for what. -- Brad Knowles, [EMAIL PROTECTED] Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. -- 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] disabling delivery of emails and yet be able to post
At 1:12 AM -0700 11/27/06, Krishna Mohan Gundu wrote: Turning off the delivery of emails unfortunately disables posting. So I will have enable/disable each time before/after I want to post. Is there a better way? This is not the way it works with any version of Mailman I have ever encountered. In fact, I recommend that people do precisely this when they want to post from multiple different addresses to lists I administer, but where they want to receive only one copy of posts to the list. What is it that you have seen that leads you to believe that this technique doesn't work? -- Brad Knowles, [EMAIL PROTECTED] Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. -- 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 Mailman Installation - Can't Send Email toaNewList (reformatted)
Mark Sapiro wrote: mcjathan wrote: In reading your instructions through what I discovered was that POSTFIX_STYLE_VIRTUAL_DOMAINS was set to false like this: POSTFIX_STYLE_VIRTUAL_DOMAINS = [] I'm assuming this may be the entire problem. Should this be set thusly?: POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain1.net', 'domain2.net'] Probably yes, but that's what you said you had in mm_cfg.py in the OP. Hi Mark, Sorry, my mistake here. I'm kind of over my head and feel like I'm chasing my tail as I try to walk through various configuration files and parameters. In fact, POSTFIX_STYLE_VIRTUAL_DOMAINS was set in mm_cfg.py, but was not set in Defaults.py. Should POSTFIX_STYLE_VIRTUAL_DOMAINS not be set in Defaults.py? Jeff -- 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] Old lists are working. New lists discard all messages. How to debug?
I have a number of lists running happily, but a couple of new ones don't want to play. For testing purposes I subscribe myself to them and a couple of other addresses. All message sent to them from subscribed addresses get automatically discarded. I can see the discards in the vette log, but that doesn't provide a reason why. Do I need to turn on verbose output or something to get a diagnostic that's meaningful? TIA Brian -- 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 Mailman Installation - Can't Send Email toaNewList (reformatted)
On 11/27/06, mcjathan [EMAIL PROTECTED] wrote: In fact, POSTFIX_STYLE_VIRTUAL_DOMAINS was set in mm_cfg.py, but was not set in Defaults.py. Should POSTFIX_STYLE_VIRTUAL_DOMAINS not be set in Defaults.py? Any settings in mm_cfg.py override the identical setting in Defaults.py. So, if POSTFIX_STYLE_VIRTUAL_DOMAINS is unset in Defaults.py (or even set to 'foobarmonkey', for whatever reason), any setting (correct, valid, or otherwise) of POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py will be used, instead. The rule of thumb is that you should never alter Defaults.py, since this file can (and probably will) be overwritten during an upgrade of Mailman. mm_cfg.py, however, will NOT be overwritten by Mailman's installation scripts, so it's safe to put configuration data there. -- - Patrick Bogen -- 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 Mailman Installation - Can't Send Email toaNewList (reformatted)
mcjathan sent the message below at 04:16 11/27/2006: Mark Sapiro wrote: mcjathan wrote: In reading your instructions through what I discovered was that POSTFIX_STYLE_VIRTUAL_DOMAINS was set to false like this: POSTFIX_STYLE_VIRTUAL_DOMAINS = [] I'm assuming this may be the entire problem. Should this be set thusly?: POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain1.net', 'domain2.net'] Probably yes, but that's what you said you had in mm_cfg.py in the OP. Hi Mark, Sorry, my mistake here. I'm kind of over my head and feel like I'm chasing my tail as I try to walk through various configuration files and parameters. In fact, POSTFIX_STYLE_VIRTUAL_DOMAINS was set in mm_cfg.py, but was not set in Defaults.py. Should POSTFIX_STYLE_VIRTUAL_DOMAINS not be set in Defaults.py? End original message. - There is a comment right at the top of Defaults.py that says don't edit this file. Anything you want to change goes into mm_cfg.py and will override values in Defaults.py The reason for this is that Defaults.py gets rebuilt and overwritten when you do make install. mm_cfg.py does not get overwritten so it is the place your overrides for site specific options are supposed to go. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- 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 Mailman Installation - Can't Send Email toaNewList(reformatted)
mcjathan wrote: In fact, POSTFIX_STYLE_VIRTUAL_DOMAINS was set in mm_cfg.py, but was not set in Defaults.py. Should POSTFIX_STYLE_VIRTUAL_DOMAINS not be set in Defaults.py? You should not make any changes in Defaults.py (see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.021.htp and other replies in this thread) Your setting in mm_cfg.py overrides the default in Defaults.py, and that's the way it should be. So we're back to the original question. Please go back to http://mail.python.org/pipermail/mailman-users/2006-November/054347.html and try to understand what I wrote there. As I said there, The fact that you have nothing in virtual-mailman after running bin/genaliases and/or creating lists indicates you have no lists whose host_name attribute is in the POSTFIX_STYLE_VIRTUAL_DOMAINS list. Since POSTFIX_STYLE_VIRTUAL_DOMAINS is apparently correct, the problem is with the lists. This is because the various DEFAULT_*_HOST settings and add_virtualhost directives are not correct in mm_cfg.py or weren't when the lists were created. The post referenced above says more about this. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Old lists are working. New lists discard allmessages. How to debug?
Brian Parish wrote: I have a number of lists running happily, but a couple of new ones don't want to play. For testing purposes I subscribe myself to them and a couple of other addresses. All message sent to them from subscribed addresses get automatically discarded. I can see the discards in the vette log, but that doesn't provide a reason why. Do I need to turn on verbose output or something to get a diagnostic that's meaningful? I think there are just two ways this can happen. 1) You are 'moderated' and member_moderation_action is Discard. 2) Your post is seen as from a nonmember and either you are in discard_these_nonmembers or generic_nonmember_action is Discard. You can get more information in case 2) by setting forward_auto_discards to Yes. (All the above settings except your moderated bit are on Privacy options...-Sender filters) -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] ics / iCalendar attachments?
Has anyone configured Mailman to allow ICS / iCalendar attachments? I've added text/calendar to the pass_mime_types setting in content filtering, but the ICS attachment was removed. The full content of pass_mime_types is: multipart/mixed multipart/alternative multipart/related text/plain text/html text/calendar application/pdf Here's how the mime attachment was included for the ICS file (I mangled it a bit to make sure it didn't get parsed) ... -- Content- Type: text/calendar; method=REQUEST; name=invite.ics; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST snip -- Any suggestions? Thanks! david -- 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] trying to access archives - access denied
Hello, I am the manger for a couple of different lists that are relatively new. It has come to my attention in the last few days that our members are unable to access the archives when they click on the archives link (http://lists.genuinecontact.info/pipermail/genuinecontact/). When you click on the link, it takes you to a page that says Forbidden: You don't have permission to access /pipermail/genuinecontact/ on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. I don't have very much experience managing these things, and very little technical understanding. Does anyone have any ideas about how to resolve this? I've already checked the settings of the archives, and they are set to archive messages, the archive file source is for public, and new archive volumes should be set yearly. Also, from the list management page, I can click on Edit List Archives and it will take me to the archives for editing, but if I click on Go To List Archives, I get the same message as above. I feel like this should be something really easy to fix, but couldn't find any reference in the help section available. This is the same on all of the lists I manage (6) so I am assuming it is a setting somewhere? Thanks, Rachel The day will come when after harnessing the ether, the winds, the tides, gravitation, we shall harness for God the energies of love. And on that day for the second time in the history of the world, man will have discovered fire. ~ Teilhard de Chardin -- 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] trying to access archives - access denied
On 11/27/06, Rachel Assuncao [EMAIL PROTECTED] wrote: I am the manger for a couple of different lists that are relatively new. It has come to my attention in the last few days that our members are unable to access the archives when they click on the archives link (http://lists.genuinecontact.info/pipermail/genuinecontact/). When you click on the link, it takes you to a page that says Forbidden: You don't have permission to access /pipermail/genuinecontact/ on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. This looks like a web server (e.g., apache) configuration, and/or permissions issue. I think the problem is that the user apache is running as can't access your /pipermail tree. Did you install Mailman from source, or did you use a packaged version? You might want to run through Chapter 5 of the installation manual http://www.gnu.org/software/mailman/mailman-install/node10.html and make sure you followed everything properly. It might be worthwhile to run check_perms, as well, although I'm not sure if it actually checks these particular permisisons. -- - Patrick Bogen -- 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] trying to access archives - access denied
Thanks for the quick response Patrick. I didn't install Mailman. Our web host (Blue Genesis) offers Mailman as part of their independent server package. We create the mailing list through their host control panel (Pleask) and then do all of the management of it through the Mailman online mailing list administration. They are the ones responsible for installation, and I assume it is installed correctly, if many of their clients are using it. What is check_perms? Thanks, Rachel The day will come when after harnessing the ether, the winds, the tides, gravitation, we shall harness for God the energies of love. And on that day for the second time in the history of the world, man will have discovered fire. ~ Teilhard de Chardin -Original Message- From: Patrick Bogen [mailto:[EMAIL PROTECTED] Sent: November 27, 2006 1:52 PM To: Rachel Assuncao Cc: mailman-users@python.org Subject: Re: [Mailman-Users] trying to access archives - access denied On 11/27/06, Rachel Assuncao [EMAIL PROTECTED] wrote: I am the manger for a couple of different lists that are relatively new. It has come to my attention in the last few days that our members are unable to access the archives when they click on the archives link (http://lists.genuinecontact.info/pipermail/genuinecontact/). When you click on the link, it takes you to a page that says Forbidden: You don't have permission to access /pipermail/genuinecontact/ on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. This looks like a web server (e.g., apache) configuration, and/or permissions issue. I think the problem is that the user apache is running as can't access your /pipermail tree. Did you install Mailman from source, or did you use a packaged version? You might want to run through Chapter 5 of the installation manual http://www.gnu.org/software/mailman/mailman-install/node10.html and make sure you followed everything properly. It might be worthwhile to run check_perms, as well, although I'm not sure if it actually checks these particular permisisons. -- - Patrick Bogen -- 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] ics / iCalendar attachments?
David Gibbs wrote: The full content of pass_mime_types is: multipart/mixed multipart/alternative multipart/related text/plain text/html text/calendar application/pdf Here's how the mime attachment was included for the ICS file (I mangled it a bit to make sure it didn't get parsed) ... -- Content- Type: text/calendar; method=REQUEST; name=invite.ics; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline That should do it. What are your other content filtering settings? And what is the complete MIME structure of the message containing the calendar? I.e., is the text/calendar part a subpart of some other part type that isn't accepted? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] ics / iCalendar attachments?
Mark Sapiro wrote:
That should do it. What are your other content filtering settings?
filter_content = yes
filter_mime_types = blank
pass_mime_types = multipart/mixed multipart/alternative
multipart/related text/plain text/html text/calendar application/pdf
filter_filename_extensions = exe bat cmd com pif scr vbs cpl
pass_filename_extensions = blank
collapse_alternatives = yes
convert_html_to_plaintext = yes
filter_action = forward to owner
And what is the complete MIME structure of the message containing the
calendar? I.e., is the text/calendar part a subpart of some other part
type that isn't accepted?
Don't think so ... but I'm not an expert in mime-encodong ..
Here's the a full message that has the calendar attachment ...
Return-Path: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on mail.nospam.com
X-Spam-Level:
X-Spam-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_50,
DK_POLICY_SIGNSOME,MIME_BASE64_NO_NAME autolearn=ham version=3.1.7
Received: from mail.il.us.asdf.com (mail.il.us.asdf.com [127.0.0.2])
by mail.nospam.com (8.13.7/8.13.7) with ESMTP id kAR1vZsv029181
for [EMAIL PROTECTED]; Sun, 26 Nov 2006 19:57:40 -0600
Received: from ilntexch.asdf.com (ilntexch.asdf.com [10.17.1.10])
by mail.il.us.asdf.com (Postfix) with ESMTP id 5B696182A
for [EMAIL PROTECTED]; Sun, 26 Nov 2006 19:27:30 -0500 (EST)
Content-class: urn:content-classes:calendarmessage
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary=_=_NextPart_001_01C711C7.683876B5
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: test
Date: Sun, 26 Nov 2006 19:57:35 -0600
Message-ID: [EMAIL PROTECTED]
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: test
Thread-Index: AccRx2gZFDduLb4eQTWBBmJeW2QHRgTY
From: David Gibbs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
X-Virus-Scanned: ClamAV 0.88.6/2242/Sat Nov 25 12:29:12 2006 on
rivendell.nospam.com
X-Virus-Status: Clean
Status: RO
X-Status: A
Content-Length: 2042
X-UID: 1576
X-Keywords:
This is a multi-part message in MIME format.
--_=_NextPart_001_01C711C7.683876B5
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: base64
VHlwZTpTaW5nbGUgTWVldGluZw0KT3JnYW5pemVyOkRhdmlkIEdpYmJzDQpTdGFydCBUaW1lOlN1
bmRheSwgTm92ZW1iZXIgMjYsIDIwMDYgODowMCBQTQ0KRW5kIFRpbWU6U3VuZGF5LCBOb3ZlbWJl
ciAyNiwgMjAwNiA4OjMwIFBNDQpUaW1lIFpvbmU6KEdNVC0wNjowMCkgQ2VudHJhbCBUaW1lIChV
UyAmIENhbmFkYSkNCkxvY2F0aW9uOm5vd2hlcmUNCg0KKn4qfip+Kn4qfip+Kn4qfip+Kg0KDQoN
Cg0K
--_=_NextPart_001_01C711C7.683876B5
Content-class: urn:content-classes:calendarmessage
Content-Type: text/calendar;
method=REQUEST;
name=meeting.ics
Content-Transfer-Encoding: 8bit
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:(GMT-06.00) Central Time (US Canada)
X-MICROSOFT-CDO-TZID:11
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=4;BYDAY=1SU
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20061127T015737Z
DTSTART;TZID=(GMT-06.00) Central Time (US Canada):20061126T20
SUMMARY:test
UID:{2DEE9D74-A5C9-4082-B980-549FDF93EA67}
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=[EMAIL
PROTECTED]:MAILTO:[EMAIL PROTECTED]
ORGANIZER;CN=David Gibbs:MAILTO:[EMAIL PROTECTED]
LOCATION:nowhere
DTEND;TZID=(GMT-06.00) Central Time (US Canada):20061126T203000
DESCRIPTION:\N\N
SEQUENCE:1
PRIORITY:5
CLASS:
CREATED:20061127T015735Z
LAST-MODIFIED:20061127T015735Z
STATUS:CONFIRMED
TRANSP:OPAQUE
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-OWNERAPPTID:-1
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT00H15M00S
END:VALARM
END:VEVENT
END:VCALENDAR
--_=_NextPart_001_01C711C7.683876B5--
Thanks!
david
--
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 has just stopped sending out mail to allmailing lists
I have reinstalled over the top of my installation. Doing a diff -u of the source directory after a make and /usr/local/mailman produced nothing of interest. The make install has a large number of pointers differ in signedness warnings I did an 'unshunt' and here are some results Some extracts from the logs: == smtp-failure Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') this is a snapshot of the last few lines. Each recipient has one of a similar set of messages for every .pck. == error Nov 27 21:53:24 2006 (12031) SHUNTING: 1162300907.583493+aa39005732b51ab067ad1e5ac45d4cf8cb1bf3f1 Nov 27 21:53:24 2006 (12031) Uncaught runner exception: 'str' object has no attribute 'get_sender' Nov 27 21:53:24 2006 (12031) Traceback (most recent call last): File /usr/local/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/local/mailman/Mailman/Queue/Runner.py, line 162, in _onefile sender = msg.get_sender() AttributeError: 'str' object has no attribute 'get_sender' Nov 27 21:53:24 2006 (12031) SHUNTING: 1162300907.5915849+536fe1680b23dc5e1d4773156e3c0e98b6e64ed0 this is one of these for every pck == smtp Nov 27 21:53:23 2006 (12035) [EMAIL PROTECTED] smtp to dxspider-support for 1 recips, completed in 0.007 seconds Nov 27 21:53:23 2006 (12035) [EMAIL PROTECTED] smtp to pelicans for 2 recips, completed in 0.009 seconds Nov 27 21:53:24 2006 (12035) [EMAIL PROTECTED] smtp to pelicans for 204 recips, completed in 0.024 seconds Nov 27 21:53:25 2006 (12035) [EMAIL PROTECTED] smtp to pelicans for 204 recips, completed in 0.053 seconds entirely normal == post Nov 27 21:53:23 2006 (12035) post to pelicans from [EMAIL PROTECTED], size=4440, message-id=[EMAIL PROTECTED], 2 failures Nov 27 21:53:24 2006 (12035) post to pelicans from [EMAIL PROTECTED], size=18105, message-id=[EMAIL PROTECTED], 204 failures Nov 27 21:53:25 2006 (12035) post to pelicans from [EMAIL PROTECTED], size=153840, message-id=[EMAIL PROTECTED], 204 failures Hope this helps Dirk -- 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] ics / iCalendar attachments?
David Gibbs wrote: Here's the a full message that has the calendar attachment ... Return-Path: [EMAIL PROTECTED] snip Content-class: urn:content-classes:calendarmessage MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=_=_NextPart_001_01C711C7.683876B5 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 snip --_=_NextPart_001_01C711C7.683876B5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 snip --_=_NextPart_001_01C711C7.683876B5 Content-class: urn:content-classes:calendarmessage Content-Type: text/calendar; method=REQUEST; name=meeting.ics Content-Transfer-Encoding: 8bit snip --_=_NextPart_001_01C711C7.683876B5-- The overall message above is multipart/alternative with a text/plain subpart and a text/calendar subpart. Apparently, Microsoft Exchange mails a calendar with a text/plain alternative for those mail clients that don't understand the calendar in the same way as it might include a text/plain alternative to a text/html message. Since your content filtering options include collapse_alternatives = yes, Mailman selects only the first alternative of those that remain after initial filtering for delivery to the list. Thus the text/calendar alternative is dropped in favor of the text/plain alternative. You have two choices: 1) teach Microsoft Exchange to send the calendar part only without the text/plain alternative, or generate the message differently so it does that, or 2) set collapse_alternatives = no, but this may have other, unwanted effects. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] ics / iCalendar attachments?
Mark Sapiro wrote: Since your content filtering options include collapse_alternatives = yes, Mailman selects only the first alternative of those that remain after initial filtering for delivery to the list. Thus the text/calendar alternative is dropped in favor of the text/plain alternative. Ok, that I can understand. 1) teach Microsoft Exchange to send the calendar part only without the text/plain alternative, or generate the message differently so it does that, or Two words: Brick-wall Head (as in: hitting one against the other ... I'll accomplish the same whichever I do). Although I don't think it's a M$ Exchange problem ... when I sent a event attachment with GMail, I get the same behavior. 2) set collapse_alternatives = no, but this may have other, unwanted effects. Maybe. I'll have to experiment. david -- 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] trying to access archives - access denied
Rachel Assuncao wrote: I didn't install Mailman. Our web host (Blue Genesis) offers Mailman as part of their independent server package. We create the mailing list through their host control panel (Pleask) and then do all of the management of it through the Mailman online mailing list administration. They are the ones responsible for installation, and I assume it is installed correctly, if many of their clients are using it. What is check_perms? Not relevant to you in the above scenario. It is a Mailman command line tool for checking permissions available only to those who have shell access to the Mailman installation. Can you access the archives via a url like http://lists.genuinecontact.info/mailman/private/genuinecontact/? This URL should look like those you use to access the list admin or moderator interface except with 'private' instead of 'admin' or 'admindb'. This should get a login page and you should be able to log in with either a list member's email address and list password or the list admin password. If you can get to the archives this way, that verifies the archives are OK, but there still could be a permissions issue or a misconfiguration of theweb server for the lists.genuinecontact.info domain. Do you have access to the web server logs for this domain? If so, what's in the error log for the 403 errors? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] ics / iCalendar attachments?
David Gibbs wrote: Two words: Brick-wall Head (as in: hitting one against the other ... I'll accomplish the same whichever I do). Although I don't think it's a M$ Exchange problem ... when I sent a event attachment with GMail, I get the same behavior. If all the MUA's send the text/calendar part with a text/plain alternative, then what you need to do is 2). 2) set collapse_alternatives = no, but this may have other, unwanted effects. Maybe. I'll have to experiment. The potentially unwanted effects I had in mind are that your current settings accept both text/plain and text/html, but if a text/html part has a text/plain alternative, only the text/plain part is sent to the list. Setting collapse_alternatives = no will mean that in these cases, both alternatives will be sent to the list in the original multipart/alternative form. You may see this as neutral, positive or negative. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman and (really) large lists
Thank you for all your comments, next time I'll RTFM a bit more :) I'll let you know how it goes, Mathias On 11/25/06, Jack Stone [EMAIL PROTECTED] wrote: As one stat, one of my lists of 10,000 is usually completed within 24 mins. I usually drop all filter scans during that time, plus I use 20 separate mail queues (sendmail) so too many don't pile up in a single queue and has to start over delaying send-outs. These 2 things have affected my speed more than anything else -- except maybe a custom footer which I avoid using. Brad Knowles [EMAIL PROTECTED] wrote: At 8:39 AM +0100 11/24/06, Mathias Andre wrote: In parallel of this migration we have been ask to set up a very large mailing list: between 15000 to 25000 users. This would be a moderated list (actually more like some kind of newsletter). I was wondering how well would mailman cope with such a large list. Check the FAQ. 15,000-25,000 is only a moderately large mailing list, as far as Mailman is concerned. Has any of you done anything similar? Check the FAQ. There's lots of good stuff there. -- Brad Knowles, Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. -- 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/antennex%40swbell.net Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.027.htp (^-^) Best regards, Jack L. Stone -- 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] ics / iCalendar attachments?
Mark Sapiro wrote: If all the MUA's send the text/calendar part with a text/plain alternative, then what you need to do is 2). Yep, figured that. The potentially unwanted effects I had in mind are that your current settings accept both text/plain and text/html, but if a text/html part has a text/plain alternative, only the text/plain part is sent to the list. Setting collapse_alternatives = no will mean that in these cases, both alternatives will be sent to the list in the original multipart/alternative form. You may see this as neutral, positive or negative. This is for one list with a very limited audience, so I don't think the ramifications will be significant. Thanks very much for your help. david -- 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 has just stopped sending out mail toallmailing lists
Dirk Koopman wrote: The make install has a large number of pointers differ in signedness warnings I think the only things that would produce this are the compilations of the wrappers, and I don't see that wrapper issues could cause the problem you're having. Did you do any kind of Python update just before things stopped working? I did an 'unshunt' and here are some results Some extracts from the logs: == smtp-failure Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Nov 27 21:53:25 2006 (12035) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') this is a snapshot of the last few lines. Each recipient has one of a similar set of messages for every .pck. Strange, as the shunting occurs well before delivery, but in any case, the above are not related to the shunting errors. These errors occur between Mailman and the outgoing MTA. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.073.htp and http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.014.htp == error Nov 27 21:53:24 2006 (12031) SHUNTING: 1162300907.583493+aa39005732b51ab067ad1e5ac45d4cf8cb1bf3f1 Nov 27 21:53:24 2006 (12031) Uncaught runner exception: 'str' object has no attribute 'get_sender' Nov 27 21:53:24 2006 (12031) Traceback (most recent call last): File /usr/local/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/local/mailman/Mailman/Queue/Runner.py, line 162, in _onefile sender = msg.get_sender() AttributeError: 'str' object has no attribute 'get_sender' Nov 27 21:53:24 2006 (12031) SHUNTING: 1162300907.5915849+536fe1680b23dc5e1d4773156e3c0e98b6e64ed0 this is one of these for every pck Expected as the shunted queue entries are defective (the question is how did they get that way). You need to apply the workaround discussed at http://mail.python.org/pipermail/mailman-users/2006-September/053556.html and then try to unshunt. The workaround will also allow new messages to process OK. == smtp Nov 27 21:53:23 2006 (12035) [EMAIL PROTECTED] smtp to dxspider-support for 1 recips, completed in 0.007 seconds Nov 27 21:53:23 2006 (12035) [EMAIL PROTECTED] smtp to pelicans for 2 recips, completed in 0.009 seconds Nov 27 21:53:24 2006 (12035) [EMAIL PROTECTED] smtp to pelicans for 204 recips, completed in 0.024 seconds Nov 27 21:53:25 2006 (12035) [EMAIL PROTECTED] smtp to pelicans for 204 recips, completed in 0.053 seconds entirely normal Except all the deliveries failed. == post Nov 27 21:53:23 2006 (12035) post to pelicans from [EMAIL PROTECTED], size=4440, message-id=[EMAIL PROTECTED], 2 failures Nov 27 21:53:24 2006 (12035) post to pelicans from [EMAIL PROTECTED], size=18105, message-id=[EMAIL PROTECTED], 204 failures Nov 27 21:53:25 2006 (12035) post to pelicans from [EMAIL PROTECTED], size=153840, message-id=[EMAIL PROTECTED], 204 failures These again relate to the sending issue, not the shunting issue, but these two issues could be related at the Python level. Again, have there been any Python changes? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] trying to access archives - access denied
Hello Mark, Thanks for the follow up. I checked the link you provided, and yes, I can access the archives that way. So, it is good to know that the archives are OK! I've also been talking with our web host, who tried to help, couldn't, and has now referred me to Pleask's service team for further follow up. I have access to a variety of logs through Pleask's systems, but couldn't find anything that referenced the error code, so maybe the logs I am able to access aren't the right ones. Rachel The day will come when after harnessing the ether, the winds, the tides, gravitation, we shall harness for God the energies of love. And on that day for the second time in the history of the world, man will have discovered fire. ~ Teilhard de Chardin -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: November 27, 2006 4:52 PM To: Rachel Assuncao; mailman-users@python.org; [EMAIL PROTECTED] Subject: Re: [Mailman-Users] trying to access archives - access denied Rachel Assuncao wrote: I didn't install Mailman. Our web host (Blue Genesis) offers Mailman as part of their independent server package. We create the mailing list through their host control panel (Pleask) and then do all of the management of it through the Mailman online mailing list administration. They are the ones responsible for installation, and I assume it is installed correctly, if many of their clients are using it. What is check_perms? Not relevant to you in the above scenario. It is a Mailman command line tool for checking permissions available only to those who have shell access to the Mailman installation. Can you access the archives via a url like http://lists.genuinecontact.info/mailman/private/genuinecontact/? This URL should look like those you use to access the list admin or moderator interface except with 'private' instead of 'admin' or 'admindb'. This should get a login page and you should be able to log in with either a list member's email address and list password or the list admin password. If you can get to the archives this way, that verifies the archives are OK, but there still could be a permissions issue or a misconfiguration of theweb server for the lists.genuinecontact.info domain. Do you have access to the web server logs for this domain? If so, what's in the error log for the 403 errors? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Change the Webinterface url
Hi, how can I change the url to the webinterface of an already existing list setup? Because I wanted to switch to https, but I don't see the option for an existing setup. Every new list is working fine with the new configuration in the mm_cfg.py but the old once doesn't care about the changes. stephan signature.asc Description: This is a digitally signed message part -- 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] Change the Webinterface url
Stephan Jennewein wrote: how can I change the url to the webinterface of an already existing list setup? Because I wanted to switch to https, but I don't see the option for an existing setup. Every new list is working fine with the new configuration in the mm_cfg.py but the old once doesn't care about the changes. Then all you need to do for the existing lists is run fix_url. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.069.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman and (really) large lists
Can you elaborate more? How to seperate the mail queues and drop the filter scans? Mathias Andre wrote: Thank you for all your comments, next time I'll RTFM a bit more :) I'll let you know how it goes, Mathias On 11/25/06, Jack Stone [EMAIL PROTECTED] wrote: As one stat, one of my lists of 10,000 is usually completed within 24 mins. I usually drop all filter scans during that time, plus I use 20 separate mail queues (sendmail) so too many don't pile up in a single queue and has to start over delaying send-outs. These 2 things have affected my speed more than anything else -- except maybe a custom footer which I avoid using. Brad Knowles [EMAIL PROTECTED] wrote: At 8:39 AM +0100 11/24/06, Mathias Andre wrote: In parallel of this migration we have been ask to set up a very large mailing list: between 15000 to 25000 users. This would be a moderated list (actually more like some kind of newsletter). I was wondering how well would mailman cope with such a large list. Check the FAQ. 15,000-25,000 is only a moderately large mailing list, as far as Mailman is concerned. Has any of you done anything similar? Check the FAQ. There's lots of good stuff there. -- Brad Knowles, Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. -- 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/antennex%40swbell.net Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.027.htp (^-^) Best regards, Jack L. Stone -- 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/stanley%40chen.com.hk Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Regards, Stanley Chen Mobile/SMS: +852.61007076 Fax: +852.82066697 Email/MSN: [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] I sent out a mailing, how can I know it's done or not?
When I read on the logs/smtp, many of the records said All recipients refused: (452, '4.4.5 Insufficient disk space; try again later'), but there are actually plenty of the disk space left in the server, why? Mark Sapiro wrote: Jack Stone wrote: I usually look in ~mailman/qfiles/out and when I see 0, that's good enough for me, although I know there may be some stragglers in the MTA mail queues. But, MM is through with its part. Prior to Mailman 2.1.9, the entry would be removed from the 'out' queue at the start of delivery to the MTA. For a large list, there could be some time before delivery to the MTA is complete. Beginning with 2.1.9, there will be a .bak file in the 'out' queue while delivery to the MTA is in process. You can look in Mailman's 'smtp' log for the message-id smtp for nnn recips, completed in tt.ttt seconds message. When that message is logged, Mailman's delivery to the MTA is complete. Prior to the logging of that message, there's no way to know how close to done Mailman is. -- Regards, Stanley Chen Mobile/SMS: +852.61007076 Fax: +852.82066697 Email/MSN: [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] Old lists are working. New lists discard allmessages. How to debug?
Mark Sapiro wrote: Brian Parish wrote: I have a number of lists running happily, but a couple of new ones don't want to play. For testing purposes I subscribe myself to them and a couple of other addresses. All message sent to them from subscribed addresses get automatically discarded. I can see the discards in the vette log, but that doesn't provide a reason why. Do I need to turn on verbose output or something to get a diagnostic that's meaningful? I think there are just two ways this can happen. 1) You are 'moderated' and member_moderation_action is Discard. 2) Your post is seen as from a nonmember and either you are in discard_these_nonmembers or generic_nonmember_action is Discard. You can get more information in case 2) by setting forward_auto_discards to Yes. (All the above settings except your moderated bit are on Privacy options...-Sender filters) Thanks Mark, But: 1. I am moderated, but member_moderation_action is hold 2. If I switch off my moderation bit, the behavior is unaffected 3. I am subscribed to the list under two addresses and sending from either I get discarded 4. discard_these_nonmembers is blank and generic_nonmember_action is hold 5. forward_auto_discards is set to Yes, so I see the discards, but with no explanation as to why Given point 4, I don't understand how mailman can do anything but hold the message for approval, whether I am correctly subscribed or not. I am more than happy to provide admin access to this list if you feel like having a play. thanks again Brian -- 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
