Thanks a lot Mark,

I have found in the /var/log/maillog a lot of messages like this:

Mar 10 19:53:43 e-listas postfix/smtpd[2190]: NOQUEUE: reject: RCPT from localhost[::1]: 554 5.7.1 <carlmari@fcm.unicamp.br>: Relay access denied; from=<redenaus-l-bounces@e-listas.uerj.br> to=<carlmari@fcm.unicamp.br> proto=ESMTP helo=<e-listas.uerj.br>

Mar 10 19:53:45 e-listas postfix/smtpd[2190]: too many errors after RCPT from localhost[::1] Mar 10 19:53:45 e-listas postfix/smtpd[2190]: disconnect from localhost[::1] Mar 10 19:53:45 e-listas postfix/smtpd[2190]: connect from localhost[::1]

I think mailman is assembling the message with errors. So, Postfix is rejecting it.

As I have said before, after restoring the image from virtual machine (machine crashed yesterday), I have restored all files from my daily backup of yesterday (/var/lib/mailman, /usr/lib/mailman and /var/spool).

All file of /etc directory that Mailman needs is up to date, too.

I have started Postfix first and then Mailman.

As I have already said, Postfix is working fine, I am sure.

I found Mailman version 2.1.12 in the file /usr/lib/mailman/Mailman/Version.py

I don´t know if there is a command like a flush or reset in the queues of Mailman in order to put it to work properly.

Maybe I should not restore /var/spool of the system or queues of Mailman and consider all of them lost, maybe.

Even so, thanks a lot for your help.

-----Mensagem original----- De: Mailman-Developers [mailto:mailman-developers-bounces+jovino=uerj.br@python.org] Em nome de Mark Sapiro Enviada em: terça-feira, 10 de março de 2015 18:20 Para: mailman-developers@python.org Assunto: Re: [Mailman-Developers] Mailman error after restoring backup

On 03/10/2015 01:13 PM, jovino Borret wrote:

The problem is that after restarting Postfix and Mailman, many error messages

Is been logged in the /var/log/mailman. He is some examples:

1.  /var/log/mailman/post   
   
   
   
          Mar 10 15:20:20 2015 (1454) post to uerjxxi from 

   weber@globo.com, size=3146, message-id=<EA367EE3-C7A4-4B8E-8464-D5B246CE68F4@globo.com>, 206 failures

This doesn't say much. The smtp-failure log is more informative.

2.  /var/log/mailman/qrunner

Mar 10 15:20:46 2015 (1449) ArchRunner qrunner caught SIGTERM. Stopping.

Mar 10 15:20:46 2015 (1449) ArchRunner qrunner exiting.

And is there a message like

Mar 10 15:20:46 2015 (pppp) Master qrunner detected subprocess exit (pid: 1449, sig: xxx, sts: xx, class: ArchRunner, slice: 1/1)

in the log too.

It's hard to say much from this without seeing all the qrunner log messages from this time frame and error log messages too if any.

3.  /var/log/mailman/smtp-failure

Mar 10 17:07:23 2015 (1701) delivery to lullimilman@uol.com.br failed with code -1: Server not connected

This could occur if you started Mailman before Postfix and Mailman had messages queued. Are these messages still occurring?

I am sure that Postfix is running ok (I have done some tests).

I think Mailman is not "talking" with Postfix, I mean it is not working properly with Postfix.

If there is an ongoing problem between Mailman and Postfix and the Postfix logs don't help, see the FAQ article at <http://wiki.list.org/x/4030716> for a way to get more debugging info.

