Re: [Mailman-Users] Issues with replaced characters/newlines inmailmanlists
On Feb 3, 2006, at 5:10 PM, Matt Zorzin wrote: > This is an exact copy and paste of an affected subject, with info > obfuscated but of an identical length to the original information: > > Subject: [Suspect List XX] 11-11: Subject of emails > coming from > mailing lists with "?" between words > > Our mail clients all run through AVG Enterprise antivirus. > > One interesting note is that it seems that many posts from this very > list (mailman-users) are exhibiting the same symptoms; i'm getting the > nonprintable characters in Mozilla, and a 'view source' shows a > newline > in the subject. > We ran into a similar issue here. It turned out that some virus- scanning MTA was incorrectly handling the folding of long headers. (Where "long" was greater than about 70 characters or so.) You can try isolating the problem by connecting (via telnet) to the SMTP port of the various MTAs in the delivery path, and manually typing in messages with long header lines. In our case: A long test header: Reply-to: "A very long real name. 0123456789012345678901234567890123456789012345678901234567890123456789" <0123456789012345678901234567890123456789012345678901234567890123456789@ 0123456789012345678901234567890123456789012345678901234567890123456789.0 123456789012345678901234567890123456789012345678901234567890123456789> After passing through the virus scanning system: Reply-To: "A very long real name. 01234567890123456789012345678901234567890 12345678901234567890123456789" <0123456789012345678901234567890123456789012.345678901234567890123456789 @01234567890123456789012345678901234567890123456.78901234567890123456789 . 012345678901234567890123456789012345678901234567890.1234567890123456789> Note the insertion of an extra space in the "real name" portion of the address, and the insertion of extra dots in the address portion. Perhaps something similar is happening at your site. -- Matt Emerson [EMAIL PROTECTED] -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] creating a list of moderators
On Jan 11, 2006, at 3:20 PM, Glenn Sieb wrote: > Mark Sapiro wrote: > >> You could probably replace the >> >> /usr/share/mailman/bin/withlist -q -a -r printowners | tr A-Z a-z | >> sort | uniq >> >> part of this pipe with >> >> /usr/share/mailman/bin/list_owners >> > It appears to also do the uniq for you... I own a few lists on my box, > and that command lists me once (which is fine for the purpose intended > by the OP). I think I didn't use the list_owners command because it treats email addresses which differ only in capitalization as distinct. -- Matt Emerson [EMAIL PROTECTED] -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] creating a list of moderators
On Jan 11, 2006, at 12:34 PM, David Benson wrote: > I'm a site administrator and I'd like to be able to send messages > out to all of my moderators at once. Does the current version of > Mailman have functionality to do this, i.e. can it automatically > generate a 'list' of moderators? ...or will I have to write my own > code to make it happen? We created a mailing list called "list-owners", which we update once a day via the following command. /usr/share/mailman/bin/withlist -q -a -r printowners | tr A-Z a-z | sort | uniq | /usr/share/mailman/bin/sync_members -w=no -g=no -f - list-owners >>/tmp/list-owner-updates The printowners helper script, which we put in /usr/share/mailman/bin/ printowners.py, contains the following. (It's probably better to keep local stuff out of Mailman's bin directory, but since I'm a python caveman, I just put the local script there anyway.) #!/usr/bin/python def printowners(m): for i in m.owner: print i If you want the list moderators (distinct from the list owners), you'd want to use m.moderator in lieu of m.owner. -- Matt Emerson [EMAIL PROTECTED] -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] mailman watchdog - status report
On Dec 21, 2005, at 4:02 PM, Con Wieland wrote: > I recently had some (more) problem's that Mark Shapiro helped me out > with. In that exchange I asked about a watchdog type program to help > in early problem detection. One thing we use here is a script that keeps an eye on the qrunners. They've died on us for some reason once or twice, so we use this script to notify us of the problem. We run it from cron. #!/bin/sh # check-qrunner # see if mailman's qrunners appear to be running and squawk if # they're not. if ps axw | grep -v grep | grep -v check-qrunner | grep qrunner >/dev/ null; then :; # life is good else # life is bad. try to restart the qrunners, and tell someone /usr/share/mailman/bin/mailmanctl -s start worked="did not work"; if ps axw | grep -v grep | grep qrunner >/dev/null; then worked="worked"; fi echo "Hi. I am /usr/local/bin/check-qrunners on `hostname`. The Mailman qrunners seem to have died. It appears that my attempt to restart them $worked." | mail -s "mailman qrunners" [EMAIL PROTECTED] fi -- Matt Emerson [EMAIL PROTECTED] -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] How can our MM site admin see unadvertisedlists via web interface?
Steve Rifkin <[EMAIL PROTECTED]> writes:
> I'd have to have a list available to me (we could
> potentially have dozens of lists made where the list admins would
> choose whether to advertise the list or not), and I was hoping I'd
> have that list available through a password-protected webpage,
> especially since there are other pages that require the site admin
> to log in within Mailman (specific list maintenance, etc.)
I wrote a nasty script to generate an HTML file that lists all the
lists.
I run it daily from cron because I didn't want to monkey around with a
setuid mailman CGI program.
Use your web server to restrict access to the generated HTML file as
appropriate.
Here's an example. Customize as required. Works for me; it might
work for you.
#!/usr/bin/perl
# Create a web page from the output of the Mailman list_lists command.
$cmd="/usr/share/mailman/bin/list_lists";
open LISTINFO, "$cmd |" or die "cannot run $cmd: $!\n";
print '
http://www.w3.org/TR/html4/strict.dtd";>
Mailing lists
.shaded {background: #EE;}
Mailing lists
';
$rownumber = 0;
$headerline = ;
while () {
chop;
($listname, $description) = split / - /;
$listname =~ s/^\s+//;
if ($rownumber % 2) {
$class = "";
} else {
$class = 'class="shaded"';
}
$rownumber++;
$lc_listname = lc $listname;
print "\n";
print "$listname\n";
print "$description\n";
print "mailto:[EMAIL PROTECTED]">
mail list owner\n";
print "\n";
}
print "";
# page footer
print '
';
--
Matt Emerson
[EMAIL PROTECTED]
--
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=show&file=faq01.027.htp
[Mailman-Users] new list announcements coming from "mailman-admin"
On our system (Mac OS X Server, using the bundled Postfix and bundled Mailman 2.1.4), when we create a new list with the newlist command, the new list announcement that is sent to the list owner comes from "[EMAIL PROTECTED]". This address is also cited as the address to which questions should be sent. However, when a user sends mail to mailman-admin, the system thinks it's a bounce. Unrecognized bounces get forwarded to the list owners, so we do see them, but this is obviously sub-optimal. So, it seems that we have two options: 1. We could edit the aliases file. It currently reads as follows. mailman: "|/usr/share/mailman/mail/mailman post mailman" mailman-admin: "|/usr/share/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/share/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/share/mailman/mail/mailman confirm mailman" mailman-join:"|/usr/share/mailman/mail/mailman join mailman" mailman-leave: "|/usr/share/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/share/mailman/mail/mailman owner mailman" mailman-request: "|/usr/share/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/share/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe mailman" If we made mailman-admin just be an alias for mailman, this could possibly work, although I worry that this alteration would be undone if someone ever ran genaliases. (I also note that the admin and bounces scripts in /usr/share/mailman/scripts are identical.) 2. We could edit the newlist command, and where it says siteadmin = Utils.get_site_email(mlist.host_name, 'admin') we could make it read siteadmin = Utils.get_site_email(mlist.host_name) This is not very appealing---I'd rather not have to remember to make this change when we update the Mailman software. Is there something else that we are doing wrong? Perhaps our site list is somehow set up incorrectly? I did read the FAQ and search the archives a bit, but I'm sure it's possible that I missed a solution. Any pointers or help would be appreciated. -- Matt Emerson [EMAIL PROTECTED] -- 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=show&file=faq01.027.htp
