[Mailman-Users] How to re-send list traffic from archives?

[Dan Mahoney, System Admin]

Hey there all,

Due to a VERP misconfig on one of our systems, we had a number of outbound 
posts bounce with a 500-series error.


What we'd like to do is go through the archives for the period of time we 
missed, and re-send those messages.  Is this something anyone's had to do 
in the past and could maybe provide pointers?


Failing that, can someone tell me why it might be a really bad idea?

-Dan Mahoney

--

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Gratuitous "True".

[Dan Mahoney, System Admin]

On Fri, 16 Jan 2009, Mark Sapiro wrote:


I took a closer look at my own archives and I see it is related to
Richard's patches, but it is not the patch that's the problem. The
'True' is supposed to be "" The problem is that
you have (probably in mm_cfg.py, but maybe in Defaults.py)

ARCHIVE_INDEXING_ENABLE = 'True'

instead of or overriding

ARCHIVE_INDEXING_ENABLE = ''


Yup, I found that -- it took me a while because of the variables, I 
actually had ARCHIVE_INDEXING_ENABLE=1, and I was grepping all my configs 
and the patches for "True".


I also found a bug in his docs with at least one variable he's not 
documenting right.


Also, can you see why one would think that these lines would be a boolean?

-Dan

--

"If you need web space, give him a hard drive.  If you need to do something really 
heavy, build him a computer."

-Ilzarion, late friday night

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

--
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] Gratuitous "True".

[Dan Mahoney, System Admin]

Hey all,

After updating to 2.1.11 (from BSD ports, against python2.5), I'm seeing 
that several of my list archives have the word "True" scattered througout 
(at the bottoms of tables).


Something like this:

October 2008:

  [ Thread ]

  [ Subject ]
  [ Author ]
True
  [ Date ]


[ Text 556 bytes ]



  

True

It would appear that the arch command is printing something it shouldn't 
be (either a config variable or something else?)


Anyone have any idea what could be causing this?

-Dan

--

[23:49:00] LarpGM: Did my little TP comment scare you off?
[23:49:22] ilzarion: no, the shrieking retarded child eating people did

-Feb 06, 2001, times apparent.


Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

--
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] Email subscription not working

[Dan Mahoney, System Admin]

On Thu, 8 Jan 2009, Mark Sapiro wrote:


Dan Mahoney, System Admin wrote:


Hey all, I'm hitting a little snag.  Email subscribe isn't doing anything.

Postfix delivers the email to mailman, but then as far as I can tell,
nothing more happens with it.

Where would be the best place to debug this from a mailman perspective?

Jan  7 21:05:34 lister postfix/qmgr[97071]: DDFD010E528:
from=, size=2716, nrcpt=1 (queue
active)
Jan  7 21:05:35 lister postfix/local[38795]: DDFD010E528:
to=, relay=local, delay=0.18,
delays=0.01/0/0/0.17, dsn=2.0.0, status=sent (delivered to command:
/usr/local/mailman/mail/mailman join testing)
Jan  7 21:05:35 lister postfix/qmgr[97071]: DDFD010E528: removed

And that's where it stops.  The address doesn't show in any logs or
anything from that point forward.



The above says Postfix successfully piped the mail to the wrapper which
presumably invoked the 'join' script to queue the mail in the
'commands' queue.


From there it is processed by CommandRunner.


Step 1) is CommandRunner running or is the message still sitting in
qfiles/commands ?


I don't see a persistent process with that name, but qfiles/commands is 
empty.



Anything obvious I should be checking?  Perhaps the possibility that the
"to" address is getting altered in transit?  Does mailman log discarded
subscription messages?  Is there a debug option?



The message got delivered to the correct address according to Postfix.

Messages with precedence 'bulk', 'junk' or 'list' are discarded, but
the discard is logged in Mailman's vette log with a message like

Precedence: xxx message discarded by: testing-requ...@example.com


This hasn't been logged at all.  In fact a grep for the address on all 
logfiles gives nothing.  However, see my next bit...



