Bug 267336 - Mails to addresses on freebsd.org domain are rejected even with registered email address
Summary: Mails to addresses on freebsd.org domain are rejected even with registered em...
Status: Closed FIXED
Alias: None
Product: Services
Classification: Unclassified
Component: Mailing Lists (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: postmaster
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-25 13:47 UTC by Tomoaki AOKI
Modified: 2022-11-02 21:32 UTC (History)
2 users (show)

See Also:


Attachments
Transcript of junchoon@dec.sakura.ne.jp (5.46 KB, message/rfc822)
2022-10-25 13:53 UTC, Tomoaki AOKI
no flags Details
Transcript of junchoon@aurora.dti.ne.jp (10.07 KB, text/plain)
2022-10-25 13:59 UTC, Tomoaki AOKI
no flags Details
Transcript of junchoon@aurora.dti.ne.jp #2 (10.02 KB, text/plain)
2022-10-26 11:07 UTC, Tomoaki AOKI
no flags Details
Transcript of junchoon@dec.sakura.ne.jp #2 (5.18 KB, message/rfc822)
2022-10-29 04:09 UTC, Tomoaki AOKI
no flags Details
Transcript of junchoon@dec.sakura.ne.jp #3 (3.47 KB, message/rfc822)
2022-10-29 11:21 UTC, Tomoaki AOKI
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomoaki AOKI 2022-10-25 13:47:54 UTC
At least 2 of email servers are rejected.

dec.sakura.ne.jp (maybe an alias of www121.sakura.ne.jp, but assigned domain name is dec.sakura.ne.jp for me.)
I've using junchoon@dec.sakura.ne.jp on freebsd.org MLs for years.

aurora.dti.ne.jp
Used to report the problem above. Not registered for freebsd.org MLs.
This is a clowd-based service, so possibly cannot resolved from IP address.

I'll upload transcripts shortly.
Comment 1 Tomoaki AOKI 2022-10-25 13:53:20 UTC
Created attachment 237616 [details]
Transcript of junchoon@dec.sakura.ne.jp

Rejected mail 1 (from junchoon@dec.sakura.ne.jp)
Transcript part is as follows.

From: Mail Delivery Subsystem <MAILER-DAEMON>
To: <junchoon@dec.sakura.ne.jp>
Subject: Returned mail: see transcript for details
Date: Tue, 25 Oct 2022 18:47:15 +0900 (JST)

The original message was received at Tue, 25 Oct 2022 18:47:06 +0900 (JST)
from 123-1-88-210.area1b.commufa.jp [123.1.88.210]

   ----- The following addresses had permanent fatal errors -----
<yuri@FreeBSD.org>
    (reason: 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists)
<dev-commits-ports-main@freebsd.org>
    (reason: 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists)

   ----- Transcript of session follows -----
... while talking to mx1.freebsd.org.:
>>> RCPT To:<dev-commits-ports-main@freebsd.org>
<<< 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists
<<< 550 5.7.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 25 09:47:14) and client (153.125.133.21).
550 5.1.1 <dev-commits-ports-main@freebsd.org>... User unknown
>>> RCPT To:<yuri@FreeBSD.org>
<<< 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists
<<< 550 5.7.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 25 09:47:15) and client (153.125.133.21).
550 5.1.1 <yuri@FreeBSD.org>... User unknown
>>> DATA
<<< 554-5.5.1 Error: no valid recipients
<<< 554 5.5.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 25 09:47:15) and client (153.125.133.21).
451 4.4.1 reply: read error from mx1.freebsd.org.


Reporting-MTA: dns; www121.sakura.ne.jp
Received-From-MTA: DNS; 123-1-88-210.area1b.commufa.jp
Arrival-Date: Tue, 25 Oct 2022 18:47:06 +0900 (JST)

Final-Recipient: RFC822; yuri@FreeBSD.org
X-Actual-Recipient: rfc822; yuri@FreeBSD.org
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.freebsd.org
Diagnostic-Code: SMTP; 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists
Last-Attempt-Date: Tue, 25 Oct 2022 18:47:15 +0900 (JST)

Final-Recipient: RFC822; dev-commits-ports-main@freebsd.org
X-Actual-Recipient: rfc822; dev-commits-ports-main@freebsd.org
Action: failed
Status: 5.7.1
Remote-MTA: DNS; mx1.freebsd.org
Diagnostic-Code: SMTP; 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists
Last-Attempt-Date: Tue, 25 Oct 2022 18:47:15 +0900 (JST)
Comment 2 Tomoaki AOKI 2022-10-25 13:59:30 UTC
Created attachment 237617 [details]
Transcript of junchoon@aurora.dti.ne.jp

