Lucio Chiappetti | 1 Apr 09:57 2011
Picon

Re: bug adding user, and archiving gets "shunted"

On Thu, 31 Mar 2011, Mark Sapiro wrote:

> This error is due to one of several known incompatibilities between
> Mailman versions older than 2.1.12 and Python 2.6 or later. See the
> FAQ at <http://wiki.list.org/x/pYA9>.

I read the FAQ, which was however last updated in 2009.

This MIGHT not be a problem, because I'm running tests (as a sort of power 
user) on my machine (suse 11.3 installed last december), but this is NOT 
the target system. I'm pretty sure the target system will have suse 11.4 
which came out recently.

suse 11.3 bundles mailman 2.1.11-13.2 and python 2.6.5-2.11 (however they 
provide separately mailman 2.1.14-21.1 and python 2.7-43.1)

suse 11.4 bundles mailman 2.1.14-4.7.1 and python 2.7-8.2 (and provides 
also 2.7-43.1)

I am really confused by all these minor subsubversions.

Is the suse 11.4 mm/python coupling sound ?
If so I will tell our sysadm to proceed, and pass on my test experience.
I might do a few further tests on my machine and occasionally report 
problems here (be free to reply "usual 2.1.11/2.6 incompatibility").

Eventually I could upgrade mailman on my test machine (but not python)
if that is likely to work (just to test also the upgrade procedure).

> If suse is packaging Mailman 2.1.11 with the Python 2.6.5 that you are 
(Continue reading)

Lucio Chiappetti | 1 Apr 10:38 2011
Picon

separate mx, mailman and web host

On Wed, 30 Mar 2011, Mark Sapiro wrote:
> Lucio Chiappetti wrote:

>>>> (QUESTION 5)
>>>> The arrangement on the target system will be more complicated.
>>
>> because our aliases are mantained on the NIS master server. The master and
>> slave servers are also the domain main and backup MX.
>>
>> However the web server is on a third machine. A configuration like the one
>> I use on my test machine (local sendmail aliases inherited from local
>> mailman aliases, which "pipe" into local mailman executables) is likely
>> to work there ...

> I don't think I actually understand the configuration or what the
> problem is.
>
> Ultimately, mail to a list must be delivered to the Mailman machine,
> but I don't understand why the existing MXs can't relay it there or
> can they?

So far not unless explicitly aliased.
This is how I see it (and how our other things work currently).

- all our e-mail are of the form  user <at> domain
   NOT user <at> host.domain

- all outgoing mail is masqueraded as user <at> domain by sendmail

- the DNS advertises two MX's for the domain. We do not advertise MX's for
(Continue reading)

Chris Bruno | 1 Apr 16:41 2011
Picon

usubscribe all

usubscribe all

Mark Sapiro | 1 Apr 17:30 2011
Picon

Re: bug adding user, and archiving gets "shunted"

Lucio Chiappetti wrote:

>On Thu, 31 Mar 2011, Mark Sapiro wrote:
>
>> This error is due to one of several known incompatibilities between
>> Mailman versions older than 2.1.12 and Python 2.6 or later. See the
>> FAQ at <http://wiki.list.org/x/pYA9>.
>
>I read the FAQ, which was however last updated in 2009.

Yes, but the key part in this case is

"Update - March 2009: Mailman 2.1.12 has been released and requires
Python 2.4.x or later. It is the *first* Mailman release compatible
with Python 2.6." (emphasis mine).

>This MIGHT not be a problem, because I'm running tests (as a sort of power 
>user) on my machine (suse 11.3 installed last december), but this is NOT 
>the target system. I'm pretty sure the target system will have suse 11.4 
>which came out recently.
>
>suse 11.3 bundles mailman 2.1.11-13.2 and python 2.6.5-2.11 (however they 
>provide separately mailman 2.1.14-21.1 and python 2.7-43.1)
>
>suse 11.4 bundles mailman 2.1.14-4.7.1 and python 2.7-8.2 (and provides 
>also 2.7-43.1)
>
>I am really confused by all these minor subsubversions.

Everything to the right of the hyphen (-) is a designation by the
(Continue reading)

Mark Sapiro | 1 Apr 18:25 2011
Picon

Re: separate mx, mailman and web host

Lucio Chiappetti wrote:
>
>- all our e-mail are of the form  user <at> domain
>   NOT user <at> host.domain

OK

>- all outgoing mail is masqueraded as user <at> domain by sendmail

OK

>- the DNS advertises two MX's for the domain. We do not advertise MX's for
>   particular hosts. Hosts other than MX's should have the SMTP port
>   blocked by a firewall on the boundary router (we are several institutes
>   in the same building, the boundary router is not managed by ours).

OK

[...]
>
>- mailman will be installed on a given host (I call it mmhost for the
>   purposes of this mail, but the real name will be different). Most
>   likely it will be our www server (www.domain where www is a CNAME
>   for its real host name), NOT the MXs (the two MXs are redundant,
>   and are also the primary and secondary DNS and NIS servers).

