Mailman 3 January 2007 - Mailman-coders

[ mailman-Bugs-1635915 ] Variables in the template postauth.txt are not substituted
by SourceForge.net Jan. 15, 2007

Jan. 15, 2007

Bugs item #1635915, was opened at 2007-01-15 16:31 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jussi Hirvi (jhirvi) Assigned to: Nobody/Anonymous (nobody) Summary: Variables in the template postauth.txt are not substituted Initial Comment: The template file postauth.txt contains: > As list administrator, your authorization is requested for thefollowing > mailing list posting: > List: %(listname)s@%(hostname)s From: %(sender)s Subject: > %(subject)s Reason: %(reason)s > > At your convenience, visit: > %(admindb_url)s > to approve or deny the request. When an email is sent to the administrator, the variables are of course supposed to be substituted with their respective values. THis didn't happen, however. I cannot think of another explanation than a bug. My Mailman version is 2.1.8. In this case, I'm using Finnish versions of the templates (modified by me), but that shouldn't affect this, I think. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_…

1 0

[ mailman-Patches-1123383 ] Daily Status Report script...
by SourceForge.net Jan. 13, 2007

Jan. 13, 2007

Patches item #1123383, was opened at 2005-02-15 12:14 Message generated for change (Comment added) made by daveyost You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- Comment By: Dave Yost (daveyost) Date: 2007-01-12 23:32 Message: Logged In: YES user_id=330919 Originator: NO I suggest incorporating the readme into the shell script, so there is only the one file. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2006-01-25 17:55 Message: Logged In: YES user_id=18417 Folks, Okay, I just uploaded version 0.0.15, which addresses the most recent comments here from Mark and Tom, and makes a few additional tweaks as well. See the version comments at the top of the script. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-06 10:25 Message: Logged In: YES user_id=1123998 The vette log summary lists posts held for moderation individually under "Other Errors:". The following patch (watch out for wrapped lines) summarizes them by list instead. --- mmdsr 2005-09-29 21:31:33.000000000 -0700 +++ mmdsrx 2005-11-06 08:20:58.835895418 -0800 @@ -415,10 +415,15 @@ echo "------------------------------" >> $TMP $GREP -i 'Posting to a moderated newsgroup' $TMPLOG | $AWK '{ print $6 }' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + echo "" >> $TMP + echo "Post to moderated list (by list):" >> $TMP + echo "------------------------------" >> $TMP + $GREP -i 'Post to moderated list' $TMPLOG | $AWK '{ print $6 }' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + echo "" >> $TMP echo "Other Errors:" >> $TMP echo "------------------------------" >> $TMP - $EGREP -vi '(Post by non-member|suspicious header|message approved|Discarded posting|bulk message discarded|junk message discarded|Message has implicit destination|Posting to a moderated newsgroup|Message discarded, msgid)' $TMPLOG | $SED 's/^.* ([0-9]*) //' | $SORT | $UNIQ -c | $SORT -nr >> $TMP + $EGREP -vi '(Post by non-member|suspicious header|message approved|Discarded posting|bulk message discarded|junk message discarded|Message has implicit destination|Posting to a moderated newsgroup|Post to moderated list|Message discarded, msgid)' $TMPLOG | $SED 's/^.* ([0-9]*) //' | $SORT | $UNIQ -c | $SORT -nr >> $TMP else ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-10-19 01:23 Message: Logged In: YES user_id=1159458 ps output on solaris is full of whitespace but a further echo get's rid of it. The lines in the smtp log are sometimes broken up by a newline (right before the msgid) which throws of the summary. Piping it through sed first will rejoin the broken lines. Use $AWK instead of awk. Patch inserted below: --- mmdsr.orig 2005-10-19 09:42:30.000000000 +0200 +++ mmdsr 2005-10-19 09:44:23.000000000 +0200 @@ -203,7 +203,8 @@ # there is an easier cross-platform way to do it, please let me know. ############################################################################### -MYUID=`$PS -o user -p $$ | $TAIL -1` +GRABUID=`$PS -o user -p $$ | $TAIL -1` +MYUID=`echo $GRABUID` RUNAS="mailman" ############################################################################### @@ -254,7 +255,7 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG + $SED -e :a -e '$!N;s/\n //;ta' -e 'P;D' $LOGDIR/$LOG | $GREP -si "^$DAY [0-9][0-9:]* $YEAR" >> $TMPLOG if [ -f "$LOGDIR/${LOG}" ] ; then @@ -264,7 +265,7 @@ echo "Hourly Summary of Posts" >> $TMP echo "-----------------------" >> $TMP - $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.*$//' $TMPLOG | $UNIQ -c | $SORT -n +1 | awk '{ printf( "%8d %02d:00-%02d :59\n", $1, $2, $2 ) }' >> $TMP + $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.*$//' $TMPLOG | $UNIQ -c | $SORT -n +1 | $AWK '{ printf( "%8d %02d:00-%02 d:59\n", $1, $2, $2 ) }' >> $TMP echo "" >> $TMP echo "Post Count by List" >> $TMP @@ -295,7 +296,7 @@ echo "" >> $TMP echo "Hourly Summary of Messages Sent" >> $TMP echo "-------------------------------" >> $TMP - $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.* for / /' -e 's/ recips,.*$//' $TMPLOG | awk '{ val=int($1); sum[val]+=$2 } END { for (i=0; i<24; i++) { printf "%8d %02d:00-%02d:59\n", sum[i], i, i } }' >> $TMP + $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e 's/:.* for / /' -e 's/ recips,.*$//' $TMPLOG | $AWK '{ val=int($1); sum[val]+=$ 2 } END { for (i=0; i<24; i++) { printf "%8d %02d:00-%02d:59\n", sum[i], i, i } }' >> $TMP else ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-22 16:17 Message: Logged In: YES user_id=18417 Okay, I took Mark's comments and incorporated them. Adrian Wells also pointed out a log file difference between Mailman 2.1.5 and 2.1.6 that caused the summary of the "smtp" log to be munged. I've now fixed these bugs, deleted the old file, and uploaded the new one (version 0.0.12). Thanks! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-10 19:22 Message: Logged In: YES user_id=1123998 Oooops! I mistakenly thought I could add the mmdsr.patch as a downloadable file, but I can't so here it is. Watch out for wrapped lines ... --- mmdsr.orig 2005-09-06 20:37:53.000000000 -0700 +++ mmdsr 2005-09-10 18:33:14.532393572 -0700 @@ -132,6 +132,7 @@ MMDIR="/usr/local/mailman" TMPDIR="/tmp" +LOGDIR="/var/log/mailman" ############################################################################### # Maximum number of subdirectory entries to display in report @@ -234,9 +235,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "post" ] ; then @@ -304,9 +305,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "error" ] ; then @@ -453,4 +454,4 @@ $CAT $TMP fi -$RM $TMP +$RM -f $TMP $TMPLOG ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-10 19:16 Message: Logged In: YES user_id=1123998 I tried the script and other than the expected site specific changes, I found two issues which are both addressed by the patch in the mmdsr.patch file. 1) Mailman's log files are not necessarily in $var_prefix/logs/ - they can be in any directory. The patch adds a LOGDIR directory independant of MMDIR. 2) The $TMPLOG file is not removed at completion. The patch removes it. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-06 07:06 Message: Logged In: YES user_id=18417 Okay, I've deleted the old version of the mmdsr script that was attached, and uploaded the latest version. This is what we're currently using to monitor the lists on python.org, and we have found it very useful. Any comments you may have will be appreciated. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-02-22 12:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 07:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 00:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_…

1 0

[ mailman-Feature Requests-1634521 ] Need admin alerts
by SourceForge.net Jan. 13, 2007

Jan. 13, 2007

Feature Requests item #1634521, was opened at 2007-01-12 19:58 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1634521&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None >Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Yost (daveyost) Assigned to: Nobody/Anonymous (nobody) Summary: Need admin alerts Initial Comment: I just noticed that for some reason none of our mailing lists have been archived for a while. Yikes. It would be good if mailman by default would notify admins if anything goes wrong with archiving. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-01-12 20:31 Message: Logged In: YES user_id=1123998 Originator: NO I am moving this to feature requests because that's what it is. As far as your issue of not archiving is concerned, it seems that perhaps ArchRunner is/was not running. If this is the case, addressing the issuue that caused it to die and restarting it will probably archive all the unprocessed messages in the archive/ queue. OTOH, possible there is some issue causing the messages to be shunted. In this case, fixing the underlying issue and running bin/unshunt should archive the messages. It would be very unusual if the messages were completely lost. Regarding your feature request, look at the "Daily status report script" (mmdsr) <http://sourceforge.net/tracker/index.php?func=detail&aid=1123383&group_id=1…> and in Mailman's contrib/ directory since 2.1.7. It's not a 'default' but it does a good job of reporting things that go wrong. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1634521&group_…

