Re: [Mailman-Users] Stripped Subject
10-Dec-03 at 11:58, Paulo R Kappke ([EMAIL PROTECTED]) wrote : Something very weird is happening with my Mailman. When someone sends an e-mail to a mailing list and put a long subject, 60 or 70 characters, the e-mail is being received with the prefix ([list-name]) only. Looks like Mailman is stripping the subject. I am running Mailman version 2.1.1 in a RedHat 9 box. Is it stripping the subject completely, or is it adding a completely legal linebreak? Have you checked the raw message headers? RFC 822: Each header field can be viewed as a single, logical line of ASCII characters, comprising a field-name and a field-body. For convenience, the field-body portion of this conceptual entity can be split into a multiple-line representation; this is called folding. The general rule is that wherever there may be linear-white-space (NOT simply LWSP-chars), a CRLF immediately followed by AT LEAST one LWSP-char may instead be inserted. RFC 2822: Each header field is logically a single line of characters comprising the field name, the colon, and the field body. For convenience however, and to deal with the 998/78 character limitations per line*, the field body portion of a header field can be split into a multiple line representation; this is called folding. The general rule is that wherever this standard allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP. For example, the header field: Subject: This is a test can be represented as: Subject: This is a test * 998 being a sort of absolute maximum understood by a majority of MTAs; 78 being a recommended maximum line length. Regards, -- Simon White. Internet Consultant, Linux/Windows Server Administration. email, dns and web servers; php javascript perl asp; MySQL MSSQL Access Bridging the gap between management, HR and the tech team. -- 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] Footer in Mailman
[EMAIL PROTECTED] scripsit/wrote: Like [EMAIL PROTECTED] should be sent to 3 emails ad xyz company. So everybody can post to [EMAIL PROTECTED] Works fine.. Hm. Using aliases would be an easier way for that, don't you think so? But each email has an footer containing information to go to archives.. and kind of everybody could than read all archives on this private system.. Why don't you disable archiving completely or make the archive private (i.e. open only to list members)? So Wat i wnat is that email posted by non-members should not include the archive and mailman info footer Is that possible to be configured this way... I don't think so, but you could also disable the footer completely (or change it). -thh -- 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] Postfix won't listen?
We're pulling our hair out over this one. Why can't our newly installed Panther Mailman talk to Postfix? Is this a relaying problem? Postfix is set to listen to localhost/127.0.0.1 of course and we can telnet port 25 and dump mail all we want, no problem. This also shows up in mail.log. But when we add a new list and user, the outgoing qrunner process grabs 100% CPU and stays that way indefinitely. Mail.log logs nothing that indicates mailman talking to it, but the mailman delivery failure log says delivery to [EMAIL PROTECTED] failed with code -1:ignore. The mailman delivery log says all recipients refused and no address associated with nodename. Anyone have tips on where to start looking? More info, screenshots, error logs, DNS data and loose hair provided on request :-) /Peter Nilsson /Rickard Andersson /thedumbfvcksatdicom.se -- 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] Stripped Subject
No Simon, the subject was stripped. Here is the header: Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from mail.cyclades.com (localhost [127.0.0.1]) by intra.cyclades.com (Postfix) with ESMTP id 00FFF8001AA; Tue, 9 Dec 2003 09:25:01 -0800 (PST) Delivered-To: [EMAIL PROTECTED] Received: from cyclades.com (unknown [192.168.44.203]) by intra.cyclades.com (Postfix) with ESMTP id 6D0EE8000B1 for [EMAIL PROTECTED]; Tue, 9 Dec 2003 09:24:57 -0800 (PST) Message-ID: [EMAIL PROTECTED] Date: Tue, 09 Dec 2003 09:24:32 -0800 From: Paulo Kappke [EMAIL PROTECTED] Organization: Cyclades Corporation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Cyclades-MailScanner: Found to be clean, Found to be clean X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.1 Precedence: list Reply-To: [EMAIL PROTECTED] List-Id: cyus.test.cyclades.com List-Unsubscribe: http://listserv.cyclades.com/mailman/listinfo/cyus.test, mailto:[EMAIL PROTECTED] List-Archive: http://listserv.cyclades.com/mailman/private/cyus.test List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://listserv.cyclades.com/mailman/listinfo/cyus.test, mailto:[EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] X-Cyclades-MailScanner-Information: Please contact the ISP for more information Subject: [Cyus.test] I have written 59 characters in this e-mail. Regards, Paulo K Simon White wrote: 10-Dec-03 at 11:58, Paulo R Kappke ([EMAIL PROTECTED]) wrote : Something very weird is happening with my Mailman. When someone sends an e-mail to a mailing list and put a long subject, 60 or 70 characters, the e-mail is being received with the prefix ([list-name]) only. Looks like Mailman is stripping the subject. I am running Mailman version 2.1.1 in a RedHat 9 box. Is it stripping the subject completely, or is it adding a completely legal linebreak? Have you checked the raw message headers? RFC 822: Each header field can be viewed as a single, logical line of ASCII characters, comprising a field-name and a field-body. For convenience, the field-body portion of this conceptual entity can be split into a multiple-line representation; this is called folding. The general rule is that wherever there may be linear-white-space (NOT simply LWSP-chars), a CRLF immediately followed by AT LEAST one LWSP-char may instead be inserted. RFC 2822: Each header field is logically a single line of characters comprising the field name, the colon, and the field body. For convenience however, and to deal with the 998/78 character limitations per line*, the field body portion of a header field can be split into a multiple line representation; this is called folding. The general rule is that wherever this standard allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP. For example, the header field: Subject: This is a test can be represented as: Subject: This is a test * 998 being a sort of absolute maximum understood by a majority of MTAs; 78 being a recommended maximum line length. Regards, -- 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] Stripped Subject
11-Dec-03 at 08:16, Paulo R Kappke ([EMAIL PROTECTED]) wrote : No Simon, the subject was stripped. Hmmm... It was a guess - I have seen issues like that before. If it was stripped entirely I'm not sure where you need to be looking, maybe somebody else has a bit of an idea? Regards, -- Simon White. Internet Consultant, Linux/Windows Server Administration. email, dns and web servers; php javascript perl asp; MySQL MSSQL Access Bridging the gap between management, HR and the tech team. -- 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] Stripped Subject
Simon, this is really weird. I could not find any hint, but maybe someone has an idea. Thanks, Paulo K Simon White wrote: 11-Dec-03 at 08:16, Paulo R Kappke ([EMAIL PROTECTED]) wrote : No Simon, the subject was stripped. Hmmm... It was a guess - I have seen issues like that before. If it was stripped entirely I'm not sure where you need to be looking, maybe somebody else has a bit of an idea? Regards, -- 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] Spaces in Email Addresses
I have a problem with spaces in my lists email names. Awhile back I mass subscribed a list of email and real names that was exported from another list manager program. The format of export was [EMAIL PROTECTED] realname. It added these entries to Mailman with the space and realname as the email address. However, from the admin pages, I can't unsubscribe these names, as apparently Mailman doesn't see them as being subscribed. I have tried entering the email only, and the email and name in quotes, and both return errors from Mailman saying I can't unsubscribe nonmemebers. Is there another way I can dump these accounts? Thanks. -- -- 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] Spaces in Email Addresses
I had a similar problem just last week where I had an address with 2 @'s in it. Actually it was to addresses concatenated but whenever Mailman displayed the addy it was truncated at the second @. My final solution was to dump the config: # bin/config_list -o outfile listname then dump the userlist: # bin/list_members listname outfile2 Here you should munge up outfile2 so it's the proper format for re-insertion later. destroy the list (leaving archives in tact): # bin/rmlist listname recreate the list (the user and password here mean little because of the next step): # bin/newlist listname [EMAIL PROTECTED] write your old config over it: # bin/config_list -i outfile listname resubscribe your members silently: # bin/add_members -r outfile2 -w n -a n Of course you'll have to deal with your digest vs. regular subscribers on your own. Most of my lists are either announce-only or low-traffic so all my members are regular. Hope this helps! (And I hope there's a better way than all that, but it works in a pinch) -Frank On Thu, 11 Dec 2003, Jonathan Garton wrote: # I have a problem with spaces in my lists email names. Awhile back I mass # subscribed a list of email and real names that was exported from another # list manager program. The format of export was [EMAIL PROTECTED] realname. # It added these entries to Mailman with the space and realname as the # email address. However, from the # admin pages, I can't unsubscribe these names, as apparently Mailman # doesn't see them as being subscribed. # # I have tried entering the email only, and the email and name in quotes, # and both return errors from Mailman saying I can't unsubscribe # nonmemebers. # # Is there another way I can dump these accounts? # # Thanks. -- 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] Spaces in Email Addresses
On Thu, 2003-12-11 at 11:42, Jonathan Garton wrote: I have a problem with spaces in my lists email names. Awhile back I mass subscribed a list of email and real names that was exported from another list manager program. The format of export was [EMAIL PROTECTED] realname. It added these entries to Mailman with the space and realname as the email address. However, from the admin pages, I can't unsubscribe these names, as apparently Mailman doesn't see them as being subscribed. I have tried entering the email only, and the email and name in quotes, and both return errors from Mailman saying I can't unsubscribe nonmemebers. Is there another way I can dump these accounts? Thanks. Read the FAQ... Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py I think the easiest way to do this is to use a hex editor and simply insert a valid character where the spaces are. Then you can treat them as ordinary email addresses. Note: the address may appear in the database in multiple places. Good Luck - Jon Carnes -- 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] semi-virtual domains under exim
mailman 2.1.3 under freebsd 4.9-stable with exim-4.24 nigel's faq on mailman, http://www.exim.org/howto/mailman21.html has left me a bit confused regarding semi-virtual domains. i can not understand how to have lists on the same host (with no list name collisions) come from different aliases of that host. in exim, i don't use the full virt domain stuff, but just alias all the other domains to my main domain using a list kept in domainlist local_domains = /usr/local/etc/exim/local.domains and i have lists of the form [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] all working on the same host under majordomo and exim4. in majordomo's listname.config, i just say resend_host = ops.ietf.org and the OUTGOING MAIL HEADERS all seem to work. but i can't seem to suss this out with mailman. i did search the archives, read the faq, ... and found nothing useful. this is hard to believe, so i guess i just am searching poorly. sorry. any clues or pointers? randy -- 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] public archive not-accessible, private archives are - permissions problem?
[I have send this earlier, but it didn't seem to make it to the list.] Hello, I have recvently migrated my mail- and mailinglistserver to a new box. All works well except for one thing: access to the public archives is denied. The box is running Linux 2.4.10, with Exim 4.20, Apache 2.n and Mailman 2.1. All is running well. Except for one thing: access to private archives available, to public archives denied. damogran:/ # la -dA /usr/lib/mailman/ drwxrwsr-x 20 root mailman 536 Dec 9 00:28 /usr/lib/mailman/ damogran:/ # la -dA /usr/lib/mailman/archives drwxrwsr-x4 root mailman96 Dec 7 18:44 /usr/lib/mailman/archives damogran:/ # la -A /usr/lib/mailman/archives total 1 drwxrws--x 27 wwwrun mailman 1016 Dec 8 02:00 private drwxrwsr-x2 wwwrun mailman 376 Dec 9 01:15 public damogran:/ # la /usr/lib/mailman/archives/public/test-ml* lrwxrwxrwx1 wwwrun mailman41 Dec 7 18:40 /usr/lib/mailman/archives/public/test-ml - /usr/lib/mailman/archives/private/test-ml lrwxrwxrwx1 wwwrun mailman46 Dec 7 18:40 /usr/lib/mailman/archives/public/test-ml.mbox - /usr/lib/mailman/archives/private/test-ml.mbox damogran:/ # la -Ad /usr/lib/mailman/archives/private/test-ml drwxrwsr-x5 wwwrun mailman 360 Dec 8 03:27 /usr/lib/mailman/archives/private/test-ml And, as for the Apache configuration: VirtualHost * [...] ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Alias /pipermail/ /usr/lib/mailman/archives/public/ Directory /usr/lib/mailman/ Options FollowSymLinks /Directory Directory /usr/lib/mailman/cgi-bin AllowOverride None Options None Order allow,deny Allow from all /Directory /VirtualHost Of course I did run check_perms (which no longer gives any warnings) and check Google. To no avail. Someone an idea? -- Rejo Zenger [EMAIL PROTECTED] - http://rejo.zenger.nl - PGP 0x75FC50F3 -- 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] ability to view all members in list?
Hi, How can I view all members in a list rather than only in chunks for each letter? Thanks Ricardo -- 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] Debian Back-Port?
rr == Raquel Rice Re: [Mailman-Users] Debian Back-Port? Thu, 11 Dec 2003 11:57:52 -0800 rr On Tue, 09 Dec 2003 14:56:16 -0500 rr John A. Martin [EMAIL PROTECTED] wrote: rr == Raquel Rice [Mailman-Users] Debian Back-Port? Tue, 9 Dec 2003 08:07:52 -0800 rr Does anyone know of back-ports for Debian. For stable, way too hard to be useful, IMHO. rr current Debian stable version of Mailman is 2.0.11. But currently apt-get install mailman/unstable will get you mailman-2.1.3-2 and pull in all the needed dependencies. You might want to use the -u switch as well while apt-listchanges is your friend to keep you from being surprised too much by the dependencies being upgraded. Maintenance will be easier using apt_preferences(5). rr I'm new to Debian, Perhaps I should have mentioned also 'man sources.list(5)'. rr so I'm not sure of what all this means. However, I am trying rr to figure it all out ... and not just wanting a free ride. It's more of a concern that a Do this may just tell someone how to shoot their foot off. rr I read man apt-get. The -u option is listed but blank. ,[ man apt-get ] -u --show-upgraded Show upgraded packages; Print out a list of all packages that are to be upgraded. Configuration Item: APT::Get::Show- Upgraded. ` rr I'm reading man apt_preferences now. rr I'm still trying to find information on apt-listchanges. ,[ dpkg -s apt-listchanges ] Package: apt-listchanges Status: install ok installed Priority: optional Section: utils Installed-Size: 296 Maintainer: Matt Zimmerman [EMAIL PROTECTED] Version: 2.42 Depends: python (= 2.3), apt (= 0.5.3), python-apt, debconf, ucf Suggests: x-terminal-emulator, www-browser, debianutils Conffiles: /etc/apt/apt.conf.d/20listchanges 39204938ee32c5ebd503167ace5c1d0c Description: Display new Debian changelog entries from .deb archives apt-listchanges is a tool to show what has been changed in a new version of a Debian package, as compared to the version currently installed on the system. It does this by extracting the relevant entries from the Debian changelog file, usually found in /usr/share/doc/package/changelog.Debian.gz . It can be run on several .deb archives at a time to get a list of all of the changes that would be effected by installing or upgrading a group of packages. It can be configured to do this automatically during upgrades using apt. ` I find apt-show-versions(1) indispensable when managing a mixed system. The following shows a reasonable Mailman box. (O'Well, pflogsumm-1.0.10 is not well matched to the current Postfix snapshots.) ,[ apt-show-versions -a -r -p \ 'postfix|pflogsumm|bind9|apache|python|mailman' ] apache-common 1.3.29-1install ok installed apache-common 1.3.26-0woody3 stable apache-common 1.3.29-1unstable apache-common/unstable uptodate 1.3.29-1 apache-ssl 1.3.29-1install ok installed apache-ssl 1.3.26.1+1.48-0woody3 stable apache-ssl 1.3.29-1unstable apache-ssl/unstable uptodate 1.3.29-1 postfix 2.0.16-20031207-1 install ok installed postfix 1.1.11-0.woody3 stable postfix 2.0.16-4unstable postfix: No available version python2.3-iconvcodec1.1.2-1 install ok installed No stable version python2.3-iconvcodec1.1.2-1 unstable python2.3-iconvcodec/unstable uptodate 1.1.2-1 apache-utils1.3.29-1install ok installed No stable version apache-utils1.3.29-1unstable apache-utils/unstable uptodate 1.3.29-1 python2.1 2.1.3-20install ok installed python2.1 2.1.3-3.2 stable python2.1 2.1.3-20unstable python2.1/unstable uptodate 2.1.3-20 mailman 2.1.3-2 install ok installed mailman 2.0.11-1woody5 stable mailman 2.1.3-2 unstable mailman/unstable uptodate 2.1.3-2 python2.1-email 2.5.4-2 install ok installed No stable version python2.1-email 2.5.4-2 unstable python2.1-email/unstable uptodate 2.5.4-2 python2.2-optik 1.4.1-2 install ok installed python2.2-optik 1.3-1 stable python2.2-optik 1.4.1-2 unstable python2.2-optik/unstable uptodate 1.4.1-2 python2.3 2.3.2.91-1 install ok installed No stable version python2.3 2.3.2.91-1 unstable python2.3/unstable uptodate 2.3.2.91-1 bind9-host 1:9.2.3-2 install ok installed bind9-host 1:9.2.1-2.woody.1 stable bind9-host 1:9.2.3-2 unstable bind9-host/unstable uptodate 1:9.2.3-2 python 2.3.2.91-1 install ok installed python 2.1.3-3.2 stable python 2.3.2.91-1 unstable python/unstable uptodate 2.3.2.91-1 pflogsumm 1.0.10-1install ok installed pflogsumm 1.0.4-1 stable pflogsumm 1.0.10-1unstable pflogsumm/unstable uptodate 1.0.10-1 python2.2 2.2.3-7 install ok installed python2.2 2.2.1-4.2 stable python2.2 2.2.3-7
[Mailman-Users] Installing Latst Version?
The system admin where I have my mailing list asks if there is a way to install the latest version of mailman without blowing everything away. I guess he means can he preserve exisitng lists, config files, etc. when he updates. We're using V1.1 (he's hard to convince!) Thanks, Pete -- 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] Installing Latst Version?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pete Holsberg wrote: The system admin where I have my mailing list asks if there is a way to install the latest version of mailman without blowing everything away. I guess he means can he preserve exisitng lists, config files, etc. when he updates. We're using V1.1 (he's hard to convince!) There is a file called UPGRADING in the mailman tarball that details the steps you'd need to take to accomplish this. I'm sure there is some other info in the archives of this list as well. Point your sysadmin in that direction. - -- ToddOpenPGP - KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp == If the world didn't suck, we'd all fall off. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE/2OaAuv+09NZUB1oRAleAAKCQqARu38QcGY29pi0/O/AMTXKbOACgtd3R y8xUysDpAbCSoCzxq0Fs/no= =2CUK -END PGP SIGNATURE- -- 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] Looking for the reverse of a ban list
Scott C. Villinski wrote: I'd like to configure a set of domain names that are allowed to subscribe to lists. It could be the equivalent of a Ban list with some domain names as exceptions. Or just an Allow List. Any thoughts? I saw in the archives the messages about allow lists for sending messages - but I don't think this will help me. Thanks, Scott I'll reply to my own message since I figured out a way to do this. If you want the reverse of the ban_list (for subscriptions), then what you can do is modify the $prefix/Mailman/MailList.py file, and on line 770 (of Mailman v 2.1.3) starts the ban_list processing. Change the ban=0 to ban=1, and replace the original ban=1 with ban=0. What this does is change the code from blocking a user that matches the pattern to only allowing users that match. It's a hack - but it seems to work. When you are done, you should only have made 3 changes (one ban=0 to ban=1, and two ban=1 to ban=0). I was happy to see how simple it was. So far I haven't seen any bad side effects of making this change - but maybe somebody will have and idea. Scott -- 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] incoming qrunner does not run
Hello everyone... I am using debian woody with exim as MTA. I upgraded my mailman from 2.0.x to 2.1.2 using debian package. But I hit a problem that the email is not delivered to the list members and archives either. I found that at /var/log/mailman/qrunner, the incoming qrunner fails to run as follows (please see the log message below): Any ideas on this? Thanks very much in advance. - Dec 12 09:18:17 2003 (1634) BounceRunner qrunner started. Dec 12 09:18:17 2003 (1633) ArchRunner qrunner started. Dec 12 09:18:18 2003 (1635) CommandRunner qrunner started. Dec 12 09:18:18 2003 (1636) IncomingRunner qrunner started. Dec 12 09:18:18 2003 (1638) OutgoingRunner qrunner started. Dec 12 09:18:18 2003 (1639) VirginRunner qrunner started. Dec 12 09:18:18 2003 (1637) NewsRunner qrunner started. Dec 12 09:18:18 2003 (1632) Master qrunner detected subprocess exit (pid: 1636, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:20 2003 (1642) IncomingRunner qrunner started. Dec 12 09:18:20 2003 (1632) Master qrunner detected subprocess exit (pid: 1642, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:21 2003 (1646) IncomingRunner qrunner started. Dec 12 09:18:21 2003 (1632) Master qrunner detected subprocess exit (pid: 1646, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:22 2003 (1651) IncomingRunner qrunner started. Dec 12 09:18:22 2003 (1632) Master qrunner detected subprocess exit (pid: 1651, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:23 2003 (1653) IncomingRunner qrunner started. Dec 12 09:18:23 2003 (1632) Master qrunner detected subprocess exit (pid: 1653, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:24 2003 (1656) IncomingRunner qrunner started. Dec 12 09:18:24 2003 (1632) Master qrunner detected subprocess exit (pid: 1656, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:25 2003 (1659) IncomingRunner qrunner started. Dec 12 09:18:26 2003 (1632) Master qrunner detected subprocess exit (pid: 1659, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:28 2003 (1661) IncomingRunner qrunner started. Dec 12 09:18:29 2003 (1632) Master qrunner detected subprocess exit (pid: 1661, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:31 2003 (1669) IncomingRunner qrunner started. Dec 12 09:18:31 2003 (1632) Master qrunner detected subprocess exit (pid: 1669, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:33 2003 (1670) IncomingRunner qrunner started. Dec 12 09:18:34 2003 (1632) Master qrunner detected subprocess exit (pid: 1670, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:34 2003 (1675) IncomingRunner qrunner started. Dec 12 09:18:35 2003 (1632) Master qrunner detected subprocess exit (pid: 1675, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 12 09:18:35 2003 (1632) Qrunner IncomingRunner reached maximum restart limit of 10, not restarting. -- 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] incoming qrunner does not run
:: But I hit a problem that the email is not delivered to the list :: members and archives either. :: :: I found that at /var/log/mailman/qrunner, the incoming qrunner :: fails to run as follows (please see the log message below): :: :: Any ideas on this? Clear out any files you have in ~mailman/qfiles/in/ and then try to start up the qrunner again. Cheers - Erick -- 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] incoming qrunner does not run
On Thu, Dec 11, 2003 at 05:22:32PM -0800, Erick Mechler wrote: :: But I hit a problem that the email is not delivered to the list :: members and archives either. :: :: I found that at /var/log/mailman/qrunner, the incoming qrunner :: fails to run as follows (please see the log message below): :: :: Any ideas on this? Clear out any files you have in ~mailman/qfiles/in/ and then try to start up the qrunner again. Cheers - Erick Thank you very much! Deleting all the files in that directory recovered my mailman back! Thank you -- 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] help mailman-users-request@python.org
Please help someone is tring to fun my e-mails and my accounts can you find
out who they are by an ip- address??
The following are some of the ip addresses that keep poping up...this one I
have an e-mail address:
[EMAIL PROTECTED]
and this is one of the received mail from you to me post349.
received from mail python.prg (12.155.117.291) by me 12-f12hotmail.com
received from localhostdomain (1127.0.0.1) helo=mail python.org)by r sender
[EMAIL PROTECTED] x-message-info:
JGTYoYD78jE/+0xRzN63zxZWx73Y4vYb
X-beenthere: [EMAIL PROTECTED]
X-Mailman-Version:2.1.4a0
Precedence: list
List-id: mailman mailing list management users mailman-users.python.org
List-Unsubscribe: http://mail.python.org/mailman/listinfo/mailman-users,
List-Archive: http://mail.[ython.org/pipermail/mailman-users
List-Post: mailto:[EMAIL PROTECTED]
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe: http://mail.python.org/mailman/listinfo/mailman-users.m:
Errors-To: [EMAIL PROTECTED]:
Message-id: ELARaO0-0003NW-9pWmail.python.org
return-Path: [EMAIL PROTECTED]
X-OrginalArrivalTime:03 Dec 2003 17:02:03.0945 )UTC) FILETIME={2C1
View e-mail Message Source
Content-Type: multipart/mixed: boundary=16
content-Type: text/plain; charset=us-ascii
Content-Description: Mailman-users Digest, vol 15, Issue
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
content-Type: text/plain; charset=us-ascii
Content-Description: Today's Topics (10 messages)
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
_
Browse styles for all ages, from the latest looks to cozy weekend wear at
MSN Shopping. And check out the beauty products! http://shopping.msn.com
--
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