If it is not the www server, you can use one of the methods in FAQ 4.84

>- I know now that DEFAULT_URL_HOST shall point to www.domain (or
>   perhaps a dedicated virtual www server)
(Continue reading)

Eric Aldhizer | 1 Apr 16:44 2011

Trouble Sending

I am having trouble with all of my lists.  I can send an email to any of
them, the mail shows up in the archives, but doesn't distribute to any
(including poster) members.  This was sudden, I hadn't logged into admin on
any lists.

Eric

Patti Beadles | 1 Apr 09:57 2011

Topics and friendly rejections of topicless messages

I'm trying to set up a list with the topics feature, and I'm
having a little bit of trouble achieving what I want.  The
basic feature is fine, but making it a smooth user experience
is being problematic.  In particular, what I want is this:

A) Allow topic-based list subscription
B) Every message must have a topic
C) Messages that don't have a topic get bounced back to the user
D) The bounced messages must be "pretty", and explain what to do

A was easy enough.

I implemented B and C by using spam filtering, and setting the
spam filter to bounce mail whose subject line matches a regular 
expression.  That regex is essentially "not (topic1 | topic2)".
That solution is functional, if not particularly elegant.

Item D is throwing me for a loop.  I can make it happen with a
one-line change to SpamDetect.py, but that's probably not going
to fly.  The host runs multiple lists, and doing this would 
constrain the other lists in ways that aren't really acceptable.

I've wandered through this list's archives pretty extensively.
If this question has been answered then I haven't found the
right search incantation to get at the information.  Is there
a good way to accomplish what I'm trying to do?  Is there a way
to bounce spam to some particular email address, and run a 
script at that address to send back a pretty, helpful bounce?

The meta-problem that I'm trying to solve is this:  there's a
(Continue reading)

Mark Sapiro | 2 Apr 19:18 2011
Picon

Re: Trouble Sending

Eric Aldhizer wrote:

>I am having trouble with all of my lists.  I can send an email to any of
>them, the mail shows up in the archives, but doesn't distribute to any
>(including poster) members.  This was sudden, I hadn't logged into admin on
>any lists.

Either OutgoingRunner is not running or is encountering errors or, if
the outgoing MTA is separate from the incoming MTA, perhaps it isn't
running. If you have access, check Mailman's 'error' and 'qrunner'
logs and possibly Mailman's 'smtp' and 'smtp-failure' logs and the MTA
logs. Also, see the FAQ at <http://wiki.list.org/x/A4E9>.

If you don't have access, contact the Mailman hosting provider.

--

-- 
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

Stephen J. Turnbull | 2 Apr 19:33 2011
Picon

Topics and friendly rejections of topicless messages

Patti Beadles writes:

 > Item D is throwing me for a loop.  I can make it happen with a
 > one-line change to SpamDetect.py, but that's probably not going
 > to fly.  The host runs multiple lists, and doing this would 
 > constrain the other lists in ways that aren't really acceptable.

I do this kind of thing in several Handlers.  There are two ways to
approach this.  The easy way is that the Handler knows what list it is
processing (the mlist argument to process()):

    if mlist.internal_name() in my_lists:
        # do my thing

The more elegant way (and not much harder) is to define a
MyVeryOwnSpamDetect handler (which starts as a copy of
SpamDetect.py!), save it to the Handlers directory, then insert it in
the list's configuration with

$ cd /path/to/mailman/lib; bin/withlist -l mylist
> mlist.pipeline = GLOBAL_PIPELINE
> mlist.pipeline[position_of_SpamDetect] = 'MyVeryOwnSpamDetect'
> mlist.Save()
> <Ctrl-D>
$

And now you know why all the cool kids love Mailman!

Mark Sapiro | 2 Apr 20:01 2011
Picon

Re: Topics and friendly rejections of topicless messages

Patti Beadles wrote:

>I'm trying to set up a list with the topics feature, and I'm
>having a little bit of trouble achieving what I want.  The
>basic feature is fine, but making it a smooth user experience
>is being problematic.  In particular, what I want is this:
>
>A) Allow topic-based list subscription
>B) Every message must have a topic
>C) Messages that don't have a topic get bounced back to the user
>D) The bounced messages must be "pretty", and explain what to do
>
>A was easy enough.

Congratulations. Was the FAQ at <http://wiki.list.org/x/G4CE> helpful?
Did you even see it?

>I implemented B and C by using spam filtering, and setting the
>spam filter to bounce mail whose subject line matches a regular 
>expression.  That regex is essentially "not (topic1 | topic2)".
>That solution is functional, if not particularly elegant.
>
>Item D is throwing me for a loop.  I can make it happen with a
>one-line change to SpamDetect.py, but that's probably not going
>to fly.  The host runs multiple lists, and doing this would 
>constrain the other lists in ways that aren't really acceptable.

I think a better solution to B, C and D. is a custom handler. A custom
handler can be enabled for only a single list and should therefore be
acceptable to the host. See the FAQ at <http://wiki.list.org/x/l4A9>
(Continue reading)


Gmane