Rejected email 2 from junchoon@aurora.dti.ne.jp.
Transcript part is as follows.

From: Mail Delivery Subsystem <MAILER-DAEMON@vsmtp01.cm.dti.ne.jp>
To: <junchoon@aurora.dti.ne.jp>
Subject: Warning: could not send message for past 3 hours
Date: Tue, 25 Oct 2022 22:12:33 +0900 (JST)

    **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Tue, 25 Oct 2022 19:03:41 +0900 (JST)
from 123-1-88-210.area1b.commufa.jp [123.1.88.210]

   ----- Transcript of session follows -----
... while talking to mx1.freebsd.org.:
>>> DATA
<<< 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
<<< 450 4.7.25 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 25 13:12:32) and client (2001:2e8:702::236:70:63).
<postmaster@FreeBSD.org>... Deferred: 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
<<< 554-5.5.1 Error: no valid recipients
<<< 554 5.5.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 25 13:12:32) and client (2001:2e8:702::236:70:63).
... while talking to mx66.freebsd.org.:
>>> DATA
<<< 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
<<< 450 4.7.25 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 25 13:12:33) and client (2001:2e8:702::236:70:63).
<postmaster@FreeBSD.org>... Deferred: 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
<<< 554-5.5.1 Error: no valid recipients
<<< 554 5.5.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 25 13:12:33) and client (2001:2e8:702::236:70:63).
Warning: message still undelivered after 3 hours
Will keep trying until message is 1 day old
Comment 3 Tomoaki AOKI 2022-10-26 11:07:37 UTC
Created attachment 237649 [details]
Transcript of junchoon@aurora.dti.ne.jp #2

Delayed email from aurora.dti.ne.jp is finally rejected.

Transcript part is as follows.

From: Mail Delivery Subsystem <MAILER-DAEMON@vsmtp01.cm.dti.ne.jp>
To: <junchoon@aurora.dti.ne.jp>
Subject: Returned mail: see transcript for details
Date: Wed, 26 Oct 2022 19:08:17 +0900 (JST)

The original message was received at Tue, 25 Oct 2022 19:03:41 +0900 (JST)
from 123-1-88-210.area1b.commufa.jp [123.1.88.210]

   ----- The following addresses had permanent fatal errors -----
<postmaster@FreeBSD.org>
    (reason: 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63])

   ----- Transcript of session follows -----
... while talking to mx1.freebsd.org.:
>>> DATA
<<< 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
<<< 450 4.7.25 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 26 10:08:16) and client (2001:2e8:702::236:70:63).
<postmaster@FreeBSD.org>... Deferred: 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
<<< 554-5.5.1 Error: no valid recipients
<<< 554 5.5.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 26 10:08:16) and client (2001:2e8:702::236:70:63).
... while talking to mx66.freebsd.org.:
>>> DATA
<<< 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
<<< 450 4.7.25 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 26 10:08:17) and client (2001:2e8:702::236:70:63).
<postmaster@FreeBSD.org>... Deferred: 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
<<< 554-5.5.1 Error: no valid recipients
<<< 554 5.5.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 26 10:08:17) and client (2001:2e8:702::236:70:63).
Message could not be delivered for 1 day
Message will be deleted from queue


Reporting-MTA: dns; vsmtp01.cm.dti.ne.jp
Arrival-Date: Tue, 25 Oct 2022 19:03:41 +0900 (JST)

Final-Recipient: RFC822; postmaster@FreeBSD.org
Action: failed
Status: 4.4.7
Remote-MTA: DNS; mx66.freebsd.org
Diagnostic-Code: SMTP; 450-4.7.25 Client host rejected: cannot find your hostname, [2001:2e8:702::236:70:63]
Last-Attempt-Date: Wed, 26 Oct 2022 19:08:17 +0900 (JST)
Comment 4 Tomoaki AOKI 2022-10-26 11:11:44 UTC
FYI: 1.1.1.1 (Cloudflare open DNS) could resolve the IPv6 address as follows.

% drill -x 2001:2e8:702::236:70:63 @1.1.1.1
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 59349
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; 3.6.0.0.0.7.0.0.6.3.2.0.0.0.0.0.0.0.0.0.2.0.7.0.8.e.2.0.1.0.0.2.ip6.arpa.    IN      PTR

