[Mailman-Users] mailman + postfix issue
Hi! I'm trying to configure mailman+postix in a debian machine and I found some problems... It seems that postfix don't know how to pipe emails to correct location (mailman) and is trying to deliver the message to a mailbox that do not exists Apr 21 16:19:44 davos postfix/virtual[17439]: 929404A7FE: to= t...@davos.web83.es, relay=virtual, delay=63369, delays=63369/0.02/0/0.02, dsn=4.2.0, status=deferred (delivery failed to mailbox /var/mail/vmail/|/var/lib/mailman/mail/mailman post test: unable to create lock file /var/mail/vmail/|/var/lib/mailman/mail/mailman post test.lock: No such file or directory) Any idea? What logs do you need to see my configuration? thanks in advance!! -- Backup not found: (A)bort, (R)etry, (S)uicide? David Fernandez Lopez -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Want posts from mylist to mylist to be held
Hi mailman experts, My mailman list 'mylist' has non-member posts set to be rejected. This has done an excellent job of preventing spam in the past. Recently, a spam message was successfully posted to mylist. The From field showed myl...@myserver.edu (i.e., the same address that one uses when posting *to* mylist). Looking in the list of subscribers, I don't see 'mylist' as a member. And typically posts do not come from the list; rather, they are just posted *to* the list *from* an individual subscriber's email address. Why aren't posts *from* myl...@myserver.edu being rejected, since myl...@myserver.edu is a non-member from the point of view of the list? I thought about putting From: myl...@myserver.edu in the spam filter, and setting the action to Hold; however, I don't want a message being sent to everyone on mylist every time a spam message gets held for moderator approval. I do, however, want these messages held, so I can inspect them. (Or at least a copy emailed to me, the list moderator, before the message is discarded.) Thanks, Donna -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Setting Password reminder problem
I have 2 mail lists and in General Options set both lists to NO on Sending monthly password reminders. All new subscribers are still set to YES when they join. The mailman is provided by my host company and lists are managed through cPanel. The hosting company was able to replicate the issue. It is Mailman version 2.1.10 Gary gels...@juno.com Always a good call. Click now to establish your local phone service! http://thirdpartyoffers.juno.com/TGL2141/fc/BLSrjpTHbDiaO2fMfcBikU7uzprAPtog78siaXnscyNuXRfnEsRzYXt2f0s/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Cluster of postfix
Hello, i used the NFS shared files. A day the Nas Server crashed and my smtp servers could not work normaly. I had the conf files and the all db files. Thank you. Date: Fri, 17 Apr 2009 19:19:40 +0200 From: Melvyn Sopacua m...@dnr.servegame.org Subject: Re: Cluster of postfix On Friday 17 April 2009 18:16:01 Victor Duchovni wrote: On Fri, Apr 17, 2009 at 06:11:24PM +0200, Melvyn Sopacua wrote: Mailbox files, on the other hand, are usually overwritten, and they are updated in place. This almost works reliably, especially if you use dotlock files and turn off NFS attribute caching. And I was talking about OP's case of sharing configuration files. I do a lot more with nfs, where multiple machines can write to the same file. As long as I do it in sequence, the other ones will see the changes. Two people editing the same file falls into shooting yourself in the foot category and is not specific to NFS or even two different machines. It is IMHO much more sensible to push config files from a central machine where the configs are kept under revision control in CVS, SVN, ... than to share configs (and indexed tables) via NFS. I'm looking to save work, not add more or replace one with the other. Plus I have ZFS snapshots [1]. Either way, as long as I keep bdb libraries in sync on the machines, my initial tests show this is working as I expected. Now I'll just sit and wait for the corner cases where it won't work, but can't think of any. ;) [1] http://people.freebsd.org/~pjd/misc/zfs/zfs_snapshot.swf - -- Melvyn Sopacua -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] strange problem mailman 2.1.10
Thanks for answer ;) You are right...it was selected that that user does not want to receive mails...very strange since users cannot configure anything...but whatever..its ok now :) Thanks :) Radim On 04/17/2009 06:56 PM, Mark Sapiro wrote: Radim Roska, IAESTE CVUT wrote: I've got strange problem. It looks mailman does not send mails to all list members. My mailman is 2.1.10 with modinc-2.1.9-0.1.patch and mhonarc-2.1.9-0.1.patch patches... # list_members mail-list | wc -l 45 And what do you get from # list_members --regular --nomail=enabled mail-list | wc -l log in mailman: Apr 17 00:46:18 2009 (5109)49e7b53f.8050...@domain.tld smtp to mail-list for 43 recips, completed in 0.081 seconds If the number of regular members with delivery enabled (at the time of the post) is 43, the reasons for non-delivery to a member could be - The poster has selected the option to not receive her own posts. - One or more list members was directly addressed in the To: or Cc: of the post and has selected the option to not receive duplicates from the list. -- Radim Roska ___ IAESTE CVUT Praha Technicka 4, CZ-166 07 Praha 6 - Dejvice TEL: +420 224 352 659 | http://www.cvut.iaeste.cz FAX: +420 224 352 635 | http://www.iKariera.cz GSM: +420 737 541 447 | radim.ro...@iaeste.cz ___ iKariera.cz - students recruitment portal -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] mails bounce when sent to join address
On Fri, Apr 17, 2009 at 17:09, punit_j puni...@rediffmail.com wrote: Hi ,I am integrating mailman with postfix. I have created new transport by name mailman :-mailmannbsp;nbsp; unixnbsp; -nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; nnbsp;nbsp;nbsp;nbsp;nbsp;nbsp; If you can't persuade your webmail interface to send only in plain text then I suspect you'll get little help from the list. Your messages are impossible to understand, as Mark has already said. -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Cluster of postfix
on 4/18/09 10:23 AM, Juan Antonio Cuesta said: i used the NFS shared files. A day the Nas Server crashed and my smtp servers could not work normaly. I had the conf files and the all db files. I think you sent this to the wrong list. The message you are responding to appears more likely to have been on the postfix-users mailing list. I have a great deal of respect for what Victor Duchovni has to say about postfix, but so far as I know he is not a subscriber to this list, and I don't recall seeing any such discussion recently on this list. -- Brad Knowles b...@shub-internet.orgIf you like Jazz/RB guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://tinyurl.com/y8kpxuhttp://preview.tinyurl.com/bigsbytracks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Sending bulk mail (400,000 users)
On Sat, Apr 11, 2009 at 09:38:05PM +0530, Phoenix Kiula wrote: Hi. I need to send annoucements to a large opt-in list. Having never done this before [...] Since you've never done this before, and you mention that the list has 400K users, I urge extreme caution. Unless you/your operation have explicitly requested and explicitly received permission from all 400K users to send them bulk email, then you should not do so. Note that permission is NOT transferable: a user who has given permission to A to receive bulk email from A has not given that same permission to B. Permission cannot be bought, sold, traded, presumed or inferred: and the sending of bulk email without permission is called spamming. For further explanation, please see: http://www.spamhaus.org/faq/answers.lasso?section=Marketing%20FAQs ---Rsk -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman + postfix issue
David Fernandez Lopez wrote: I'm trying to configure mailman+postix in a debian machine and I found some problems... It seems that postfix don't know how to pipe emails to correct location (mailman) and is trying to deliver the message to a mailbox that do not exists Apr 21 16:19:44 davos postfix/virtual[17439]: 929404A7FE: to= t...@davos.web83.es, relay=virtual, delay=63369, delays=63369/0.02/0/0.02, dsn=4.2.0, status=deferred (delivery failed to mailbox /var/mail/vmail/|/var/lib/mailman/mail/mailman post test: unable to create lock file /var/mail/vmail/|/var/lib/mailman/mail/mailman post test.lock: No such file or directory) Any idea? What logs do you need to see my configuration? It looks like your postfix configuration is incorrect. You are using virtual delivery instead of local delivery for this mail. This is a Postfix configuration issue, not a Mailman issue per se, but if you post the output of postconf -n, someone here may be able to help you. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Want posts from mylist to mylist to be held
Donna Dierker wrote: Recently, a spam message was successfully posted to mylist. The From field showed myl...@myserver.edu (i.e., the same address that one uses when posting *to* mylist). Looking in the list of subscribers, I don't see 'mylist' as a member. And typically posts do not come from the list; rather, they are just posted *to* the list *from* an individual subscriber's email address. Why aren't posts *from* myl...@myserver.edu being rejected, since myl...@myserver.edu is a non-member from the point of view of the list? They should be. It may be too late to find why this one was accepted, but if you have access, you can find the post in the archives/private/LISTNAME.mbox/LISTNAME.mbox file and see some of the original headers. A post is considered to be from a list member if any of From:, Reply-To: or Sender: or the envelope sender is a list member. It is also possible, although not likely, that the spammer knows the list admin or moderator password and put an Approved: password header in the post, but if this was done, the evidence will be gone. I thought about putting From: myl...@myserver.edu in the spam filter, and setting the action to Hold; however, I don't want a message being sent to everyone on mylist every time a spam message gets held for moderator approval. I do, however, want these messages held, so I can inspect them. (Or at least a copy emailed to me, the list moderator, before the message is discarded.) This is difficult. You could use header_filter_rules to discard the message, but then you won't see it even with forward_auto_discards true because that applies only to moderated and non-member auto discards. If you hold the message, the notice to the sender, even if to the list, should not be accepted as it is from LISTNAME-bounces, but if you want to be really sure, you could set respond_to_post_requests to No so there is no held notice back to the poster. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Setting Password reminder problem
Gary Elsner wrote: I have 2 mail lists and in General Options set both lists to NO on Sending monthly password reminders. All new subscribers are still set to YES when they join. These are two different settings. If the list's Send monthly password reminders? (send_reminders) is No, monthly reminders will not be sent regardless of the user setting. The user's setting allows a user to opt out if send_reminders is yes, but does not allow opting in is send_reminders is no. The default for new members for the reminder option is one of the new_member_options bits, but it is not one that's available through the web admin interface. It can only be set to No by turning on the 32 bit in the lists new_member_options attribute via bin/withlist or bin/config_list, but as noted above, this is unnecessary, as setting Send monthly password reminders? (send_reminders) to No says no monthly reminders are sent regardless of user settings. The mailman is provided by my host company and lists are managed through cPanel. The hosting company was able to replicate the issue. See the FAQ at http://wiki.list.org/x/sYA9. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman 2.1.12 - Python 2.4.[456] incompatibility
On Mon, 16 Mar 2009 10:52:05 Mark Sapiro wrote:
There is an internal inconsistency in the 3.0.2 email package that
shipped with Python 2.4.4 through 2.4.6. This has to do with the
Charset.Charset() constructor setting input_charset to a unicode which
then causes TypeError: decoding Unicode is not supported exceptions in
other parts of the email package. This problem does not seem to occur
with email 3.0.1 and Python 2.4.[123].
This (along with other stuff) is discussed in the bug report at
https://bugs.launchpad.net/mailman/+bug/328353 and there is a patch
for email/Charset.py at
http://launchpadlibrarian.net/23670138/Charset.py.patch
At this point, the best advice seems to be use Python 2.5 or 2.6 with
Mailman 2.1.12.
The patch is to module Charset.py. I was looking for that in my
2.1.12 directories, and I cannot find it. In comparing my 2.1.11
directories with my 2.1.12 directories I find the problem.
These directories are where I built my Ubuntu packages from the
SourceForge source.
In
build_mailman_2.1.11/mailman-2.1.11/misc/Makefile.in
I have
EMAILPKG= email-2.5.8
JACODECSPKG=JapaneseCodecs-1.4.11
KOCODECSPKG=KoreanCodecs-2.0.5
and I have the same in Makefile.in . But in
build_mailman_2.1.12/mailman-2.1.12/misc/Makefile.in
I have
EMAILPKG= @EMAILPKG@
JACODECSPKG=JapaneseCodecs-1.4.11
KOCODECSPKG=KoreanCodecs-2.0.5
and in Makefile.in
EMAILPKG=
JACODECSPKG=JapaneseCodecs-1.4.11
KOCODECSPKG=KoreanCodecs-2.0.5
As a result, I have in the misc directory for 2.1.12
email-2.5.8.tar.gz
and that tarball was not untarred, so I do not have Charset.py .
In the build process output for 2.1.11 I see
for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \
do \
gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \
...
and for 2.1.12 I see
for p in JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \
do \
gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \
...
In the 2.1.12 configure I see
# Should we rely on Python's own email package or use the pre-packaged version?
if test $needemailpkg = ok
then
EMAILPKG=
else
EMAILPKG=email-2.5.8
fi
echo $as_me:$LINENO: result: $needemailpkg 5
echo ${ECHO_T}$needemailpkg 6
and in the build output I see
checking Python version... 2.4.3
checking Python's email package... ok
I am confused. Is the 2.1.12 build using the Python-supplied e-mail
library, and thus the patch to Charset.py has to be made there?
Or do I have to specify something to get the Mailman-supplied
e-mail package untarred? Thanks.
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory Phone:+1 (630) 252-7277
9700 South Cass Avenue Facsimile:+1 (630) 252-4601
Building 222, Room D209 Internet: bsfin...@anl.gov
Argonne, IL 60439-4828 IBMMAIL: I1004994
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman 2.1.12 - Python 2.4.[456]incompatibility
Barry Finkel wrote: On Mon, 16 Mar 2009 10:52:05 Mark Sapiro wrote: There is an internal inconsistency in the 3.0.2 email package that shipped with Python 2.4.4 through 2.4.6. This has to do with the Charset.Charset() constructor setting input_charset to a unicode which then causes TypeError: decoding Unicode is not supported exceptions in other parts of the email package. This problem does not seem to occur with email 3.0.1 and Python 2.4.[123]. This (along with other stuff) is discussed in the bug report at https://bugs.launchpad.net/mailman/+bug/328353 and there is a patch for email/Charset.py at http://launchpadlibrarian.net/23670138/Charset.py.patch At this point, the best advice seems to be use Python 2.5 or 2.6 with Mailman 2.1.12. The patch is to module Charset.py. I was looking for that in my 2.1.12 directories, and I cannot find it. In comparing my 2.1.11 directories with my 2.1.12 directories I find the problem. These directories are where I built my Ubuntu packages from the SourceForge source. Charset.py is not a Mailman module; it is a Python email module. In 2.1.11, we actually install email 2.5.8 in Mailman's pythonlib. Beginning in 2.1.12, we import email during configure, and if it is new enough, we do not install email 2.5.8 in pythonlib. This is where the problem arises. If you have a python installed that includes email 3.0.2 (python 2.4.4 - 2.4.6), we will accept that, and it is that email library that has the inconsistency. [various observations snipped] I am confused. Is the 2.1.12 build using the Python-supplied e-mail library, and thus the patch to Charset.py has to be made there? Yes. That's exactly the issue. Or do I have to specify something to get the Mailman-supplied e-mail package untarred? Thanks. That would be another approach. After running ./configure and before running any make commands, you could edit misc/Makefile to replace the line EMAILPKG= with EMAILPKG= email-2.5.8 to install email 2.5.8 in Mailman's pythonlib. Then you wouldn't need to patch anything. But, how this fits with the Ubuntu package, I don't know. Note that the only Charset.py that needs patching is the one from email 3.0.2 which shipped only with Python 2.4.4 through python 2.4.6 -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
