Re: [Mailman-Users] Mailman and qmail problem

2015-10-29 Thread Mark Sapiro 
On 10/29/2015 06:19 AM, Abdallah Dhaou wrote:
> I have a problem configuring mailman 2.1.18 with qmail on Debian .
...
> To finish creating your mailing list, you must edit your /etc/aliases (or
> equivalent) file by adding the following lines, and possibly running the
> `newaliases' program:
> 
> ## list1 mailing list
> list1:  "|/var/lib/mailman/mail/mailman post list1"
> list1-admin:"|/var/lib/mailman/mail/mailman admin list1"
> list1-bounces:  "|/var/lib/mailman/mail/mailman bounces list1"
> list1-confirm:  "|/var/lib/mailman/mail/mailman confirm list1"
> list1-join: "|/var/lib/mailman/mail/mailman join list1"
> list1-leave:"|/var/lib/mailman/mail/mailman leave list1"
> list1-owner:"|/var/lib/mailman/mail/mailman owner list1"
> list1-request:  "|/var/lib/mailman/mail/mailman request list1"
> list1-subscribe:"|/var/lib/mailman/mail/mailman subscribe list1"
> list1-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe list1"
> 
...
> My questions are the following:
> 1- where those alias are stored ?
> 2- is there an addional config to do with qmail ?
> 3- why the user receive email to subscribe/unsubscribe , but the admin
> couldn't sedn email to the list ?


Those aliases are generic for sendmail and postfix. Qmail is different.
See  for some
information about mail delivery from Qmail to Mailman.

Also note if you are installing the Debian Mailman package with Qmail as
the MTA, this should somehow be covered in Debian's documentation and if
it isn't that's a Debian bug. See .

As to your third question, Mailman has no problem delivering outgoing
mail to Qmail via SMTP to port 25 on localhost, but Qmail doesn't know
how to deliver incoming list mail to Mailman. The info at
 should help with
that.

-- 
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

[Mailman-Users] Mailman and qmail problem

2015-10-29 Thread Abdallah Dhaou 

I have a problem configuring mailman 2.1.18 with qmail on Debian .

Short version : The package is installed, users could subscribe to the 
list, unsubscribe ... everything work fine, but it always fail to send 
an email to all members.


Long version : The package is installed, users could subscribe to the 
list, unsubscribe ... everything work fine. Once I access to the email 
of the list's administartor and try to send an email to all members, it 
always fail. This is what I have in the log


 start copy 
@4000563118d016611294 status: local 0/10 remote 0/20
@4000563118fa225c516c new msg 394714
@4000563118fa225c610c info msg 394714: bytes 1519 from 
 qp 30138 uid 901
@4000563118fa229d1774 starting delivery 1: msg 394714 to local 
l...@ipb-srv41.domain41.com

@4000563118fa229d1f44 status: local 1/10 remote 0/20
@4000563118fa229d232c starting delivery 2: msg 394714 to local 
list-listso...@lists.ipb-srv41.domain41.com

@4000563118fa229d2714 status: local 2/10 remote 0/20
@4000563118fa255f583c delivery 2: failure: 
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/

@4000563118fa255f67dc status: local 1/10 remote 0/20
@4000563118fa29c93654 delivery 1: success: 
October_28,_2015,_6:50_pm_-_30142_-_DIR:/tmp/emails/mail1446058224.65219600/_Fim/did_0+0+1/

@4000563118fa29c949dc status: local 0/10 remote 0/20
@4000563118fa2b23730c bounce msg 394714 qp 30153
@4000563118fa2b237ec4 end msg 394714
@4000563118fa2b2ac9f4 new msg 394975
@4000563118fa2b2acddc info msg 394975: bytes 2092 from <> qp 30153 
uid 906
@4000563118fa2b5e64e4 starting delivery 3: msg 394975 to local 
l...@ipb-srv41.domain41.com

@4000563118fa2b5e6cb4 status: local 1/10 remote 0/20
@4000563118fa2b5e6cb4 starting delivery 4: msg 394975 to local 
so...@domain41.com

@4000563118fa2b5e709c status: local 2/10 remote 0/20
 End copy 

While I create a list from the command line
---
ipb-srv41:/var/qmail# newlist list1
Enter the email of the person running the list: administra...@domain41.com
Initial list1 password:
To finish creating your mailing list, you must edit your /etc/aliases (or
equivalent) file by adding the following lines, and possibly running the
`newaliases' program:

## list1 mailing list
list1:  "|/var/lib/mailman/mail/mailman post list1"
list1-admin:"|/var/lib/mailman/mail/mailman admin list1"
list1-bounces:  "|/var/lib/mailman/mail/mailman bounces list1"
list1-confirm:  "|/var/lib/mailman/mail/mailman confirm list1"
list1-join: "|/var/lib/mailman/mail/mailman join list1"
list1-leave:"|/var/lib/mailman/mail/mailman leave list1"
list1-owner:"|/var/lib/mailman/mail/mailman owner list1"
list1-request:  "|/var/lib/mailman/mail/mailman request list1"
list1-subscribe:"|/var/lib/mailman/mail/mailman subscribe list1"
list1-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe list1"

Hit enter to notify list1 owner...

ipb-srv41:/var/qmail#
---

My questions are the following:
1- where those alias are stored ?
2- is there an addional config to do with qmail ?
3- why the user receive email to subscribe/unsubscribe , but the admin 
couldn't sedn email to the list ?

--
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] Mailman and qmail problem

2015-10-29 Thread fsantiago 
See if this helps you:

http://wiki.qmailtoaster.com/index.php/Mailman

But probably a question better asked on a Qmail related mailing list like:

qmailtoaster-l...@qmailtoaster.com


Sincerely,

Fabian Santiago

Sent from my iPhone

