Re: SSL3 alert write:fatal:decode error

On Fri, Feb 10, 2023 at 09:22:57AM +, Marko ANGELSKI wrote: > I'm having trouble with one client (iot) not able to send emails via > postfix. This is the log: > > postfix/smtps/smtpd[4420]: initializing the server-side TLS engine > postfix/smtps/smtpd[4420]: connect from unknown[xxx.xxx.xxx.x

RE: missing log entries for old version of postfix

Wietse, Great call: Feb 9 12:58:01 ip-10-104-84-189 journal: Suppressed 5141 messages from /user.slice/user-0.slice Feb 9 13:00:00 ip-10-104-84-189 journal: Suppressed 7542 messages from /user.slice/user-0.slice Feb 9 13:00:37 ip-10-104-84-189 journal: Suppressed 22 messages from /user.slice

Re: missing log entries for old version of postfix

Sean Hennessey: > I have a machine running a very old version of postfix. In trying > to troubleshoot a discrepancy between what some reports I was > pulling from the postfix logs vs what my upstream relay was saying > I was sending I noticed something that looks off to me. Logging from qmgr and

missing log entries for old version of postfix

I have a machine running a very old version of postfix. In trying to troubleshoot a discrepancy between what some reports I was pulling from the postfix logs vs what my upstream relay was saying I was sending I noticed something that looks off to me. [ssm-user@ip-10-104-84-189 ~]$ sudo grep -E

Re: different treatment for different From: domains

Wietse Venema wrote on 2/10/23 08:24: There are two features that support sender-dependent routing: sender_dependent_relayhost_maps This looks up a relayhost value that depends on sender. Like relayhost, this uses default_transport. It is seached with the envelope sender addres

Re: SSL3 alert write:fatal:decode error

Marko ANGELSKI: > Hi, > > I appreciate the reply, the time is all the same - everything at the same > second. You also deleted the useful information about what a packet was sent by the client and what was sent by the server. Basically, this needs all packets after the TCP handshake. Wi

RE: SSL3 alert write:fatal:decode error

Hi, I appreciate the reply, the time is all the same - everything at the same second. Marko -Original Message- From: Wietse Venema Sent: Friday, February 10, 2023 1:30 PM To: Marko ANGELSKI Cc: postfix-users@postfix.org Subject: Re: SSL3 alert write:fatal:decode error Marko ANGELSKI:

Re: different treatment for different From: domains

D. R. Evans: > I have a postfix setup that, for a long time, has done exactly what I want. > But now I have to change something and I have no idea how to make this > particular change: > > E-mail from several domains are sourced on my network. Now I need to treat > e-mail with the From: line >

different treatment for different From: domains

I have a postfix setup that, for a long time, has done exactly what I want. But now I have to change something and I have no idea how to make this particular change: E-mail from several domains are sourced on my network. Now I need to treat e-mail with the From: line u...@domain1.com differ

Re: SSL3 alert write:fatal:decode error

Marko ANGELSKI: > Hi, all, > > > > I'm having trouble with one client (iot) not able to send emails via > postfix. This is the log: > > postfix/smtps/smtpd[4420]: initializing the server-side TLS engine You deleted the useful time information, and added the useless debug logging. Wi

SSL3 alert write:fatal:decode error

Hi, all, I'm having trouble with one client (iot) not able to send emails via postfix. This is the log: postfix/smtps/smtpd[4420]: initializing the server-side TLS engine postfix/smtps/smtpd[4420]: connect from unknown[xxx.xxx.xxx.xxx] postfix/smtps/smtpd[4420]: setting up TLS connection fr