If you have an autoresponder set for requests to this list, the message
will be autoresponded to per the autoresponder settings and logged in
the vette log as "replied and discard".

Also look for messages in Mailman's error (and other) logs with
timestamp within a few seconds of Jan  7 21:05:35.


Oh here's something:

Jan 07 21:05:05 2009 (69945) Uncaught runner exception: 'NoneType' object 
has no attribute 'lower'

Jan 07 21:05:05 2009 (69945) Traceback (most recent call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop
self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 241, in 
_dispose

res.do_command('join')
  File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 139, in 
do_command

return handler.process(self, args)
  File "/usr/local/mailman/Mailman/Commands/cmd_subscribe.py", line 74, in 
process

if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'

Jan 07 21:05:05 2009 (69945) SHUNTING: 
1231362305.1949821+1175967c099dad2a1abd84668491378c9ec3d2f3
Jan 07 21:05:35 2009 (69945) Uncaught runner exception: 'NoneType' object 
has no attribute 'lower'

Jan 07 21:05:35 2009 (69945) Traceback (most recent call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop
self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 241, in 
_dispose

res.do_command('join')
  File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 139, in 
do_command

return handler.process(self, args)
  File "/usr/local/mailman/Mailman/Commands/cmd_subscribe.py", line 74, in 
process

if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'

Jan 07 21:05:35 2009 (69945) SHUNTING: 
1231362335.060303+d4ab606e4d64c835df5f64f7aaff37fe61bee8e8
Jan 07 21:05:47 2009 (69945) Uncaught runner exception: 'NoneType' object 
has no attribute 'lower'

Jan 07 21:05:47 2009 (69945) Traceback (most recent call last):
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop
self._onefile(msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 241, in 
_dispose

res.do_command('join')
  File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 139, in

[Mailman-Users] Email subscription not working

[Dan Mahoney, System Admin]

Hey all, I'm hitting a little snag.  Email subscribe isn't doing anything.

Postfix delivers the email to mailman, but then as far as I can tell, 
nothing more happens with it.


Where would be the best place to debug this from a mailman perspective?

Jan  7 21:05:34 lister postfix/qmgr[97071]: DDFD010E528: 
from=, size=2716, nrcpt=1 (queue 
active)
Jan  7 21:05:35 lister postfix/local[38795]: DDFD010E528: 
to=, relay=local, delay=0.18, 
delays=0.01/0/0/0.17, dsn=2.0.0, status=sent (delivered to command: 
/usr/local/mailman/mail/mailman join testing)

Jan  7 21:05:35 lister postfix/qmgr[97071]: DDFD010E528: removed

And that's where it stops.  The address doesn't show in any logs or 
anything from that point forward.


Anything obvious I should be checking?  Perhaps the possibility that the 
"to" address is getting altered in transit?  Does mailman log discarded 
subscription messages?  Is there a debug option?


-Dan

--

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

--
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] repurposing the -request alias on an autogenerated aliases file?

[Dan Mahoney, System Admin]

Here at work, we've found that mailman's "-request" alias has stomped 
another already-existing function (under our previous list, we used that 
for administrative requests, and on this particular list, that's not 
negotiable -- it needs to duplicate the function of xxx-owner).


However, we're using automatic aliases.  Is there some way to quell or 
suppress the creation (or re-creation) of that particular alias (for one 
list only), without having to go to manual aliases?


That is to say, if I hand-edited both $mailman/data/aliases and aliases.db 
(by rebuilding it from the new aliases file) -- would mailman revert it on 
me the next time I created a list?


-Dan Mahoney


--

"Let me tell you something about regrowing your dead wife Lucy, Harry.
It's probably illegal, potentially dangerous, and definitely crazy."

-Harry nods-

Vincent Spano, as Boris in "Creator".


Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

--
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] Subscribing other lists to a list.

[Dan Mahoney, System Admin]

On Sat, 6 Dec 2008, Mark Sapiro wrote:


Dan Mahoney, System Admin wrote:


What I'd like to know if is possible within mailman is the following:

a) A per-user flag that makes a user admin-control ONLY.  No auto-bounce
handling, no unsubscribe options, no password reminders...nothing.
Essentially, this would move the "umbrella" setting from a global to a
single address.  This would solve about half the problem (the headers
would still need to be fixed, mainly the to: header).



