Re: [Mailman-Users] Syslog in Mailman

2015-05-03 Thread Mark Sapiro
On 05/03/2015 02:54 PM, Eric Lamer wrote:
> 
>I have Mailman installed on my Debian and I don't get any message in my 
> syslog server from Mailman.  I have exim4 on the same server and I get syslog 
> from it.


Mailman has its own logging facility. It calls it syslog, but it is
Mailman's own logging, not the system syslog.


>I have generated some stuff in mailman, like creating a list etc and I see 
> the message in /var/log/mailman/  bounce,error,smtp etc.  so I know the 
> message are getting in the log files.  Just no syslog.


Exactly. Mailman logs to it's own files which in a Debian package are in
/var/log/mailman. That's the only logging Mailman does.

-- 
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] Syslog in Mailman

2015-05-03 Thread Eric Lamer
Hi,

   I have Mailman installed on my Debian and I don't get any message in my 
syslog server from Mailman.  I have exim4 on the same server and I get syslog 
from it.

   I have generated some stuff in mailman, like creating a list etc and I see 
the message in /var/log/mailman/  bounce,error,smtp etc.  so I know the message 
are getting in the log files.  Just no syslog.

   Any idea?

  I am using Mailman 2.1.18 on Debian 8.

Thanks.

[cid:45762505-9551-43f5-9158-58708DA84162.jpg]


[cid:logo-new.jpg]


Eric Lamer
CEO
Phoenix Secure Inc.
[cid:phone.png] 514-914-5599
[cid:printer_and_fax.png] 514-800-2556
[cid:mail_32.png] e...@phoenixsecure.com

[cid:button-facebook.png]  
[cid:button-linkedin.png]    
[cid:button-twitter.png]    
[cid:button-youtube.png] 
 
[cid:button-google.png] 



[cid:C44700B8-0227-4717-A5D5-7935D46B0F9D.jpg]
--
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] /etc/mailman/mm_cfg.py

2015-05-03 Thread Stephen J. Turnbull
Mark Sapiro writes:

 > Debian also puts the files where they belong, including putting
 > mm_cfg.py in /etc/mailman/ which I agree is the right place, but Mailman
 > still thinks all the files are in /var/lib/mailman

Ah, OK, I see what you mean.  Except IIRC Mailman proper knows the
absolute paths to where its list data is.  The problem is that the
scripts in bin expect relative paths, so the admin wants to cd to
/var/lib/mailman and operate from there, thus the link to bin for the
admin's convenience, and the scripts in bin expect Mailman to be at
../Mailman, so a link to Mailman is needed too.

 > While this all works, and it is arguably better than patching
 > Mailman in ways that make it more difficult to upgrade from source
 > should you want to,

That is a PITA, so let's not even think about anybody doing that! :-)

 > it just seems somehow unclean to me, and that's all I meant to say.

Indeed, I agree with that.  I don't see any way to avoid uncleanness,
though, given "dynamic linking" (here, importing) of "shared" modules,
and the occasional dependency on minor-version-specific
idiosyncracies.  This particular ugliness is especially useful to
admins (although we might want to make sure we reduce or avoid it in
Mailman 3)?
--
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] /etc/mailman/mm_cfg.py

2015-05-03 Thread Mark Sapiro
On 05/03/2015 05:15 PM, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
>  > 
>  > Actually, AFAIK, the Red Hat (hence CentOS) Mailman package is the only
>  > one that does it right.
> 
> I don't understand what you mean by "right".


I actually meant 'right' in a much more limited sense. Also, I had
actually forgotten John Dennis' whole mm_cfg.py thing and it's
'exceptional' treatment in Red Hat. I agree with what you've said here.

I only meant that for the most part Red Hat puts the files where they
belong under FHS and teaches Mailman to look for them there.

Debian also puts the files where they belong, including putting
mm_cfg.py in /etc/mailman/ which I agree is the right place, but Mailman
still thinks all the files are in /var/lib/mailman and those that
aren't, which is a bunch, are symlinked from there including a symlink
from /var/lib/mailman/Mailman to /usr/lib/mailman/Mailman and then a
second one from /usr/lib/mailman/Mailman/mm_cfg.py to
/etc/mailman/mm_cfg.py. While this all works, and it is arguably better
than patching Mailman in ways that make it more difficult to upgrade
from source should you want to, it just seems somehow unclean to me, and
that's all I meant to say.

Does it right was really not the correct characterization, particularly
since I'm reminded of Red Hat's mm_cfg.py handling.

-- 
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] /etc/mailman/mm_cfg.py