1 0

[ mailman-Bugs-1634521 ] Need admin alerts
by SourceForge.net Jan. 13, 2007

Jan. 13, 2007

Bugs item #1634521, was opened at 2007-01-12 19:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634521&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.0.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Yost (daveyost) Assigned to: Nobody/Anonymous (nobody) Summary: Need admin alerts Initial Comment: I just noticed that for some reason none of our mailing lists have been archived for a while. Yikes. It would be good if mailman by default would notify admins if anything goes wrong with archiving. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634521&group_…

1 0

[ mailman-Bugs-1634504 ] Mailman blows away <x-flowed>
by SourceForge.net Jan. 13, 2007

Jan. 13, 2007

Bugs item #1634504, was opened at 2007-01-12 18:41 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.0.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Yost (daveyost) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman blows away <x-flowed> Initial Comment: Somebody replies to a list message, with To going to a me, and Cc going to the list. The former has this body: <x-flowed> Dave Yost wrote: > blah blah blah </x-flowed> Whereas the latter has this body: Dave Yost wrote: > blah blah blah _______________________________________________ Foo mailing list foo(a)bar.com https://bar.com/cgi-bin/mailman/listinfo/foo ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-01-12 19:13 Message: Logged In: YES user_id=1123998 Originator: NO Mailman is not doing this unless the original message contains alternative parts and content filtering is removing the part with <x-flowed></x-flowed> tags. Under some circumstances, Mailman will remove an RFC 3676 Format=Flowed parameter from the Content-Type: header. This is bug #1495122 <https://sourceforge.net/tracker/index.php?func=detail&aid=1495122&group_id=…>. If some MTA/MDA/MUA is generating the <x-flowed></x-flowed> tags from the Format=Flowed parameter, then Mailman could be indirectly responsible. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&group_…

1 0

[ mailman-Bugs-1634504 ] Mailman blows away <x-flowed>
by SourceForge.net Jan. 13, 2007

Jan. 13, 2007

Bugs item #1634504, was opened at 2007-01-12 18:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.0.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Yost (daveyost) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman blows away <x-flowed> Initial Comment: Somebody replies to a list message, with To going to a me, and Cc going to the list. The former has this body: <x-flowed> Dave Yost wrote: > blah blah blah </x-flowed> Whereas the latter has this body: Dave Yost wrote: > blah blah blah _______________________________________________ Foo mailing list foo(a)bar.com https://bar.com/cgi-bin/mailman/listinfo/foo ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&group_…

1 0

[ mailman-Bugs-1634501 ] Does mailman blow away <x-flowed>
by SourceForge.net Jan. 13, 2007

Jan. 13, 2007

Bugs item #1634501, was opened at 2007-01-12 18:36 Message generated for change (Settings changed) made by daveyost You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634501&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Deleted Resolution: None Priority: 5 Private: No Submitted By: Dave Yost (daveyost) Assigned to: Nobody/Anonymous (nobody) Summary: Does mailman blow away <x-flowed> Initial Comment: Somebody to a list message, with To going to a person, and Cc going to the list. The person gets this body: <x-flowed> Dave Yost wrote: > blah blah blah </x-flowed> Whereas the list gets this body: Dave Yost wrote: > blah blah blah _______________________________________________ Foo mailing list foo(a)bar.com https://bar.com/cgi-bin/mailman/listinfo/foo ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634501&group_…

1 0

[ mailman-Bugs-1634501 ] Does mailman blow away <x-flowed>
by SourceForge.net Jan. 13, 2007

Jan. 13, 2007

Bugs item #1634501, was opened at 2007-01-12 18:36 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634501&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Yost (daveyost) Assigned to: Nobody/Anonymous (nobody) Summary: Does mailman blow away <x-flowed> Initial Comment: Somebody to a list message, with To going to a person, and Cc going to the list. The person gets this body: <x-flowed> Dave Yost wrote: > blah blah blah </x-flowed> Whereas the list gets this body: Dave Yost wrote: > blah blah blah _______________________________________________ Foo mailing list foo(a)bar.com https://bar.com/cgi-bin/mailman/listinfo/foo ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634501&group_…

1 0

[ mailman-Bugs-1629971 ] Repeat Emails from Mailman 2.1.9
by SourceForge.net Jan. 12, 2007

Jan. 12, 2007

