headers
Charles Sprickman | 1 Aug 2006 01:08
Picon
Favicon
Gravatar

duplicate messages from shunt queue

Hi all,

Recently I found a fairly huge amount of files in the shunt queue (around 
1500).  All I could gather from the error log is that most of them were from an 
old bug in parsing weird charsets and the later ones were due to the post and 
smtp-failur logfiles being owned by root.  So I fixed the perms (had already 
upgraded to 2.1.8 a month or so ago) and all was well.

Then I ran bin/unshunt.

Then people started complaining that they were getting a few hundred old 
messages. :)

What am I missing here?  From what I've been able to dig up on the list 
archives the qfiles/shunt directory should only contain messages that never 
made it out to any lists due to some error in config, perms or some bug in 
mailman itself.  But it's looking like these all did somehow make it through 
mailman previously and were sent a second time.  A few other tidbits:

-looking at some samples, msgids are the same, so it wasn't a user getting a 
rejection and then posting again

-the dupes DO NOT show up in the web archive

Any other info I can supply here?  Mailman 2.1.8, ruby 1.8.2, FreeBSD 4.7.

Thanks,

Charles
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jim Popovitch | 1 Aug 2006 01:32
Picon
Favicon

collapse_alternatives

What exactly does collapse_alternatives do?

What is the recommended setting for collapse_alternatives?

Tia,

-Jim P.
Permalink | Reply | 1 comment |
headers
Mark Sapiro | 1 Aug 2006 01:48

Re: duplicate messages from shunt queue

Charles Sprickman wrote:
>
>Then I ran bin/unshunt.
>
>Then people started complaining that they were getting a few hundred old 
>messages. :)

There are several possibilities here.

1) users are complaining that they received messages posted long ago in
threads long since dead, not necessarily that they previously received
the same message (message-id).

2) when the original didn't reach the list, the OP 'fixed' the problem
and reposted, thus the current message only appears to be a dupe.

3) if a message is shunted because SMTPDirect.py can't write the 'post'
log, it has already been sent, but OutgoingRunner.py doesn't know this
when it catches the exception and shunts the message. So those
messages which were shunted because of ownership/permission issues on
the 'post' log probably were duplicated when you ran unshunt

>What am I missing here?  From what I've been able to dig up on the list 
>archives the qfiles/shunt directory should only contain messages that never 
>made it out to any lists due to some error in config, perms or some bug in 
>mailman itself.

This is not always true, as in case 3) above. Thus, you have to use
judgement in unshunting.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mark Sapiro | 1 Aug 2006 02:12

Re: collapse_alternatives

Jim Popovitch wrote:

>What exactly does collapse_alternatives do?
>
>What is the recommended setting for collapse_alternatives?

collapse_alternatives was added in 2.1.7. The Defaults.py setting for
DEFAULT_COLLAPSE_ALTERNATIVES is Yes, which sets collapse_alternatives
to Yes for new and 'migrated' lists. I guess this makes 'Yes' the
'recommended' setting. This makes the behavior as in 2.1.6 and prior.

The 2.1.6/collapse_alternatives=Yes behavior is if filter_content is
Yes, "each multipart/alternative section will be replaced by just the
first alternative that is non-empty after filtering".

E.g. if the whole message is multipart/alternative with text/plain and
text/html subparts, even if both text/plain and text/html are accepted
MIME types, the resultant message will be 'collapsed' to just a
text/plain message containing the text/plain part and the text/html
part will be discarded.

This requires people who want to allow html on the list but filter some
other content to post html only and not multipart/alternative.

If collapse_alternatives=No, this replacement of "each
multipart/alternative section ... by just the first alternative that
is non-empty after filtering" is not done and all the alternatives
which aren't otherwise removed will remain as multipart/alternative
subparts in the final message.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Rubin | 1 Aug 2006 12:09

Strange address

Hi,

Very quick question.

Do you know of any easy way to remove this e-mail address from a list:

wjdtnsdlr <at> hotmaiw <at> explido.de

I have tried remove_member and the web interface, but neither works:

[root <at> tbnonline /var/mailman]# bin/find_member  wjdtnsdlr
wjdtnsdlr <at> hotmail.com found in:
     brdcst-pc
     master
wjdtnsdlr <at> hotmaiw <at> explido.de found in:
     brdcst-pc
[root <at> tbnonline /var/mailman]# 

[root <at> tbnonline /var/mailman]# bin/remove_members --fromall -n -N
wjdtnsdlr <at> hotmaiw <at> explido.de                                
Traceback (most recent call last):
  File "bin/remove_members", line 186, in ?
    main()
  File "bin/remove_members", line 176, in main
    admin_notif, userack)
  File "/var/mailman/Mailman/MailList.py", line 1014, in
ApprovedDeleteMember
    self.removeMember(emailaddr)
  File "/var/mailman/Mailman/OldStyleMemberships.py", line 220, in
removeMember
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mark Sapiro | 1 Aug 2006 14:29

Re: Where do I find mm_cfg.py

troubleshooter <at> jimstudebaker.org wrote:

>I wish to filter the emails to a mail list owner by doing the following:
>
>insert the line:
>OWNER_PIPELINE.insert(1, 'SpamAssassin')
>in mm_cfg.py.

If you are going to do that, you must have a SpamAssassin.py handler
and it needs to be installed in Mailman/Handlers/ - mm_cfg.py is
normally in the same Mailman/ directory as the Handlers/ subdirectory,
but

>I am using fedora core linux server system.

In older RedHat Systems, the Mailman directory was
/var/mailman/Mailman. More recently, RedHat has moved things according
to the Filesystem Hierarchy Standard (FHS) and the Mailman directory
is /usr/lib/mailman/Mailman. I think that mm_cfg.py is
/usr/lib/mailman/Mailman/mm_cfg.py and there is a symlink to that at
/etc/mailman/mm_cfg/py. See
<http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html>.

--

-- 
Mark Sapiro <msapiro <at> value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
Permalink | Reply | 0 comments |
headers
A. Khattri | 1 Aug 2006 16:41
Picon
Favicon

Setting subscriber bits from command line


Is there a command-line tool for setting/unsetting the various subscriber
flags?

--

-- 
A
Permalink | Reply | 1 comment |
headers
Shane Harsch | 1 Aug 2006 17:37

Extending Mailman - Contant Parser / Substituter

I want to write a script that looks for a particularly formatted string
in the body of a message, process it, and then replace that string with
the appropriate output. Is there a standard method for doing this, and
if so where?

Thanks.
Permalink | Reply | 1 comment |
headers
Mark Sapiro | 1 Aug 2006 18:34

Re: Setting subscriber bits from command line

A. Khattri wrote:
>
>Is there a command-line tool for setting/unsetting the various subscriber
>flags?

Only bin/withlist. For example, in withlist, one could do something like

from Mailman import mm_cfg
m.getMemberOption('user <at> example.com', mm_cfg.AcknowledgePosts)
m.setMemberOption('user <at> example.com', mm_cfg.AcknowledgePosts, True)

See mm_cfg.py/Defaults.py and MemberAdaptor.py/OldStyleMemberships.py
for more detail.

--

-- 
Mark Sapiro <msapiro <at> value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
Permalink | Reply | 0 comments |
headers
Mark Sapiro | 1 Aug 2006 19:32

Re: [Fwd: Formatting Questions]

Jewel wrote:

>I can't seem to send the following message to the Mailman listserv.
>Please help.

<snip>

>The message's content type was not explicitly allowed

You are sending an HTML post which is not accepted by content
filtering. Send either plain text or multipart/alternative with a
text/plain alternative.

>I am having trouble formatting a signature on the welcome message. Are
>there any formatting tips someone can advise me on? I am going into
>General Options and into the welcome message. I want the signature to
>look like this:
>
>
>
>Jewel Makda
>
>Student Computer Services Coordinator
>
>Washburn University School of Law Library
>
>1700 SW College Ave. Topeka, KS 66621
>
>
>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane