community.openvpn.net unreachable via SMTP

[hildeb]

From my mailq:

3vpRJs161zzXDr1 4373 Thu Mar 23 00:50:53 Ralf.Hildebrandt@…

(connect to community.openvpn.net[54.241.178.103]:25: Connection timed out)

trac@…

$ host -t mx community.openvpn.net
community.openvpn.net has no MX record

Looking at the logs:
Mar 23 10:39:27 mail-cbf postfix/smtp [64028] : 3vpRJs161zzXDr1: to=<trac@…>, relay=none, delay=35314, delays=35284/0/30/0, dsn=4.4.1, status=deferred (connect to community.openvpn.net[54.241.178.103]:25: Connection timed out)

trying from another network (mail.python.org):

$ telnet -4 community.openvpn.net 25
Trying 54.241.178.103...
... connection times out...

[hildeb]

This makes it impossible to use email to answer tickets.

[Samuli Seppänen]

Yes, port 25 is blocked by design for security reasons on multiple levels. Based on a quick search it looks like ​ MailToTracPlugin is needed for the requested feature to work. So far you're the first person to ask for this, so the demand does not seem very high.

[Gert Döring]

There's two things to it - one is "use mail to reply to tickets" (which I didn't know was an option), the other is "do not send mail from addresses that cannot be replied to", and I think we should get the latter fixed. Like, point the MX to an existing mail system which will accept mail to trac@ and autoreply with "mail replies to tickets are not possible in our setup".

[Gert Döring]

@samuli: bump?

[Samuli Seppänen]

I opened an internal infrastructure ticket about this. I'll lower the priority, though, as this is clearly not a critical issue.

[Gert Döring]

bump?