Re: [Mailman-Users] Problem with mailman-loop address

[ratatouille]

Hello!

Mark Sapiro  schrieb am 08.06.19 um 08:13:24 Uhr:

> On 6/8/19 3:29 AM, ratatouille wrote:
> > 
> > In /var/lib/mailman/data/aliases there is no alias like mailman-loop.
> > 
> > What's wrong here and how do I fix this?  
> 
> 
> There should be. If Mailman is generating this file, it should contain
> 
> # The ultimate loop stopper address
> mailman-loop: /var/lib/mailman/data/owner-bounces.mbox
> 
> Try running Mailman's bin/genaliases

I did this already, it is not there.

 # STANZA START: mailman
# CREATED: Sat Jun  8 11:43:23 2019
mailman: "|/usr/lib/mailman/mail/mailman post mailman"
mailman-admin:   "|/usr/lib/mailman/mail/mailman admin mailman"
mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman"
mailman-join:"|/usr/lib/mailman/mail/mailman join mailman"
mailman-leave:   "|/usr/lib/mailman/mail/mailman leave mailman"
mailman-owner:   "|/usr/lib/mailman/mail/mailman owner mailman"
mailman-request: "|/usr/lib/mailman/mail/mailman request mailman"
mailman-subscribe:   "|/usr/lib/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman"
# STANZA END: mailman

  Andreas
--
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] Problem with mailman-loop address

[Mark Sapiro]

On 6/8/19 3:29 AM, ratatouille wrote:
> 
> In /var/lib/mailman/data/aliases there is no alias like mailman-loop.
> 
> What's wrong here and how do I fix this?


There should be. If Mailman is generating this file, it should contain

# The ultimate loop stopper address
mailman-loop: /var/lib/mailman/data/owner-bounces.mbox

Try running Mailman's bin/genaliases

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem Delivering Mail

[Odhiambo Washington]

Hi David,

You'll have to dig deeper into cPanel documentation to find where the
problem is.

If you have shell access, then a simple exim -bt j...@nfbnet.org should
tell you whether the address is deliverable or not.

Exim+Mailman integration involves the MACROS, the routers and transports,
and the mm_cfg.py and I must say I don't know how those are done with
cPanel. I know how to do them via CLI though.


On 15 January 2018 at 23:26, David Andrews  wrote:

> Some of my lists, and some of my users are unable to send mail. The users
> get a message like this:
>
> Subject: Mail delivery failed: returning message to sender
>
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   j...@nfbnet.org
> local delivery failed
>
> Reporting-MTA: dns; host.nfbnet.org
>
> Action: failed
> Final-Recipient: rfc822;j...@nfbnet.org
> Status: 5.0.0
>
> Received: from smtp33.relay.iad3a.emailsrvr.com (localhost [127.0.0.1])
> by smtp33.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id
> D8CA42B83
> for ; Mon, 15 Jan 2018 13:26:18 -0500 (EST)
> Received: by smtp33.relay.iad3a.emailsrvr.com (Authenticated sender:
> xxx@yyy.zzzus) with ESMTPSA id A014A5807
> for ; Mon, 15 Jan 2018 13:26:18 -0500 (EST)
> Received: from mmlenovo ([UNAVAILABLE]. [173.217.232.59])
> (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384)
> by 0.0.0.0:465 (trex/5.7.12);
> Mon, 15 Jan 2018 13:26:18 -0500
> Received: from smtp64.iad3a.emailsrvr.com ([173.203.187.64]:33780)
> by host.nfbnet.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-
> SHA384:256)
> (Exim 4.89_1)
>
>
> It is on more than one list -- and more than one user.  This is a cPanel
> installation, but I don't know that this is related, and I have access to
> everything.
>
> Thanks for any ideas.
>
> Dave
>
>
>
> --
> 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/ma
> ilman-users%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/odhiam
> bo%40gmail.com
>



-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."
--
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] Problem Delivering Mail

[David Andrews]

At 03:03 PM 1/15/2018, Mark Sapiro wrote:
On 01/15/2018 12:26 PM, David Andrews wrote: > 
Some of my lists, and some of my users are 
unable to send mail. The > users get a message 
like this: > > Subject: Mail delivery failed: 
returning message to sender > > This message was 
created automatically by mail delivery 
software. > > A message that you sent could not 
be delivered to one or more of its > recipients. 
This is a permanent error. The following 
address(es) failed: > > Â  j...@nfbnet.org > Â Â 
  local delivery failed > > Reporting-MTA: dns; 
host.nfbnet.org > > Action: failed > 
Final-Recipient: rfc822;j...@nfbnet.org > 
Status: 5.0.0 ... > It is on more than one list 
-- and more than one user.  This is a cPanel > 
installation, but I don't know that this is 
related, and I have access > to everything. So 
presumably j...@nfbnet.org is the list. If this 
is cPanel, the MTA is almost certainly Exim, and 
in my experiencer, Exim logs aren't as detailed 
as the ones I'm more used to, but what is in the 
Exim logs related to this message. You might 
also consider contacting cPanel about this. See 
 and 
. -- Mark Sapiro



Thanks everybody, things working again.  Not sure 
what caused the problem, I did delete a file last 
night, but it shouldn't have broken all lists, but maybe it did.
Got a auto message from cPanel about Mailman RPM 
being out of kilter, and gave me a command to 
fix. It basically reinstalled Mailman I think, but everything working again.


Dave

p.s.  I know just enough to be dangerous -- which isn't very much!

DA



--
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] Problem Delivering Mail

[Mark Sapiro]

On 01/15/2018 12:26 PM, David Andrews wrote:
> Some of my lists, and some of my users are unable to send mail. The
> users get a message like this:
> 
> Subject: Mail delivery failed: returning message to sender
> 
> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
> 
>   j...@nfbnet.org
>     local delivery failed
> 
> Reporting-MTA: dns; host.nfbnet.org
> 
> Action: failed
> Final-Recipient: rfc822;j...@nfbnet.org
> Status: 5.0.0
...
> It is on more than one list -- and more than one user.  This is a cPanel
> installation, but I don't know that this is related, and I have access
> to everything.


So presumably j...@nfbnet.org is the list. If this is cPanel, the MTA is
almost certainly Exim, and in my experiencer, Exim logs aren't as
detailed as the ones I'm more used to, but what is in the Exim logs
related to this message.

You might also consider contacting cPanel about this. See
 and .

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with AOL

[David Andrews]

Thanks!  As usual You're the man!

Dave

p.s.  I suppose I could edit and use for gmail too, and put them in a 
cron job and run once a day to take care of new folks.



At 04:30 PM 2/14/2017, Mark Sapiro wrote:

On 02/14/2017 07:40 AM, David Andrews wrote:
>
> Well I will have to investigate further and see if that is the problem.
> You said "some time ago," and it is recent with me, which means it could
> be something else, or not.


True, but you should be able to tell from mail logs or Mailman's bounce
log. I.e., when an AOL user posts, does only the delivery to that AOL
user bounce or does delivery to all AOL users bounce.

The former was my case.


> Have you written, or is there a script to go
> through all lists and change attribute, and/or would it work to send
> them post acknowledgement? With 300 lists and over 12,000 users I can't
> really do it by hand.


Here's a withlist script. Save it in Mailman's bin/ directory as
aol_notmetoo.py

--- cut here ---
from Mailman import mm_cfg

def aol_notmetoo(mlist):
if not mlist.Locked():
mlist.Lock()
for member in mlist.getMembers():
if member.lower().endswith('@aol.com'):
mlist.setMemberOption(
member, mm_cfg.DontReceiveOwnPosts, 1)
# If you don't want to set 'ack' remove the next two lines
mlist.setMemberOption(
member, mm_cfg.AcknowledgePosts, 1)
mlist.Save()
mlist.Unlock()
--- cut here ---


Then you can run this via withlist

bin/withlist -a -r aol_notmetoo

That will set 'not metoo' and optionally 'ack' for every @aol.com member
on every list



--
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan


--
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] Problem with AOL

[Mark Sapiro]

On 02/13/2017 07:45 PM, David Andrews wrote:
> Does anyone know if AOL has changed its DMARC policies recently.  All of
> a sudden I am getting lots of AOL bounces, or maybe they have black
> listed us?  nfbnet.org


Back to the original question.

I don't think AOL has changed anything with respect to DMARC. If it is
not the case that these are bounces of users own posts, then there is
another issue. What do the bounces (or rejects in the mail log) say is
the reason?

You may find  helpful.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with AOL

[Mark Sapiro]

On 02/14/2017 07:40 AM, David Andrews wrote:
> 
> Well I will have to investigate further and see if that is the problem.
> You said "some time ago," and it is recent with me, which means it could
> be something else, or not.


True, but you should be able to tell from mail logs or Mailman's bounce
log. I.e., when an AOL user posts, does only the delivery to that AOL
user bounce or does delivery to all AOL users bounce.

The former was my case.


> Have you written, or is there a script to go
> through all lists and change attribute, and/or would it work to send
> them post acknowledgement? With 300 lists and over 12,000 users I can't
> really do it by hand.


Here's a withlist script. Save it in Mailman's bin/ directory as
aol_notmetoo.py

--- cut here ---
from Mailman import mm_cfg

def aol_notmetoo(mlist):
if not mlist.Locked():
mlist.Lock()
for member in mlist.getMembers():
if member.lower().endswith('@aol.com'):
mlist.setMemberOption(
member, mm_cfg.DontReceiveOwnPosts, 1)
# If you don't want to set 'ack' remove the next two lines
mlist.setMemberOption(
member, mm_cfg.AcknowledgePosts, 1)
mlist.Save()
mlist.Unlock()
--- cut here ---


Then you can run this via withlist

bin/withlist -a -r aol_notmetoo

That will set 'not metoo' and optionally 'ack' for every @aol.com member
on every list



-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with AOL

[David Andrews]

At 08:57 AM 2/14/2017, Mark Sapiro wrote:

On 02/13/2017 09:33 PM, Jayson Smith wrote:
>
> One of my mailing lists has one AOL user who finally got tired of *his*
> messages to the list being rejected by AOL.


Some time ago, I noticed that when an AOL user posts to a list, the list
copy sent back to that user, but not other AOL users, was always
rejected with the "AOL will not accept delivery of this message."
reason. This is similar to Gmail (see )
except Gmail just drops the message rather than bouncing it.

Anyway, I just set all the AOL list members to not receive their own
posts (they weren't receiving them anyway), and that worked around the
problem.


Well I will have to investigate further and see if that is the 
problem. You said "some time ago," and it is recent with me, which 
means it could be something else, or not.  Have you written, or is 
there a script to go through all lists and change attribute, and/or 
would it work to send them post acknowledgement? With 300 lists and 
over 12,000 users I can't really do it by hand.


Dave


--
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] Problem with AOL

[Mark Sapiro]

On 02/13/2017 09:33 PM, Jayson Smith wrote:
> 
> One of my mailing lists has one AOL user who finally got tired of *his*
> messages to the list being rejected by AOL.


Some time ago, I noticed that when an AOL user posts to a list, the list
copy sent back to that user, but not other AOL users, was always
rejected with the "AOL will not accept delivery of this message."
reason. This is similar to Gmail (see )
except Gmail just drops the message rather than bouncing it.

Anyway, I just set all the AOL list members to not receive their own
posts (they weren't receiving them anyway), and that worked around the
problem.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with AOL

[Jayson Smith]

Hi,

A while back, I was getting irregular AOL bounces. By that, I mean some 
messages would go through just fine, and some would bounce with the 
error "AOL will not accept delivery of this message." Very unhelpful, as 
you can see. Furthermore, if a message bounced, it was probably always 
going to bounce no matter what you did E.G. send a copy to that 
particular user rather than a mailing list, etc.


One of my mailing lists has one AOL user who finally got tired of *his* 
messages to the list being rejected by AOL. We did some investigating, 
and it turns out they have a whitelist program. I don't know the exact 
URL but can probably find it if you're interested.


Hope this helps,

Jayson

On 2/13/2017 10:45 PM, David Andrews wrote:
Does anyone know if AOL has changed its DMARC policies recently.  All 
of a sudden I am getting lots of AOL bounces, or maybe they have black 
listed us?  nfbnet.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/jaybird%40bluegrasspals.com


.



--
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] Problem pgp signed messages

[Stephen J. Turnbull]

Mark Sapiro writes:

 > Perhaps the sigs being stripped are another protocol, e.g.
 > application/pkcs7-signature or ??

That was the first thing that occurred to me, although I was thinking
S-MIME.

--
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] Problem with this list archive

[Mark Sapiro]

On 11/21/15 7:59 AM, Mark Sapiro wrote:
> On 11/21/15 3:22 AM, Alain Williams wrote:
>> It seems to have recently gone to HTTPS and is generating a 404 for HTTP 
>> URLs.
...
> There is a rewrite from http to https in the apache config for
> mail.python.org. It was working.
> 
> The server was rebooted at about 20/Nov/2015:09:50 (-0500) and since
> then the rewrite is apparently not working


Thanks to Ernest W. Durbin III, this is now fixed. At some point an
Apache update added a symlink

/etc/apache2/sites-enabled/000-default.conf ->
/etc/apache2/sites-available/000-default.conf

and when the server was rebooted, this overrode our config for the port
80 listener.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem pgp signed messages

[Mark Sapiro]

On 11/21/15 3:39 AM, Alain Williams wrote:
> I am trying to allow signed messages on a mail list.
> 
> I added multipart/signed & application/pgp-signature to pass_mime_types which
> stopped signed emails being rejected by mailman.
> 
> My problem is that the signature attachment is being stripped from the 
> message.
> What should I be doing ?


What you have done should be working.

This list for example has in pass_mime_types

multipart
text/plain
text/x-diff
application/pgp-signature

and I'm sure my sig will come through.

Perhaps the sigs being stripped are another protocol, e.g.
application/pkcs7-signature or ??

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
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] Problem with this list archive

[Mark Sapiro]

On 11/21/15 3:22 AM, Alain Williams wrote:
> It seems to have recently gone to HTTPS and is generating a 404 for HTTP URLs.
> 
> This causes a problem with archives email that contains a link to old 
> messages. Eg:
> 
> https://mail.python.org/pipermail/mailman-users/2005-January/042243.html
> 
> contains a link to:
> 
> http://mail.python.org/pipermail/mailman-users/2005-January/041697.html
> 
> which comes up 404. However, if you manually convert ''http:'' to ''https:'' 
> the
> URL then works. Could you persuade Apache to do that redirect ?



There is a rewrite from http to https in the apache config for
mail.python.org. It was working.

The server was rebooted at about 20/Nov/2015:09:50 (-0500) and since
then the rewrite is apparently not working. I can't see that anything in
the apache configs has changed, and I have tried both reloading and
restarting apache to no avail.

Apparently something changed when the server was rebooted yesterday, but
I don't know what.

Perhaps another postmaster or 'rooter' has an idea.

(I'm on vacation in Croatia at the moment and don't have a lot of time
to devote to this)

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] problem with accented characters, converting HTML to plain text

[Mark Sapiro]

On 7/21/15 12:42 AM, Laura Creighton wrote:
 
 My new rule in my mailer for how to display html text is:
 
 w3m -dump -o display_link_number=1 -cols 78 -T text/html -I $(echo %a | sed 
 -r 's/.*charset=?([-a-zA-Z0-9_]*).*/\1/') -O utf-8 | less
 
 which is one heck of a mouthful, but hasn't caused me any problems since.
 
 Just in case somebody else wants to ditch lynx ...


While I'm sure Laura's command above works well as an HTML viewer for an
MUA such as might be specified in a mutt mailcap file, there are issues
with trying to use this as a Mailman HTML_TO_PLAIN_TEXT_COMMAND because
it gets the input charset from the message's Content-Type: header and
none of the message's headers are passed to HTML_TO_PLAIN_TEXT_COMMAND.
Also, it specifies the output charset as utf-8, but Mailman will not
change the charset parameter in the converted MIME part. It only changes
the MIME type from text/html to text/plain so if the original HTML
charset is not utf-8, creating utf-8 output would be wrong.

While one could use some w3m command in HTML_TO_PLAIN_TEXT_COMMAND, the
appropriate command might be something like

w3m -dump -o display_link_number=1 -cols 78 -T text/html %(filename)s

without the -I and -O options, and this could wind up with the same
charset issues as lynx.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] problem with accented characters, converting HTML to plain text

[Laura Creighton]

In a message of Mon, 20 Jul 2015 11:04:08 -0700, Mark Sapiro writes:
On 7/19/15 1:13 PM, Dominique Asselineau wrote:
 Hello,
 
 When a e-mail in text/html content-type is converted in to plain text,
 the accented characters are not treated correctly.


There are potential issues with this. Mailman gets the content of the
text/html part and calls HTML_TO_PLAINTEXT_COMMAND (lynx -dump in the
default case) to convert the HTML to a plain text rendering and replaces
the content of the part with that and changes the Content-Type: to
text/plain while maintaining any charset= parameter.

Lynx normally does not recode any characters, so the output of lynx
-dump should be in the same charset is the input and it should be OK.

Problems arise if the input has characters represented as HTML entities
such as aacute; or egrave;. In this case, lynx outputs the characters
encoded in a charset which may not match the messages encoding.

In order to say more, I would need to see a raw message as sent to the
list with all headers intact and the resultant raw message from the list
with all headers intact.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--

I had enough trouble with lynx over this -- it used to be how I
converted all html mail my mail reader saw, but such characters
are not rare in the mail I receive -- that I gave up on lynx.

My new rule in my mailer for how to display html text is:

w3m -dump -o display_link_number=1 -cols 78 -T text/html -
I $(echo %a | sed -r 's/.*charset=?([-a-zA-Z0-9_]*).*/\1/') -O utf-8 | less

which is one heck of a mouthful, but hasn't caused me any problems since.

Just in case somebody else wants to ditch lynx ...

Laura
--
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] problem with accented characters, converting HTML to plain text

[Mark Sapiro]

On 7/19/15 1:13 PM, Dominique Asselineau wrote:
 Hello,
 
 When a e-mail in text/html content-type is converted in to plain text,
 the accented characters are not treated correctly.


There are potential issues with this. Mailman gets the content of the
text/html part and calls HTML_TO_PLAINTEXT_COMMAND (lynx -dump in the
default case) to convert the HTML to a plain text rendering and replaces
the content of the part with that and changes the Content-Type: to
text/plain while maintaining any charset= parameter.

Lynx normally does not recode any characters, so the output of lynx
-dump should be in the same charset is the input and it should be OK.

Problems arise if the input has characters represented as HTML entities
such as aacute; or egrave;. In this case, lynx outputs the characters
encoded in a charset which may not match the messages encoding.

In order to say more, I would need to see a raw message as sent to the
list with all headers intact and the resultant raw message from the list
with all headers intact.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with Postfix

[Mark Sapiro]

On 05/11/2015 07:38 PM, Eric Lamer wrote:
 Hi,
 
When I am sending mail to my mailman server I get this error:
 
 
 Remote Server returned ' #5.3.0 x-unix; Group mismatch error. Mailman 
 expected the mail wrapper script to be executed as group mailman, but the 
 system's mail server executed the mail script as group nobody. Try tweaking 
 the mail server to run the script as group mailman, or re-run configure, 
 providing the command line option `--with-mail-gid=nobody'.'
 Any idea how to fix it?


See the FAQ at http://wiki.list.org/x/4030645.

Note that with Postfix, the pipe to the mail wrapper will be executed as
the user that owns the aliases.db file in which the alias is found.

If you have Mailman/Postfix integration configured this will be
/path/to/mailman/data/aliases.db which chould be owned by 'mailman'.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem after switching servers

[Mark Sapiro]

On 05/10/2015 10:45 AM, Eric Lamer wrote:
 
 When I access the web
 server and click on a list it try to go to
 http://list.aaa.com/cgi-bin/mailman/listinfo/g711.1ac  instead of
 http://list.aaa.com/mailman/listinfo/g711.1ac so my old server had
 cgi-bin in the url and my new server does not.  How can I fix this?


Put

DEFAULT_URL_PATTERN = 'http://%s/mailman/'

in mm_cfg.py and run Mailman's

bin/withlist -a -l -r fix_url

See the FAQ at http://wiki.list.org/x/4030616 for more info.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with missing text

[Mark Sapiro]

On 03/10/2014 12:27 PM, sherwin wrote:
 Hello,
 
 
 As administrator for the Midfex forum on Ibiblio, I am having a problem
 with a user
 who posts messages that result in no text appearing on the final
 message.  I do see
 the text in the moderated request sent to me.  Here is the message he is
 sending.
 Note that this request for confirmation from Ibiblio contains the text,
 but after
 approving the message, it is no longer present.


The message you included below is exactly what we would want to see,
i.e. the complete raw message of a held message notification to the list
admin.

Unfortunately, it appears to be the wrong held message notification. It
is a notification of your list post

...
 Subject: [Bulk] Status of Empty Messages
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
 Content-Transfer-Encoding: 7bit
 
 Hi All,
 
 You may have seen a few empty messages recently posted.  This
 happened before last January.  So far, only two users are having
 this problem.  I am investigating this issue and hopefully will find
 some resolution.  In the meantime, you may see a few test messages
 appearing that you can ignore.
 
  Sherwin Dubren
  Midfex Forum Administrator


I am guessing that this is not the message that resulted in an empty
message being delivered to the list.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with messages held in Moderator Queue

[Mark Sapiro]

On 02/21/2014 08:07 AM, Andy Jeffries wrote:
 
 Every time, the HTTP request POSTs to
 /cgi-bin/mailman/admindb/mailing-list-name-here, which 301 redirects to the
 same URL and the GET request loads exactly the same as before (i.e. it
 didn't remove any of the stuck emails).


That's the issue. The redirect is losing the POST data. See the FAQ at
http://wiki.list.org/x/ioA9 (3rd paragraph).


 Can anyone suggest what I should try next to get the web interface working?


Fix your web server to not redirect. If this is a redirect from http to
https, see paragraph 2 of the above FAQ.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] problem after changing the server name

[Mark Sapiro]

On 01/05/2014 08:00 AM, Dominique Asselineau wrote:
 
 It seeems the server name is encoded in file
 /var/lib/mailman/lists/list-name/config.pck updated by the command
 config_list -i config-file-name, but i do not find manner to
 modify the server name into those pages. host_name specifies only the
 domain in the e-mail adresses.


See the FAQs at http://wiki.list.org/x/gIA9 and
http://wiki.list.org/x/mIA9.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] problem after changing the server name

[Tanstaafl]

On 2014-01-05 12:05 PM, Mark Sapiro m...@msapiro.net wrote:

On 01/05/2014 08:00 AM, Dominique Asselineau wrote:


It seeems the server name is encoded in file
/var/lib/mailman/lists/list-name/config.pck updated by the command
config_list -i config-file-name, but i do not find manner to
modify the server name into those pages. host_name specifies only the
domain in the e-mail adresses.



See the FAQs at http://wiki.list.org/x/gIA9 and
http://wiki.list.org/x/mIA9.


Thanks Dominique and Mark - I had completely forgotten about this after 
migrating everything to my new server yesterday.


Mark - the only setting that changed on mine is the DEFAULT_URL_PATTERN, 
but I'm guessing I still need to do the full command.


So, before I do something dumb and blindly run the command and possibly 
mess up my lists (that seem to be working fine), I simply cd to the /bin 
directory, and run:


bin/withlist -l -a -r fix_url -- [fix_url options]

?

Or do I need to actually specify something for the word 'options'?

Thanks again!

Charles
--
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] problem after changing the server name

[Mark Sapiro]

On 01/05/2014 09:24 AM, Tanstaafl wrote:
 
 Mark - the only setting that changed on mine is the DEFAULT_URL_PATTERN,
 but I'm guessing I still need to do the full command.
 
 So, before I do something dumb and blindly run the command and possibly
 mess up my lists (that seem to be working fine), I simply cd to the /bin
 directory, and run:
 
 bin/withlist -l -a -r fix_url -- [fix_url options]
 
 ?
 
 Or do I need to actually specify something for the word 'options'?


[fix_url options] in the above stands for those options (i.e., -u HOST
and/or -v) you might want to specify to fix_url.

Assuming you have only one URL domain and email domain and they are
properly set as DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST, what you need
to run after changing DEFAULT_URL_PATTERN is just

bin/withlist -l -a -r fix_url

or to see what it's doing

bin/withlist -l -a -r fix_url -- -v

(the -- separates the fix_url options from the withlist options).

If you have multiple virtual hosts, it's more complicated. You need to run

bin/withlist -l -r fix_url LISTNAME -u HOSTNAME

where LISTNAME is a list name and HOSTNAME is the URL host for that list
separately for each list.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] problem after changing the server name

[Tanstaafl]

On 2014-01-05 12:53 PM, Mark Sapiro m...@msapiro.net wrote:

Assuming you have only one URL domain and email domain and they are
properly set as DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST, what you need
to run after changing DEFAULT_URL_PATTERN is just

bin/withlist -l -a -r fix_url

or to see what it's doing

bin/withlist -l -a -r fix_url -- -v


Spot on as always, Mark, thx - and yeah, I just have the one domain, so 
it was easy peasy... took all of what, .5 seconds? :)

--
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] Problem with mailman web interface on Debian/Apache

[Mark Sapiro]

On 10/20/2013 06:26 AM, Sascha Rissel wrote:
 
 I just setup mailman on Debian and created the first list mailman.
...
 I used the following tutorial:
 http://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-on-debian-squeeze


Please see the FAQ at http://wiki.list.org/x/OIDD.


 Can anyone help me?


See http://www.list.org/mailman-install/node10.html.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with mailman and outlook.com

[Tim Sterk]

On 07-10-13 04:36, Mark Sapiro wrote:

On 10/04/2013 05:51 AM, Tim Sterk wrote:

Hi All,

I'm having a problem with outlook.com and mailman. When I'm trying to
send a message through Outlook.com marks it as spam, but when I'm
sending a message from the same domain (and IP address), it is accepted
without a hitch.

Underneath the headers of a message that is rejected at outlook.com:


Rejected or marked as spam? They are not the same. And if it was
rejected, where did you find the headers?


They are moved into the unwanted box, so I was able to view the message 
and headers from there.






*Is there anybody who can help me solving this problem?


Probably only Microsoft, but the FAQ at http://wiki.list.org/x/4oA9
may help.



The interesting part for me is that this problem only applies to mail 
sent through mailman, if I'm sending an email to the same address from 
the same domain name it is accepted without a problem, so I'm thinking 
that there is something in the headers that triggers this reaction at 
outlook.com.


p.s. the messages are accepted without a problem at gmail.com (I haven't 
tried any other major mail providers).


Greetings,
Tim Sterk

--
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] Problem with mailman and outlook.com

[Mark Sapiro]

On 10/09/2013 12:45 AM, Tim Sterk wrote:
 
 They are moved into the unwanted box, so I was able to view the message
 and headers from there.


So they were not rejected but rather marked as spam and put in a spam
box rather than the inbox. Had they been rejected, you wouldn't have
seen them at all, and they would have been recorded as a bounce by Mailman.


 The interesting part for me is that this problem only applies to mail
 sent through mailman, if I'm sending an email to the same address from
 the same domain name it is accepted without a problem, so I'm thinking
 that there is something in the headers that triggers this reaction at
 outlook.com.


Exactly. It could be the 'Precedence: list' header or some other header
or combination of headers, but only Microsoft knows for sure, and they
won't tell you because they consider it proprietary information which
would be useful to spammers.

Since you apparently use Mutt and have your own server, you could
experiment by resending the message directly with all Mailman's added
headers and delete headers one by one to find the header(s) that trigger
it, but it is possible that this is a more complex situation than that
which depends on the presence of certain headers in combination together
with body contents.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with mailman and outlook.com

[Mark Sapiro]

On 10/04/2013 05:51 AM, Tim Sterk wrote:
 Hi All,
 
 I'm having a problem with outlook.com and mailman. When I'm trying to
 send a message through Outlook.com marks it as spam, but when I'm
 sending a message from the same domain (and IP address), it is accepted
 without a hitch.
 
 Underneath the headers of a message that is rejected at outlook.com:


Rejected or marked as spam? They are not the same. And if it was
rejected, where did you find the headers?


 *Is there anybody who can help me solving this problem?


Probably only Microsoft, but the FAQ at http://wiki.list.org/x/4oA9
may help.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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] Problem with duplicate emails

[Richard Damon]

On 7/7/13 7:11 PM, Javad Hoseini-Nopendar wrote:
 Hello
 I created two mailing lists on my website:
 newslet...@iranravi.com
 And:
 iranr...@iranravi.com

 Also, iranr...@iranravi.com is a member of newslet...@iranravi.com. That 
 means, when I send an email to newslet...@iranravi.com, if someone is not 
 the member of this group, but is the member of iranr...@iranravi.com, this 
 person will also receive the email. In fact, one group is only for sending 
 newsletters and the other group is for discussing about various matters. now 
 I have a problem. When I send an email, if someone is the member of both 
 groups, this person will receive two copies of the email. Is there any way I 
 can prevent duplicate emails? I saw a choice in General options:
 Prevent Duplicate Emails.

 I thought mailman would delete the duplicates automatically, but it seems 
 not to be the case. Please help.

 Thank you

Since IranRAVI is a member of newsletter, and newsletter is announce
only, there really is no big reason to subscribe to both, you just need
to subscribe to IranRAVI and you will get all the messages, and can
reply to the discussion list about them.

The problem is that each list processes its sending independently, and
don't know about the details of the interlocking subscriptions, so I
don;t think there is any way to stop the multiple emails in this case.

-- 
Richard Damon

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with duplicate emails

[Mark Sapiro]

On 07/07/2013 04:11 PM, Javad Hoseini-Nopendar wrote:

 I have a problem. When I send an email, if someone is the member of both 
 groups, this person will receive two copies of the email. Is there any way I 
 can prevent duplicate emails? I saw a choice in General options:
 Prevent Duplicate Emails.


The choice in General Options Filter out duplicate messages to list
members (if possible) is a setting for new_member_options which
controls what usetr options are set by default for new subscribers to
the list. This affects the user option Avoid duplicate copies of
messages? which in turn only affects whether the user is sent a list
copy of the mail when the user is a direct To: or Cc: recipient of the post.


 I thought mailman would delete the duplicates automatically, but it seems 
 not to be the case. Please help.


You have two choices. Either tell members of the iranr...@iranravi.com
list not to subscribe to the newslet...@iranravi.com list as it will
only result in their receiving duplicates, or delete
iranr...@iranravi.com from the newslet...@iranravi.com list and instead
add iranr...@iranravi.com to the Non-digest options -
regular_include_lists setting of the newslet...@iranravi.com list.

To make the second option completely effective, also set the
iranr...@iranravi.com list's Digest options - digestable to No because
if there are any digest subscribers, they won't receive
newslet...@iranravi.com posts.

See the FAQ at http://wiki.list.org/x/TIA9.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem listing full member names with diacritics

[Brett Delmage]

On 06/12/2013 09:36 PM, Brett Delmage wrote:


Characters with diacritics in subscriber names are coming out as ?.


On Wed, 12 Jun 2013, Mark Sapiro wrote:



You have a couple of choices:

1) You can edit bin/list_members and replace

ENC = sys.getdefaultencoding()

by

ENC = 'utf-8'


Fantastic. Thanks Mark! What a clear and prompt reply.

Now I can export the list susbscribers. Yay! (no - not leaving MM yet)

Mark, Your reply shows up as the 10,499th list posting since the first one 
I have in my mail folder from you on 2004 June 13 - Hmm, isn't that a 
coincidence. (I've been on this list since 2001).


That's a truly remarkable level of service to the Mailman community. 
Thank you for everything you've done for all of us and list users 
everywhere.


Brett




--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with plus-sign + in the list-name

[Mark Sapiro]

On 06/13/2013 03:51 AM, Gerhard Rappenecker wrote:
 Hi all,
 
 since upgrading to mailman 2.1.15 the following problem occurs:
 
 When lists admins want to change the list parameters or member-list by the 
 webinterface they receive:
 Error: The form lifetime has expired. (request forgery check) and no change 
 is done.
 
 IMPORTANT: This error only happens when the list-name contains a plus-sign 
 +, like e+t...@lists.myorg.com.


This is a bug in the new CSRF checking scheme introduced in 2.1.15. It
will take me a day or so to do a proper fix. In the mean time, you can
edit the Mailman/CSRFcheck.py module by adding immediately following the
lines

def csrf_check(mlist, token):
 check token by mailman cookie validation algorithm 

the line

return True

which will effectively disable the check and return pre-2.1.15 behavior.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with plus-sign + in the list-name

[Mark Sapiro]

On 06/13/2013 07:56 AM, Gerhard Rappenecker wrote:
 
 the workaround works fine.


This is now reported at
https://bugs.launchpad.net/mailman/+bug/1190802 and properly fixed at
http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1392.


 Thanks a lot for the great support.


We try. It's always good to hear our efforts are appreciated.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem listing full member names with diacritics

[Mark Sapiro]

On 06/12/2013 09:36 PM, Brett Delmage wrote:
 
 Characters with diacritics in subscriber names are coming out as ?.


bin/list_members uses the encoding returned by Python's
sys.getdefaultencoding() which is 'ascii' so all non-ascii characters
get converted to '?'

You have a couple of choices:

1) You can edit bin/list_members and replace

ENC = sys.getdefaultencoding()

by

ENC = 'utf-8'

2) Edit /usr/lib/pythonv.v/site.py where v.v is your Python version.
Find the definition of setencoding() and change the4th line from

encoding = ascii # Default value set by _PyUnicode_Init()

to
encoding = utf-8

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Farsi characters

[Mark Sapiro]

On 3/25/2013 5:35 PM, Javad Hoseini wrote:
 
 But mailman sends only some peculiar numbers and letters instead of Farsi 
 text. It writes something like this in the beginning of 
 welcome email:
 29@5926252wfo


It's hard to see without seeing the actual welcome email message, but my
guess is that the welcome message specifies the character set of the
body as one which doesn't support the Farsi characters, e.g. an English
language list with character set us-ascii, but possibly some other
language with a non-utf-8 character set.

If it is English and us-ascii and you have sufficient access to the
Mailman installation, you can change the character set to utf-8 as
outlined in the post at
http://mail.python.org/pipermail/mailman-users/2011-March/071320.html.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with remove-members -f filename list command not working

[Mark Sapiro]

On 3/22/2013 1:23 PM, Antonio Colin wrote:
 
 They don't work at all giving a prompt waiting for input. And it ends only 
 when I press ^C 
 (throwing a traceback which I posted here: http://pastebin.com/jt8C3Qjq ) or 
 ^Z.


The traceback you posted shows the command is not waiting for input but
for some other processes list lock to be relinquished. See the FAQ at
http://wiki.list.org/x/noA9.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Administrative requests for MailingList

[Mark Sapiro]

Tim Chesnutt wrote:

I have enabled mailing lists under cPanel on my hosting package and am 
doing my own testing to ensure I understand how it works before inviting 
other users, and putting the system into service.


See the FAQs at http://wiki.list.org/x/sYA9 and
http://wiki.list.org/x/OIDD.


When I visited the Administrative requests for mailing list page I see 
all the options, but none of them have any functionality.  That is no 
matter what option or options I select, when I click Submit All Data 
the page cycles, and returns with no change in the message status - no 
messages get Accepted, no messages get Rejected, no messages get 
Discarded, and no message is sent back to the author of the post (I have 
tried all possible combinations to see if there were someway to trigger 
action from this page, but to no avail.


See the FAQ at http://wiki.list.org/x/ioA9.

Also, examine the source of the web page and look at the action= URL in
the form tag. Is this URL identical to the URL of the page?

Also, is there any message at the top of the returned page?


In addition to not being able to administer these posts while signed in 
as the List Administrator, I note that I also can not cancel these posts 
from the email address they were originally submitted: When I follow the 
link to  cancel the posting, I am asked for a confirmation string (i.e. 
/cookie/) that you received in your email message.  There is no 
confirmation string received in the email system message telling me that 
my post is awaiting moderation.


The URL in the message you receive should be of the form

http://host/mailman/confirm/list_host/xx

where xx is a string of 40 hex digits. If you go to that URL, you
shouldn't need to provide a confirmation string, but if the URL is
split by your mail reader, you might just be going to

http://host/mailman/confirm/list_host/

or something with less than the full 40 hex digits. In any case, the 40
hex digits are the confirmation string.


The Mailman version provided is 2.1.14-1, and the hosting company has 
been of no use to date in this question as they are unfamiliar with this 
functionality.


You might consider trying to find a hosting service that is more
committed to serving its customers ;)


(there is another quirk that I mention here in case it is in some manner 
related, though I think not:  While in cPanel, looking under the heading 
Mailing Lists, the resulting page allows me to set up mailing lists, but 
for some reason the modify link with each mailing list does not take 
me to the Mailing List Administration page but to a broken link.  I had 
not worried about this lack of convenience as I can enter directly)


This is a cPanel feature which is not a part of GNU Mailman. I can't
help with cPanel's list maintenance features outside the standard GNU
Mailman web admin and admindb interfaces.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem when creating new lists

[Mark Sapiro]

David Renstrom wrote:

Everytime I create a new list using the Web interface in Mailman I get the
following error:

Bug in Mailman version 2.1.14
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but
the webmaster can find this information in the Mailman error logs. 

The file /etc/mailman/Virtual-mailman has changed ownership from mailman to
apache. I have to change it manually and then run the genaliases and postmap
commands to make the system work correctly again.


The owner of virtual-mailman shouldn't matter. The fact that this file
is in /etc/mailman/ rather than Mailman's data/ directory tells me you
are running someone's package. Please see the FAQ at
http://wiki.list.org/x/OIDD.

This could be a permissions or a SELinux issue.

What gets updated when you run genaliases? It should run both the
postalias and postmap commands. Do these succeed when you run
genaliases. You seem to imply that postalias succeeds, but postmap
fails and you need to run it by hand.


Could someone please tell me what's wrong because I'm kinda lost? See below
for more info.

Content of /var/log/mailman/error:
Aug 20 23:54:13 2012 (29703) command failed: /usr/sbin/postalias
/etc/mailman/aliases (status: 1, Operation not permitted)


Here it is postalias that fails. This has nothing to do with
virtual-mailman. It is reading /etc/mailman/aliases and updating
/etc/mailman/aliases.db and apparently doesn't have permission to do
so. If things are as they should be, the create process should be
running as the apache user with effective group = mailman (because
Mailman's cgi-bin/create wrapper is group mailman and SETGID and the
mailman group should be able to read and write /etc/mailman/aliases,
/etc/mailman/aliases.db, /etc/mailman/virtual-mailman and
/etc/mailman/virtual-mailman.db. If the permissions are OK, it is
probably a SELinux issue.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with people subscribing

[Mark Sapiro]

mike wrote:

I've ben admistering mailman for several years now. But ran into an odd
issue today. I had a customer come to me and they have a mailing list
b...@blah.com

when they have people use blah-subscr...@blah.com the people are getting
access denied errors i've checked all the settings am i over looking
something?


What is your MTA? How does it deliver to Mailman? Does it use aliases
and if so, do you have all 9 of the blah-*@blah.com aliases as well as
the b...@blah.com one?

What exactly do you mean by an access denied error? Do you mean they
mail to blah-subscr...@blah.com, get a confirmation message and then
get an http 401 when attempting to visit the URL in the confirmation
message? If so, is this different than from a subscribe attempt from
the form on the listinfo page.

Does this work for other lists?

Can they visit other list web pages like the listinfo, admin and
admindb pages and if so, is the domain in the URLs they use for those
pages the same as in the confirmation URL?

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via web interface in 2.1.11

[Stephen J. Turnbull]

On Wed, Mar 28, 2012 at 9:34 PM, Steve Matzura sm...@noisynotes.com wrote:

 user unknown in virtual mailbox table. My question is, why doesn't
 the web interface create new list feature update the aliases file?

What aliases file?  Exim, for example, doesn't need one at all.  There
are many MTAs, there are many different ways to configure them to
deliver to lists.

 Is this a bug or a feature,

It's a missing feature in your MTA. :-)  As I wrote, there are MTAs
that can be configured to automatically deliver to mailing lists (eg,
Exim is told to look for a $LIST.cfg file, and if that is found, it
delivers to | mailman post $LIST or something like that).

 or is there something I should put into
 mm_cfg.py to enable this, similar to
 owners-may-delete-their-own-lists?

We likely can help you, but you'll need to tell us exactly what MTA
you use, and how it's currently configured.  If you are using a
OS-distro-provided Mailman, tell us what distro and the full version
number of the Mailman package.  If you built from source, tell us
that.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via web interface in2.1.11

[Mark Sapiro]

Steve Matzura wrote:

It works just fine if I log in as root and use newlist, but if I try
to create a new list via the web admin interface, two things happen.
First, I get an error, whose text I do not have in front of me (I
know, I know, first rule of error reporting, report the exact error,
but you probably won't need it when I finish my explanation),


Wrong.


and
second, the aliases file is not updated, so if a subscriber tries to
send a message to the list, they receive an auto-reply telling them
user unknown in virtual mailbox table. My question is, why doesn't
the web interface create new list feature update the aliases file? Is
this a bug or a feature, or is there something I should put into
mm_cfg.py to enable this, similar to
owners-may-delete-their-own-lists?


If bin/newlist updates the aliases, web create should too, so clearly
this has something to do with the error.

If the list is created and the only problem is that aliases aren't
updated, it could be a permissions issue. Is Mailman's cgi-bin/create
wrapper group 'mailman' and SETGID and does group 'mailman' have write
permission on the aliases?

What is the error?

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in2.1.11

[Mark Sapiro]

Mark Sapiro wrote:

Steve Matzura wrote:

and
second, the aliases file is not updated, so if a subscriber tries to
send a message to the list, they receive an auto-reply telling them
user unknown in virtual mailbox table. My question is, why doesn't
the web interface create new list feature update the aliases file? Is
this a bug or a feature, or is there something I should put into
mm_cfg.py to enable this, similar to
owners-may-delete-their-own-lists?


If bin/newlist updates the aliases, web create should too, so clearly
this has something to do with the error.

If the list is created and the only problem is that aliases aren't
updated, it could be a permissions issue. Is Mailman's cgi-bin/create
wrapper group 'mailman' and SETGID and does group 'mailman' have write
permission on the aliases?


Also, the user unknown in virtual mailbox table error indicates the
list domain is a virtual domain. If the issue is that Mailman's
data/aliases is updated, but data/virtual-mailman is not, the problem
is that the email host_name for the list is not in
POSTFIX_STYLE_VIRTUAL_DOMAINS. For a web create, the host_name is
determined by taking the web host from the URL used to go to the
create page and looking it up in the VIRTUAL_HOSTS dictionary
(basically your add_virtualhost entries) and getting the host name
from there.

But, as Stephen suggests, don't make us guess. Give us all the
information.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via web interface in 2.1.11

[Steve Matzura]

The MTA is postfix. The file in question is
/var/lib/mailman/data/aliases which, according to what I've read, is
created from aliases.db. The interesting thing is, virtual-mailman
*is* updated correctly from virtual-mailman.db while aliases is not.

Mailman was installed long before I got here, but I'm assuming it was
installed via the standard package installer when Ubuntu was
originally built a few years ago. I also recognize I'm not running the
latest Ubuntu or Mailman.

Here's the perms on those four files:

-rw-rw 1 root list  6725 2012-03-28 19:07 aliases
-rw-rw 1 list list 12288 2012-03-28 19:07 aliases.db
-rw-rw 1 root list  5830 2012-03-28 19:07 virtual-mailman
-rw-r- 1 root list 12288 2012-03-28 19:07 virtual-mailman.db

On Thu, 29 Mar 2012 01:52:45 +0900, you wrote:

On Wed, Mar 28, 2012 at 9:34 PM, Steve Matzura sm...@noisynotes.com wrote:

 user unknown in virtual mailbox table. My question is, why doesn't
 the web interface create new list feature update the aliases file?

What aliases file?  Exim, for example, doesn't need one at all.  There
are many MTAs, there are many different ways to configure them to
deliver to lists.

 Is this a bug or a feature,

It's a missing feature in your MTA. :-)  As I wrote, there are MTAs
that can be configured to automatically deliver to mailing lists (eg,
Exim is told to look for a $LIST.cfg file, and if that is found, it
delivers to | mailman post $LIST or something like that).

 or is there something I should put into
 mm_cfg.py to enable this, similar to
 owners-may-delete-their-own-lists?

We likely can help you, but you'll need to tell us exactly what MTA
you use, and how it's currently configured.  If you are using a
OS-distro-provided Mailman, tell us what distro and the full version
number of the Mailman package.  If you built from source, tell us
that.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in 2.1.11

[Mark Sapiro]

Steve Matzura wrote:

The MTA is postfix. The file in question is
/var/lib/mailman/data/aliases which, according to what I've read, is
created from aliases.db.


The other way around.


The interesting thing is, virtual-mailman
*is* updated correctly from virtual-mailman.db while aliases is not.


You have it backwards. Mailman writes aliases and virtual-mailman and
then calls postalias and postmap to update the .db files from the text
files. Postfix uses the .db files even though the extensions are not
mentioned in main.cf.

You need to 'chmod 660 /var/lib/mailman/data/virtual-mailman.db' It
must be writable by the 'list group or it can't be updated by the web
server running the create CGI.


Mailman was installed long before I got here, but I'm assuming it was
installed via the standard package installer when Ubuntu was
originally built a few years ago. I also recognize I'm not running the
latest Ubuntu or Mailman.


Also, see the FAQ at http://wiki.list.org/x/OIDD.


Here's the perms on those four files:

-rw-rw 1 root list  6725 2012-03-28 19:07 aliases
-rw-rw 1 list list 12288 2012-03-28 19:07 aliases.db
-rw-rw 1 root list  5830 2012-03-28 19:07 virtual-mailman
-rw-r- 1 root list 12288 2012-03-28 19:07 virtual-mailman.db

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in2.1.11

[Steve Matzura]

It would *never* be in my best interest not to give you all the info.
The problem is, I don't know exactly what info you need or want, and
what would be superfluous. Let's see if I can provide more below.
Anything I've omitted, just ask and it shall be yours for the knowing.

On Wed, 28 Mar 2012 12:28:27 -0700, you wrote:

Mark Sapiro wrote:

Steve Matzura wrote:

and
second, the aliases file is not updated, so if a subscriber tries to
send a message to the list, they receive an auto-reply telling them
user unknown in virtual mailbox table. My question is, why doesn't
the web interface create new list feature update the aliases file? Is
this a bug or a feature, or is there something I should put into
mm_cfg.py to enable this, similar to
owners-may-delete-their-own-lists?


If bin/newlist updates the aliases, web create should too, so clearly
this has something to do with the error.

If the list is created and the only problem is that aliases aren't
updated, it could be a permissions issue. Is Mailman's cgi-bin/create
wrapper group 'mailman' and SETGID and does group 'mailman' have write
permission on the aliases?

In case it went by and you didn't see it, here are the perms on those
four files in /var/lib/mailman/data:

-rw-rw 1 root list  6725 2012-03-28 19:07 aliases
-rw-rw 1 list list 12288 2012-03-28 19:07 aliases.db
-rw-rw 1 root list  5830 2012-03-28 19:07 virtual-mailman
-rw-r- 1 root list 12288 2012-03-28 19:07 virtual-mailman.db


Also, the user unknown in virtual mailbox table error indicates the
list domain is a virtual domain. If the issue is that Mailman's
data/aliases is updated, but data/virtual-mailman is not, the problem
is that the email host_name for the list is not in
POSTFIX_STYLE_VIRTUAL_DOMAINS. For a web create, the host_name is
determined by taking the web host from the URL used to go to the
create page and looking it up in the VIRTUAL_HOSTS dictionary

That would be www.theglobalvoice.info with the additional mailman
suffix string, of course. I tried putting add_virtualhost in
mm_cfg.py, but all that did was generate an error saying I'd found a
bug! Obviously that was the wrong thing to do, so I removed it, and
now we're back to the unknown virtual host error on the web create
form.

(basically your add_virtualhost entries) and getting the host name
from there.

But, as Stephen suggests, don't make us guess. Give us all the
information.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in 2.1.11

[Steve Matzura]

On Wed, 28 Mar 2012 12:46:48 -0700, you wrote:

You need to 'chmod 660 /var/lib/mailman/data/virtual-mailman.db' It
must be writable by the 'list group or it can't be updated by the web
server running the create CGI.

I did that and am still receiving the unknown virtual host error when
creating the list from the Web interface.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in2.1.11

[Larry Stone]

On Wed, 28 Mar 2012, Steve Matzura wrote:


It would *never* be in my best interest not to give you all the info.
The problem is, I don't know exactly what info you need or want, and
what would be superfluous. Let's see if I can provide more below.
Anything I've omitted, just ask and it shall be yours for the knowing.


How about the error message you get when you try to create a list via the 
web interface. The one that you assumed we would somehow all know without 
you telling us (having never had an error when creating a list or if I 
did, not in recent years, I haven't the slightest clue what sort of error 
message you might have recieved). It seems rather likely that the error 
you received dealt with alias creation which you seem to want to think of 
as a second unrelated problem.


I'd strongly suggest you start over and provide all relevant information 
in one post so we don't have to go through several messages to find the 
information you've dribbled out to us in multiple messages.


-- Larry Stone
   lston...@stonejongleux.com
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in2.1.11

[Steve Matzura]

On Wed, 28 Mar 2012 16:24:07 -0500 (CDT), you wrote:

On Wed, 28 Mar 2012, Steve Matzura wrote:

 It would *never* be in my best interest not to give you all the info.
 The problem is, I don't know exactly what info you need or want, and
 what would be superfluous. Let's see if I can provide more below.
 Anything I've omitted, just ask and it shall be yours for the knowing.

How about the error message you get when you try to create a list via the 
web interface. The one that you assumed we would somehow all know without 
you telling us (having never had an error when creating a list or if I 
did, not in recent years, I haven't the slightest clue what sort of error 
message you might have recieved). It seems rather likely that the error 
you received dealt with alias creation which you seem to want to think of 
as a second unrelated problem.

Error already reported in a previous message, but here's the Reader's
Digest version. After going through the process of creating a new list
via the Web interface, the error message unknown virtual host is
given, and no mailing list is created.

I'd strongly suggest you start over and provide all relevant information 
in one post so we don't have to go through several messages to find the 
information you've dribbled out to us in multiple messages.

What's relevant? As previously stated, if I knew all the info to
provide, I would have done so in the first place. I've since provided
everything I know about what's going on when I try to create a list.
The real problem here is, I know just enough about Mailman to be
dangerous, so before I get dangerous and break something even further
than it's already broken, I ask questions. If I provide insufficient
information for you to help solve my problem, it's totally and
completely unintentional. The expression I don't know what I don't
know comes to mind.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterfacein2.1.11

[Mark Sapiro]

Steve Matzura wrote:

That would be www.theglobalvoice.info with the additional mailman
suffix string, of course. I tried putting add_virtualhost in
mm_cfg.py, but all that did was generate an error saying I'd found a
bug! Obviously that was the wrong thing to do, so I removed it, and
now we're back to the unknown virtual host error on the web create
form.


OK. If I understand, you attempt to create a list from the web UI and
you get an error Unknown virtual host: www.theglobalvoice.info.

This means two things: 1) the list was not created so, of course, no
aliases were created for it, and 2) the host www.theglobalvoice.info
is not a key in the VIRTUAL_HOSTS dictionary which means there is no
add_virtualhost('www.theglobalvoice.info',
'whatever.the.email.host.is') entry in mm_cfg.py.

So what add_virtualhost() did you put in mm_cfg.py?

What is in Mailman's error log corresponding to the we hit a bug?

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in2.1.11

[Larry Stone]

On Mar 28, 2012, at 4:40 PM, Steve Matzura wrote:

 On Wed, 28 Mar 2012 16:24:07 -0500 (CDT), you wrote:
 
 
 
 
 How about the error message you get when you try to create a list via the 
 web interface. The one that you assumed we would somehow all know without 
 you telling us (having never had an error when creating a list or if I 
 did, not in recent years, I haven't the slightest clue what sort of error 
 message you might have recieved). It seems rather likely that the error 
 you received dealt with alias creation which you seem to want to think of 
 as a second unrelated problem.
 
 Error already reported in a previous message, but here's the Reader's
 Digest version. After going through the process of creating a new list
 via the Web interface, the error message unknown virtual host is
 given, and no mailing list is created.
 

Just to show you how confused this became, I thought unknown virtual host was 
the error being returned to someone trying to post. I do not recall you ever 
saying that was the error the web interface was returning.


-- 
Larry Stone
lston...@stonejongleux.com
http://www.stonejongleux.com/



--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in2.1.11

[Steve Matzura]

I've obviously bunged this up badly. Now here it is, all correct and
properly assigned to each half of the problem:

When creating the list ad...@theglobalvoice.info, unknown virtual
host is the error, but some way, somehow, the list gets partially
created.

If I send a message to that partially created list, Mailman sends back
a message of undeliverability with this error text:

Remote host said: 550 5.1.1 ad...@theglobalvoice.info: Recipient
address rejected: User unknown in virtual mailbox table

I looked in postfix.cf and discovered the virtual host name is really
patronus.theglobalvoice.info, which may have something to do with why
the Web create doesn't work, but 'newlist' does.

On Wed, 28 Mar 2012 18:19:29 -0500, you wrote:


On Mar 28, 2012, at 4:40 PM, Steve Matzura wrote:

 On Wed, 28 Mar 2012 16:24:07 -0500 (CDT), you wrote:
 
 
 
 
 How about the error message you get when you try to create a list via the 
 web interface. The one that you assumed we would somehow all know without 
 you telling us (having never had an error when creating a list or if I 
 did, not in recent years, I haven't the slightest clue what sort of error 
 message you might have recieved). It seems rather likely that the error 
 you received dealt with alias creation which you seem to want to think of 
 as a second unrelated problem.
 
 Error already reported in a previous message, but here's the Reader's
 Digest version. After going through the process of creating a new list
 via the Web interface, the error message unknown virtual host is
 given, and no mailing list is created.
 

Just to show you how confused this became, I thought unknown virtual host 
was the error being returned to someone trying to post. I do not recall you 
ever saying that was the error the web interface was returning.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterfacein2.1.11

[Mark Sapiro]

Steve Matzura wrote:

When creating the list ad...@theglobalvoice.info, unknown virtual
host is the error, but some way, somehow, the list gets partially
created.


How do you know this? Is the list visible in the web UI? In
bin/list_lists?


If I send a message to that partially created list, Mailman sends back
a message of undeliverability with this error text:

Remote host said: 550 5.1.1 ad...@theglobalvoice.info: Recipient
address rejected: User unknown in virtual mailbox table

I looked in postfix.cf and discovered the virtual host name is really
patronus.theglobalvoice.info, which may have something to do with why
the Web create doesn't work, but 'newlist' does.


It may, but I can't say with the information I have. I'd need to see
'postconf -n' but I don't think that's necessary. I think the issue is
the aliases were never created because of the error in the create CGI.

Do you have

add_virtualhost('www.theglobalvoice.info', 'theglobalvoice.info')

or perhaps the equivalent

DEFAULT_URL_HOST = 'www.theglobalvoice.info'
DEFAULT_EMAIL_HOST = 'theglobalvoice.info'

followed by
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

in mm_cfg.py.

Please answer this specific question and also the other specific
questions I asked in my reply at
http://mail.python.org/pipermail/mailman-users/2012-March/073113.html.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in2.1.11

[Mark Sapiro]

Steve Matzura wrote:

I wrote:

How do you know this? Is the list visible in the web UI? In
bin/list_lists?

Neither.


Then the list didn't exist. It was not created, partially or otherwise.


Do you have

add_virtualhost('www.theglobalvoice.info', 'theglobalvoice.info')

or perhaps the equivalent

DEFAULT_URL_HOST = 'www.theglobalvoice.info'
DEFAULT_EMAIL_HOST = 'theglobalvoice.info'

followed by
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

in mm_cfg.py.

The line:

add_virtualhost('www.theglobalvoice.info', 'theglobalvoice.info')

did not exist in mm_cfg.py until now. I added it directly in front of:

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)


OK.


I then saved mm_cfg.py and restarted mailman with `mailmanctl restart'
and attempted to create the mailing list. IT WORKED! It showed up in
all four placess-output from list_lists, as the last stanza in
virtual-mailman, as the last stanza in aliases, and in the Web UI! I
thank you for bearing with me, I apologize for insufficient detailed
error reporting, but with your collective assistance, it's now running
correctly.

What is the purpose of the line I added? Does it point
www.theglobalvoice.info to the real domain of theglobalvoice.info
since that's where all the email list addresses go?


It maps the web host www.theglobalvoice.info to the email domain
theglobalvoice.info.


If that's the
case, why did the Web UI create not work? Does it carry the www
subdomain with it in the underlying commands that actually do the list
creation? If so, then that explains everything to me. If I'm totally
off the mark, then I need to go back to school!


In order to create a list, we must know two fully qualified domains.
The web domain which is the host name that will be used in URLs that
access the list and the email domain which is the domain that list
mail is sent to.

bin/newlist has command line options for specifying these and will fall
back to DEFAULT_*_HOST settings as necessary.

The web create CGI determines these domains by taking the host portion
of the URL that invoked it as the web domain and looking up the
corresponding email domain in the dictionary created by the
add_virtualhost() lines. If it can't find an entry for the web domain
in that dictionary, it can't determine the email domain for the list
so it tells you that the web domain is an unknown virtual host and
doesn't create the list.

It won't use DEFAULT_EMAIL_HOST because that's the email host
associated with DEFAULT_URL_HOST, and you must not be DEFAULT_URL_HOST
because there is *always* a

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

line. Thus, you are coming from some other (virtual) host which is
unknown because it doesn't have an add_virtualhost() line.