> On Oct 29, 2015, at 9:19 AM, Abdallah Dhaou  wrote:
> 
> I have a problem configuring mailman 2.1.18 with qmail on Debian .
> 
> Short version : The package is installed, users could subscribe to the list, 
> unsubscribe ... everything work fine, but it always fail to send an email to 
> all members.
> 
> Long version : The package is installed, users could subscribe to the list, 
> unsubscribe ... everything work fine. Once I access to the email of the 
> list's administartor and try to send an email to all members, it always fail. 
> This is what I have in the log
> 
>  start copy 
> @4000563118d016611294 status: local 0/10 remote 0/20
> @4000563118fa225c516c new msg 394714
> @4000563118fa225c610c info msg 394714: bytes 1519 from 
>  qp 30138 uid 901
> @4000563118fa229d1774 starting delivery 1: msg 394714 to local 
> l...@ipb-srv41.domain41.com
> @4000563118fa229d1f44 status: local 1/10 remote 0/20
> @4000563118fa229d232c starting delivery 2: msg 394714 to local 
> list-listso...@lists.ipb-srv41.domain41.com
> @4000563118fa229d2714 status: local 2/10 remote 0/20
> @4000563118fa255f583c delivery 2: failure: 
> Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
> @4000563118fa255f67dc status: local 1/10 remote 0/20
> @4000563118fa29c93654 delivery 1: success: 
> October_28,_2015,_6:50_pm_-_30142_-_DIR:/tmp/emails/mail1446058224.65219600/_Fim/did_0+0+1/
> @4000563118fa29c949dc status: local 0/10 remote 0/20
> @4000563118fa2b23730c bounce msg 394714 qp 30153
> @4000563118fa2b237ec4 end msg 394714
> @4000563118fa2b2ac9f4 new msg 394975
> @4000563118fa2b2acddc info msg 394975: bytes 2092 from <> qp 30153 uid 906
> @4000563118fa2b5e64e4 starting delivery 3: msg 394975 to local 
> l...@ipb-srv41.domain41.com
> @4000563118fa2b5e6cb4 status: local 1/10 remote 0/20
> @4000563118fa2b5e6cb4 starting delivery 4: msg 394975 to local 
> so...@domain41.com
> @4000563118fa2b5e709c status: local 2/10 remote 0/20
>  End copy 
> 
> While I create a list from the command line
> ---
> ipb-srv41:/var/qmail# newlist list1
> Enter the email of the person running the list: administra...@domain41.com
> Initial list1 password:
> To finish creating your mailing list, you must edit your /etc/aliases (or
> equivalent) file by adding the following lines, and possibly running the
> `newaliases' program:
> 
> ## list1 mailing list
> list1:  "|/var/lib/mailman/mail/mailman post list1"
> list1-admin:"|/var/lib/mailman/mail/mailman admin list1"
> list1-bounces:  "|/var/lib/mailman/mail/mailman bounces list1"
> list1-confirm:  "|/var/lib/mailman/mail/mailman confirm list1"
> list1-join: "|/var/lib/mailman/mail/mailman join list1"
> list1-leave:"|/var/lib/mailman/mail/mailman leave list1"
> list1-owner:"|/var/lib/mailman/mail/mailman owner list1"
> list1-request:  "|/var/lib/mailman/mail/mailman request list1"
> list1-subscribe:"|/var/lib/mailman/mail/mailman subscribe list1"
> list1-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe list1"
> 
> Hit enter to notify list1 owner...
> 
> ipb-srv41:/var/qmail#
> ---
> 
> My questions are the following:
> 1- where those alias are stored ?
> 2- is there an addional config to do with qmail ?
> 3- why the user receive email to subscribe/unsubscribe , but the admin 
> couldn't sedn email to the list ?
> --
> 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/fsantiago%40deviltracks.net

--
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] Mailman and qmail problem

2015-10-29 Thread Mark Sapiro 
On 10/29/2015 08:52 AM, Mark Sapiro wrote:
> 
> Those aliases are generic for sendmail and postfix. Qmail is different.
> See  for some
> information about mail delivery from Qmail to Mailman.
> 
> Also note if you are installing the Debian Mailman package with Qmail as
> the MTA, this should somehow be covered in Debian's documentation and if
> it isn't that's a Debian bug. See .


I am reminded by Fabian Santiago's reply that there is also a
qmail-to-mailman.py script. In a source install, the base script is in
contrib/qmail-to-mailman.py and a 'configured' script is in
build/contrib/qmail-to-mailman.py

I don't know what the situation is in the Debian package, but given
Debian's proclivity towards postfix-to-mailman.py (not distributed by
the GNU Mailman project), they may well have a way to set this up for Qmail.

-- 
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

[Mailman-Users] changing domains on Mailman implementation

2015-10-29 Thread Keith Seyffarth 


Is there an efficient way to change the domain name that mailman is
affiliated with?

I have two mailing lists that were created for an organization before
that organization had their own domain. At the time the organization was
sure they did not want their own domain and would not be getting a
domain.

Since then, they have chosen to get a domain and set up a web site.

I would like to move their mailing lists onto their domain. It looks
like the process for this is:
1) get the list of subscribers
2) delete the mailing list from the one domain (losing the archives)
3) create the mailing list on the new domain
4) subscribe the list of subscribers

This process doesn't seem too difficult, but I would prefer to keep the
archives, if possible.

Both domains are on the same server, running CentOS7 and PLESK 12.5, if
that makes a difference.

Thanks,
Keith
--
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] Mailman and qmail problem

2015-10-29 Thread Lindsay Haisley 
On Thu, 2015-10-29 at 08:52 -0700, Mark Sapiro wrote:
> On 10/29/2015 06:19 AM, Abdallah Dhaou wrote:
> > I have a problem configuring mailman 2.1.18 with qmail on Debian .
> ...
> > To finish creating your mailing list, you must edit your /etc/aliases (or
> > equivalent) file by adding the following lines, and possibly running the
> > `newaliases' program:
> > 
> > ## list1 mailing list
> > list1:  "|/var/lib/mailman/mail/mailman post list1"
> > list1-admin:"|/var/lib/mailman/mail/mailman admin list1"
> > list1-bounces:  "|/var/lib/mailman/mail/mailman bounces list1"
> > list1-confirm:  "|/var/lib/mailman/mail/mailman confirm list1"
> > list1-join: "|/var/lib/mailman/mail/mailman join list1"
> > list1-leave:"|/var/lib/mailman/mail/mailman leave list1"
> > list1-owner:"|/var/lib/mailman/mail/mailman owner list1"
> > list1-request:  "|/var/lib/mailman/mail/mailman request list1"
> > list1-subscribe:"|/var/lib/mailman/mail/mailman subscribe list1"
> > list1-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe list1"
> > 
> ...
> > My questions are the following:
> > 1- where those alias are stored ?
> > 2- is there an addional config to do with qmail ?
> > 3- why the user receive email to subscribe/unsubscribe , but the admin
> > couldn't sedn email to the list ?

