Re: [Mailman-Users] Where's Korea? (recurring problem)
Mark Sapiro wrote: It looks like the #include Python.h near the beginning of _koco.c is failing. Is there a python2.4 directory in /usr/include? That was it. python-devel was not installed on this machine. Would be nice if the configure script checked for all the necessary header files prior to compiling/installing. It installed now...though the bazillion errors were still there: src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3008: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3009: warning: pointer targets in initialization differ in signedness src/_koco_uhc.h:3009: warning: pointer targets in initialization differ in signedness In file included from src/_koco.c:121: src/euckr_codec.h: In function ‘euc_kr_encode’: src/euckr_codec.h:127: warning: format ‘%04x’ expects type ‘unsigned int’, but argument 3 has type ‘Py_UNICODE’ In file included from src/_koco.c:122: src/cp949_codec.h: In function ‘cp949_encode’: src/cp949_codec.h:151: warning: format ‘%04x’ expects type ‘unsigned int’, but argument 3 has type ‘Py_UNICODE’ In file included from src/_koco.c:123: src/koco_stream.h: In function ‘__euc_kr_decode’: src/koco_stream.h:42: warning: pointer targets in assignment differ in signedness src/koco_stream.h:43: warning: pointer targets in assignment differ in signedness src/koco_stream.h: In function ‘__cp949_decode’: src/koco_stream.h:135: warning: pointer targets in assignment differ in signedness src/koco_stream.h:136: warning: pointer targets in assignment differ in signedness -- H | It's not a bug - it's an undocumented feature. + Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 3550 Arapahoe Ave. #6 http://www.pcraft.com . . .. Boulder, CO 80303, U.S.A. -- 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] Problem with mailman in combination with sendmail
Dear list, I try to get to run mailman 2.1.9 with sendmail on Debian 4.0. With mailman everything seems to be fine. Well, I can create new lists and get a confirmation of that. Check_perms -f says that everything is all right and in the log-files of mailman are no errors at all. I configured it with: ./configure --prefix=/usr/local/mailman --with-mail-gid=mail --with-cgi-gid=www-data --with-mailhost=h1228898.stratoserver.net --with-urlhost=h1228898.stratoserver.net With: --with-mail-gid=mail I am not so very sure. In the manual is written: On systems using sendmail, the ‘sendmail.cf’ configuration file designates the group id of sendmail processes using the DefaultUser option. So I watched sendmail.cf and it`s written: # default UID (can be username or userid:groupid) O DefaultUser=mail:mail I added the user mail with useradd -g mail -s /bin/false mail - so this should be correct? Sendmail I installed with: apt-get install sendmail In /etc/aliases I have the default-mailmanlist and I have: help: |/usr/local/mailman/mail/mailman post help help-admin:|/usr/local/mailman/mail/mailman admin help help-bounces: |/usr/local/mailman/mail/mailman bounces help help-confirm: |/usr/local/mailman/mail/mailman confirm help help-join: |/usr/local/mailman/mail/mailman join help help-leave:|/usr/local/mailman/mail/mailman leave help help-owner:|/usr/local/mailman/mail/mailman owner help help-request: |/usr/local/mailman/mail/mailman request help help-subscribe:|/usr/local/mailman/mail/mailman subscribe help help-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe help After that I did newaliases and got a confirmation of that. In sendmail.cf there is No entry for smrsh, so I should not have that. The problem is still: If I send a mail to the mailinglist it`s not posted to the members of the list. Has anybode experiences with mailman in combination with sendmail? Is there anything that is important to look at? What I don`t understand: If I get a confirmation after creating a mailinglist or after subscribing a user to a list it should mean that sendmail runs correctly? Or not Thank you very much, Kai -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger -- 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] failing qrunner
Hi guys, We've got a problem with a half-completed delivery run, somehow an address with a ? at the end of the domain managed to get into the list addresses, ie, something like: [EMAIL PROTECTED] instead of just [EMAIL PROTECTED] ... now exim drops the connection when it sees this address, which means that none of the recipients in that run receives the message. Firstly, mailman should not have accepted that address, but this may have been fixed (this is a rather old version, no, I can't upgrade it, nor am I allowed to fix the exim config ... don't even bother asking). What I want to know is how mailman handles the message delivery runs. Afaik each message that needs to go out is stored in some location, along with a list of recipients, so periodically mailman checks which messages needs to go out, and to which recipients, and it then tries to make those deliveries, removing the recipients that it successfully delivers. Is there a manual way to remove the problem-causing email addy from this list for the particular message? We've already removed it from the main list so it won't cause issues in future but it's now holding up the delivery of an already sent message. Jaco -- 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] Where's Korea? (recurring problem)
Ashley M. Kirchner wrote: Mark Sapiro wrote: It looks like the #include Python.h near the beginning of _koco.c is failing. Is there a python2.4 directory in /usr/include? That was it. python-devel was not installed on this machine. Would be nice if the configure script checked for all the necessary header files prior to compiling/installing. You're right. I'll look into that. It installed now...though the bazillion errors were still there: I don't see these here. Perhaps it's some difference between gcc versions or configurations. -- 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] Problem with mailman in combination with sendmail
Kai Behncke wrote: With: --with-mail-gid=mail I am not so very sure. In the manual is written: On systems using sendmail, the 'sendmail.cf' configuration file designates the group id of sendmail processes using the DefaultUser option. So I watched sendmail.cf and it`s written: # default UID (can be username or userid:groupid) O DefaultUser=mail:mail I added the user mail with useradd -g mail -s /bin/false mail - so this should be correct? Yes. That all should be correct. Sendmail I installed with: apt-get install sendmail In /etc/aliases I have the default-mailmanlist and I have: help: |/usr/local/mailman/mail/mailman post help help-admin:|/usr/local/mailman/mail/mailman admin help help-bounces: |/usr/local/mailman/mail/mailman bounces help help-confirm: |/usr/local/mailman/mail/mailman confirm help help-join: |/usr/local/mailman/mail/mailman join help help-leave:|/usr/local/mailman/mail/mailman leave help help-owner:|/usr/local/mailman/mail/mailman owner help help-request: |/usr/local/mailman/mail/mailman request help help-subscribe:|/usr/local/mailman/mail/mailman subscribe help help-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe help After that I did newaliases and got a confirmation of that. In sendmail.cf there is No entry for smrsh, so I should not have that. The problem is still: If I send a mail to the mailinglist it`s not posted to the members of the list. Are you sending to the 'help' mailing list ([EMAIL PROTECTED])? Has anybode experiences with mailman in combination with sendmail? Is there anything that is important to look at? What happens to the mail to the list. Is it returned as undeliverable? If so, why? Look in sendmail's maillog and see what sendmail did with the mail. What I don`t understand: If I get a confirmation after creating a mailinglist or after subscribing a user to a list it should mean that sendmail runs correctly? Or not It means that sendmail is accepting mail via an SMTP connection FROM Mailman and delivering it to the recepient addresses. It does not say anything about whether or not sendmail knows how to deliver mail TO Mailman or even if the mail gets to sendmail. Note I just tried to connect to h1228898.stratoserver.net port 25 from two different machines and was unable to connect. This means that at least at this time sendmail is not listening for a port 25 connection from the outside, and thus mail from the outside cannot be delivered to this machine. -- 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] failing qrunner
Jaco Kroon wrote: What I want to know is how mailman handles the message delivery runs. Afaik each message that needs to go out is stored in some location, along with a list of recipients, so periodically mailman checks which messages needs to go out, and to which recipients, and it then tries to make those deliveries, removing the recipients that it successfully delivers. That is correct. Assuming this is at least Mailman 2.1.x, the messages to be sent are placed in Mailman's 'out' queue (normally Mailman's qfiles/out/ directory) and picked up and delivered by OutgoingRunner. If the MTA returns a non-retryable failure for one or more recipients, that is logged in Mailman's smtp-failure log and treated as a bounce for the failed recipients. If the MTA returns a retryable failure for one or more recipients, that is also logged in Mailman's smtp-failure log and the message is queued in the 'retry' queue for delivery to the failed recipients. Every 15 minutes, RetryRunner moves the message from the retry queue back to the out queue. This continues for DELIVERY_RETRY_PERIOD (default 5 days) after which, Mailman gives up on this message. Is there a manual way to remove the problem-causing email addy from this list for the particular message? We've already removed it from the main list so it won't cause issues in future but it's now holding up the delivery of an already sent message. First find the entry (a long, mostly numeric, name ending in .pck) in qfiles/retry, and move that file aside. Then use Mailman's bin/dumpdb to dump the file. This will output the raw message and the message metadata. The metadata contains a list of 'recips' which is the addresses remaining to be delivered. If you are proficient in Python, you could write a short script to unpickle the message and metadata from the file, remove the bad recipient from recips and repickle the message and metadata. then you could put the file in qfiles/out for delivery. (I'm currently debugging one I just wrote - I'll post a link soon). Alternatively, you could just remail the message outside of mailman to the remaining recipients. -- 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] failing qrunner
Mark Sapiro wrote: If you are proficient in Python, you could write a short script to unpickle the message and metadata from the file, remove the bad recipient from recips and repickle the message and metadata. then you could put the file in qfiles/out for delivery. (I'm currently debugging one I just wrote - I'll post a link soon). The minimally tested script is at http://veenet.value.net/~msapiro/scripts/remove_recips and mirrored at http://fog.ccsf.edu/~msapiro/scripts/remove_recips. -- 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] failing qrunner
Jaco Kroon wrote: Mark Sapiro wrote: Jaco Kroon wrote: Ok. That covers the 4xx and 5xx responses to rcpt to:, what happens if the MTA simply closes the connection? What I gathered the smtp conversation had to look like was something like: S: 220 servername ESMTP Exim C: helo servername S: 250 servername Hello localhost [127.0.0.1] C: mail from: [EMAIL PROTECTED] S: 250 OK C: rcpt to: [EMAIL PROTECTED] S: 250 OK C: rcpt to: [EMAIL PROTECTED] S: --- force close connection --- It will be logged in the 'smtp-failure' as a 'Low level smtp error' and in the 'post' log with the number refused. It shouldn't be retried. What's in Mailman's 'smtp', 'smtp-failure' and 'post' logs? Now, the problem here is that you don't really know whether it's a 5xx or a 4xx error code, and it actually looks like the entire run for that message gets interrupted and put to sleep in it's entirety. Thus may have been a bug that got fixed at some point (I don't even know which exact version of mailman I'm working with, but it's at the latest something released around Feb 2007). So at this point it simply wouldn't continue any further, and smtp-failures actually logs the address after the faulty one as the one causing a problem. It depends on what exception is returned by Python's smtplib. If Exim really just closes the connection, it will be logged in 'post' with a number of failures as well as being logged in 'smtp-failure' as a 'Low level' error and in 'smtp', and each attempted recipient from that transaction (all the ones up to SMTP_MAX_RCPTS (default 500) that were going to be delivered, not just the ones whose rcpt to was not sent) will be logged in 'smtp-failure' as 'code -1: error'. Then the message will be put in the retry queue with the same recips list minus any that were successfully delivered in a prior smtp transaction. What is in the Mailman logs? This continues for DELIVERY_RETRY_PERIOD (default 5 days) after which, Mailman gives up on this message. Is there a manual way to remove the problem-causing email addy from this list for the particular message? We've already removed it from the main list so it won't cause issues in future but it's now holding up the delivery of an already sent message. First find the entry (a long, mostly numeric, name ending in .pck) in qfiles/retry, and move that file aside. Then use Mailman's bin/dumpdb to dump the file. This will output the raw message and the message metadata. The metadata contains a list of 'recips' which is the addresses remaining to be delivered. I saw the dumpdb program, had no idea what it does though. Now I do, and it'll make my life a lot easier next time. Any way to repack the file? If you are proficient in Python, you could write a short script to unpickle the message and metadata from the file, remove the bad recipient from recips and repickle the message and metadata. then you could put the file in qfiles/out for delivery. (I'm currently debugging one I just wrote - I'll post a link soon). ... or issue mailmanctl stop, use vim on the file, find the invalid address and without changing the size of the file change the address to an RFC legal address that is bogus, ie, [EMAIL PROTECTED] can be changed to [EMAIL PROTECTED] which causes the pickle to not break, and will cause exim to not close the connection ... instead it will bounce back to mailman, harmlessly since this server isn't using VERP. Yes, you could do that, but as I posted later in this thread, there is now a script to just delete the bad address at http://veenet.value.net/~msapiro/scripts/remove_recips and mirrored at http://fog.ccsf.edu/~msapiro/scripts/remove_recips. And, if you really wanted to use vim, there's no need to stop Mailman. Just move the file out of the queue directory, edit it, dump it with bin/dumpdb to verify it can still be unpickled and move it back. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Approved header problem
I've been using Mailman with great success for almost 9 months through EMWD (http://www.emwd.com/mailman.html). Now I have a question that I have been unable to find a match to in the old messages or FAQ. Following the instructions in the FAQ entry 3.11, How do I create a newsletter/announcement/one-way list?, I have been sending to an announcement list for months by adding the Approved: password line at the start of the message text. But sometimes I screw up and past it into the wrong email, and then have to change the password. In an attempt to avoid that mistake I figured out how to make my email program add this as a actual header line. It adds it as the third header line, after the From and To, before the Subject. But Mailman, running version 2.1.9.cp2, rejects it and sends it back as it would if I left the Approved out. Does anyone have any ideas? I see no way in my email program to control the position of the Approved header item in the list. Thanks! Roy Harvey Beacon Falls, CT -- 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] Approved header problem
Roy Harvey wrote: But sometimes I screw up and past it into the wrong email, and then have to change the password. In an attempt to avoid that mistake I figured out how to make my email program add this as a actual header line. It adds it as the third header line, after the From and To, before the Subject. But Mailman, running version 2.1.9.cp2, rejects it and sends it back as it would if I left the Approved out. Does anyone have any ideas? I see no way in my email program to control the position of the Approved header item in the list. First, the order of the headers is not relevant. Mailman will find the Approved: header wherever it is and remove it from any message delivered to the list members. If the Approved: header contains the correct list password without any trailing whitespace, the message will be marked approved. Second, how does this protect you against revealing the password by sending it to the wrong place? You could still add the Approved: header to an email to a non-list address. Third, this is a cPanel Mailman so there could be a cPanel issue involved. See FAQ 6.11 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp. But, I suspect the issue is trailing whitespace on the Approved: password header. I.e., if the password is aBc123, 'Approved: aBc123' will work, as will 'Approve: aBc123' and even 'Approved:aBc123', but 'Approved: aBc123 ' will not. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Umbrella-bounces address?
I've been working on setting up and umbrella list that sends to four sub-lists. I have this working well if someone submits an email to the umbrella list and they are subscribed to the sub-lists. However, I have a question about the proper configuration handling a post from someone who is not a member of a sublist . In Mailman FAQ 3.69 there is a section that states: The second issue is when a member of one sub-list posts to the umbrella, her post is held by the sublists of which she is not a member. There are two ways to deal with this. if the mm_cfg.py option USE_ENVELOPE_SENDER is Yes or True, you can add the umbrella's - bounces address to accept_these_nonmembers of sublists. In any case, you can add the umbrella's -bounces address as a member with delivery disabled and password reminders off to the sublists. I know that this is a stupid question, but what is the umbrella- bounces address for any given list? If my list is [EMAIL PROTECTED], what would the -bounces address be? Thanks, J.R. -- 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] Umbrella-bounces address?
J.R. Constance wrote: I know that this is a stupid question, but what is the umbrella- bounces address for any given list? If my list is [EMAIL PROTECTED], what would the -bounces address be? [EMAIL PROTECTED] which is the Sender: and envelope sender of mail from the List-A list. -- 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] failing qrunner
On 9/15/07, Jaco Kroon wrote: So at this point it simply wouldn't continue any further, and smtp-failures actually logs the address after the faulty one as the one causing a problem. To avoid this problem in the future, try enabling personalization on the list, and using VERP. Then Mailman will make separate delivery attempts for each user, and only the invalid one would fail in the manner you described. The rest should go through normally. This would be a bigger performance hit on the server, but would help make your day-to-day operations more robust. This is especially important since you've said you can't upgrade any of the software, and we know that more recent versions of Mailman have significantly improved their ability to handle failures of various different types and continue trying to deliver everything else. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- 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