Bugs item #1629971, was opened at 2007-01-07 08:45 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: mfr301 (mfr301) Assigned to: Nobody/Anonymous (nobody) Summary: Repeat Emails from Mailman 2.1.9 Initial Comment: Hello, I currently use your software as a reseller client with ResellerZoom.com. 3 days ago my clients and myself started receiving numerous repeat emails. The emails were being sent by the mailing list section of Mailman 2.1.9. The problem is that every time (Since it started and has been going on for 3 straight days), I receive emails, they are the SAME emails over and over. Their not visible on the mailing list, their not in a que, and their not in pending messages. I have a client who kept deleting mailing lists (like test@.....) and it kept re-appearing. I have been on line with the ResellerZoom tech support CONSTANTLY from my blackberry for 3 days since the problem started and they have not been able to rectify the problem. Is there anything you can suggest? Mike mfr301(a)aol.com ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-01-07 10:21 Message: Logged In: YES user_id=1123998 Originator: NO Until you determine that there actually is a bug in Mailman, it would be better to discuss issues like this on the mailman-users(a)python.org list. See <http://mail.python.org/mailman/listinfo/mailman-users>. You say the mails you receive were sent by Mailman, but they are 'not visible on the mailing list'. What do you mean by 'not visible on the mailing list' and how do you know they are sent by Mailman? Re: deleted lists reappearing, How are the lists being deleted? It might be more productive for ResellerZoom to contact mailman-users(a)python.org directly. Also, if the Mailman is cPanel's, see <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp>. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_…

1 0

[ mailman-Bugs-1628753 ] Outbound messages have domain fubar'd
by SourceForge.net Jan. 12, 2007

Jan. 12, 2007

Bugs item #1628753, was opened at 2007-01-05 06:18 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) >Status: Deleted >Resolution: Invalid Priority: 5 Private: No Submitted By: Michael Reynolds (wshs) Assigned to: Nobody/Anonymous (nobody) Summary: Outbound messages have domain fubar'd Initial Comment: This is using a port install of mailman in FreeBSD, with version 2.1.9_1. When sending messages to users, either triggered by the web interface, or a message from a user to a mailman controlled email address, while using qmail with the included qmail-to-mailman script, the following errors litter my logs: 2007-01-05 07:53:25.924843500 info msg 5348160: bytes 1233 from <sirv-bounces(a)lists.delinked.us> qp 98922 uid 89 2007-01-05 07:53:25.961231500 starting delivery 17: msg 5348160 to remote munged(a)gmail.comyes Note the 'gmail.comyes'. A 'yes' is appended to every outbound message's target domain, thus making delivery impossible. I spent a few days thinking it was something I messed up, so I went through my entire system setup checking everything that could influence mail. I then discovered the problem is specific to mailman. Not sure what info I can provide to help, but I'd be willing to supply upon request. I am using FreeBSD 5.5, Python 2.5. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-01-12 07:44 Message: Logged In: YES user_id=1123998 Originator: NO Deleted per submitter's comment. ---------------------------------------------------------------------- Comment By: Michael Reynolds (wshs) Date: 2007-01-12 05:33 Message: Logged In: YES user_id=96949 Originator: YES I've tracked the problem down to internal stupidity, and it is not related at all to Mailman. However, it wasn't noticed until Mailman made me aware of it (patch that adversely affected smtp relaying). I do apologize for blaming mailman. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-01-05 07:11 Message: Logged In: YES user_id=1123998 Originator: NO There are many people using Mailman 2.1.9 and probably several using the FreeBSD port. This is the first report of this issue. It may have something to do with Python 2.5 or perhaps the combination of the FreeBSD port and Python 2.5. The following is an interactive Python snippet (Python responses other than prompts omitted) that sends mail in exactly the same way as Mailman does. If you have changed the assignments of SMTPHOST and/or SMTPPORT in mm_cfg.py, change them here too. Try this and see if the problem exists with it. If so, the problem is with Python, not Mailman. >>> import smtplib >>> msg = """Subject: Test Message ... Message-Id: <some-id(a)nowhere.example.com> ... From: poster(a)example.com ... To: you ... ... The body ... """ >>> rcpts = ['user1(a)example.com', 'userb(a)example.com'] >>> env = 'list-bounces(a)example.com' >>> SMTPHOST = 'localhost' >>> SMTPPORT = 0 >>> x = smtplib.SMTP() >>> x.set_debuglevel(1) >>> x.connect(SMTPHOST, SMTPPORT) >>> x.sendmail(env, rcpts, msg) >>> x.quit() ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_…

1 0