Also, I suggest stopping Mailman completely (see <http://wiki.list.org/x/4030715> for info on this) and then starting it again to see if that helps.

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

Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/jovino%40uerj.br

Security Policy: http://wiki.list.org/x/QIA9

Este email está limpo de vírus e malwares porque a proteção do avast! Antivírus está ativa. http://www.avast.com

Thank you again,

There is one Postfix that runs in the same server where Mailman runs (We have another Postfix installed in the mail server (two differents machines).

The first 9 lines of the file main.cf from Mailman server follow:

myhostname = e-listas.uerj.br mydomain = e-listas.uerj.br myorigin = $mydomain inet_interfaces = all mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mynetworks = 127.0.0.1/32 relay_domains = e-listas.uerj.br home_mailbox = Mailbox

This configuration is the same that Postfix used before the crash of yesterday.

Thank you a lot for your attention.

-----Mensagem original----- De: Mark Sapiro [mailto:mark@msapiro.net] Enviada em: terça-feira, 10 de março de 2015 21:23 Para: jovino@uerj.br; mailman-developers@python.org Assunto: Re: RES: [Mailman-Developers] Mailman error after restoring backup

On 03/10/2015 04:20 PM, jovino Borret wrote:

Thanks a lot Mark,

I have found in the /var/log/maillog a lot of messages like this:

Mar 10 19:53:43 e-listas postfix/smtpd[2190]: NOQUEUE: reject: RCPT from localhost[::1]: 554 5.7.1 <carlmari@fcm.unicamp.br>: Relay access denied; from=<redenaus-l-bounces@e-listas.uerj.br> to=<carlmari@fcm.unicamp.br> proto=ESMTP helo=<e-listas.uerj.br>

Mar 10 19:53:45 e-listas postfix/smtpd[2190]: too many errors after RCPT from localhost[::1] Mar 10 19:53:45 e-listas postfix/smtpd[2190]: disconnect from localhost[::1] Mar 10 19:53:45 e-listas postfix/smtpd[2190]: connect from localhost[::1]

I think mailman is assembling the message with errors. So, Postfix is rejecting it.

On the contrary, I think your Postfix configuration does not include the Mailman server in mynetworks (possibly an IPv4 vs IPv6 issue) and is thus refusing to relay mail from Mailman to foreign domains.

This looks like a Postfix issue to me. Is [::1]/128 in mynetworks?

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

Este email está limpo de vírus e malwares porque a proteção do avast! Antivírus está ativa. http://www.avast.com

Hi Mark,

In my last mail, replying some questions, I have forgotten to include these messages of /var/log/mailman/smtp-failure :

Mar 10 21:30:51 2015 (2185) delivery to luciamp@uol.com.br failed with code -1: Server not connected Mar 10 21:30:51 2015 (2185) delivery to tadeu.reis@gmail.com failed with code -1: Server not connected Mar 10 21:30:51 2015 (2185) delivery to jchalmeida@gmail.com failed with code -1: Server not connected Mar 10 21:30:51 2015 (2185) delivery to lcsantamaria@terra.com.br failed with code -1: Server not connected Mar 10 21:31:03 2015 (2185) Low level smtp error: [Errno 104] Connection reset by peer, msgid: <COL130-W21B523C320135A445D159D941C0@phx.gbl> Mar 10 21:31:03 2015 (2185) Low level smtp error: Server not connected, msgid: <COL130-W21B523C320135A445D159D941C0@phx.gbl> Mar 10 21:31:14 2015 (2185) Low level smtp error: Server not connected, msgid: <COL130-W21B523C320135A445D159D941C0@phx.gbl> Mar 10 21:31:25 2015 (2185) Low level smtp error: Server not connected, msgid: <COL130-W21B523C320135A445D159D941C0@phx.gbl> Mar 10 21:31:36 2015 (2185) Low level smtp error: Server not connected, msgid: <COL130-W21B523C320135A445D159D941C0@phx.gbl> Mar 10 21:31:47 2015 (2185) Low level smtp error: Server not connected, msgid: <COL130-W21B523C320135A445D159D941C0@phx.gbl>

These messages are still occurring (replying your answer) after restarting Postfix and Mailman.

Thank you.

-----Mensagem original----- De: jovino Borret [mailto:jovino@uerj.br] Enviada em: terça-feira, 10 de março de 2015 20:20 Para: 'Mark Sapiro'; 'mailman-developers@python.org' Assunto: RES: [Mailman-Developers] Mailman error after restoring backup

Thanks a lot Mark,

I have found in the /var/log/maillog a lot of messages like this:

Mar 10 19:53:43 e-listas postfix/smtpd[2190]: NOQUEUE: reject: RCPT from localhost[::1]: 554 5.7.1 <carlmari@fcm.unicamp.br>: Relay access denied; from=<redenaus-l-bounces@e-listas.uerj.br> to=<carlmari@fcm.unicamp.br> proto=ESMTP helo=<e-listas.uerj.br>

Mar 10 19:53:45 e-listas postfix/smtpd[2190]: too many errors after RCPT from localhost[::1] Mar 10 19:53:45 e-listas postfix/smtpd[2190]: disconnect from localhost[::1] Mar 10 19:53:45 e-listas postfix/smtpd[2190]: connect from localhost[::1]

I think mailman is assembling the message with errors. So, Postfix is rejecting it.

As I have said before, after restoring the image from virtual machine (machine crashed yesterday), I have restored all files from my daily backup of yesterday (/var/lib/mailman, /usr/lib/mailman and /var/spool).

All file of /etc directory that Mailman needs is up to date, too.

I have started Postfix first and then Mailman.

As I have already said, Postfix is working fine, I am sure.

I found Mailman version 2.1.12 in the file /usr/lib/mailman/Mailman/Version.py

I don´t know if there is a command like a flush or reset in the queues of Mailman in order to put it to work properly.

Maybe I should not restore /var/spool of the system or queues of Mailman and consider all of them lost, maybe.

Even so, thanks a lot for your help.

-----Mensagem original----- De: Mailman-Developers [mailto:mailman-developers-bounces+jovino=uerj.br@python.org] Em nome de Mark Sapiro Enviada em: terça-feira, 10 de março de 2015 18:20 Para: mailman-developers@python.org Assunto: Re: [Mailman-Developers] Mailman error after restoring backup

On 03/10/2015 01:13 PM, jovino Borret wrote:

The problem is that after restarting Postfix and Mailman, many error messages

Is been logged in the /var/log/mailman. He is some examples:

1.  /var/log/mailman/post   
   
   
   
          Mar 10 15:20:20 2015 (1454) post to uerjxxi from 

   weber@globo.com, size=3146, message-id=<EA367EE3-C7A4-4B8E-8464-D5B246CE68F4@globo.com>, 206 failures

This doesn't say much. The smtp-failure log is more informative.

2.  /var/log/mailman/qrunner

Mar 10 15:20:46 2015 (1449) ArchRunner qrunner caught SIGTERM. Stopping.

Mar 10 15:20:46 2015 (1449) ArchRunner qrunner exiting.

And is there a message like

Mar 10 15:20:46 2015 (pppp) Master qrunner detected subprocess exit (pid: 1449, sig: xxx, sts: xx, class: ArchRunner, slice: 1/1)

in the log too.

It's hard to say much from this without seeing all the qrunner log messages from this time frame and error log messages too if any.

3.  /var/log/mailman/smtp-failure

Mar 10 17:07:23 2015 (1701) delivery to lullimilman@uol.com.br failed with code -1: Server not connected

This could occur if you started Mailman before Postfix and Mailman had messages queued. Are these messages still occurring?

I am sure that Postfix is running ok (I have done some tests).

I think Mailman is not "talking" with Postfix, I mean it is not working properly with Postfix.

If there is an ongoing problem between Mailman and Postfix and the Postfix logs don't help, see the FAQ article at <http://wiki.list.org/x/4030716> for a way to get more debugging info.

Also, I suggest stopping Mailman completely (see <http://wiki.list.org/x/4030715> for info on this) and then starting it again to see if that helps.

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

Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/jovino%40uerj.br

Security Policy: http://wiki.list.org/x/QIA9

Este email está limpo de vírus e malwares porque a proteção do avast! Antivírus está ativa. http://www.avast.com

As long as you're here, you may as well continue this thread (which I'm going to suppress from now on on my MUA). But this list is for development of Mailman; debugging configuration is appropriate for mailman-users@python.org.