2015-05-03 Thread Stephen J. Turnbull
Mark Sapiro writes:
 > On 05/03/2015 06:17 AM, Laura Creighton wrote:

 > > On all the machines I can ssh to, I have an
 > > /etc/mailman/mm_cfg.py as well as a /usr/lib (or /var/lib)
 > > /mailman/Mailman/mm_cfg.py, and the second is a symbolic link to
 > > the first.  Why do we have an /etc/mailmand/mm_cfg.py at all?
 > 
 > In a word (or acronym), FHS.
 > 
 > 
 > Actually, AFAIK, the Red Hat (hence CentOS) Mailman package is the only
 > one that does it right.

I don't understand what you mean by "right".

John Dennis's distinction that mm_cfg.py is "executable" and others
aren't is bogus AFAICS; there are lots of apparently data-only files
that are actually interpreted code (PDF being one of the more powerful
and dangerous).

What matters here is exceptional treatment of this one file by the
PMS.  In the case of Red Hat, they cannot simply unpack the archive
into place (in practice, noboby does that any more, but that's a
different issue); they have to either avoid copying over mm_cfg.py or
preserve it and restore it.  In Debian, you can just unpack the
archive, but then you need to remove the distributed mm_cfg.py and
restore the symlink.

AFAICS these procedures are basically equivalent, except that both the
PMS and the sysadmin have to know something special about Mailman in
the Red Hat scheme.  Note that in the Debian scheme you can be an old
Mailman hand and edit /var/lib/mailman/Mailman/mm_cfg.py, or Debian
admins who don't know much about the history of Mailman can just go to
the FHS place in /etc/mailman and find mm_cfg.py there.  That's an
advantage to the Debian scheme AFAICS.  Another (minor) advantage is
that in the Debian scheme the PMS doesn't have to do anything special
to protect the "real" mm_cfg.py, it just never automatically edits
anything under /etc.

--
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] mailloop exim lmtp

2015-05-03 Thread Thomas Stein
On Sunday 03 May 2015 07:50:08 Mark Sapiro wrote:
> On 05/03/2015 06:25 AM, Thomas Stein wrote:
> > It seems mailman is unable to send mail. Sending mail as user mailman on
> > the commandline works. Strange.
> 
> These kinds of problems often result because mailman sends via SMTP to
> (by default) 'localhost' and there is a conflict because for example,
> the MTA is configured to accept mail from an IPv4 local host
> (127.0.0.1/n) and not from an IPv6 local host (::1), but 'localhost' is
> defined in /etc/hosts as the 'wrong' one.

Thanks for your answer. Changed localhost to 127.0.0.1 in mailman.cfg and now 
the error is gone. But the mail loop still is in action. It works even better 
now. :-) I guess i have to keep digging.

thanks again and cheers
t.
--
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] /etc/mailman/mm_cfg.py (was EyeLand's problem)

2015-05-03 Thread Mark Sapiro
On 05/03/2015 06:17 AM, Laura Creighton wrote:
> In poking around debian systems to see if I could shed any light on
> EyeLand's problem, I ended up with a question.  On all the machines
> I can ssh to, I have an /etc/mailman/mm_cfg.py as well as a
> /usr/lib (or /var/lib) /mailman/Mailman/mm_cfg.py, and the second is
> a symbolic link to the first.  Why do we have an /etc/mailmand/mm_cfg.py
> at all?


In a word (or acronym), FHS.


Actually, AFAIK, the Red Hat (hence CentOS) Mailman package is the only
one that does it right. See  and the
mailman-developers post linked therefrom. Debian (hence Ubuntu) puts
things in the FHS recommended places, but everything not in
/var/lib/mailman/ is symlinked from there so Mailman itself still thinks
everything is in /var/lib/mailman/.

-- 
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] mailloop exim lmtp

2015-05-03 Thread Mark Sapiro
On 05/03/2015 06:25 AM, Thomas Stein wrote:
> 
> It seems mailman is unable to send mail. Sending mail as user mailman on the 
> commandline works. Strange.


These kinds of problems often result because mailman sends via SMTP to
(by default) 'localhost' and there is a conflict because for example,
the MTA is configured to accept mail from an IPv4 local host
(127.0.0.1/n) and not from an IPv6 local host (::1), but 'localhost' is
defined in /etc/hosts as the 'wrong' one.

-- 
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] mailloop exim lmtp

