Mailman-Users July 2007

mailman-users@python.org

99 participants
95 discussions

same list name on 2 different domains
by Enzo 16 Jul '07

16 Jul '07

Hi I've configured mailman with my postfix server, i use mailman on 2 virtual hosts I can create list on both domains, but i can't create the same list with the same name on these 2 different domains for ex mylist(a)lists.domain1.org and mylist(a)lists.domain2.org I, in fact, create the first with: $newlist mylist(a)lists.domain1.org and the second with : $newlist mylist(a)lists.domain2.org But at this step, i get an error: "List already exists: mylist" Is it possible ? if yes how ? Thanks Enzo _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail

3 2

Failures showing in the log file?
by Dennis Carr 16 Jul '07

16 Jul '07

OK, something I notice in my posts log is a message not entirely unlike the following: Jul 15 09:27:31 2007 (32571) post to list from user(a)wherever.com, size=5706, message-id=<redacted>, 557 failures Now, as time progresses, that "failures" number counts down, and ultimately, there is a "success" asociated with that number. sWhat, precisely, does this message mean? -Dennis Carr

2 3

Messages not being delivered.
by Brandon Slaten 16 Jul '07

16 Jul '07

Greetings, Thanks for any time you can give this problem. I just moved our Mailman lists to a new server. Accessing the listinfo and admin pages works fine. After creating a new list mail sent to that list is delivered. However mail set to the old lists, the ones that were moved to this server, is not delivered. I do however get moderation and bounce notices from those lists. I ran check_perms to see if there were any problems with permissions and got the following: file permissions must be at least 660: /var/lib/mailman/lists/ofap_mgrs/config.db (fixing) file permissions must be at least 660: /var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/config.db (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/config.db.last (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/next-digest (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/next-digest-topics (fixing) A second run showed no errors yet still not message being delivered when sent to the older lists. I also have this from the logs. Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: from=<username(a)host.ucar.edu>, size=629, nrcpt=1 (queue active) Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from host2.atd.ucar.edu[128.117.80.16] Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B: to=<listname(a)host.ucar.edu>, relay=local, delay=0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post listname) Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed

3 3

Re: [Mailman-Users] Messages not being delivered.
by Mark Sapiro 16 Jul '07

16 Jul '07

Brandon Slaten wrote: > >Mark Sapiro wrote: >> Brandon Slaten wrote: >~mailman -> /usr/lib/mailman > >There is no lock, qfiles, or log directories there to look at to assess >items 6-8 in the link above. In redhat 2.1.5, they may be in /var/mailman (see below) >I did find the mentioned mailman logs in /var/logs/mailman Here is the >most recent entry in the errors log. atd_systems_notes is one of the >lists moved over from the old server and one I have been testing with. > >Jul 15 08:38:21 2007 (26407) No such list "aa-optical": >Jul 15 08:40:42 2007 (26482) No such list "aa-hygro-growth": >Jul 15 08:52:45 2007 (26737) No such list "aa-phys-size": >Jul 15 09:02:44 2007 (27140) No such list "aa-satellite": >Jul 15 09:09:19 2007 (4397) Uncaught runner exception: [Errno 13] >Permission denied:'/var/lib/mailman/lists/atd_systems_notes/digest.mbox' >Jul 15 09:09:19 2007 (4397) Traceback (most recent call last): > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop > self._onefile(msg, msgdata) > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in >_dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in >_dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 76, in process > mboxfp = open(mboxfile, 'a+') >IOError: [Errno 13] Permission denied: >'/var/lib/mailman/lists/atd_systems_notes/digest.mbox' > >Jul 15 09:09:19 2007 (4397) SHUNTING: >1184512159.0603149+56cd041d3f9dcb1c15807c25c069d965 >53d266da >Jul 15 09:22:48 2007 (27873) No such list "aa-model": >Jul 15 09:31:34 2007 (28149) No such list "esigupcoming": > > >The permissions on the digest.mbox seems to be the issue, after changing >it to be the same as the digest.mbox for the newly created list (660) >all seems to be working. I am surprised that the check_perms script did >not catch that. It's a recently discovered bug in check_perms fixed for 2.1.10. See <http://mail.python.org/pipermail/mailman-users/2007-June/057487.html>. You can now run bin/unshunt to reprocess the shunted messages, but first look at the files in qfiles/shunt to make sure there aren't unwanted stale messages there. You can use bin/dumpdb or bin/show_qfiles (although there is a bug in 2.1.5 show_qfiles that affects some entries, but probably not these) to look at the individual *.pck files in qfiles/shunt and can just remove unwanted ones before running bin/unshunt. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 1

(no subject)
by Jens Andersson 15 Jul '07

15 Jul '07

unsubscribe

1 0

Format conversion
by Bill Suarez 15 Jul '07

15 Jul '07

Perhaps I've missed this in the doc's (but I don't think so). How can I configure Mailman to convert an HTML post into plain text? When a member post from Hotmail or Yahoo in HTML format I end up with a .html attachment and two .txt attachments (for the list header and footer) which makes it very difficult to read messages on portable devices. Any guidance would be appreciated. Thanks in advance, Bill Suarez ________________________________________ WJSuarez - mailto:wsuarez@wsuarez.com http://www.wsuarez.com/

2 2

Re: [Mailman-Users] AOL's "Client TOS Notification"
by Krystal Zipfel 15 Jul '07

15 Jul '07

Remember, AOL is not the only "retarded" ISP out there. Working for a web hosting company, I see this happen all the time. AOL is notorious, but so is Comcast, Bellsouth, and Verizon (to name a few). but hey, if it wasn't for Spam and horrible ISP's that block everyone except themselves... think of how many jobs would be lost? :-) ----- Original Message ---- From: Larry Stone <lstone19(a)stonejongleux.com> To: Mailman <mailman-users(a)python.org> Sent: Saturday, July 14, 2007 5:51:18 PM Subject: Re: [Mailman-Users] AOL's "Client TOS Notification" On 7/14/07 3:53 PM, Dave Dewey at ddewey(a)cyberthugs.com wrote: > Quoting Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de): > >> * Rick Pasotto <rick(a)niof.net>: >> >>> I have recently been getting some of these from one of my mailing lists. >> >> Welcome to the wonderful world of AOL retards. >> >>> There is nothing in it (that I've been able to see) that would tell me >>> who the user is that is rejecting the email. There are several AOL >>> addresses subscribed but only one rejection each time a mailing goes out. >> >> Do you use VERP to send out the mails? If you do that you can see who >> the culprit is. > > VERP doesn't work any longer for these, as of a couple months ago. > They now redact ALL information that can be used to identify the > user, including verp'd addresses. That's unfortunate. At this point, what's the point of getting them if they won't give you any useful information as to who doesn't want the list mail they requested. But it's always been clear that AOL assumes everyone outside is a spammer. They probably can't get their minds around the idea that some of their own customers subscribe to lists and then mark them as spam when they no longer want them rather than properly unsubscribing. And that we, as responsible list owners, want to get them off our lists. I know some will disagree but if it comes to it, then I just make it clear that I don't accept AOL users as subscribers. If they want to subscribe, they will have to do so from a "real" ISP. > Messageid still works, for whatever reason it's the one piece of > header info that isn't redacted at this point. -- Larry Stone lstone19(a)stonejongleux.com http://www.stonejongleux.com/ ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)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/zipfel%40greenacrestec… Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp ____________________________________________________________________________________ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow

1 0

Re : Re : same list name on 2 different domains
by Enzo 14 Jul '07

14 Jul '07

In fact i've found this patch: http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patchAnd no problem to apply it, but now i've great difficulties to make it work with my postfix install I, in fact, use /etc/mailman/postfix-to-mailman.py. It used to work with mailman 2.1.5, but no more with this mailman 2.1.5 + patch any resource on internet to make this patch work with postfix ? Thanks ----- Message d'origine ---- De : Brad Knowles <brad(a)shub-internet.org> À : Enzo <jdespatis(a)yahoo.fr>; mailman-users(a)python.org Envoyé le : Samedi, 14 Juillet 2007, 4h55mn 13s Objet : [Mailman-Users] Re : same list name on 2 different domains On 7/13/07, Enzo wrote: > I use mailman 2.1.5 from debian sarge, is there a simple patch to make > real virtual domain possible ? What do you mean "simple patch"? The patch that Mark linked to is about as simple as these things get, at least as far as it comes to applying a patch. Do you mean, is there a Debian Sarge package that will automate all this for you? I have no idea -- you should talk to your Debian Sarge buddies. Or the maintainer of the Debian package for Mailman. We support Mailman and not specific OSes, so there's not much we can do to help you with OS-specific questions. -- Brad Knowles <brad(a)shub-internet.org>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4> 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail

3 2

Re : same list name on 2 different domains
by Enzo 14 Jul '07

14 Jul '07

arg.... I use mailman 2.1.5 from debian sarge, is there a simple patch to make real virtual domain possible ? ----- Message d'origine ---- De : Mark Sapiro <msapiro(a)value.net> À : Enzo <jdespatis(a)yahoo.fr>; mailman-users(a)python.org Envoyé le : Vendredi, 13 Juillet 2007, 21h24mn 42s Objet : Re: [Mailman-Users] same list name on 2 different domains Enzo wrote: > >I can create list on both domains, but i can't create the same list with the same name on these 2 different domains > <snip> > >Is it possible ? if yes how ? This is a limitation with current Mailman. This limitation will be removed in a future release, but for now, see <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.047.htp> for some links to 3rd party patches. Note also that that FAQ refers to Mailman 2.2 as the version for removal of this limitation. There has since been a renumbering of planned versions so the target for this is now called 3.0. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ___________________________________________________________________________ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com

2 1

Mailman with remote smtp
by Meenal Pant 14 Jul '07

14 Jul '07

I had sent an email to this list sometime ago with a question about using Mailman with a remote smtp server. I have managed to make this work with the following setup: webserver.foo.com is the Mailman webserver where lists are hosted and smtp.foo.com is the mailserver. Both machines have sendmail running on them. I have created a mail alias on smtp.foo.com for every list hosted on webserver.foo.com. fetchmail runs on webserver.foo.com and pops email from these accounts on smtp.foo.com and these mails are then posted to the lists based on aliases defined in /etc/alias on webserver.foo.com The problem is that this method is no at all scalable and portable. Is there a better way of doing this ? I am using a remote smtp server due to security issues. I do not want to open any ports on the webserver. However fetchmail requires running sendmail in daemon mode ( listening at port 25). Is there a good security solution if I decide to run an smtp server and the mailman webserver on the same machine ? Thanks Meenal

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →