Mail2.ecloud.global does not work with freenet.de

[Aki]

Hello,

I got an email from freenet.de. I replied to this email and get a mailer daemon.

Undelivered Mail Returned to Sender

This is the mail system at host mail2.ecloud.global.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<xxx@freenet.de>: host emig.freenet.de[2001:748:100:40::8:117] said:
    550-Inconsistent/Missing DNS PTR record (RFC 1912 2.1)
    (mail2.ecloud.global) 550 [2a01:4f9:4b:5387:d00b::2]:35058 (in reply to
    RCPT TO command)

I cross checked with an other email provider. I can write emails to the same account (freenet.de) without any problems or error messages.

I also created an issue, but unfortunately I don’t know where I should create it. So I chose “mailstack-automx”.
https://gitlab.e.foundation/e/infra/docker-mailstack/-/issues/3

[tcecyk]

Problem with sending mails to e.g. freenet: 550-Inconsistent/Missing DNS PTR record (RFC 1912 2.1)

the ptr really is inconsistent. The subnet address d00b within 2a01:4f9:4b:5387::2/64 is pointing to mail.ecloud.global instead of mail2, where the first address within that /64 range is pointing. I think it’s an oversight. Depending on product, it isn’t easy to decleare a ptr for a whole cidr. I guess I’d fix the mis pointer at :d00b::2 if its a stable address. You can forward your mail response to postmaster@ecloud.global - very likely it directly reaches a person doing mail+dns

@arnauvp I think you’d need to review the ipv6 ptr on mail2

@Aki if nothing happens, either the postmaster mail in the linked answer or forward this forum link to helpdesk@e.email

[Manoj]

Hi @Aki pl can you send the issue details on the helpdesk@e.email ID. The infra team members there would be able to help you further.

[diroots.e]

@Aki @tcecyk this should now be fixed.