2015-05-03 Thread Thomas Stein
On Sunday 03 May 2015 21:48:02 Stephen J. Turnbull wrote:
> Thomas Stein writes:
>  > Exim gives no error. Just a loop between goodnews-bounces and goodnews.
>  > What did i wrong this time? :-)
> 
> It appears that Exim can't send mail at all, and so first the error
> happens in the mailing list, then it tries to send the error
> information to the list-owner, but that fails the same way ("address
> faimily not supported by protocol").
> 
> Can't say more without seeing your configs.

> Can you send any mail at all on that host?

Yes. No problems. Here a test via command line. Mailing list is called "more".

misc ~ # exim -v m...@misc.domain.de
From: himbe...@domain.de
To: m...@misc.domain.de
Subject: Test

This is a test.
LOG: MAIN
  <= r...@misc.domain.de U=root P=local S=362
misc ~ # delivering 1Yoroo-0007Vh-Hd
Connecting to localhost [127.0.0.1]:8024 ... connected
  SMTP<< 220 misc.domain.de Python LMTP runner 1.0
  SMTP>> LHLO misc.domain.de
  SMTP<< 250 misc.domain.de
  SMTP>> MAIL FROM:
  SMTP<< 250 OK
  SMTP>> RCPT TO:
  SMTP<< 250 OK
  SMTP>> DATA
  SMTP<< 354 End data with .
  SMTP>> writing message and terminating "."
  SMTP<< 250 Ok
  SMTP>> QUIT
LOG: MAIN
  => m...@misc.domain.de R=mailman3_router T=mailman3_transport H=localhost 
[127.0.0.1] C="250 Ok"
LOG: MAIN
  Completed

So the mail is with mailman now. Mailman smtp.log still the same:

May 03 13:13:14 2015 (24469) <20150503111313.24473.30...@misc.g.de> low level 
smtp error: [Errno 97] Address family not supported by protocol
May 03 13:13:14 2015 (24469) <20150503111313.24473.30...@misc.g.de> smtp to 
m...@misc.domain.de for 1 recips, completed in 0.0038123130798339844 seconds
May 03 13:13:14 2015 (24469) <20150503111313.24473.30...@misc.g.de> post to 
m...@misc.domain.de from more-boun...@misc.domain.de, 831 bytes, 1 failures
May 03 13:13:14 2015 (24469) <20150503111313.24473.30...@misc.g.de> delivery 
to himbe...@domain.de failed with code 444, [Errno 97] Address family not 
supported by protocol
May 03 13:13:14 2015 (24469) <20150503111313.24473.98...@misc.g.de> low level 
smtp error: [Errno 97] Address family not supported by protocol

It seems mailman is unable to send mail. Sending mail as user mailman on the 
commandline works. Strange.

thanks and ciao
t.

--
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] /etc/mailman/mm_cfg.py (was EyeLand's problem)

2015-05-03 Thread Laura Creighton
In poking around debian systems to see if I could shed any light on
EyeLand's problem, I ended up with a question.  On all the machines
I can ssh to, I have an /etc/mailman/mm_cfg.py as well as a
/usr/lib (or /var/lib) /mailman/Mailman/mm_cfg.py, and the second is
a symbolic link to the first.  Why do we have an /etc/mailmand/mm_cfg.py
at all?

Just curious,
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


[Mailman-Users] mailloop exim lmtp

2015-05-03 Thread Stephen J. Turnbull
Thomas Stein writes:

 > Exim gives no error. Just a loop between goodnews-bounces and goodnews. What 
 > did i wrong this time? :-)

It appears that Exim can't send mail at all, and so first the error
happens in the mailing list, then it tries to send the error
information to the list-owner, but that fails the same way ("address
faimily not supported by protocol").

Can't say more without seeing your configs.

Can you send any mail at all on that host?

--
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] Conceal the member's address

2015-05-03 Thread Stephen J. Turnbull
EyeLand writes:

 > I not see OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES

Defaults are set in /usr/lib/mailman/Mailman/Defaults.py on my Debian
system.  You should not change that file, any changes will be
overwritten the next time you upgrade.  Instead, add those variables
and their new settings to mm_cfg.py


--
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] Conceal the member's address

2015-05-03 Thread Laura Creighton
In a message of Sun, 03 May 2015 14:04:47 +0300, EyeLand writes:
>root@vps1:~# sudo find / -name mm_cfg.py
>/usr/lib/mailman/Mailman/mm_cfg.py
>/etc/mailman/mm_cfg.py
>
>on file /usr/lib/mailman/Mailman/mm_cfg.py
>https://gist.githubusercontent.com/eyeland/e33c20045867b262d1a2/raw/1bdb433403594c4f1ab2e6c6e12007c8881fefaa/gistfile1.txt
>I not see OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES

OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES
on your machine live in /usr/lib/mailman/Mailman/Defaults.py

But _never_ _ever_ edit Defaults.py

You want to edit /usr/lib/mailman/Mailman/mm_cfg.py and put the values
you want changed _there_.

Ok?

Then you need to go to the list Admin Non-digest options page and
set Personalize to Full Personalization.

Then you need to restart mailman.

And then, we hope, you can come back and tell us that it worked. :)

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] Conceal the member's address

2015-05-03 Thread EyeLand
2015-05-03 0:32 GMT+03:00 Mark Sapiro :

