Opened 7 years ago

Last modified 18 months ago

#860 assigned Bug / Defect unreachable via SMTP

Reported by: hildeb Owned by: Samuli Seppänen
Priority: minor Milestone:
Component: Community services Version:
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:


From my mailq:

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

(connect to[]:25: Connection timed out)


$ host -t mx 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[]:25: Connection timed out)

trying from another network (

$ telnet -4 25
... connection times out...

Change History (6)

comment:1 Changed 7 years ago by hildeb

This makes it impossible to use email to answer tickets.

comment:2 Changed 7 years ago by 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.

comment:3 Changed 7 years ago by Gert Döring

Owner: set to Samuli Seppänen
Status: newassigned

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".

comment:4 Changed 5 years ago by Gert Döring

@samuli: bump?

comment:5 Changed 5 years ago by Samuli Seppänen

Priority: criticalminor

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

comment:6 Changed 18 months ago by Gert Döring


Note: See TracTickets for help on using tickets.