No. This is not possible in current Mailman.

You might want to look at the "sibling lists" feature in Mailman 2.1.10
and up. You could add the -discuss list to the regular_include_lists
attribute of the -announce list. This would send a copy of any
-announce post to all the -announce members with delivery enabled plus
any delivery enabled regular members of the -discuss list who were not
regular members of the -announce list.

The potential issues that I see are:

A regular member of the -discuss list who is a digest member of the
-announce list will receive the individual message and also receive it
in the digest.


Typically, an announce-list is not digestable so this is not a worry.


Digest members of the -discuss list will not receive the message unless
they are also members of the -announce list.


I'd have to assume there's something internal that makes this necessary -- 
I'm curious as to how much tweaking it would take to fix (i.e. make it so 
digest members receive the announcement, either in their digest or 
separately).


-Dan

--

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

--
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] Subscribing other lists to a list.

[Dan Mahoney, System Admin]

I just helped to manage a migration from Ecartis to Mailman for my day 
job.


We have a periodic -announce list that we send out on to release new 
software versions.  What I'm finding is we cannot duplicate the same 
behavior we have under Ecartis.


Ecartis had a simple "import" option, where list B could be a subset of 
list A, but list A could also contain normal users.


I've found this post http://www.saas.nsw.edu.au/solutions/umbrella.html 
and it explains things pretty well, but neither option would really work 
well for us.


Umbrella lists don't work because they say "this was sent to the umbrella 
list" in the footers (which are suppressable) but also in the TO: header 
(or the cc header).  We could send to: a fake address, with a cc: to a 
fake address, but this would set off spam filters, and we're staunchly 
anti-spam.


On the other hand, Parent lists don't work, for the same reason -- there 
are people who sign up for -announce and -discuss and want to filter them 
separately, or who don't want the noise of -discuss and want to get it as 
a digest.


Right now, the easiest (and dumbest) answer is "just make announcements to 
all three lists".  Ecartis stripped duplicates there -- if you were on 
list a, I don't believe list b was imported.


What I'd like to know if is possible within mailman is the following:

a) A per-user flag that makes a user admin-control ONLY.  No auto-bounce 
handling, no unsubscribe options, no password reminders...nothing. 
Essentially, this would move the "umbrella" setting from a global to a 
single address.  This would solve about half the problem (the headers 
would still need to be fixed, mainly the to: header).


But it's more than I have right now.

-Dan Mahoney

--

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

--
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] Duplicate detection: a plea

[Dan Mahoney, System Admin]

We recently moved over to mailman from Ecartis at $dayjob, and one of the 
largest annoyances is that mailman seems to have no ability to strip 
duplicate messages that are sent to the lists.


We moved over from our main domain name, foo.com, to lists.foo.com, so 
what happens is this:


A user posts to [EMAIL PROTECTED] -- the mailer forwards it to 
[EMAIL PROTECTED]  People reply to the list and hit reply-all, which 
directs replies to the LIST ([EMAIL PROTECTED]) but also to the 
original recipient ([EMAIL PROTECTED]).  Bam, duplicates.


I don't want to get into an evangelical holy-war about reply-all.  We 
already had it here.


I've seen mention of a fix for this via procmail, that basically creates a 
"lockfile" based on the message-id.  Our mail server's not running 
procmail, and since it's only hosting lists, not and mailboxes, it doesn't 
make a whole lot of sense to use it.


All mailman would have to do is touch a per-list lockfile based on 
message-id (one line of shell), and then at some point in the posting 
process, if that lockfile exists, drop the message (as it's already come 
through).  Cleanup is one line of shell (find foo -ctime xxx -delete) or 
can be handled from the qrunner.


