Re: [Mailman-Users] regexp help
Why don't you just add the email account to the list, set it for no mail, and set it so it's unmoderated? -Original Message- From: mailman-users-bounces+g.booth=usm@python.org [mailto:mailman-users-bounces+g.booth=usm@python.org] On Behalf Of Savoy, Jim Sent: Wednesday, October 21, 2009 11:24 AM To: mailman-users@python.org Subject: [Mailman-Users] regexp help Hi all - I am trying to have all of the mail sent to a certain email account automatically forwarded to a moderated mailing list (moderated to everyone accept the mail from this particular email account). So I created the account (we'll call it unique.n...@some.domain) and set up the mailing list (we'll call it ab...@some.domain). The only way I can think of getting the mailing list to accept the forwarded mail is to use the spam filters under [Privacy Options]. I create a new Spam Filter Rule like so: /^.*unique.name.*$/ (I will make this more specific later) But that doesn't seem to work. Mail sent to unique.n...@some.domain returns the error message you are not allowed to post to this mailing list to the original sender. I assumed that unique.name would be somewhere in the email headers, which is what the Spam rules are filtering on, right? Any ideas what I am doing wrong? Thanks. - jim - - -- 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/g.booth%4 0usm.edu -- 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] Troublesome Mailman Errors
Mark, Removing that line indeed caused our listserv mail to flow once again. You are a genius! I still got a failure showing up in the /var/log/mailman/post log when when I tried sending a test message to the list that hasn't been delivering to everyone, but I'm just glad the mail is flowing again. :) And I guess Mailman is using the 2.3 installation of Python on our system; I did a search on Python to see which version we were using, and it appears we have both 2.3 and 2.6.16 installed (I'd thought maybe we were using the 2.6.16 until I saw the 2.3 version up there - I'll ask the server admins to verify that). I also did still see the smtp error in the /var/log/mailman/error log when I restarted Mailman after removing that line: Jun 21 05:48:11 2007 (28494) Cannot connect to SMTP server 131.95.82.161 on port smtp But since mail is flowing, I don't know if I should even concern myself over that or not. Anyway, thank you again! Next time I make it to San Francisco, I owe you a beer. :) Thanks, George Booth -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Thursday, June 21, 2007 12:47 AM To: George Booth; mailman-users@python.org Subject: Re: [Mailman-Users] Troublesome Mailman Errors George Booth wrote: There was indeed a very large digest.mbox for one of the lists (not for the one we've been having issues with, though), so I removed the digest.mbox (that list is set up to be used as a departmental email address, so there are only 2 recipients on the list and they weren't digesting anyway), and that removed the MemoryErrors I've been seeing. BTW, I should mention that my version of Mailman is 2.1.5 However, now I'm getting different errors. When I restarted Mailman after removing the digest.mbox file, the errors were: Various errors and tracebacks snipped. In your OP you said I've also come across a suggestion to add the line self.__conn.set_debuglevel(1) to the SMTPDirect.py file and restarted Mailman, but that hasn't seemed to help either. No, but if it is still there it will definitely cause multiple problems of the type you are seeing with your Python version (2.3.?) That suggestion is only applicable to Python 2.4 and above. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.073.htp. At this point, I'm at a loss. I've gone through the steps outline in the FAQ entry 4.78. Troubleshooting: No mail going out to lists members, and all seems well there. Only other thing I can think of is that under my /var/mailman/locks directory, I have the following: [EMAIL PROTECTED] locks]# ls -al total 8 drwxrwsr-x 2 rootmailman 4096 Jun 20 13:30 . drwxrwsr-x 21 rootmailman 4096 Jun 19 20:02 .. -rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 master-qrunner -rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 master-qrunner.mail1.usm.edu.28475 -rw-rw-r-- 1 mailman mailman 53 Jan 18 2006 master-qrunner.mail.usm.edu.1757.1 [EMAIL PROTECTED] locks]# I don't know if these are required or if I should delete them, or if they even have anything whatsoever to do with the issue at hand. I did find it odd that two of them seem to be dated as June 21, 2007, which is tomorrow (assuming I read that correctly), although a check of the date command on the server shows the correct date and time. I'm not sure about the date issue, but those are the mailmanctl locks that attempt to prevent you starting (not restarting) Mailman when it's already running. Those locks should be there and are not the cause of your problems. If you still have the self.__conn.set_debuglevel(1) in SMTPDirect.py, remove it, and then let us know if there are any errors/problems remaining. -- 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] Troublesome Mailman Errors
failures Jun 20 13:10:39 2007 (28494) post to med.relations from [EMAIL PROTECTED], size=4429, message-id=[EMAIL PROTECTED], 1 failures And not that many attempts, based on the number of messages waiting in the outgoing queue. The smtp-failure log doesn't show anything useful that I can see: Jun 20 09:59:57 2007 (23726) Low level smtp error: [Errno 32] Broken pipe, msgid: [EMAIL PROTECTED] Jun 20 10:10:40 2007 (28494) Low level smtp error: [Errno 32] Broken pipe, msgid: [EMAIL PROTECTED] Jun 20 11:10:39 2007 (28494) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 32] Broken pipe Jun 20 11:10:39 2007 (28494) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 32] Broken pipe Jun 20 11:10:39 2007 (28494) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 32] Broken pipe Jun 20 11:10:40 2007 (28494) Low level smtp error: [Errno 32] Broken pipe, msgid: [EMAIL PROTECTED] Jun 20 12:10:39 2007 (28494) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 32] Broken pipe Jun 20 12:10:39 2007 (28494) Low level smtp error: [Errno 32] Broken pipe, msgid: [EMAIL PROTECTED] Jun 20 13:10:39 2007 (28494) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 32] Broken pipe Jun 20 13:10:39 2007 (28494) Low level smtp error: [Errno 32] Broken pipe, msgid: [EMAIL PROTECTED] At this point, I'm at a loss. I've gone through the steps outline in the FAQ entry 4.78. Troubleshooting: No mail going out to lists members, and all seems well there. Only other thing I can think of is that under my /var/mailman/locks directory, I have the following: [EMAIL PROTECTED] locks]# ls -al total 8 drwxrwsr-x 2 rootmailman 4096 Jun 20 13:30 . drwxrwsr-x 21 rootmailman 4096 Jun 19 20:02 .. -rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 master-qrunner -rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 master-qrunner.mail1.usm.edu.28475 -rw-rw-r-- 1 mailman mailman 53 Jan 18 2006 master-qrunner.mail.usm.edu.1757.1 [EMAIL PROTECTED] locks]# I don't know if these are required or if I should delete them, or if they even have anything whatsoever to do with the issue at hand. I did find it odd that two of them seem to be dated as June 21, 2007, which is tomorrow (assuming I read that correctly), although a check of the date command on the server shows the correct date and time. Once again, any help would be greatly appreciated. Thanks, George Booth George Booth iTech Applications Administrator [EMAIL PROTECTED] University of Southern Mississippi -- 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] Troublesome Mailman Errors
) File /var/mailman/pythonlib/email/Parser.py, line 218, in _parsebody payload[start:terminator]) MemoryError Jun 19 20:23:11 2007 (11284) SHUNTING: 1182292904.783638+0a96719432d01f6522da13a1fb9ef301d37d0344 June 15 is when the first of these showed up, which leads me to believe it's a seperate issue from the non-delivery of email to all recipients of a list (which, of course, I could be completely wrong about), since the last time I received a message from this list was June 11. Any pointers or suggestions would be greatly appreciated. I have asked the server admins if there could be a physical memory problem, which would cause the Memory Error listed above, and received a negative. I also have asked if the memory allocation for Python was sufficient, and was told it has access to all 16GB of memory that the server holds. I've also come across a suggestion to add the line self.__conn.set_debuglevel(1) to the SMTPDirect.py file and restarted Mailman, but that hasn't seemed to help either. Thanks in advance for any help, George Booth George Booth iTech Applications Administrator [EMAIL PROTECTED] University of Southern Mississippi -- 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] Virtual Host and Web Interface
I'm having a small problem at the moment trying to get Mailman configured
for a virtual host. Here's our situation:
Mailman resides on our mail server. In an attempt to help I/O on the mail
server, we put our webmail on a seperate server. Thus, web requests that
would have gone to the main mail server, mail.server.com (not the real FQDN)
now go to webmail.server.com
This of course broke the Mailman web interface, since it still resides on
mail.server.com, where it is redirected to the other server. In an attempt
to correct this, our consultant decided to put a virtual domain on
mail.server.com called mailman.server.com. Going directly to
mailman.server.com/mailman/admin/list-name pulls up the main page of the
list with no problem. However, all links on the page revert back to
mail.server.com, thus web management is impossible for my users. Changing
the url in the address bar to mailman.server.com as the base works, but I
can't ask my users, many of whom barely know how to operate a mouse, to do
this each time they want to click a link in the web interface.
I've changed the DEFAULT_URL_HOST in the mm_cfg.py to mailman.server.com,
which should change everything, at least as far as I've followed in the
documentation...but it doesn't. I've tried putting mailman.server.com in the
VIRTUAL_HOSTS = {} entry in mm_cfg.py, but that breaks everything and puts
up the nice Mailman has found a bug! page.
Am I missing something vital to change this? I thought this might also be an
apache configuration problem, but the administrator of the box has been
looking into it, but apparently has found nothing yet.
The server is running RedHat Linux AS3 Update 6.
I do have to wonder if the values for urlhost and hostname aren't being
updated correctly; and, if not, where do I set this information if not with
DEFAULT_URL_HOST?
Thanks in advance for any insight.
George
George Booth iTech System Administrator
[EMAIL PROTECTED]
University of Southern Mississippi
--
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 Host and Web Interface
This issue has now been resolved. Thank you, Mark, for your friendly
assistance.
Thanks,
George
George Booth iTech System Administrator
[EMAIL PROTECTED]
University of Southern Mississippi
- Original Message -
From: George Booth [EMAIL PROTECTED]
To: mailman-users@python.org
Sent: Friday, March 10, 2006 10:17 AM
Subject: [Mailman-Users] Virtual Host and Web Interface
I'm having a small problem at the moment trying to get Mailman configured
for a virtual host. Here's our situation:
Mailman resides on our mail server. In an attempt to help I/O on the mail
server, we put our webmail on a seperate server. Thus, web requests that
would have gone to the main mail server, mail.server.com (not the real FQDN)
now go to webmail.server.com
This of course broke the Mailman web interface, since it still resides on
mail.server.com, where it is redirected to the other server. In an attempt
to correct this, our consultant decided to put a virtual domain on
mail.server.com called mailman.server.com. Going directly to
mailman.server.com/mailman/admin/list-name pulls up the main page of the
list with no problem. However, all links on the page revert back to
mail.server.com, thus web management is impossible for my users. Changing
the url in the address bar to mailman.server.com as the base works, but I
can't ask my users, many of whom barely know how to operate a mouse, to do
this each time they want to click a link in the web interface.
I've changed the DEFAULT_URL_HOST in the mm_cfg.py to mailman.server.com,
which should change everything, at least as far as I've followed in the
documentation...but it doesn't. I've tried putting mailman.server.com in the
VIRTUAL_HOSTS = {} entry in mm_cfg.py, but that breaks everything and puts
up the nice Mailman has found a bug! page.
Am I missing something vital to change this? I thought this might also be an
apache configuration problem, but the administrator of the box has been
looking into it, but apparently has found nothing yet.
The server is running RedHat Linux AS3 Update 6.
I do have to wonder if the values for urlhost and hostname aren't being
updated correctly; and, if not, where do I set this information if not with
DEFAULT_URL_HOST?
Thanks in advance for any insight.
George
George Booth iTech System Administrator
[EMAIL PROTECTED]
University of Southern Mississippi
--
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/g.booth%40usm.edu
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Setting sitewide defaults that can't be changed?
- Original Message - From: Mark Sapiro [EMAIL PROTECTED] To: George Booth [EMAIL PROTECTED]; mailman-users@python.org Sent: Wednesday, May 18, 2005 5:21 PM Subject: Re: [Mailman-Users] Setting sitewide defaults that can't be changed? George Booth wrote: - Original Message - From: Brad Knowles [EMAIL PROTECTED] Why not instead have the following in mm_cfg.py: ADMIN_CATEGORIES = [ # First column 'general', 'passwords', 'language', 'members', 'nondigest', 'digest', # Second column # Old version commented out, and archive removed # 'privacy', 'bounce', 'archive', 'gateway', 'autoreply', 'privacy', 'bounce', 'gateway', 'autoreply', 'contentfilter', 'topics', ] Wonderful, that worked nicely. Thank you! :) If you didn't make other changes, I think you will find that even though the link is gone from the admin pages that you will still be able to go ditectly to the http://www.example.com/mailman/admin/list/archive page. To prevent this, I think you need to remove the line from Archive import Archive from Mailman/Gui/__init__.py It's fine that the page is still accessible; my users aren't, uhm...bright enough to figure out how to get directly to the archive page without that link on the main page. :) George Booth iTech System Administrator [EMAIL PROTECTED] University of Southern Mississippi -- 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?
- Original Message - From: Mark Sapiro [EMAIL PROTECTED] To: Mike Alberghini [EMAIL PROTECTED]; mailman-users@python.org Sent: Wednesday, May 18, 2005 2:27 PM Subject: Re: [Mailman-Users] Setting sitewide defaults that can't be changed? You can modify the GUI to remove the option from the web interface. That still allows changes with bin/config_list or bin/withlist, but that's presumably limited to the site admins. Short of that, I don't think there's a way. Where is the GUI file kept? I have a need to remove the option from the GUI allowing users to activate their archives (we don't allow them because of performance degradation with email when Mailman archives), but have no idea where the GUI file might be kept. George Booth iTech System Administrator [EMAIL PROTECTED] University of Southern Mississippi -- 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?
- Original Message - From: Brad Knowles [EMAIL PROTECTED] To: George Booth [EMAIL PROTECTED] Cc: mailman-users@python.org Sent: Wednesday, May 18, 2005 3:04 PM Subject: Re: [Mailman-Users] Setting sitewide defaults that can't be changed? At 2:52 PM -0500 2005-05-18, George Booth wrote: Where is the GUI file kept? I have a need to remove the option from the GUI allowing users to activate their archives (we don't allow them because of performance degradation with email when Mailman archives), but have no idea where the GUI file might be kept. It's not a GUI file. It is the GUI as created by the Python programs that generate the required HTML. So, you're talking about hacking Python code. That would explain why I couldn't find it. So, it's a binary code, not conf files or anything I can directly edit. Not very convenient, eh? Anyway, thanks for the info. :) George Booth iTech System Administrator [EMAIL PROTECTED] University of Southern Mississippi -- 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?
- Original Message -
From: Brad Knowles [EMAIL PROTECTED]
To: Mark Sapiro [EMAIL PROTECTED]
Cc: Mark Sapiro [EMAIL PROTECTED]; George Booth [EMAIL PROTECTED];
mailman-users@python.org
Sent: Wednesday, May 18, 2005 4:23 PM
Subject: Re: [Mailman-Users] Setting sitewide defaults that can't be
changed?
At 2:09 PM -0700 2005-05-18, Mark Sapiro wrote:
ADMIN_CATEGORIES.remove('archive')
Why not instead have the following in mm_cfg.py:
ADMIN_CATEGORIES = [
# First column
'general', 'passwords', 'language', 'members', 'nondigest', 'digest',
# Second column
# Old version commented out, and archive removed
# 'privacy', 'bounce', 'archive', 'gateway', 'autoreply',
'privacy', 'bounce', 'gateway', 'autoreply',
'contentfilter', 'topics',
]
Wonderful, that worked nicely. Thank you! :)
George Booth iTech System Administrator
[EMAIL PROTECTED]
University of Southern Mississippi
--
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] Shunted messages idea?
- Original Message -
From: Mark Sapiro [EMAIL PROTECTED]
To: George Booth [EMAIL PROTECTED]; mailman-users@python.org
Sent: Monday, April 04, 2005 2:44 PM
Subject: Re: [Mailman-Users] Shunted messages idea?
Your error trace below shows a problem in scrubbing an attachment which
is only done for digests and archives. Possibly the list was set up
this time with different content filtering or with no digests or
archives.
Hmm...when I recreated the list the last time, I actually did turn off
digesting. It doesn't require digesting, so I figured I'd turn it off, but
got distracted by several fires that needed attending to and forgot I'd done
that. Strange that none of the other lists are having a problem with
digesting. Archives are turned off for all lists because of mail delivery
degradation when it's turned on.
I don't know why you couldn't find the files. The first several are
Mailman modules and the rest are Python library modules. They were
clearly there when the error occurred, and unless Mailman and/or
Python moved in the interim, they must still be there.
It was most likely user error on my part in not finding the files. That and
I was swamped with a few other things and probably didn't search hard enough
when the pathway didn't come through.
Mailman is attempting to scrub an attachment from the digest. It is
attempting to get the file name from the Content-Disposition: header
using the email.Message.get_filename('') method from the Python
library. It appears that this header is malformed in some way
(possibly bad RFC 2231 encoding) that is causing the ultimate error in
the library routines.
Hmm, most of the messages came from a Mac user; I don't know if that one
specifically did or not. Wonder if that could be part of the problem?
There should be some kind of error trace analogous to this one for each
of the shunted messages although the error may not always be the same.
Thanks, I'll check when I get the chance. :)
George Booth iTech System Administrator
[EMAIL PROTECTED]
University of Southern Mississippi
--
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] Shunted messages idea?
I've encountered a very strange error. Out of 779 lists, we have 1 that keeps shunting messages. Currently, there are 34 shunted messages that will not unshunt. I've completely blown away the list and recreated it several times, all to no avail. Any suggestions would be appreciated. Running Mailman 2.1.5 on Red Hat AS 3. Thanks, George George Booth iTech System Administrator [EMAIL PROTECTED] University of Southern Mississippi -- 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] Administrative notices
For accreditation reasons, we are setting up automated lists for the colleges of our university. Since we were using Mailman already, we set up a seperate server, and scripts automatically create/delete lists based on automated data that comes from our PeopleSoft database. These lists are set up as announcement-only lists, so only specified people are able to send email. The Dean of each college is defaulted as the owner of the list for that college, but since we put this into Beta to test it, they've been receiving unwanted notifications that pending messages are awaiting approval, although there are no messages there. Now, we've created and blown away lists several times testing this, and we're thinking maybe some spam had tried coming through during one of the incarnations of the lists, but when the lists were destroyed, that the data was destroyed as well...but Mailman doesn't see it that way, and even though there are no messages pending approval, the software is still sending daily notices that there are some out there. These pending messages would be kept in the data directory under the mailman directory, correct? Is there any other place these messages might be kept that we're overlooking? And is there any way to tell Mailman to stop sending notifications for pending messages that don't exist? :) Thanks, George George Booth iTech System Administrator [EMAIL PROTECTED] University of Southern Mississippi -- 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] checkdbs command question
Forgot to mention: Mailman version 2.1.5 OS is RH Linux AS3 - Original Message - From: George Booth [EMAIL PROTECTED] To: mailman-users@python.org Sent: Friday, March 04, 2005 3:41 PM Subject: [Mailman-Users] checkdbs command question Does the checkdbs command do ANYTHING other than send out pending notifications to the list owners? Would disabling it in cron cripple the Mailman software in any way, shape, or form? Comments in the cron file suggest that all it does is send out notifications, but there are no comments one way or the other within the actual checkdbs file as whether it does more than that or not. If that's all it does, we definitely want to disable it for the 'special' instance of Mailman we are setting up, but we don't want to cripple the software if it does more than just send out pending notifications. Thanks, George George Booth iTech System Administrator [EMAIL PROTECTED] University of Southern Mississippi -- 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/g.booth%40usm.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] mailing list problem...
- Original Message - From: Dev Team [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 26, 2004 2:43 PM Subject: [Mailman-Users] mailing list problem... Well, how can i start to recover this ? are there any command line utilities/scripts to check the integrity of all files for this list ? I had this same problem a few weeks ago, with 2 lists that just stopped responding to web interface logins. I just used the 'list_members' function, piped it into a temporary file, removed the list, recreated it, and used the 'add_members' function to import the members back in. Of course, remembering the exact configuration was a bit tricky, but if this is a major list, chances are you remember how it was set up (restricted posting, closed membership, list owner, etc). I've no idea what caused it, but recovery wasn't really that much of a hassle. Hope that helps. George *** George Booth iTech Systems, TIU System Administrator [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] bypassing sending out the 'you have been subscribed' messages on mass subscriptions
If you're adding them through the web interface, there's a radio button just above the entry field; just click the one that says 'no' for 'Send welcome message to this batch?'. If you're doing it throught he command line with the 'add_members' command, there's this option: --welcome-msg=y|n -w y|n set whether or not to send the list members a welcome message, overriding whatever the list's `send_welcome_msg' setting is. Just type 'add_members -h' at the command line to get the help message for it. :) If you're doing something other than these two options, hopefully someone else will have an answer. :) Thanks, George Quoting Jonathan Vanasco [EMAIL PROTECTED]: i'm moving over a nightclub announcement list over to mailman ( he's got 1400 subscribers he's been bcc'ing every week ) i'd like to make the mail change transparent to users -- ie, not send out the 'you have been subscribed' messages from the mass subscription entry. there doesn't seem to be an option to do this. short of turning off exim for 20minutes and manually deleting items from the queue, does anybody know where in the source i can adjust things? -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/g.booth%40usm.edu * George Booth[EMAIL PROTECTED] Systems Analyst II http://ocean.otr.usm.edu/~ghbooth TSM and Listserv Administrator Technology Infrastructure Unit - iTech @ University of Southern Mississippi -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] *** List Management sending mail very delaying ***
We had a similar problem here; ours was caused by the archiving that Mailman does. We just shut off archiving on all our lists, and now mail squeaks through the system like lightning. :) I don't know if this might be your problem, but it's worth looking into. George Quoting Fabio Gil [EMAIL PROTECTED]: Hi, I have install Mailman on machine's with GNU/Linux Debian v. 3.0 wood. The package installed is 2.0.11-1woody5 and use the sendmail mail manager for send the emails of memberlist. The configuration is ok, but the sending of mail is very delay!! It is delaying more or but one 40 minutes! The file /var/lib/mailman/mail/wrapper binary is the problem?? Somebody would know to say me what it is occurring?? Thanks -- Brazil =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-= ///, \ /, / . Fábio Gil Linuxer # 225204 \ /, _/ /. \_ /_/ /. Email: [EMAIL PROTECTED] \__/_ / \_\_ EEP - Escola de Engenharia de Piracicaba /,)^_._ \ http://www.eep.br (/ \\ /\\\ // Seja Livre!! Use Linux!!! ==((`=== =-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/g.booth%40usm.edu * George Booth[EMAIL PROTECTED] Systems Analyst II http://ocean.otr.usm.edu/~ghbooth TSM and Listserv Administrator Technology Infrastructure Unit - iTech @ University of Southern Mississippi -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Host name problem
Mailman Version: 2.0.13 OS: Redhat Linux Hi Mailman users, Currently, we're migrating from Majordomo to Mailman, and have run into a host name issue. The email server we use has one domain, while we use an aliasing system for our email addresses; for instance, my alias is [EMAIL PROTECTED], but this mail would be forwarded through our LDAP system to [EMAIL PROTECTED], which is also the server our Mailman lists are on. This causes a problem with list names and the admin email addresses for each list. Changing the host name for each list to [EMAIL PROTECTED], which is how our system needs to operate, causes the problem of having [EMAIL PROTECTED] to appear, which needs to remain as [EMAIL PROTECTED] In order to get [EMAIL PROTECTED] to work, we would have to add, for over 1000 lists, that alias into our routing system, from which our LDAP draws information. That would be for listname-request, listname-admin, listname-owner, etc. We would rather not have to go through that. It would be much simpler if there were a way to modify the default message that Mailman sends out when someome subscribers, when user password notifications go out once a month, etc. Is there, perhaps, a central location that I've not run across as yet to modify these emails to provide for 2 different host names (one for the list address, one for the administration addresses)? I'll be happy to clarify any part of this that I may not have made clear. :) Thanks, George * George Booth[EMAIL PROTECTED] Systems Analyst II http://ocean.otr.usm.edu/~ghbooth TSM, Listserv, and Web Accounts Administrator Technology Infrastructure Unit - iTech @ University of Southern Mississippi -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
