On 2023-09-11 at 12:15:10 UTC-0400 (Mon, 11 Sep 2023 09:15:10 -0700
(PDT))
Fred Morris via Postfix-users
is rumored to have said:
Looks like you've got the general idea.
On Mon, 11 Sep 2023, Jesper Hansen via Postfix-users wrote:
[...]
All the non port 25 tests, took about 15-27 hops.
But
On Mon, Sep 11, 2023 at 09:15:10AM -0700, Fred Morris via Postfix-users wrote:
> I think we've reached the limits of scope for a mailing list devoted to an
> MTA. It appears that traffic improbably ends up at 192.168.20.20. That's
> probably good enough, digging into the /why/ could become a
Looks like you've got the general idea.
On Mon, 11 Sep 2023, Jesper Hansen via Postfix-users wrote:
[...]
All the non port 25 tests, took about 15-27 hops.
But the port 25 ones only took 7 or 8, and have a look at the IP at the
next-to-last hop of the route.
192.168.20.20?? What?
[...]
5
The situation is not solved yet, but I want to express a big thanks to everyone
who replied.
I’m waiting for a reply from my ISP about the port 25 interference.
I’ve leaned a lot from your suggestions, although some are at the edge of my
capabilities.
Setting up a new VPS is actually what I
Dnia 10.09.2023 o godz. 10:20:19 Bill Sommerfeld via Postfix-users pisze:
> There's another possible workaround, if the ISP won't budge (or even
> if it does and you still find yourself blocked based on your
> providers IP reputation): some service providers may let you
> purchase outbound mail
On Sun, 10 Sep 2023, Erwan David via Postfix-users wrote:
On Sun, 10 Sep 2023, postfix--- via Postfix-users wrote:
Try a telnet connection to those host (gmail/mail-tester) on 25 and see
who actually answers.
1) Send SYNs with varying TTLs to determine the number of hops to alleged
Le 10/09/2023 à 20:12, Fred Morris via Postfix-users a écrit :
Other replies have identified what's probably happening: redirection
to a specific mail relay or honeypot.
I have a couple of suggestions, which you should consider carefully
(for legality and possible retaliation) before trying.
Other replies have identified what's probably happening: redirection to a
specific mail relay or honeypot.
I have a couple of suggestions, which you should consider carefully (for
legality and possible retaliation) before trying. I'd consider them ok
where I am, but YMMV.
Also, consider any
On 9/10/23 08:22, Bill Cole via Postfix-users wrote:
On 2023-09-10 at 04:28:38 UTC-0400 (Sun, 10 Sep 2023 15:28:38 +0700)
Jesper Hansen via Postfix-users
is rumored to have said:
I simply sit on their fiber and does not relaying anything through them.
Yes, but your packets traverse their
On 2023-09-10 at 04:28:38 UTC-0400 (Sun, 10 Sep 2023 15:28:38 +0700)
Jesper Hansen via Postfix-users
is rumored to have said:
[...]
Then, about an hour later, I got this message to postaster@mydomain:
- Transcript of session follows -
... Deferred: Connection timed
out with
On 10.09.23 21:05, Jesper Hansen via Postfix-users wrote:
My ISP might be filtering port 25, I have no idea.
BUT, I’m NOT connecting to my ISP as the mail log show.
I connect directly to the recipients SMTP and get the right reply.
That’s why I find suspicious that I get a bounce where the ISP
My ISP might be filtering port 25, I have no idea.
BUT, I’m NOT connecting to my ISP as the mail log show.
I connect directly to the recipients SMTP and get the right reply.
That’s why I find suspicious that I get a bounce where the ISP is mentioned.
Unless they, considering this is Thailand, is
Sep 10 12:21:39 wopr postfix/smtp[25425]: 94E7840E5C: to=,
relay=gmail-smtp-in.l.google.com[74.125.130.27]:25, delay=0.85,
delays=0.03/0.04/0.56/0.22, dsn=2.0.0, status=sent (250 2.0.0
38A5LeYj001108-38A5LeYl001108 Message accepted for delivery)
Reporting-MTA: dns;
13 matches
Mail list logo