Heck, if you want to be fancy, give me a list of regexes that match 
recipients, and more than one must match to make this happen.


I also tried sending this to the -developers list.  No response.  But 
maybe that's the wrong place since I'm not developing, or submitting a 
patch.  Just saying I need a simple feature and could pay something for it 
if need be.  Not something amazing, but enough for a nice dinner and 
drinks (or if you're local to silicon valley, I'll buy).


Can mailman please have this functionality natively?

-Dan

--


Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---

--
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] Re: Virus Just Got Through on TOTALLYMODERATEDlist.

[Dan Mahoney, System Admin]

On Sat, 5 Feb 2005, Mark Sapiro wrote:
Dan Mahoneywrote:
On Sat, 5 Feb 2005, Jeff Groves wrote:
I think the two Received: headers could be enough considering the worm
probably has it's own SMTP engine. The way to answer this for sure is
to see if it is in the 'post' log.
Jan 27 22:55:10 2005 (39139) post to vgc-announce from
[EMAIL PROTECTED], size=39384,
message-id=<[EMAIL PROTECTED]>, success
I agree with Mark and would go even further that it is all you need to know.
The pcp08579508pcs.alxndr01.va.comcast.net address, which is indicative of a
Comcast end-user in Alexandria, Virginia, is plenty to know that the user
that had the address at the particular time (Thu, 27 Jan 2005 21:15:35 -0500
(EST)) was infected with some type of worm.
Jeff, I had already worked out that much.  And it might have trolled the
list posting address from an address book or a previous email...but...
1) (This is the question I've been wanting the answer to the whole
time)...Why did it not require approval?  When Eric Graves (the same guy,
same email address, the list owner and moderator), goes to make a post, it
gets held back with a "requires approval".  Up until recently, we took
this as a sign that security was as it should be.  Even if someone spoofed
the email address, we'd have a chance to catch it.
We clearly don't know the answer to this. Assuming it is in the 'post'
log and thus for sure came from the list and wasn't just spoofed to
look like it came from the list, the only way I know for it to get
through is if it contained an Approved: header or first line with the
list password.
There was some conjecture earlier in this thread about how this might
happen, but it seems highly unlikely and the characteristics of
[EMAIL PROTECTED] which you identified in the OP would seem to preclude
it, so I'm at a loss for an explanation.
2) Why isn't it in the vette log?
Because it wasn't held for approval.
3) If the worm spoofed all the x-mailman headers and everything, and
magically managed to insert itself into the pipermail archives, why are
the logs missing?
I forgot you said it was in the archive. Was there an entry in the
'post' log? Was there an entry or entries in the 'smtp' log? If these
are absent, it may be a clue.
As I said before, the information we really need in order to figure
this out would be the post as received by Mailman, not the one sent
out, but there's no way to get this from Mailman after the fact.
*that* is a problem.  I see no reason there shouldn't be an option to log 
this (either in the archives or a logfile, or maybe a "view original post" 
option in the archives, something possibly admin-only?.

-Dan
--
"You're not normal!"
-Michael G. Kessler, referring to my modem online time.
Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---
--
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

Re: [Mailman-Users] Re: Virus Just Got Through on TOTALLYMODERATED list.

[Dan Mahoney, System Admin]

On Sat, 5 Feb 2005, Jeff Groves wrote:
I think the two Received: headers could be enough considering the worm
probably has it's own SMTP engine. The way to answer this for sure is
to see if it is in the 'post' log.
Jan 27 22:55:10 2005 (39139) post to vgc-announce from 
[EMAIL PROTECTED], size=39384, 
message-id=<[EMAIL PROTECTED]>, success

I agree with Mark and would go even further that it is all you need to know. 
The pcp08579508pcs.alxndr01.va.comcast.net address, which is indicative of a 
Comcast end-user in Alexandria, Virginia, is plenty to know that the user 
that had the address at the particular time (Thu, 27 Jan 2005 21:15:35 -0500 
(EST)) was infected with some type of worm.
Jeff, I had already worked out that much.  And it might have trolled the 
list posting address from an address book or a previous email...but...

1) (This is the question I've been wanting the answer to the whole 
time)...Why did it not require approval?  When Eric Graves (the same guy, 
same email address, the list owner and moderator), goes to make a post, it 
gets held back with a "requires approval".  Up until recently, we took 
this as a sign that security was as it should be.  Even if someone spoofed 
the email address, we'd have a chance to catch it.