There's an excellent program in Mailman's contrib folder in the source
called qmail-to-mailman.py which eliminates the need for specific
aliases as you have listed. It's been years since I used qmail but as I
recall, qmail has the ability to process a mail to a list through a
configurable program. I adapted qmail-to-mailman.py to create
courier-to-mailman (also in contrib) for the courier MTA, which is
similar to qmail in some regards, and it works perfectly.


> Those aliases are generic for sendmail and postfix. Qmail is different.
> See  for some
> information about mail delivery from Qmail to Mailman.
> 
> Also note if you are installing the Debian Mailman package with Qmail as
> the MTA, this should somehow be covered in Debian's documentation and if
> it isn't that's a Debian bug. See .
> 
> As to your third question, Mailman has no problem delivering outgoing
> mail to Qmail via SMTP to port 25 on localhost, but Qmail doesn't know
> how to deliver incoming list mail to Mailman. The info at
>  should help with
> that.
> 

-- 
Lindsay Haisley   | "The only unchanging certainty
FMP Computer Services |is the certainty of change"
512-259-1190  |
http://www.fmp.com| - Ancient wisdom, all cultures

--
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] changing domains on Mailman implementation

2015-10-29 Thread Mark Sapiro 
On 10/29/2015 09:35 AM, Keith Seyffarth wrote:
> 
> Is there an efficient way to change the domain name that mailman is
> affiliated with?
...
> I would like to move their mailing lists onto their domain. It looks
> like the process for this is:
> 1) get the list of subscribers
> 2) delete the mailing list from the one domain (losing the archives)
> 3) create the mailing list on the new domain
> 4) subscribe the list of subscribers
> 
> This process doesn't seem too difficult, but I would prefer to keep the
> archives, if possible.


That's unduly complex and disruptive. Don't do any of that.


> Both domains are on the same server, running CentOS7 and PLESK 12.5, if
> that makes a difference.


Note: the following is for standard Mailman. Plesk may be different.

First make sure you have

add_virtualhost('their.web.domain', 'their.email.domain')

im mm_cfg.py.

Then for each affected list you run Mailman's

bin/withlist -l -r fix_url listname --urlhost=their.web.domain

That takes care of most of it, but there may be issues with delivery of
mail to Mailman. If you use Postfix with Postfix-Mailman integration for
automatic generation of aliases and virtual mappings, you probably also
want to add 'their.email.domain' to the POSTFIX_STYLE_VIRTUAL_DOMAINS
list in mm_cfg.py. Then running Mailman's

bin/genaliases

is all you need. In other cases, you may need to manually update virtual
mappings. Aliases generally don't need to be changed.

-- 
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