Opened 5 years ago

Last modified 5 years ago

#8967 assigned Bug/Something is broken

email dont receive and send

Reported by: asistente@… Owned by: https://id.mayfirst.org/erq
Priority: Urgent Component: Tech
Keywords: Cc:
Sensitive: no

Description

Hello.

The email jan@… don´t receive and send mails.

Could you help us?

Regards, Sofía

Change History (7)

comment:1 Changed 5 years ago by https://id.mayfirst.org/erq

hola, me encuentro revisando en este momento el servidor, espero tener pronto diagnóstico. Saludos Enrique

comment:2 Changed 5 years ago by https://id.mayfirst.org/erq

  • Owner set to https://id.mayfirst.org/ross
  • Status changed from new to assigned

Hi ross

I'm seeing postfix errors like this one:

Apr 10 09:46:34 mx1 postfix/error[14675]: 608C429C3F: to=<raulhdezg@laneta.apc.org>, orig_to=<alternativas@laneta.apc.org>, relay=none, delay=3109, delays=2888/221/0/0.2, dsn=4.4.2, status=deferred (delivery temporarily suspended: conversation with 127.0.0.1[127.0.0.1] timed out while receiving the initial server greeting)

And like this other ones:

Apr 10 13:47:29 mx1 postfix/smtpd[22782]: warning: network_biopair_interop: error writing 53 bytes to the network: Connection reset by peer
Apr 10 13:47:29 mx1 postfix/smtpd[22782]: warning: network_biopair_interop: error writing 37 bytes to the network: Broken pipe

I hope you can have an idea about what could be wrong, I'm still searching. Enrique

Last edited 5 years ago by https://id.mayfirst.org/erq (previous) (diff)

comment:3 Changed 5 years ago by https://id.mayfirst.org/erq

Oh, no. It looks like the update of the server, could had have a negative impact:

0 mx1:~# cat /var/log/mail.log|grep TLS|grep erro
Apr 10 12:31:47 mx1 postfix/smtpd[2365]: warning: TLS library problem: 2365:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:
Apr 10 12:31:47 mx1 postfix/smtpd[2364]: warning: TLS library problem: 2364:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:
Apr 10 12:31:47 mx1 postfix/smtpd[2337]: warning: TLS library problem: 2337:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:
Apr 10 12:31:47 mx1 postfix/smtpd[2445]: warning: TLS library problem: 2445:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:
Apr 10 12:41:53 mx1 postfix/smtpd[4021]: warning: TLS library problem: 4021:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:
Apr 10 12:41:53 mx1 postfix/smtpd[4024]: warning: TLS library problem: 4024:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:
Apr 10 12:59:22 mx1 postfix/smtpd[4510]: warning: TLS library problem: 4510:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:
Apr 10 13:35:15 mx1 postfix/smtpd[21842]: warning: TLS library problem: 21842:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1108:SSL alert number 42:

Although I don't see more of this warnings before or after.

Last edited 5 years ago by https://id.mayfirst.org/erq (previous) (diff)

comment:4 Changed 5 years ago by https://id.mayfirst.org/ross

  • Resolution set to fixed
  • Status changed from assigned to closed

I just updated the server's packages which included all of the clamv-* packages. This seems to have resolved the problem as the mailq went from 5112 to 9, and I no longer see the timed out errors.

~/ross

comment:5 Changed 5 years ago by https://id.mayfirst.org/ross

  • Resolution fixed deleted
  • Status changed from closed to assigned

oops I take it back...now I see those errors again :-(

comment:6 Changed 5 years ago by https://id.mayfirst.org/ross

It looks like it may have been amavis not doing it's job. I restarted amavis and currently things look like they are being processed correctly. Though it is really slow and process intensive. I'll keep my eye on it to see if the time outs return.

comment:7 Changed 5 years ago by https://id.mayfirst.org/erq

  • Owner changed from https://id.mayfirst.org/ross to https://id.mayfirst.org/erq

It looks like that solve the issue. right? Thanks Ross

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.