On Wed, Dec 04, 2024 at 09:04:43PM +1300, Tim Harman wrote:
> > This seemed to be about TLS handshake failures, not connection loss
> > after a successful handshake... Did I misunderstand?
>
> No, you don't misunderstand. Their ticket/bug is about TLS handshake
> failing.
> I was clearly gettin
On Wed, 4 Dec 2024 at 00:16, Tim Harman via Postfix-users
wrote:
>
> FIXED
>
> smtpd_tls_session_cache_timeout = 0
> So there must be something going on in the version of Debian I have (10)
> where TLS session tickets aren't working/negotiated/stored correctly.
I have postfix on Debian 10 wi
On 04/12/2024 7:45 pm, Viktor Dukhovni via Postfix-users wrote:
On Wed, Dec 04, 2024 at 12:13:13PM +1300, Tim Harman via Postfix-users
wrote:
FIXED
smtpd_tls_session_cache_timeout = 0
This is very odd, because:
- Session tickets are either successfuly decrypted or not.
- If ye
On Wed, Dec 04, 2024 at 12:13:13PM +1300, Tim Harman via Postfix-users wrote:
> FIXED
>
> smtpd_tls_session_cache_timeout = 0
This is very odd, because:
- Session tickets are either successfuly decrypted or not.
- If yes, the TLS handshake proceeds more quickly, and
the clien
FIXED
smtpd_tls_session_cache_timeout = 0
This is instantly resolved the issue
Previously I had smtpd_tls_session_cache_timeout = 604800
I noted that turning this to 0 also disabled session tickets, and I'd
read this: https://github.com/mjl-/mox/issues/237 (After searching
MailOp)
So t
Jaroslaw Rafa via Postfix-users:
> Dnia 3.12.2024 o godz. 17:38:40 Wietse Venema via Postfix-users pisze:
> > (*) Someone roported long ago that they fixed an obscure Postfix
> > networking problem by plugging the server into a different port.
>
> Hm... candidate for another case of "500 mile
Dnia 3.12.2024 o godz. 17:38:40 Wietse Venema via Postfix-users pisze:
> (*) Someone roported long ago that they fixed an obscure Postfix
> networking problem by plugging the server into a different port.
Hm... candidate for another case of "500 mile email" ?
--
Regards,
Jaroslaw Rafa
On 04/12/2024 11:38 am, Wietse Venema via Postfix-users wrote:
If a "newer" server works, then I guess the problem is due to
differences in the TLS stack. or in the TLS configuration, or
that the cause is some obscure data-dependent problem(*). TLS makes
data larger and more random.
Compared to
Tim Harman via Postfix-users:
> > But it hangs up after EHLO-STARTTLS-EHLO. Something it does not like
> > after the (second) EHLO response?
>
> Yes, I've even tried filtering out a few EHLO messages using postfix,
> but still the same behaviour from Microsoft/Outlook/365.
If a "newer" server wo
from
*.outbound.protection.outlook.com is failing:
postfix/smtpd[15735]: lost connection after EHLO from
mail-australiasoutheastazon11020092.outbound.protection.outlook.com[52.101.152.92]
postfix/smtpd[15717]: lost connection after EHLO from
mail-psaapc01on2110.outbound.protection.outlook.com
Viktor Dukhovni via Postfix-users:
> > Trusted TLS - so I think that proves my SSL is good?
>
> No, that means they presented a client certificate for no particularly
> good reason, one that happened to chain up to a known trust anchor.
This reason:
> smtpd_tls_ask_ccert = yes
But it hangs up a
e incorrect DANE TLSA records for your domain, or perhaps
broken MTA-STS. But that's not the case here.
> Dec 3 11:59:36 mail postfix/smtpd[16112]: connect from
> mail-australiaeastazon11021121.outbound.protection.outlook.com[40.107.39.121]
> Dec 3 11:59:37 mail postfix/smtpd[1611
Tim Harman via Postfix-users skrev den 2024-12-03 03:02:
# Don't offer Auth until STARTTLS has setup
smtpd_tls_auth_only = yes
try comment this one, should imho only be overrided in master.cf not
used/set in main.cf
___
Postfix-users mailing list
. So, quite a few people. This is what appears in my
mail.log:
Dec 3 11:38:18 mail postfix/smtpd[15735]: lost connection after EHLO from
mail-australiasoutheastazon11020092.outbound.protection.outlook.com[52.101.152.92]
[...]
Here's my main.cf
[...]
# Ask for a Client Cert
smtpd_t
st_match:
mail-psaapc01on2132.outbound.protection.outlook.com: no match
postfix/smtpd[27329]: match_list_match: 40.107.255.132: no match
postfix/smtpd[27329]: send attr request = disconnect
postfix/smtpd[27329]: send attr ident = smtp:40.107.255.132
postfix/smtpd[27329]: private/anvil:
mail.log:
Dec 3 11:38:18 mail postfix/smtpd[15735]: lost connection after EHLO
from
mail-australiasoutheastazon11020092.outbound.protection.outlook.com[52.101.152.92]
Dec 3 11:38:28 mail postfix/smtpd[15717]: lost connection after EHLO
from mail-psaapc01on2110.outbound.protection.outlook.com[
On 2018-02-08 (22:43 MST), motty cruz wrote:
>
> match_hostname: smtpd_client_event_limit_exceptions: neon.domain.com ~?
> 189.45.22.55
postconf -n
What (and why) do you have smtpd_client_event_limit_exceptions set to?
Also, I don't believe for a second that domain.com is connecting to you.
Dr. Wietse,
Thank you very much for taking the time to reply to my email.
I enabled TLS on Postfix with a certificate from letsencrypt.com for
temporary solution. This solved the problem, we're now able to received
emails from that specific client.
Your support on this matter is appreciated
Bastian Blank:
> On Thu, Feb 08, 2018 at 09:43:51PM -0800, motty cruz wrote:
> > I am trying to figure out why my Postfix disconnect after EHLO command. A
> > customer is trying to email me something but Postfix disconnect: ( on the
> > customer side this is the bounced message "Remote Server retur
On 09-02-18 18:35, Motty Cruz wrote:
If you have any other ideas please share, I appreciate your help!
You could try getting a packet trace on your end. It might show you in
more detail what is going on. Worst case you learn nothing new.
regards,
Erik
Thanks Bill,
The customer is from fairly large company and they're able to send email
to other clients. They will not cooperate to help me troubleshoot this
issue. I am working from the assumption the problem is on my side.
We were getting emails from that client up to few weeks ago. Nothing
One more thing...
On 9 Feb 2018, at 9:09, Motty Cruz wrote:
Isn't because my smtp server does not support TLS?
Yes, it could be. Their broken firewall may be set to require TLS
support.
Which is not in itself a bad thing. The only thing broken about this IF
it's because they require TLS
On 9 Feb 2018, at 9:09, Motty Cruz wrote:
Hello Bastian,
you're right "
( on the
customer side this is the bounced message "Remote Server returned '<
spring1.mydomain.com #5.0.0 smtp; 554 Security violation. Email
Session
ID:" )
This is a message generated by a dysfunctional and misguided
;http://neon.domain.com> ~? 189.45.22.55
Feb 8 09:46:04 spring1 postfix/smtpd[47824]: lost connection after EHLO
from neon.domain.com <http://neon.domain.com>[189.45.22.55]
Isn't because my smtp server does not support TLS? or do you have any
idea how to solve this problem?
is
owns you.
> Feb 8 09:46:04 spring1 postfix/smtpd[47824]: lost connection after EHLO
> from neon.domain.com[189.45.22.55]
You really know someone owning domain.com?
Bastian
--
Peace was the way.
-- Kirk, "The City on the Edge of Forever", stardate unknown
smtpd_client_event_limit_exceptions: neon.domain.com ~? 189.45.22.55
Feb 8 09:46:04 spring1 postfix/smtpd[47824]: lost connection after EHLO
from neon.domain.com[189.45.22.55]
Feb 8 09:46:04 spring1 postfix/smtpd[47824]: disconnect from
neon.domain.com[189.45.22.55] ehlo=1 commands=1
Feb 8 09:
> > we are getting lot of messages in the mail log showing the
> > following
> >
> > Jan 20 00:15:21 mailgate postfix/smtpd[18917]: lost
> > connection after EHLO from unknown[173.225.251.221]
> > Jan 20 00:26:21 mailgate postfix/smtpd[18917]: lost
> > conne
t;
> Jan 20 00:15:21 mailgate postfix/smtpd[18917]: lost connection after
> EHLO from unknown[173.225.251.221]
> Jan 20 00:26:21 mailgate postfix/smtpd[18917]: lost connection after
> CONNECT from unknown[173.225.251.221]
> Jan 20 03:17:53 mailgate postfix/smtpd[20255]: lost con
hi,
this pertains to the issue raised by our unit in barbados, having ip
address 173.225.251.221, i have included the said ip in debug_peer_list
we are getting lot of messages in the mail log showing the following
Jan 20 00:15:21 mailgate postfix/smtpd[18917]: lost connection after EHLO
from
000 bytes)
Jun 1 15:59:38 smtp postfix/smtpd[23929]: connect from
unknown[10.184.10.213]
Jun 1 15:59:38 smtp postfix/smtpd[23929]: lost connection after EHLO
from unknown[10.184.10.213]
Jun 1 15:59:38 smtp postfix/smtpd[23929]: disconnect from
unknown[10.184.10.213]
Jun 1 16:01:42 smtp postfix/sm
:38 smtp postfix/smtpd[23929]: connect from
unknown[10.184.10.213]
Jun 1 15:59:38 smtp postfix/smtpd[23929]: lost connection after EHLO from
unknown[10.184.10.213]
Jun 1 15:59:38 smtp postfix/smtpd[23929]: disconnect from
unknown[10.184.10.213]
Jun 1 16:01:42 smtp postfix/smtpd[23449]: conn
ror message:
> The mail server sent an incorrect greeting: .
> And in the server's maillog, there are some errors:
>
> Dec 20 09:14:54 server postfix/smtpd[20034]: lost connection after EHLO
> from 58.16.broadband2.iol.cz[83.208.16.58]
> Dec 20 09:14:54 server postf
n the server's maillog, there are some errors:
Dec 20 09:14:54 server postfix/smtpd[20034]: lost connection after EHLO
from 58.16.broadband2.iol.cz[83.208.16.58]
Dec 20 09:14:54 server postfix/smtpd[20034]: disconnect from
58.16.broadband2.iol.cz[83.208.16.58]
Same problem with Windows
33 matches
Mail list logo