[...]
Everything checks out and the new mailing list is operating correctly.


Good.


Did I forget to check or report on anything?


Well, you never answered the questions I asked at
http://mail.python.org/pipermail/mailman-users/2012-March/073113.html
so we don't know what was wrong there, but presumably, you don't care
as you reversed whatever you did and it's working now.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem creating mailing lists via webinterface in2.1.11

[Steve Matzura]

On Wed, 28 Mar 2012 19:37:42 -0700, you wrote:

Did I forget to check or report on anything?


Well, you never answered the questions I asked at
http://mail.python.org/pipermail/mailman-users/2012-March/073113.html
so we don't know what was wrong there, but presumably, you don't care
as you reversed whatever you did and it's working now.

Actually, I didn't reverse anything. You asked:

So what add_virtualhost() did you put in mm_cfg.py?

I actually tried, and backed out, two things before coming for help to
this list, both of which made things worse! I tried
add_virtualhost('www.theglobalvoice.info', 'www.theglobalvoice.info'),
and the same line without the www.. Adding this line gave me the
You hit a bug message in the Web create UI, which is why I backed it
out and set things back the way they'd been.

Regarding:

What is in Mailman's error log corresponding to the we hit a bug?

I don't know because I don't know enough about Mailman to have even
had a chance to look. There's one thing about all of this you don't
know because I haven't mentioned it, and it goes back to when I said I
don't even know what I don't know. While I've been tasked to keeping
theglobalvoice.info running, my only credentials for doing so are that
I'm reasonably good at learning quickly--I am not a *ux system or site
administrator of any stripe. Ask me lots of questions about VAX/Alpha
VMS and I can talk your ear off, as that's what I've spent the last 30
years doing professionally. Show me a *ux system prompt and the first
thing I know to do is man {something}, and if that doesn't solve
whatever is wrong, I start Googling until I find something to at least
try. I'd gotten to that point and figured out it probably had
something to do with add_virtualhost, but not understanding (until
now) exactly what that directive does, I was floundering. Apparently
my predecessor, someone actually far more qualified to do this job
than I, either didn't know about the proper use of add_virtualhost, or
was happy enough with using the command-line `newlist' to create new
mailing lists, because there are eight of them already on the system
running successfully. The site owner told me that she always knew
there was a problem with the Web UI, but the previous techie guy had a
workaround for it--namely, using `newlist' as root. I, being the type
who doesn't like loose ends or unsolved mysteries, stuck my neck out
and said I'd fix it ... and you know the rest.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with password to unsubscribe user from list through mail command

[Mark Sapiro]

On 1/23/2012 9:46 PM, Степанов Роман Владимирович wrote:
 
 I have a problem when I send mail command to unsubscribe user from specified 
 mail list with mail command:
 
  unsubscribe somepass address=some email address
 
  
 
 I have got message from mailman that password was wrong. 
 
 At the same time I can use GUI with the same password. It is strange fail 
 because command works for some addresses works and for some will return an 
 error.


The password in the email unsubscribe command must be the password of
the user being unsubscribed. The list admin password is not acceptable
in this context.

I don't know why it would work for some addresses and not others unless
the password provided for the ones that worked was actually the user's
password or the ones that worked were for lists for which unsubscribe
requires admin approval in which case the password is ignored.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman not working...

[Troy Campbell]

Thanks again.  Observations: Somehow the stale lock was stopping all 
emails from going out
and secondly, /var/lock/mailman is where the lock was.  I'm not sure how 
I happened to figure
that lock location out as it isn't ~mailman/locks.  Perhaps my config is 
non-standard.


Troy
This email was created using 100% recycled organic free range electrons.


On 1/13/2012 4:11 PM, Mark Sapiro wrote:

Troy Campbell wrote:


It appears there was a list that created locks in /var/lock/mailman so I
deleted this list and recreated it
and life seems to be good again...thanks again man for the excellent
support!


I'm glad things are again working well for you, but deleting and
recreating the list was probably overkill. The FAQ at
http://wiki.list.org/x/noA9  gives information about clearing
stale/orphaned locks. I have now added a pointer to this FAQ from
section 7 of the FAQ athttp://wiki.list.org/x/A4E9.



--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman not working...

[Mark Sapiro]

Troy Campbell wrote:

Thanks again.  Observations: Somehow the stale lock was stopping all 
emails from going out
and secondly, /var/lock/mailman is where the lock was.  I'm not sure how 
I happened to figure
that lock location out as it isn't ~mailman/locks.  Perhaps my config is 
non-standard.


Is this a RedHat RPM installation? See http://wiki.list.org/x/KYCB.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman not working...

[Troy Campbell]

It appears there was a list that created locks in /var/lock/mailman so I 
deleted this list and recreated it
and life seems to be good again...thanks again man for the excellent 
support!


Troy
This email was created using 100% recycled organic free range electrons.


On 1/12/2012 8:05 PM, Mark Sapiro wrote:

On 1/12/2012 6:09 PM, Troy Campbell wrote:


It seems to be recognizing the email as local now:

Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015:
to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00,
xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1],
dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878)
Jan 12 18:57:28 request1 postfix/local[1069]: C7FE237878:
to=troyt...@mailman2.rmtc.fedex.com, relay=local, delay=0.23,
delays=0.07/0/0/0.16, dsn=2.0.0, status=sent (delivered to command:
/usr/lib/mailman/mail/mailman post troytest)

No email is coming out though?  It should be expanding to my email
address?


OK. The mail was piped to the wrapper to be posted to the list, so now
it's getting to Mailman.

See the FAQ athttp://wiki.list.org/x/A4E9, particularly sections 2b,
6b, 7, 8, 9 and 13.


--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman not working...

[Mark Sapiro]

Troy Campbell wrote:

It appears there was a list that created locks in /var/lock/mailman so I 
deleted this list and recreated it
and life seems to be good again...thanks again man for the excellent 
support!


I'm glad things are again working well for you, but deleting and
recreating the list was probably overkill. The FAQ at
http://wiki.list.org/x/noA9 gives information about clearing
stale/orphaned locks. I have now added a pointer to this FAQ from
section 7 of the FAQ at http://wiki.list.org/x/A4E9.


-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman not working...

[Mark Sapiro]

Troy Campbell wrote:

For some reason Mailman just stopped working and I must confess that I 
have forgot how to debug since it
has run so well for the last couple of years...it appears
that when a Mailman email is sent to the Mailman server it that it 
doesn't recognize it as local but instead tries to
relay out and then the relay sends it back and this happens multilple 
times if I'm reading the logs right so I assume
that the aliases file for the Mailman lists isn't being recognized 
properly by Postfix?


Yes, it sounds like a Postfix issue, but in order to say anything, we'd
need to see postconf -n and some relevant Postfix log messages.


Here is some info (yes, I know it's ancient):

rpm -qa | grep -i mailman
mailman-2.1.9-4.el5

/etc/postfix/main.cf:
alias_maps =hash:/etc/aliases
 hash:/etc/mailman/aliases

and in /etc/mailman/aliases it has the list troytest with this:
# STANZA START: troytest
# CREATED: Sun Mar 14 19:20:17 2010
troytest: |/usr/lib/mailman/mail/mailman post troytest
troytest-admin:   |/usr/lib/mailman/mail/mailman admin troytest
troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest
troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest
troytest-join:|/usr/lib/mailman/mail/mailman join troytest
troytest-leave:   |/usr/lib/mailman/mail/mailman leave troytest
troytest-owner:   |/usr/lib/mailman/mail/mailman owner troytest
troytest-request: |/usr/lib/mailman/mail/mailman request troytest
troytest-subscribe:   |/usr/lib/mailman/mail/mailman subscribe troytest
troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest
# STANZA END: troytest

There is also a python process owned by mailman that is varying between 
75-100% of the CPU.


Which one? (ps -fw)


I realize that Postfix per se is out of the scope of this list but any 
suggestions/tips are sincerely appreciated.
My current thinking is I need to run a postmap command to update the 
aliases config perhaps?


The command is postalias, not postmap, and it's unlikely to help unless
perhaps you previously ran 'postmap /etc/mailman/aliases', but it
couldn't hurt to run 'postalias /etc/mailman/aliases'.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman not working...

[Troy Campbell]

Thanks so much Mark...see inline replies below

Troy
This email was created using 100% recycled organic free range electrons.


On 1/12/2012 5:48 PM, Mark Sapiro wrote:

Troy Campbell wrote:


For some reason Mailman just stopped working and I must confess that I
have forgot how to debug since it
has run so well for the last couple of years...it appears
that when a Mailman email is sent to the Mailman server it that it
doesn't recognize it as local but instead tries to
relay out and then the relay sends it back and this happens multilple
times if I'm reading the logs right so I assume
that the aliases file for the Mailman lists isn't being recognized
properly by Postfix?


Yes, it sounds like a Postfix issue, but in order to say anything, we'd
need to see postconf -n and some relevant Postfix log messages.

# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliaseshash:/etc/mailman/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
html_directory = no
inet_interfaces = all
local_recipient_maps =
mail_owner = postfix
mailbox_size_limit = 0
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
mydestination = $myhostname
localhost.$mydomainlocalhost
localhost.localdomainrequest1.localdomain
request2.localdomain
request1.rmtc.fedex.com
request2.rmtc.fedex.com
mailman.rmtc.fedex.commailman2.rmtc.fedex.com
mynetworks = 127.0.0.1/32146.18.0.0/16
155.161.0.0/16161.135.0.0/16
165.150.0.0/16170.5.0.0/16
170.86.0.0/16172.18.64.0/18
192.189.184.0/22198.140.0.0/22
199.81.0.0/16199.82.0.0/16
204.135.100.0/23204.135.106.0/23
204.135.108.0/23204.135.92.0/23
204.135.94.0/23204.135.96.0/23
204.135.97.0/23172.31.248.0/23
172.31.252.0/23

newaliases_path = /usr/bin/newaliases.postfix
owner_request_special = no
permit_mx_backup_networks = $mynetworks
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES
recipient_delimiter = +
relay_domains = cosd.fedex.comrmtc.fedex.com
relayhost = mapper.mail.fedex.com
sample_directory = /usr/share/doc/postfix-2.3.3/samples
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smtpd_authorized_verp_clients = localhost
smtpd_recipient_restrictions = check_recipient_access 
hash:/etc/postfix/accesspermit_mynetworks
reject_unauth_destination

transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 550




Here is some info (yes, I know it's ancient):

rpm -qa | grep -i mailman
mailman-2.1.9-4.el5

/etc/postfix/main.cf:
alias_maps =hash:/etc/aliases
 hash:/etc/mailman/aliases

and in /etc/mailman/aliases it has the list troytest with this:
# STANZA START: troytest
# CREATED: Sun Mar 14 19:20:17 2010
troytest: |/usr/lib/mailman/mail/mailman post troytest
troytest-admin:   |/usr/lib/mailman/mail/mailman admin troytest
troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest
troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest
troytest-join:|/usr/lib/mailman/mail/mailman join troytest
troytest-leave:   |/usr/lib/mailman/mail/mailman leave troytest
troytest-owner:   |/usr/lib/mailman/mail/mailman owner troytest
troytest-request: |/usr/lib/mailman/mail/mailman request troytest
troytest-subscribe:   |/usr/lib/mailman/mail/mailman subscribe troytest
troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe

troytest

# STANZA END: troytest

There is also a python process owned by mailman that is varying between
75-100% of the CPU.


Which one? (ps -fw)
mailman  21869 21862 92 16:16 ?02:24:52 /usr/bin/python 
/usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s




I realize that Postfix per se is out of the scope of this list but any
suggestions/tips are sincerely appreciated.
My current thinking is I need to run a postmap command to update the
aliases config perhaps?


The command is postalias, not postmap, and it's unlikely to help unless
perhaps you previously ran 'postmap /etc/mailman/aliases', but it
couldn't hurt to run 'postalias /etc/mailman/aliases'.

It seems to be recognizing the email as local now:

Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: 
to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, 
xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], 
dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878)
Jan 12 18:57:28 request1 

Re: [Mailman-Users] problem with mailman not working...

[Mark Sapiro]

On 1/12/2012 6:09 PM, Troy Campbell wrote:

 It seems to be recognizing the email as local now:
 
 Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015:
 to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00,
 xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1],
 dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878)
 Jan 12 18:57:28 request1 postfix/local[1069]: C7FE237878:
 to=troyt...@mailman2.rmtc.fedex.com, relay=local, delay=0.23,
 delays=0.07/0/0/0.16, dsn=2.0.0, status=sent (delivered to command:
 /usr/lib/mailman/mail/mailman post troytest)
 
 No email is coming out though?  It should be expanding to my email
 address?


OK. The mail was piped to the wrapper to be posted to the list, so now
it's getting to Mailman.

See the FAQ at http://wiki.list.org/x/A4E9, particularly sections 2b,
6b, 7, 8, 9 and 13.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Blackberry

[Mark Sapiro]

Jeff Basham wrote:

I have a subscriber who is on multiple lists that I run.  He gets email on
his Blackberry, and one list is completely fine ... the other list he can't
see the body of the email, only the header.  The only difference with the
2nd list is that it has a header configured in the admin interface.  I
removed the header, and he saw the message without the header just fine,
but leaving it off permanently is not an option.
[...]
Any ideas on what to try next?  I am thinking that the blackberry mail
software is seeing the header as a 'signature' and not displaying anything
below it, but I might be way off-base.  I don't have a blackberry, and
never have had one, so I am a little blind on that end.


The header is added as a separate MIME part because the original
message is already multipart or doesn't consist of a single text/plain
message body.

The Blackberry sees the initial header text/plain part as the message
body and everything else as either attachments or things to be
ignored. This has nothing to do with the content of msg_header, just
the fact that there is one.

See the FAQ at http://wiki.list.org/x/84A9 for more information.

In your user's case, this is basically a problem with the Blackberry
mail client. It is not unique to Blackberry, many smart phone mail
clients fail miserably at displaying messages with any sort of complex
MIME structure.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem sending multiple listserv commands via email

[Christine Cubillo]

Thanks for responding.  Sorry, I pasted the usage message from one of
my unsubscribe tests.  Here are the results I get when i attempt to
subscribe multiple email addresses.  The first subscribe command is
always processed and the remaining subscribe commands are left
unprocessed.  Is there a way I can get all commands in my email to be
processed?