> On 05/02/2015 01:31 PM, EyeLand wrote:
>
> > - On Debian when I can find file $prefix/Mailman/Defaults.py,
> > $prefix/Mailman/mm_cfg.py ?
>
>
> As far as I know, in the Debian package, $prefix is /var/lib/mailman,
> but there may also be a symlink from /usr/lib/mailman/Mailman to
> /var/lib/mailman/Mailman.
>
> If that doesn't help, try
>
> locate mm_cfg.py
>
> or
>
> sudo find / -name mm_cfg.py
>
> --
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
>

root@vps1:~# locate mm_cfg.py
/etc/mailman/mm_cfg.py
/etc/mailman/mm_cfg.py~
/usr/lib/mailman/Mailman/mm_cfg.py
/usr/lib/mailman/Mailman/mm_cfg.py.dist
/usr/lib/mailman/Mailman/mm_cfg.pyc
/usr/local/ispconfig/server/conf/mm_cfg.py.master
/usr/share/doc/mailman/examples/mm_cfg.py.gz
root@vps1:~# sudo find / -name mm_cfg.py
/usr/lib/mailman/Mailman/mm_cfg.py
/etc/mailman/mm_cfg.py

on file /usr/lib/mailman/Mailman/mm_cfg.py
https://gist.githubusercontent.com/eyeland/e33c20045867b262d1a2/raw/1bdb433403594c4f1ab2e6c6e12007c8881fefaa/gistfile1.txt
I not see OWNERS_CAN_ENABLE_PERSONALIZATION and VERP_PERSONALIZED_DELIVERIES
--
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] mailloop exim lmtp

2015-05-03 Thread Thomas Stein
Hola.

After having mailman3 installation behind me a first test post seems to lead 
to a kind of mailloop. mailman smtp.log says:

May 03 10:17:37 2015 (24469) <20150503080846.24473.69262@misc.domain> smtp to 
goodnews@misc.domain for 1 recips, completed in 0.014857053756713867 seconds
May 03 10:17:37 2015 (24469) <20150503080846.24473.69262@misc.domain> post to 
goodnews@misc.domain from goodnews-owner@misc.domain, 19631 bytes, 1 failures
May 03 10:17:37 2015 (24469) <20150503080846.24473.69262@misc.domain> delivery 
to goodnews-owner@misc.domain failed with code 444, [Errno 97] Address family 
not supported by protocol
May 03 10:17:37 2015 (24469) <20150503080846.24473.31080@misc.domain> low 
level smtp error: [Errno 97] Address family not supported by protocol
May 03 10:17:37 2015 (24469) <20150503080846.24473.31080@misc.domain> smtp to 
goodnews@misc.domain for 1 recips, completed in 0.022059917449951172 seconds
May 03 10:17:37 2015 (24469) <20150503080846.24473.31080@misc.domain> post to 
goodnews@misc.domain from goodnews-owner@misc.domain, 31458 bytes, 1 failures
May 03 10:17:37 2015 (24469) <20150503080846.24473.31080@misc.domain> delivery 
to goodnews-owner@misc.domain failed with code 444, [Errno 97] Address family 
not supported by protocol
May 03 10:17:37 2015 (24469) <20150503080846.24473.49233@misc.domain> low 
level smtp error: [Errno 97] Address family not supported by protocol
May 03 10:17:37 2015 (24469) <20150503080846.24473.49233@misc.domain> smtp to 
goodnews@misc.domain for 1 recips, completed in 0.014764547348022461 seconds
May 03 10:17:37 2015 (24469) <20150503080846.24473.49233@misc.domain> post to 
goodnews@misc.domain from goodnews-owner@misc.domain, 19614 bytes, 1 failures
May 03 10:17:37 2015 (24469) <20150503080846.24473.49233@misc.domain> delivery 
to goodnews-owner@misc.domain failed with code 444, [Errno 97] Address family 
not supported by protocol
May 03 10:17:38 2015 (24469) <20150503080847.24473.74610@misc.domain> low 
level smtp error: [Errno 97] Address family not supported by protocol
May 03 10:17:38 2015 (24469) <20150503080847.24473.74610@misc.domain> smtp to 
goodnews@misc.domain for 1 recips, completed in 0.01850271224975586 seconds
May 03 10:17:38 2015 (24469) <20150503080847.24473.74610@misc.domain> post to 
goodnews@misc.domain from goodnews-owner@misc.domain, 21954 bytes, 1 failures
May 03 10:17:38 2015 (24469) <20150503080847.24473.74610@misc.domain> delivery 
to goodnews-owner@misc.domain failed with code 444, [Errno 97] Address family 
not supported by protocol

Exim gives no error. Just a loop between goodnews-bounces and goodnews. What 
did i wrong this time? :-)

thanks and ciao
t.
--
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