;; ANSWER SECTION:
3.6.0.0.0.7.0.0.6.3.2.0.0.0.0.0.0.0.0.0.2.0.7.0.8.e.2.0.1.0.0.2.ip6.arpa.       300     IN      PTR     vsmtp01.ipv6.cm.dream.jp.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 1503 msec
;; SERVER: 1.1.1.1
;; WHEN: Wed Oct 26 19:59:36 2022
;; MSG SIZE  rcvd: 128
Comment 5 Tomoaki AOKI 2022-10-29 04:09:05 UTC
Created attachment 237702 [details]
Transcript of junchoon@dec.sakura.ne.jp #2

No changes until now. :-(

The original message was received at Sat, 29 Oct 2022 12:45:41 +0900 (JST)
from 123-1-88-210.area1b.commufa.jp [123.1.88.210]

   ----- The following addresses had permanent fatal errors -----
<stephen@FreeBSD.org>
    (reason: 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists)
<dev-commits-ports-main@freebsd.org>
    (reason: 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists)

   ----- Transcript of session follows -----
... while talking to mx1.freebsd.org.:
>>> RCPT To:<dev-commits-ports-main@freebsd.org>
<<< 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists
<<< 550 5.7.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 29 03:45:48) and client (153.125.133.21).
550 5.1.1 <dev-commits-ports-main@freebsd.org>... User unknown
>>> RCPT To:<stephen@FreeBSD.org>
<<< 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists
<<< 550 5.7.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 29 03:45:48) and client (153.125.133.21).
550 5.1.1 <stephen@FreeBSD.org>... User unknown
>>> DATA
<<< 554-5.5.1 Error: no valid recipients
<<< 554 5.5.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 29 03:45:48) and client (153.125.133.21).
451 4.4.1 reply: read error from mx1.freebsd.org.
Comment 6 Tomoaki AOKI 2022-10-29 04:21:13 UTC
Can anyone on postmaster@ explain why this is happeneing?
Without it, I cannot even contact to hosting provider of this shared web/mail service.

My email domain (dec.sakura.ne.jp) is owned by the service provider and I myself cannot touch its configuration at all.

Is it because they didn't support DKIM and/or SPF?
(Even freebsd.org MLs doesn't seem to use them, though.)


My last email accepted was

 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
 To: stable@freebsd.org
 Subject: Policy for future importing of openzfs on stable branches?
 Date: Sun, 23 Oct 2022 11:39:57 +0900

so any changes on freebsd.org side after that caused the fatal (yes, FATAL!) problem.
I've been using this email account on FreeBSD.org MLs until 2013. So it shouldn't be rejected!
Comment 7 Philip Paeps freebsd_committer freebsd_triage 2022-10-29 04:40:01 UTC
Your mail server's IP address is listed in the Abusix denylist:

https://lookup.abusix.com/search?q=153.125.133.21

It looks like the address is also listed in SORBS as an active spam source.  The Abusix listing 

I'll allowlist you on mx1.freebsd.org for a few days for your provider to sort these issues out.
Comment 8 Philip Paeps freebsd_committer freebsd_triage 2022-10-29 04:48:48 UTC
The problem with 2001:2e8:702::236:70:63 is different:

2001:2e8:702::236:70:63 resolves to vsmtp01.ipv6.cm.dream.jp but vsmtp01.ipv6.cm.dream.jp does not resolve to 2001:2e8:702::236:70:63 (or at all).

We do not have an allowlist for misconfigured servers.
Comment 9 Tomoaki AOKI 2022-10-29 07:57:29 UTC
(In reply to Philip Paeps from comment #7)

Thanks!
I've reported to Sakura Internet with your info.
It would be started handled on Monday working time JST (+9) at earliest.
Maybe need some more days (if there's any actual spammer among users, possibly require weeks [or months]) to finish...

BTW, is my email address (junchoon@dec.sakura.ne.jp) not yet white-listed (temporarily)?
Comment 10 Tomoaki AOKI 2022-10-29 08:02:36 UTC
(In reply to Philip Paeps from comment #8)

Unfortunately, IIRC and IIUC, it would be because the MTA is clowd based.
Maybe resolving from name to IP would be chosen randomly from server firm, and all servers would be reverse-resolved as the same name.
I think some kind of load balancer choses which actual server to be resolved on each query requested.
Comment 11 Tomoaki AOKI 2022-10-29 08:04:34 UTC
(In reply to Tomoaki AOKI from comment #10)

Forgot to mention.
IIUC, all users having @*.dti.ne.jp or @*.dream.jp would be affected, too.
Comment 12 Philip Paeps freebsd_committer freebsd_triage 2022-10-29 08:11:54 UTC
I have allowlisted 153.125.133.21.  That should allow anyone using that relay to get past that check.

Forward-confirmed reverse DNS is not optional for mail servers.  We do not have an allowlist in our configuration for such misconfigurations.  At the very least, vsmtp01.ipv6.cm.dream.jp will have to resolve to something.

https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS
Comment 13 Tomoaki AOKI 2022-10-29 11:19:05 UTC
(In reply to Philip Paeps from comment #12)
Thanks. I've reported this to DTI. Hope they fixes the issue...

OTOH, unfortunately, email from junchoon@dec.sakura.ne.jp is still blocked.
(Tried sending help request to users-jp+help@freebsd.org not to pollute actual ML.)

I'll upload returned mail shortly.
Comment 14 Tomoaki AOKI 2022-10-29 11:21:52 UTC
Created attachment 237704 [details]
Transcript of junchoon@dec.sakura.ne.jp #3

Still blocked. Transcript part is as below.

From: Mail Delivery Subsystem <MAILER-DAEMON>
To: <junchoon@dec.sakura.ne.jp>
Subject: Returned mail: see transcript for details
Date: Sat, 29 Oct 2022 20:12:48 +0900 (JST)

The original message was received at Sat, 29 Oct 2022 20:12:41 +0900 (JST)
from 123-1-88-210.area1b.commufa.jp [123.1.88.210]

   ----- The following addresses had permanent fatal errors -----
<users-jp+help@freebsd.org>
    (reason: 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists)

   ----- Transcript of session follows -----
... while talking to mx1.freebsd.org.:
>>> RCPT To:<users-jp+help@freebsd.org>
<<< 550-5.7.1 Service unavailable; client [153.125.133.21] blocked using DNS-based denylists
<<< 550 5.7.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 29 11:12:48) and client (153.125.133.21).
550 5.1.1 <users-jp+help@freebsd.org>... User unknown
>>> DATA
<<< 554-5.5.1 Error: no valid recipients
<<< 554 5.5.1 in case of permanent delivery errors (e.g. 5XX SMTP errors) please send your problem report from a non-blocked location (e.g. gmail/yahoo) to postmaster@FreeBSD.org and include the following information: time (Oct 29 11:12:48) and client (153.125.133.21).
451 4.4.1 reply: read error from mx1.freebsd.org.
Comment 15 Philip Paeps freebsd_committer freebsd_triage 2022-10-29 11:25:04 UTC
Please try again.  It looks like the allowlist was not picked up automatically.
Comment 16 Tomoaki AOKI 2022-10-29 11:42:21 UTC
(In reply to Philip Paeps from comment #15)

Thanks! Now mail to users-jp+help@freebsd.org was accepted and help mail was sent to me as expected.

I'll report back here if Sakura Internet and/or DTI sent me any feedback.
Comment 17 Philip Paeps freebsd_committer freebsd_triage 2022-10-31 03:07:18 UTC
The Abusix listing for 153.125.133.21 has expired.  The address is still listed in SORBS, but that shouldn't by itself block email.  I'll remove the allowlist entry.

Please reopen this bug if mail still gets blocked.
Comment 18 Tomoaki AOKI 2022-10-31 11:45:38 UTC
(In reply to Philip Paeps from comment #17)

Thanks! Confirmed still OK for ML help request.

Sakura Internet determined which user could causing the blacklist, coped with the user and confirmed dropped from abusix. For SORBS and others they know of, requested for removal.

DTI started investigating the problem. (Now in the process.)

I'll let you know here on updates.

Thanks again!
Comment 19 Tomoaki AOKI 2022-11-02 12:14:19 UTC
(In reply to Philip Paeps from comment #12)

DTI sent me email that they had fixed this issue.
I've sent an email (previously returned one + additional comment) to postmaster@freebsd.org.

If it reaches to anyone on postmaster@, it would mean this is actually fixed.
Currently, the email is not returned, but considering the previous behaviour, it could need 4+ hours if it is not fixed.

I'll comment again here the result if no one notes the arrival of my email within 2 days. (Returned by FreeBSD.org MTA or not.)
Comment 20 Philip Paeps freebsd_committer freebsd_triage 2022-11-02 15:18:20 UTC
Your message reached postmaster@freebsd.org safely.
Glad to hear this was fixed!
Comment 21 Tomoaki AOKI 2022-11-02 21:32:36 UTC
(In reply to Philip Paeps from comment #20)

Thanks!
Confirmed your reply to my email. Now DTI should be OK for mailing to FreeBSD.org.

Thanks for your effort and info to provide to DTI.