The results of your email command are provided below. Attached is your
original message.

- Results:
You are already subscribed!

- Unprocessed:
subscribe MyPassword nodigest address=addre...@somewhere.net
subscribe MyPassword nodigest address=addre...@somewhere.net
subscribe MyPassword nodigest address=addre...@somewhere.net
subscribe MyPassword nodigest address=addre...@somewhere.net
subscribe MyPassword nodigest address=addre...@somewhere.net
subscribe MyPassword nodigest address=addre...@somewhere.net
subscribe MyPassword nodigest address=addre...@somewhere.net


- Done.

On Tue, Nov 1, 2011 at 8:33 AM, Mark Sapiro m...@msapiro.net wrote:
 Christine Cubillo wrote:

***Response Received:



- Results:
    Usage:

    unsubscribe [password] [address=address]
        Unsubscribe from the mailing list.  If given, your password must match
        your current password.  If omitted, a confirmation email will be sent
        to the unsubscribing address. If you wish to unsubscribe an address
        other than the address you sent this request from, you may specify
        `address=address' (no brackets around the email address, and no
        quotes!)


- Unprocessed:
subscribe MyPassword nodigest address=ema...@someaddress.com
subscribe MyPassword nodigest address=ema...@someaddress.com

- Done.


 The second and subsequent commands are not processed because the first
 command results in an error. That's why you see a Usage: message.

 It appears that something has been broken in your Mailman installation
 as the subscribe commands appear to be invoking the cmd_unsubscribe
 module rather than the cmd_subscribe module.

 --
 Mark Sapiro m...@msapiro.net        The highway is for gamblers,
 San Francisco Bay Area, California    better use your sense - B. Dylan


--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem sending multiple listserv commands via email

[Mark Sapiro]

Christine Cubillo wrote:

Thanks for responding.  Sorry, I pasted the usage message from one of
my unsubscribe tests.  Here are the results I get when i attempt to
subscribe multiple email addresses.  The first subscribe command is
always processed and the remaining subscribe commands are left
unprocessed.  Is there a way I can get all commands in my email to be
processed?


You can include multiple commands in one email, but the first command
which is unrecognized, fails or results in an error terminates
processing.

In the case below, the first command attempted to subscribe an address
which is already a member so it failed and the remaining commands were
unprocessed.

All commands will be processed if and only if they are all valid and
all succeed.


The results of your email command are provided below. Attached is your
original message.

- Results:
You are already subscribed!

- Unprocessed:
subscribe MyPassword nodigest address=3daddre...@somewhere.net
subscribe MyPassword nodigest address=3daddre...@somewhere.net
subscribe MyPassword nodigest address=3daddre...@somewhere.net
subscribe MyPassword nodigest address=3daddre...@somewhere.net
subscribe MyPassword nodigest address=3daddre...@somewhere.net
subscribe MyPassword nodigest address=3daddre...@somewhere.net
subscribe MyPassword nodigest address=3daddre...@somewhere.net

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem sending multiple listserv commands via email

[Carl Zwanzig]

On 11/1/2011 12:29 PM, Mark Sapiro wrote:


In the case below, the first command attempted to subscribe an address
which is already a member so it failed and the remaining commands were
unprocessed.


Why is that an error?  I would expect it to ignored, just like setting a 
property to it's current value.


z!
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem sending multiple listserv commands viaemail

[Mark Sapiro]

Carl Zwanzig wrote:

 In the case below, the first command attempted to subscribe an address
 which is already a member so it failed and the remaining commands were
 unprocessed.

Why is that an error?  I would expect it to ignored, just like setting a 
property to it's current value.


Because Mailman/commands/cmd_subscribe.py distinguishes it from success
and calls it fatal. Granted, an argument could be made that it
shouldn't be fatal and similarly that unsubscribe of a non-member
address shouldn't be fatal either, but it isn't completely obvious
that that should be the case.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem sending multiple listserv commands viaemail

[Richard Damon]

On 11/1/11 4:55 PM, Mark Sapiro wrote:

Carl Zwanzig wrote:

In the case below, the first command attempted to subscribe an address
which is already a member so it failed and the remaining commands were
unprocessed.

Why is that an error?  I would expect it to ignored, just like setting a
property to it's current value.


Because Mailman/commands/cmd_subscribe.py distinguishes it from success
and calls it fatal. Granted, an argument could be made that it
shouldn't be fatal and similarly that unsubscribe of a non-member
address shouldn't be fatal either, but it isn't completely obvious
that that should be the case.

One issue I see with this behavior, is that this breaks the privacy that 
mailman gives to lists. The web interface is very careful to NOT let you 
know if a given address is subscribed or not (unless the list publishes 
its subscriber list). This gives a method that you can get a message to 
one email address indicating that another, unrelated, email address is 
subscribed to the list.


--
Richard Damon

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with Mailman on Mac OS X Snow Leopard client

[Larry Stone]

On Mon, 10 Oct 2011, Graham Young wrote:

Mail generated by Mailman hangs in my dedicated, on-board MTA's queue 
unless I remove a certain bit of custom Postfix configuration that I 
entered following instructions kindly posted here by one Larry Stone.


I guess I'm best to answer this.


The bit of custom Postfix configuration that I've experimented with 
removing is exactly as follows: hash:/etc/postfix/aliases


The context in which this bit is supposed to appear is as follows:
alias_maps = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases.

I just remove the bit, leaving: alias_maps = 
hash:/usr/local/mailman/data/aliases. Again, with just this as remnant 
of my custom Postscript configuration, Mailman-generated mail gets sent.


alias_maps is this list of aliases, local addresses which do not get 
delivered locally but rather get sent elsewhere. That could be another 
address (for instance, on my system, postmaster is an alias for me so I 
get all postmaster mail) or for Mailman, a pipe to the Mailman mail input 
script.


The error message that Postfix repeatedly issues when I don't have the 
suspect portion of this bit of custom Postscript configuration removed 
is as follows:
Oct 10 21:10:05 email postfix/local[75578]: fatal: open database 
/etc/postfix/aliases.db: No such file or directory


It means exactly what it says. /etc/postfix/aliases.db does not exist.

Finally, inasmuch as it may be relevant, I next post feedback that I get 
from a certain postconf command, specifically postconf alias_maps: 
alias_maps = hash:/etc/aliases


That should be the outpust of postconf -d alias_maps. -d means the 
default value. On my system (and I have never touched this part), 
/etc/aliases is a softlink to /etc/postfix/aliases (in other words, just a 
pointer to that file).


So the real is why does /etc/postfix/aliases.db not exist. It's not really 
required and it isn't part of Mailman. I had assumed it was past of the 
standard Postfix installation on OS X client but perhaps not (or maybe it 
was and no longer is but I didn't realize that because I've been upgrading 
or moving all the way from 10.3.


(a digression as to how aliases.db is created. aliases is a text file in a 
prescribed format. To turn it into the hash table Postfix wants to use, 
it's run through postmap. postmap hash:aliases created aliases.db)


The purpose of that customization is to append Mailman's alias file to the 
existing alias file.


If you don't have /etc/postfix/aliases.db, then don't include it in 
alias_maps. It's that simple. If you have a different aliases file, use 
that in place of /etc/postfix/aliases in alias_maps.


The best way to do this is to look in your Postfix main.cf for an earlier 
definition of alias_maps. So if you find

alias_maps = hash:foo, then replace my instructions with
alias_maps = hash:foo,
  hash:/usr/local/mailman/data/aliases

If there is no prior definition of alias_maps in main.cf, then do
postconf -d alias_maps and then:
alias_maps = (whatever postconf -d alias_maps returned),
  hash:/usr/local/mailman/data/aliases

However, please note that my instructions assume and expect familiarity 
with Postfix. If you don't understand Postfix, you will almost certainly 
have other problems in the future.


-- Larry Stone
   lston...@stonejongleux.com
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Mailman+Postfix

[Mark Sapiro]

On 7/22/2011 4:32 AM, gigahe...@fettabernett.de wrote:
 Hi there.
 I´m using Postfix + Dovevot + Mailman on Debian Lenny with ISPConfig3
 Setup.
 I´ve installed Mailman seperate from ISPConfig via apt-get,
 administrating lists works fine but there is one problem: Postfix does
 not accept incoming mails to the mailing list.
 
 mail.info:
 Jul 22 10:53:13 atom-29 postfix/smtpd[12620]: NOQUEUE: reject: RCPT from
 mailout-de.gmx.net[213.165.64.22]: 550 5.1.1 t...@xyz.net: Recipient
 address rejected: User unknown in virtual mailbox table;
 from=a...@gmx.de to=t...@xyz.net proto=SMTP helo=mailout-de.gmx.net
 
 main.cf of Postfix:
[...]
 alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
 alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
[...]
 virtual_alias_domains =
 virtual_alias_maps =
 proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf,
 mysql:/etc/postfix/mysql-virtual_email2email.cf
 virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf
 virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf
[...]
 
 What am I doing wrong?


'postconf -n' is generally more useful than main.cf.

It appears the problem is that your list domain is a virtual mailbox
domain, but you have no virtual mapping for the list addresses.

If that is indeed the problem, you need to add
hash:/var/lib/mailman/data/virtual-mailman to virtual_alias_maps in
main.cf. You also need to put your list domaian (xyz.net) in
POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py as in

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['xyz.net']

and run Mailman's bin/genaliases to generate virtual-mailman.

Also, you should not have hash:/var/lib/mailman/data/aliases because it
will cause Postfix's newaliases command to rebuild
hash:/var/lib/mailman/data/aliases.db which may adversely affect the
owner:group of this file.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman handling incomming mail

[Maxime Longuepee]

Mark Sapiro a écrit :

On 6/2/11 8:13 AM, Maxime Longuepee wrote:
  

Here is the output of postconf -n:



[...]
  

virtual_alias_maps =
mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/aliases




This is wrong. You need to add hash:/usr/local/mailman/data/aliases to
alias_maps, not to virtual_alias_maps. Probably something like

alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases

Then you need

virtual_alias_maps =
mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/virtual-mailman

and if it isn't already there, you need

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org']

in mm_cfg.py, and if that wasn't already there, you need to run
Mailman's bin/genaliases to create the virtual-mailman* files.

  

Hi Mark,

Thanks a lot, it's working perfectly!!!

Now, if I want to add a mailing list with another domain name i own 
(it's hosted on the same machine), what should i do? I tryed to add a 
new mailing list specifying the domain name with


/usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org

I can access the administration page over the web interface but when i 
send an email to that address, i get an error (here is the postfix log):


postfix/smtpd[94206]: NOQUEUE: reject: RCPT from myhome.org[MY.IP]: 550 
5.1.1 name-of-the-list  @myotherdomain.org: Recipient address 
rejected: User unknown in virtual mailbox table; from=m...@email.com 
to=name-of-the-list??@myotherdomain.org proto=ESMTP helo=[MY.IP]


Thanks a lot in advance for helping me!

-- Maxime Longuepee
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman handling incomming mail

[Mark Sapiro]

On 6/4/11 6:30 AM, Maxime Longuepee wrote:
 
 Now, if I want to add a mailing list with another domain name i own
 (it's hosted on the same machine), what should i do? I tryed to add a
 new mailing list specifying the domain name with
 
 /usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org
 
 I can access the administration page over the web interface but when i
 send an email to that address, i get an error (here is the postfix log):
 
 postfix/smtpd[94206]: NOQUEUE: reject: RCPT from myhome.org[MY.IP]: 550
 5.1.1 name-of-the-list  @myotherdomain.org: Recipient address
 rejected: User unknown in virtual mailbox table; from=m...@email.com
 to=name-of-the-list??@myotherdomain.org proto=ESMTP helo=[MY.IP]


You need to add

add_virtualhost('myotherdomain.org', 'myotherdomain.org')

to mm_cfg.py and add the domain to POSTFIX_STYLE_VIRTUAL_DOMAINS as in

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org', 'myotherdomain.org']

This assumes the web domain is the same myotherdomain.org as the email
domain. If not, the only difference is add_virtualhost is

add_virtualhost('myotherwebdomain.org', 'myotherdomain.org')

After adding 'myotherdomain.org' to POSTFIX_STYLE_VIRTUAL_DOMAINS, run
bin/genaliases to update data/virtual-mailman*

Also not that the notation

/usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org

is deprecated and doesn't do the intuitive thing (but does the right
thing if the web domain and email domain are the same). See

/usr/local/mailman/bin/newlist --help

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, CaliforniaBetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman handling incomming mail

[Maxime Longuepee]

Mark Sapiro a écrit :

On 6/4/11 6:30 AM, Maxime Longuepee wrote:
  

Now, if I want to add a mailing list with another domain name i own
(it's hosted on the same machine), what should i do? I tryed to add a
new mailing list specifying the domain name with

/usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org

I can access the administration page over the web interface but when i
send an email to that address, i get an error (here is the postfix log):

postfix/smtpd[94206]: NOQUEUE: reject: RCPT from myhome.org[MY.IP]: 550
5.1.1 name-of-the-list  @myotherdomain.org: Recipient address
rejected: User unknown in virtual mailbox table; from=m...@email.com
to=name-of-the-list??@myotherdomain.org proto=ESMTP helo=[MY.IP]




You need to add

add_virtualhost('myotherdomain.org', 'myotherdomain.org')

to mm_cfg.py and add the domain to POSTFIX_STYLE_VIRTUAL_DOMAINS as in

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org', 'myotherdomain.org']

This assumes the web domain is the same myotherdomain.org as the email
domain. If not, the only difference is add_virtualhost is

add_virtualhost('myotherwebdomain.org', 'myotherdomain.org')

After adding 'myotherdomain.org' to POSTFIX_STYLE_VIRTUAL_DOMAINS, run
bin/genaliases to update data/virtual-mailman*

Also not that the notation

/usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org

is deprecated and doesn't do the intuitive thing (but does the right
thing if the web domain and email domain are the same). See

/usr/local/mailman/bin/newlist --help

  

Hi Mark!

I tryed what you said and it's not working.. I have this error:

postfix/smtpd[99110]: NOQUEUE: reject: RCPT from myhome.org[MY.HOME.IP]: 
550 5.1.1 test-l...@myotherdomain.org: Recipient address rejected: 
User unknown in virtual mailbox table; from=m...@email.com 
to=test-l...@myotherdomain.org proto=ESMTP helo=[MY.HOME.IP]


Mailman was originally configured with mydomain.org which still works 
well. The web domain i use to manage mailman is webmail.mydomain.org. 
The other domain i'm trying to add is myotherdomain.org and following 
your advices it didn't worked.


So, I did that in mm_cfg.py:

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org', 'myotherdomain.org']
add_virtualhost('myotherdomain.org')

Then, I ran genaliases and also restarted mailman. I added the list 
test-list for myotherdomain.org with: /usr/local/mailman/bin/newlist 
--urlhost=webmail.mydomain.org --emailhost=myotherdomain.org test-list


and it doesn't work :|

What did I do wrong?
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman handling incomming mail

[Mark Sapiro]

Maxime Longuepee wrote:

I tryed what you said and it's not working.. I have this error:

postfix/smtpd[99110]: NOQUEUE: reject: RCPT from myhome.org[MY.HOME.IP]: 
550 5.1.1 test-l...@myotherdomain.org: Recipient address rejected: 
User unknown in virtual mailbox table; from=m...@email.com 
to=test-l...@myotherdomain.org proto=ESMTP helo=[MY.HOME.IP]

Mailman was originally configured with mydomain.org which still works 
well. The web domain i use to manage mailman is webmail.mydomain.org. 
The other domain i'm trying to add is myotherdomain.org and following 
your advices it didn't worked.

So, I did that in mm_cfg.py:

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org', 'myotherdomain.org']
add_virtualhost('myotherdomain.org')

Then, I ran genaliases and also restarted mailman. I added the list 
test-list for myotherdomain.org with: /usr/local/mailman/bin/newlist 
--urlhost=webmail.mydomain.org --emailhost=myotherdomain.org test-list


If you want all lists to use the same web host (webmail.mydomain.org)
and only different email domains, you do not want an add_virtualhost()
for the other domains.

You want

DEFAULT_URL_HOST = 'webmail.mydomain.org'
DEFAULT_EMAIL_HOST = 'mail.mydomain.org'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org',
'myotherdomain.org']

However, the

add_virtualhost('myotherdomain.org')

doesn't really do any harm. So I don't understand what the problem is.
The newlist command you gave should have created the list with a
host_name attribute (visible on the list's General Options page) of
myotherdomain.org, and if that domain was in
POSTFIX_STYLE_VIRTUAL_DOMAINS when the list was created, the required
virtual maps should have been added to data/virtual-mailman.

So, what is the host_name for test-list?

Does it match exactly a domain in POSTFIX_STYLE_VIRTUAL_DOMAINS in
mm_cfg.py?

Is there only one POSTFIX_STYLE_VIRTUAL_DOMAINS assignment in mm_cfg.py?

What's in data/virtual-mailman?

is the time stamp of data/virtual-mailman.db the same or more recent
than that of data/virtual-mailman?

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with max_num_recipients

[Mark Sapiro]

On 6/3/2011 10:45 AM, Glenn Sieb wrote:
 
 I have a list where, as a rule, we don't allow CCs to other
 people/lists. So we set max_num_recipients to 2.
[...]
 Now, my question would be.. *why* would a *blank* CC: line trip this
 flag? It just strikes me as kind of odd.


We get the values of the To: and Cc: headers. In this case that returns
the list ['listn...@lists.mysite.tld', ''], i.e.,
'listn...@lists.mysite.tld' from the To: header and '' from the CC:
header. We parse that with Python's email.Utils.getaddresses() function
which returns a list of (real name, address) tuples, in this case [('',
'listn...@lists.mysite.tld'), ('', '')]. The length of this list is two,
so we think the message has two recipients. We don't notice that one of
the addresses is null.

If you consider this to be a bug, you can report it at
https://bugs.launchpad.net/mailman/+filebug, and I'll fix it.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman handling incomming mail

[Mark Sapiro]

On 6/1/11 6:50 AM, Maxime Longuepee wrote:
 
   The mail system
 
 |/usr/local/mailman/mail/mailman post mailman@mail.mydomain.org
 (expanded
from mail...@mail.mydomain.org): unknown user:
|/usr/local/mailman/mail/mailman post mailman*


Postfix is apparently trying to deliver to the alias via a transport
that doesn't do pipe delivery, i.e. some transport other than 'local'.

We need to see the output from 'postconf -n' to say more.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, CaliforniaBetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman handling incomming mail

[Maxime Longuepee]

Hi Mark!

Thanks for your reply!

Here is the output of postconf -n:

address_verify_map = btree:/var/spool/postfix/address_verify
broken_sasl_auth_clients = yes
command_directory = /usr/local/sbin
config_directory = /usr/local/etc/postfix
daemon_directory = /usr/local/libexec/postfix
data_directory = /var/spool/postfix
debug_peer_level = 2
disable_vrfy_command = yes
html_directory = no
inet_interfaces = $myhostname, localhost
invalid_hostname_reject_code = 450
mail_owner = postfix
mailq_path = /usr/local/bin/mailq
manpage_directory = /usr/local/man
maps_rbl_reject_code = 450
mydestination = mail.mydomain.org, localhost.mydomain.org, localhost, mail
myhostname = mail.mydomain.org
mynetworks = 127.0.0.1, mail.mydomain.org
mynetworks_style = host
myorigin = mail.mydomain.org
newaliases_path = /usr/local/bin/newaliases
non_fqdn_reject_code = 450
owner_request_special = no
queue_directory = /var/spool/postfix
readme_directory = no
recipient_delimiter = +
sample_directory = /usr/local/etc/postfix
sendmail_path = /usr/sbin/sendmail
setgid_group = maildrop
smtp_tls_cert_file = /etc/ssl/server.crt
smtp_tls_key_file = /etc/ssl/server.key
smtp_tls_security_level = may
smtp_tls_session_cache_database =
btree:/var/spool/postfix/smtp_tls_session_cache
smtpd_data_restrictions = reject_unauth_pipelining,
reject_multi_recipient_bounce,permit
smtpd_helo_required = yes
smtpd_recipient_restrictions = permit_mynetworks   
permit_sasl_authenticatedpermit_tls_clientcerts   
reject_unauth_destinationreject_invalid_helo_hostname   
reject_non_fqdn_senderreject_non_fqdn_recipient   
reject_rbl_client cbl.abuseat.orgreject_rbl_client list.dsbl.org   
reject_rbl_client opm.blitzed.orgreject_rbl_client
sbl.spamhaus.orgreject_rbl_client bl.spamcop.net   
reject_rbl_client dnsbl.sorbs.net=127.0.0.2reject_rbl_client
dnsbl.sorbs.net=127.0.0.3reject_rbl_client
dnsbl.sorbs.net=127.0.0.4reject_rbl_client
dnsbl.sorbs.net=127.0.0.5reject_rbl_client
dnsbl.sorbs.net=127.0.0.7reject_rbl_client
dnsbl.sorbs.net=127.0.0.9reject_rbl_client
dnsbl.sorbs.net=127.0.0.11reject_rbl_client
dnsbl.sorbs.net=127.0.0.12
smtpd_sasl_auth_enable = yes
smtpd_sasl_path = private/auth
smtpd_sasl_security_options = noanonymous
smtpd_sasl_type = dovecot
smtpd_tls_ask_ccert = yes
smtpd_tls_cert_file = /etc/ssl/server.crt
smtpd_tls_key_file = /etc/ssl/server.key
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_security_level = may
smtpd_tls_session_cache_database =
btree:/var/spool/postfix/smtpd_tls_session_cache
tls_random_source = dev:/dev/urandom
unknown_local_recipient_reject_code = 550
virtual_alias_maps =
mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/aliases
virtual_gid_maps = static:6
virtual_mailbox_base = /usr/vmail
virtual_mailbox_domains =
mysql:$config_directory/mysql_virtual_domains_maps.cf
virtual_mailbox_maps =
mysql:$config_directory/mysql_virtual_mailbox_maps.cf
virtual_minimum_uid = 143
virtual_transport = dovecot
virtual_uid_maps = static:143

On Thu, 02 Jun 2011 07:40:43 -0700, Mark Sapiro m...@msapiro.net wrote:
 On 6/1/11 6:50 AM, Maxime Longuepee wrote:

   The mail system

 |/usr/local/mailman/mail/mailman post mailman@mail.mydomain.org
 (expanded
from mail...@mail.mydomain.org): unknown user:
|/usr/local/mailman/mail/mailman post mailman*
 
 
 Postfix is apparently trying to deliver to the alias via a transport
 that doesn't do pipe delivery, i.e. some transport other than 'local'.
 
 We need to see the output from 'postconf -n' to say more.
 
 --
 Mark Sapiro m...@msapiro.netThe highway is for gamblers,
 San Francisco Bay Area, CaliforniaBetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with mailman handling incomming mail

[Mark Sapiro]

On 6/2/11 8:13 AM, Maxime Longuepee wrote:
 
 Here is the output of postconf -n:
 
[...]
 virtual_alias_maps =
 mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/aliases


This is wrong. You need to add hash:/usr/local/mailman/data/aliases to
alias_maps, not to virtual_alias_maps. Probably something like

alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases

Then you need

virtual_alias_maps =
mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/virtual-mailman

and if it isn't already there, you need

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org']

in mm_cfg.py, and if that wasn't already there, you need to run
Mailman's bin/genaliases to create the virtual-mailman* files.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, CaliforniaBetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with delivery

[Ralf Hildebrandt]

* Larry Prevo llpr...@gmail.com:
 I got a email this morning telling me.   I was going to be disable because of 
 bad mail delivery
 I don't know what address fail can you tell me
 la...@prevo.net   my mail list kofc4090.org

Please show the exact mail you received.

Also note that I already answered to your question yesterday. Was
there anything unclear about my answer?

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12203 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  ralf.hildebra...@charite.de | http://www.charite.de

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with delivery

[Mark Sapiro]

Larry Prevo wrote:

I got a email this morning telling me.   I was going to be disable because of 
bad mail delivery
I don't know what address fail can you tell me
la...@prevo.net   my mail list kofc4090.org


The bouncing address is in the To: header of the notice you received.

When I replied to the message you sent yesterday to
mailman-users-owner, I was under the impression that the bounce you
received was from the mailman-users@python.org list. If it was some
other, non-python.org list, you'll need to follow up with the admins
of that server/list to get more information than is in the disable
notification.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with bounce_matching_headers

[Mark Sapiro]

Barry Finkel wrote

I added a line to bounce_matching_headers

  Subject: .remove.


I don't know why this didn't work unless it contains trailing
whitespace (leading whitespace is removed before matching). However,
if you are trying to match the 'word' remove, I would use

   Subject: \Wremove\W

See http://docs.python.org/library/re.html#regular-expression-syntax

Note that bounce_matching_headers (and header_filter_rules) are matched
case insensitively.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with bounce_matching_headers

[Richard Damon]

On 4/14/11 3:12 PM, Barry Finkel wrote:

I am running 2.1.14, and we had a problem where a list owner
subscribed a number of persons to a list, and many of these
persons want to be unsubscribed.  To catch mail directed
toward the list:

 Subject: Please remove me from your list

I added a line to bounce_matching_headers

 Subject: .remove.

(I placed it at the end of the Mailman-supplied lines),
and the next mail with that subject line was sent to the
list moderators.  Another mail message arrived:

 Subject: Again... Please remove me from this list

but this one was not diverted to the moderators.  What is
wrong with my bounce_matching_headers line?  Thanks.


Doesn't . only match a single character? I use filters more like

Subject: .*remove.*

so the .* matches any number of characters between the Subject header 
and the word.
This filter likely will have false positives, you may want something 
more like


Subject: .*remove.*list.*

--
Richard Damon

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with bounce_matching_headers

[Mark Sapiro]

Richard Damon wrote:

Doesn't . only match a single character? I use filters more like

Subject: .*remove.*

so the .* matches any number of characters between the Subject header 
and the word.

bounce_matching_headers is different from header_filter_rules. For
header_filter_rules, you might want something like

 ^Subject:.*remove

because the search is against all of the message's headers.

For bounce_matching_headers,

  Subject: .remove.

says search the subject header value for the pattern '.remove.' which
ought to succeed unless 'remove is at the very beginning or end of the
header.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem e.g. with subscription of new members

[Mark Sapiro]

Werner Spirk wrote:

I have installed mailman-2.1.14 on NFS.
We use NFS as the common platform between mailman server and
WWW server.

The problem is that it could happen that
the subscription of new members ether via the add-members cmd
or via the WWW surface as an admin did not do:
the members have got welcome messages, there are log entries
in the subscribe log but the members aren't in the list
(no changes/mail addresses in the pck-file).

If you repeat the subscription directly after the first trail
it will normally do.

There were no activities on the mailman server at that times.


There is an issue that can cause this behavior, but it only occurs if
two parallel processes, e.g. the member add and another member add or
a post to the same list, occur within the same second.


In the locks log there can be an entry - not always
when  subsrcriptions fails:
list.lock lifetime has expired, breaking
But there are no lock/unlock entries.


You can get more information including lock/unlock entries in the locks
log by putting

LIST_LOCK_DEBUGGING = On

in mm_cfg.py and restarting Mailman.

Is there anything in Mailman's error log?

I have attached a patch (list_reload.patch.txt) that addresses the
issue I mention above. It may help, but I suspect some kind of NFS
delays are involved. Try setting LIST_LOCK_DEBUGGING = On and report
what's in the locks log.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

=== modified file 'Mailman/MailList.py'
--- Mailman/MailList.py 2008-08-21 21:35:20 +
+++ Mailman/MailList.py 2008-08-22 22:16:29 +
@@ -599,8 +599,11 @@
 # file doesn't exist, we'll get an EnvironmentError with errno set
 # to ENOENT (EnvironmentError is the base class of IOError and
 # OSError).
+# We test strictly less than here because the resolution is whole
+# seconds and we have seen cases of the file being updated by
+# another process in the same second.
 mtime = os.path.getmtime(dbfile)
-if mtime = self.__timestamp:
+if mtime  self.__timestamp:
 # File is not newer
 return None, None
 fp = open(dbfile)
@@ -618,8 +621,9 @@
 return None, e
 finally:
 fp.close()
-# Update timestamp
-self.__timestamp = mtime
+# Update the timestamp.  We use current time here rather than mtime
+# so the test above might succeed the next time.
+self.__timestamp = int(time.time())
 return dict, None
 
 def Load(self, check_version=True):

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

[Sebastian Kronenwerth]

Hi Jim,

I have had the same problem. With some tricks you can use your virtual
domains. Here an example how it works fine on my machine, but at this I
used your domain:

Add/modify this in your main.cf:

mydestination =
localhost
localhost.wrightthisway.com

alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases

virtual_alias_maps = hash:/etc/postfix/virtual_alias


Don't use the /usr/local/mailman/data/virtual-mailman. Mailman overwrite
this file and therefore you can't modify this. Instead of this, put per
hand in your /etc/postfix/virtual_alias:

mailman-l...@wrightthisway.com  mailman-l...@localhost
t...@wrightthisway.com  t...@localhost
test-ad...@wrightthisway.comtest-ad...@localhost
test-boun...@wrightthisway.com  test-boun...@localhost
test-conf...@wrightthisway.com  test-conf...@localhost
test-j...@wrightthisway.com test-j...@localhost
test-le...@wrightthisway.comtest-le...@localhost
test-ow...@wrightthisway.comtest-ow...@localhost
test-requ...@wrightthisway.com  test-requ...@localhost
test-subscr...@wrightthisway.comtest-subscr...@localhost
test-unsubscr...@wrightthisway.com  test-unsubscr...@localhost

Don't forget to run postmap virtual_alias and after this your
mailinglist should work.

Best regards
Sebastian
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

[Mark Sapiro]

Sebastian Kronenwerth wrote:

Don't use the /usr/local/mailman/data/virtual-mailman. Mailman overwrite
this file and therefore you can't modify this. Instead of this, put per
hand in your /etc/postfix/virtual_alias:

mailman-l...@wrightthisway.com mailman-l...@localhost
t...@wrightthisway.com t...@localhost
test-ad...@wrightthisway.com   test-ad...@localhost
test-boun...@wrightthisway.com test-boun...@localhost
test-conf...@wrightthisway.com test-conf...@localhost
test-j...@wrightthisway.comtest-j...@localhost
test-le...@wrightthisway.com   test-le...@localhost
test-ow...@wrightthisway.com   test-ow...@localhost
test-requ...@wrightthisway.com test-requ...@localhost
test-subscr...@wrightthisway.com   test-subscr...@localhost
test-unsubscr...@wrightthisway.com test-unsubscr...@localhost


If you have a recent Mailman, you can accomplish the same thing in
virtual-mailman by putting

VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost'

in mm_cfg.py.

This setting was introduced in Mailman 2.1.14. Also see
https://bugs.launchpad.net/mailman/+bug/328907.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

[Mark Sapiro]

Jim Wright wrote:

I did some new googling using postfixadmin and mailman, and came across this 
page: http://freemars.org/howto/mailman.html, this got me a lot closer, I just 
needed to track down the most recent postfix-to-mailman.py script, make the 
required edits for my site, and I have now successfully created and sent email 
to my test list.


While this may be an acceptable solution for you, you should be aware
that use of postfix_to_mailman.py will create the same issues for
non-list mail to the list domain that you had originally for list mail.

I.e. postfix_to_mailman.py is designed for situations where there is a
dedicated domain or domains for list mail only.

You can work around this by generating transport maps to map only list
addresses to the postfix_to_mailman.py (mailman) transport using the
method of the FAQ at http://wiki.list.org/x/ZoCj substituting
'mailman' for 'local'. But then you could also use aliases with this
method by specifying the local transport.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

[Jim Wright]

On Jan 4, 2011, at 12:12 PM, Mark Sapiro wrote:

 Jim Wright wrote:
 
 I did some new googling using postfixadmin and mailman, and came across this 
 page: http://freemars.org/howto/mailman.html, this got me a lot closer, I 
 just needed to track down the most recent postfix-to-mailman.py script, make 
 the required edits for my site, and I have now successfully created and sent 
 email to my test list.
 
 
 While this may be an acceptable solution for you, you should be aware
 that use of postfix_to_mailman.py will create the same issues for
 non-list mail to the list domain that you had originally for list mail.
 
 I.e. postfix_to_mailman.py is designed for situations where there is a
 dedicated domain or domains for list mail only.

Right, I did create a separate domain for the lists, I didn't see it as being a 
huge issue.  It was definitely easier than revamping my postfix config.  ;)

Thanks, Mark!


--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

[Jim Wright]

On Jan 3, 2011, at 12:15 AM, Jim Wright wrote:

 Jan  2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: BBA681B43CF: 
 to=t...@wrightthisway.com, relay=virtual, delay=0.1, 
 delays=0.08/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: 
 t...@wrightthisway.com)

Hi, just a followup to my previous message, I have confirmed that the 'test' 
mailing list I created seems to be listed correctly in the virtual-mailman db, 
using the following command:

sh-3.2# postmap -q t...@wrightthisway.com 
hash:/usr/local/mailman/data/virtual-mailman
test

sh-3.2# postmap -s hash:/usr/local/mailman/data/virtual-mailman
test-conf...@wrightthisway.com  test-confirm
test-j...@wrightthisway.com test-join
test-subscr...@wrightthisway.comtest-subscribe
mailman-l...@wrightthisway.com  mailman-loop
t...@wrightthisway.com  test
test-ad...@wrightthisway.comtest-admin
test-boun...@wrightthisway.com  test-bounces
test-le...@wrightthisway.comtest-leave
test-ow...@wrightthisway.comtest-owner
test-requ...@wrightthisway.com  test-request
test-unsubscr...@wrightthisway.com  test-unsubscribe

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

[Mark Sapiro]

Jim Wright wrote:

However, I cannot send email to this list without the mail being rejected back 
as being to an unknown user.

Based on all of my reading, I think I've done everything correctly.  From my 
Postfix log, it doesn't appear that the aliases file is being consulted at 
all, but I am seeing a line indicating that the virtual-mailman file was 
referenced.


That is correct. Aliases are not consulted because the virtual mapping
in virtual-mailman is

t...@wrightthisway.com  test


This maps 't...@wrightthisway.com' to 'test'. The unqualified address
'test' is assumed by Postfix to be qualified with $myorigin, which
defaults to $myhostname which is 'wrightthisway.com' which is a
virtual domain. Aliases only apply to local domains, i.e., those in
$mydestination.

[...]
sh-3.2# postconf -n
address_verify_sender = 
alias_database = hash:/etc/postfix/aliases, 
hash:/usr/local/mailman/data/aliases


The above should be in alias_maps, not alias_database. Fixing this may
solve your problem, but it I suspect it will not be sufficient.


alias_maps = hash:/etc/postfix/aliases
[...]
mydestination = 


At a minimum, mydestination should include localhost.


mydomain = wrightthisway.com
myhostname = wrightthisway.com
[...]
virtual_alias_maps = proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf, 
hash:/usr/local/mailman/data/virtual-mailman
[...]
Jan  2 23:46:45 wrights-Mac-mini postfix/virtual[81790]: BBA681B43CF: 
to=t...@wrightthisway.com, relay=virtual, delay=0.1, 
delays=0.08/0.01/0/0.02, dsn=5.1.1, status=bounced (unknown user: 
t...@wrightthisway.com)


In order for aliases to be consulted, delivery must be 'local' not
'virtual'

The solution in your case is to put
hash:/usr/local/mailman/data/aliases in alias_maps; add localhost to
mydestination and put

VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost'

in mm_cfg.py and run Mailman's bin/genaliases to create virtual-mailman
mappings like

t...@wrightthisway.com  t...@localhost

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with Postfix/virtual setup, unknown user

[Jim Wright]

On Jan 3, 2011, at 1:34 PM, Mark Sapiro wrote:

 In order for aliases to be consulted, delivery must be 'local' not
 'virtual'
 
 The solution in your case is to put
 hash:/usr/local/mailman/data/aliases in alias_maps; add localhost to
 mydestination and put
 
 VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhost'
 
 in mm_cfg.py and run Mailman's bin/genaliases to create virtual-mailman
 mappings like
 
 t...@wrightthisway.com  t...@localhost

Hi, Mark.  I appreciate the suggestions, but I was hesitant to reconfigure my 
postfix that way, for fear of borking my working virtual domains.  I should 
have mentioned earlier that I have my site configured using postfix admin, and 
after seeing your mention of changing the delivery, that got me thinking about 
the problem in more depth.

I did some new googling using postfixadmin and mailman, and came across this 
page: http://freemars.org/howto/mailman.html, this got me a lot closer, I just 
needed to track down the most recent postfix-to-mailman.py script, make the 
required edits for my site, and I have now successfully created and sent email 
to my test list.

Thanks!

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with accept_these_nonmembers using anotherlist in installation

[Mark Sapiro]

Aaron Ray wrote:

The a...@domain list contains every e-mail from the other 3 lists. So I am
adding the a...@domain mailing list to the other mailing list's
accept_these_nonmembers sender filter with the following syntax:

@all

I have also tried:

@a...@domain

Neither of them seem to work. I appreciate any advice/help anyone can offer.


You have to use the cPanel list name. This is the list name that is
used in web URLs. For most cPanel lists it is of the form
LISTNAME_DOMAIN.

Try

@all_domain

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem with accept_these_nonmembers using anotherlist in installation

[aray10]

Thanks Mark that did the trick. I saw that I had to use the cPanel listname  
elsewhere, but I was using the name listed in the table on cPanel's  
interface rather than the URL. It is working as expected now.


On Oct 19, 2010 9:49am, Mark Sapiro m...@msapiro.net wrote:

Aaron Ray wrote:







The a...@domain list contains every e-mail from the other 3 lists. So I am



adding the a...@domain mailing list to the other mailing list's



accept_these_nonmembers sender filter with the following syntax:







@all







I have also tried:







@a...@domain






Neither of them seem to work. I appreciate any advice/help anyone can  
offer.







You have to use the cPanel list name. This is the list name that is



used in web URLs. For most cPanel lists it is of the form



LISTNAME_DOMAIN.





Try





@all_domain





--



Mark Sapiro m...@msapiro.net The highway is for gamblers,



San Francisco Bay Area, California better use your sense - B. Dylan




--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with emails

[Mark Sapiro]

On 9/29/2010 10:48 PM, kobi barnea wrote:
 
 however, when i send emails to the default mail address none of subscribers
 gets the email.
 
 when i check the inbox of that mail i dont see the emails i sent there - i
 guess mailman pull them.


If your MTA is properly configured for Mailman, no list mail is
delivered to any inbox. It is piped to a Mailman command which stores it
in Mailman's in/ queue.

One possibility is you are posting from your gmail address and posts are
being delivered, but you aren't seeing them. See the FAQ at
http://wiki.list.org/x/2IA9. Otherwise, see the FAQ at
http://wiki.list.org/x/A4E9.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] problem with emails

[Odhiambo Washington]

On Thu, Sep 30, 2010 at 8:48 AM, kobi barnea barne...@gmail.com wrote:

 hi

 i installed mailman and i think it a good solution for me

 however, when i send emails to the default mail address none of subscribers
 gets the email.

 when i check the inbox of that mail i dont see the emails i sent there - i
 guess mailman pull them.

 please advice


What MTA are you running?
Have you checked it's logs for clues on what is happening?



-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
If you have nothing good to say about someone, just shut up!.
   -- Lucky Dube
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem building Mailmn 2 1 4

[Mark Sapiro]

lists.mailman-us...@duinheks.nl wrote:

I'm trying to intake Mailman 2.1.4 on my SlackWare 13.0 system.


Normally, I would assume 2.1.4 was a typo and you really mean 2.1.14,
but see below.


I configure it with
   ./configure
--prefix=/opt/mailman --with-mail-gid=mailman --with-cgi-gid=www
and see no messages there.


I assume here you mean no *error* messages. There should be a fair
amount of *normal* output.


But when I do a make install i see:
   Creating architecture independent directories...
...
Compiling /opt/mailman/Mailman/versions.py ...
bin/update:37: DeprecationWarning: the md5 module is deprecated; use hashlib 
instead
   import md5
/opt/mailman/Mailman/Utils.py:32: DeprecationWarning: the sha module is 
deprecated; use the hashlib module instead
   import sha
Traceback (most recent call last):
   File bin/update, line 48, in module
 from Mailman import MailList
   File /opt/mailman/Mailman/MailList.py, line 49, in module
 from Mailman.Archiver import Archiver
   File /opt/mailman/Mailman/Archiver/__init__.py, line 17, in module
 from Archiver import *
   File /opt/mailman/Mailman/Archiver/Archiver.py, line 31, in module
 from Mailman import Mailbox
   File /opt/mailman/Mailman/Mailbox.py, line 21, in module
 import mailbox
   File /usr/lib/python2.6/mailbox.py, line 19, in module
 import email.message
ImportError: No module named message
make: *** [update] Error 1
What's happening? As I am no C programmer, I don't know what to do.


Apparently, your Python version is 2.6 or later. The first Mailman
version that is compatible with Python 2.6 is Mailman 2.1.12. See the
FAQ at http://wiki.list.org/x/pYA9.


The current version is 2.1.14. Please download Mailman 2.1.14 and try
again. See http://www.list.org/download.html.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem regarding creating mailing list

[Mark Sapiro]

On 7/27/2010 5:27 AM, sandeep kumar wrote:
 1.While creating a mailing list through command line, the owner of
 the list creator does get any mail regarding creation of mailisg list
 . What is the procedure actually to create the mailing list , does
 the owner requires any privelages .


If you create a list via bin/newlist, the list owner address should
receive an emailed notice provided the '-q' option is not given to
newlist, and provided Mailman (mailmanctl and the qrunners) is running.

If the qrunners are not running, the notice will be queued and will be
sent when Mailman is started.

The list owner is only an email address. Nothing is required of it other
than it be valid. The person running bin/newlist itself must be either
root or a member of Mailman's group.


 2. While creating mailing list through web interface using 
 http://domain name/mailman/create , it asks for list creater password
 , We reset the password of admin and list creator password using
 mmsitepass but the password which is reset is not accepted in the
 interface .


What is the exact error? Are you certain you are giving the creator
password or site admin password exactly as set by mmsitepass?


 Is there any procedure to update passwords or any other way to create
 mailing list


Lists are created either via the web create or bin/newlist.

The site admin and/or list creator passwords are set/changed with
bin/mmsitepass.

List admin and moderator passwords can be set/changed via the list's web
admin interface. List admin passwords can also be changed via bin/change_pw.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problem regarding creating mailing list

[Adam McGreggor]

On Tue, Jul 27, 2010 at 05:57:13PM +0530, sandeep kumar wrote:

 does the owner requires any privelages .

You'll need to be able to write to the appropriate directories, and
probably have a sane umask.

(In my case, I interact with Mailman from a user account which is a
member of the 'list' or 'mailman' groups (so I don't need to su), and
has a umask of 0002. YMMV.)

-- 
``Bernard: It's another of those irregular verbs. I hold 
  confidential briefings, you leak, he's been charged 
  under section 2A of the Official Secrets Act. ''
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org