2) Why isn't it in the vette log?
3) If the worm spoofed all the x-mailman headers and everything, and 
magically managed to insert itself into the pipermail archives, why are 
the logs missing?

--
"Happy, Sad, Happy, Sad, Happy, Sad, Happy, Intruiged!  I've never been so
in touch with my emotions!"
-AndrAIa as Hexadecimal, Reboot Episode 3.2.3
Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---
--
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

Re: [Mailman-Users] Re: Virus Just Got Through on TOTALLY MODERATED list.

[Dan Mahoney, System Admin]

On Thu, 3 Feb 2005, David M.Besonen wrote:
I just had a small problem.  A virus was just sent to all the list members
which had spoofed the moderator's email address.  No "requires approval"
message was sent, despite the fact that everyone (even the moderator) has
the "mod" bit set to "on".
so what happened Dan?  15 people have replied to your post.  i'm
waiting to hear if you discovered anything.  did you check the vette
log?
I saw a lot of people saying "this is why I strip attachments".  I saw 
Stephanie's (very helpful) post, but when I checked the box she referenced 
I found it empty, as I expected.  I found that even the list owner's mod 
bit (who the virus spoofed) was set, and the list owner in turn scanned 
his own machine for virii right after this got out.  Nada.

I checked the vette log.  The message isn't even in there.  Some of the 
auto-replies to it are (i.e. "message rejected, it's a virus").  And the 
message shows in the pipermail archives.

In the end, this group I'm working with has had a lot of unsubscribes as a 
result of this, and are switching to a different system that I'm not 
hosting, so I'm a bit apathetic about the whole deal.  I'm still sure 
there's something I'm missing, and if someone wanted to try and give me a 
clue as to how this happened, I've saved that day's sendmail logs, and 
I've got all the following:

Here's the message in the archives:
http://lists.vagrassroots.org/pipermail/vgc-announce/2005q1/38.html
Here's a snippet of that day's vette log:
Jan 26 21:26:54 2005 (39137) Vgc-announce post from 
[EMAIL PROTECTED] held, message-id=<01a901c50416$42a15c70$a3bafea9
@micronxp>: Message has implicit destination
Jan 26 21:28:58 2005 (3682) held message approved, message-id: 
<[EMAIL PROTECTED]>
Jan 26 21:28:58 2005 (3682) vgc-announce: Discarded posting:
From: [EMAIL PROTECTED]
Subject: Fwd: FW: Media Advisory
Reason: No reason given
Jan 27 23:12:05 2005 (39137) Vgc-announce post from 
[EMAIL PROTECTED] held, message-id=<05b001c504ef$a199e740$6b0
[EMAIL PROTECTED]>: Post to moderated list
Jan 27 23:25:36 2005 (39137) Vgc-announce post from 
[EMAIL PROTECTED] held, message-id=<010901c504ef$fe21a5c0$a3bafea9
@micronxp>: Post to moderated list
Jan 27 23:27:42 2005 (39495) held message approved, message-id: 
<[EMAIL PROTECTED]>
Jan 27 23:27:43 2005 (39495) vgc-announce: Refused posting:
From: [EMAIL PROTECTED]
Subject: Reply: virus in your message from: [Virginia Grassroots 
Coalition] Delivery by mail
Reason: No reason given
Jan 28 08:46:48 2005 (39137) Vgc-announce post from [EMAIL PROTECTED] 
held, message-id=<[EMAIL PROTECTED]
org>: Post by non-member to a members-only list
Jan 28 08:53:02 2005 (99241) vgc-announce: Discarded posting:
From: [EMAIL PROTECTED]
Subject: Delivery service mail
Reason: No reason given

Here's the full headers of the thing:
Return-Path: <[EMAIL PROTECTED]>
Received: from prime.gushi.org (localhost [IPv6:::1])
by prime.gushi.org (8.13.1/8.13.1) with ESMTP id j0S2GH5b080701
for <[EMAIL PROTECTED]>; Thu, 27 Jan 2005 22:50:56 -0500 (EST)
Received: from ROBERTA.net (pcp08579508pcs.alxndr01.va.comcast.net
[68.83.208.54])
by prime.gushi.org (8.13.1/8.13.1) with SMTP id j0S2FV8o080233
for <[EMAIL PROTECTED]>;
Thu, 27 Jan 2005 21:15:35 -0500 (EST)
Date: Thu, 27 Jan 2005 21:05:09 -0500
From: "Ericgraves" <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
X-Security: MIME headers sanitized on prime.gushi.org
See http://www.impsec.org/email-tools/sanitizer-intro.html
for details. $Revision: 1.139 $Date: 2003-09-07 10:14:23-07
X-Security: The postmaster has not enabled quarantine of poisoned 
messages.
Content-Type: multipart/mixed; boundary="qptymaiwwlishntudcfk"
Subject: [Virginia Grassroots Coalition] Delivery by mail
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: [EMAIL PROTECTED]
Cc: Virginia Grassroots Coalition Broadcast 
<[EMAIL PROTECTED]>
List-Id: Virginia Grassroots Coalition Broadcast

List-Unsubscribe: 
,

List-Archive: 
List-Help: 
List-Subscribe: 
,

To: [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-Envelope-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on prime.gushi.org
X-Spam-Status: No, score=2.7 required=5.0 tests=BAYES_00,HTML_50_60,
HTML_MESSAGE,HTML_SHORT_LENGTH,MSGID_SPAM_LETTERS,RCVD_IN_NJABL_DUL,
RCVD_IN_SORBS_DUL autolearn=no version=3.0.2
X-Spam-Level: **
P



ciao,
david
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users

[Mailman-Users] Virus Just Got Through on TOTALLY MODERATED list.

[Dan Mahoney, System Admin]

Guys,
I just had a small problem.  A virus was just sent to all the list members 
which had spoofed the moderator's email address.  No "requires approval" 
message was sent, despite the fact that everyone (even the moderator) has 
the "mod" bit set to "on".

http://securityresponse.symantec.com/avcenter/venc/data/[EMAIL PROTECTED]
Are there any known and open bugs in 2.1.5 that would allow this behavior?
Is there any way of telling in the headers (or archives, or logs?) how a 
message was approved?

Here's the headers:
Return-Path: <[EMAIL PROTECTED]>
Received: from prime.gushi.org (localhost [IPv6:::1])
by prime.gushi.org (8.13.1/8.13.1) with ESMTP id j0S2GH5b080701
for <[EMAIL PROTECTED]>; Thu, 27 Jan 2005 22:50:56 -0500 (EST)
Received: from ROBERTA.net (pcp08579508pcs.alxndr01.va.comcast.net
[68.83.208.54])
by prime.gushi.org (8.13.1/8.13.1) with SMTP id j0S2FV8o080233
for <[EMAIL PROTECTED]>;
Thu, 27 Jan 2005 21:15:35 -0500 (EST)
Date: Thu, 27 Jan 2005 21:05:09 -0500
Any ideas?
-Dan Mahoney
--
"Ca. Tas. Tro. Phy."
-John Smedley, March 28th 1998, 3AM
Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---
--
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/

Re: [Mailman-Users] changing MTA from sendmail -> procmail

[Dan Mahoney, System Admin]

On Fri, 19 Nov 2004, Aaron Bennett wrote:
Procmail is not an MTA.  It does not speak SMTP inbound or outbound.  It 
is merely a "delivery agent", which takes the mail once sendmail (or 
another MTA) gets it in from the grid and handles stuffing it in a box.

I'm quite familiar with the setup you're going to -- essentially you use 
procmail to replace sendmail's mail.local.

Postfix, is a different animal.

Hi,
I've got an established mailman installation on RHEL 3 and I'm planning to 
change that system's MTA from sendmail to procmail.  Does anyone know of any 
gotchas or other things I need to look out for?  I'm assuming that in a 
non-virtual-domain setup like this it should be fairly simple: make sure I've 
got backups of /etc/aliases and then uses Redhat's nifty little 
redhat-switch-mail program to change to postfix

Anyone have scars from a similiar assumption?
:-)

--
"We are basically...'Bandwidth Pimps'...Hrmmm...But that's cool man!  You see these 
gold chains?  It's all good!"
-Ali Dhoon
03/03/2003, 7PM
Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

Re: [Mailman-Users] Mailman configuration error

[Dan Mahoney, System Admin]

On Wed, 27 Oct 2004, Adam G. Garson wrote:
Hi -- I'm trying to install Mailman on a Mandrake 10.1 system.  I have new
installations of Python 2.3.4 and GCC 3.4.2 both compiled from source -- no
rpms.  When I run the configure script I get the error quoted below.  This
occurs even as root, so I don't think it's a permission problem.   I've done
everything I can think of but can't resolve the issue.  Can anybody give me
some guidance on how to troubleshoot this one (I'm not a programmer)?
Thanks very much.
Give it the path to the python executable, not to the lib directory.
-Dan
Adam Garson
* Distutils is not available or is incomplete for /usr/bin/python
* If you installed Python from RPM (or other package manager)
* be sure to install the -devel package, or install Python
* from source.  See README.LINUX for details
bash-2.05b$
/configure --with-username=adam --with-cgi-gid=webgroup --with-mailhost=nan
nypay.net --with-urlhost=nannypay.net --with-python=/usr/local/lib/python2.3
checking for --with-python... /usr/local/lib/python2.3
checking Python interpreter... /usr/local/lib/python2.3
checking Python version... ./configure: line 1379:
/usr/local/lib/python2.3: is a directory
cat: conftest.out: No such file or directory
configure: error:
* /usr/local/lib/python2.3 is too old (or broken)
* Python 2.1 or newer is required
* Python 2.1.3 or better is recommended
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
--
"I can feel it, comin' back again...Like a rolling thunder chasin' the
wind..."
-Dan Mahoney, JS, JB & SL, May 10th, 1997, Approx 1AM
Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

[Mailman-Users] CC, from, and TO headers.

[Dan Mahoney, System Admin]

Hello all,
I'm managing a mailing list (obviously) and the problem we're having is 
with the list address being placed in the "CC" header of the email.

This is an annoucement only list, so we'd like to simply remove that 
feature for this specific list.  Is there a way of doing that?  We don't 
want to make the list anonymous (i.e. hiding the sender), we just don't 
want 20 people sending a reply to the sender plus a bounce to the list.

-Dan
--
"Be happy.  Try not to hurt each other.  Hope you fall in love."
--Mallory, Family Ties Finale (on the meaning of life)
Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

[Mailman-Users] None

[Dan Mahoney, System Admin]

Hi all, quick question.

My host name is prime.gushi.org, but I operate several vhosts under it.  I
am easily able to make a few virtusertable tweaks that allow me to have
users point to [EMAIL PROTECTED] instead of
[EMAIL PROTECTED], but there's no place to edit this in the
configs.  (i.e. all the HTML pages, welcome emails all say post to
[EMAIL PROTECTED]).

Is there a workaround for this?

-Dan Mahoney

 --

"there is no loyalty in the business, so we stay away from things that piss people off"

-The Boss, November 12, 2002

Dan Mahoney
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org