• Community Support
  • USEnglish

  • Mailcow works perfect, but isn't reachable from some places

Hello,

my mailcow works behind a static IP (IPV4).
I’ve openend the typical ports in the firewall, i’ve made the DNS configuration and server records.

The cow works perfect from the most Networks (Private ISP, Home DSL, Smartphones and so on).
It works with Outlook, Thunderbird and other Mailclients.

But i have the effect, that from some Networks the mailcow isn’t available.
All trys to connect with Imap, Smtp, Web-Config over Port 443 aren’t working.
I get a timout.
For example i’ve set up an email-account on my notebook.
It’s working from everywhere fine, but from some normal ISPs or Networks i don’t get a connection.

A ping to the mailcow works ALWAYS from every network with the DNS-Names and with the static IP.
A traceroute also responds, and i can do a telnet to port 25…telnet ALWAYS answers correct with
“220 mail.xxxxxx.de ESMTP Postcow”.
In the mailcow postfix-Log always see "CONNECT from [“external IP-address”]:63541 to [172.22.1.253]:25″.
But when i try to connect FROM THE SAME network with my mail-software (for example Thunderbird), that works fine from other ISPs and Networks, i get a timeout.

Is it possible that i get this effect because i don’t have the the RDNS / PTR-Entry in my DNS?

Best regards,
Didi

  • The problem is solved, replaced the router with a new one ans everything works fine.
    I think the old Router had problems with newer TLS.

    Thanks for reading.

Meanwhile my ISP has made the PTR-Record for my fixed IP-address.
But that changed nothing.
Mailcow is reachable from the most Networks, but from some other Networks no connection possible.

Has anyone an idea?

    Have something to say?

    Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

    dietherr Not reachable in general or only inaccessible via SMTP/IMAP?

    HTTP/HTTPs works?

      It is perfectly reachable from the most networks: SMTP / IMAP and HTTP / HTTPS.
      From the other “non-working” networks everything is not reachable:

      • no SMTP
      • no IMAP
      • no HTTP / HTTPS

      I don’t know, why.
      The very curious thing is, that from the “non-working” networks there are some other mailcows (4) perfectly reachable.

      As i wrote, in case when no SMTP / IMAP / HTTPS works, a ping and a traceroute surprisingly works perfect.
      Since this morning there is also a correct PTR-Entry redistered.

      The problem is solved, replaced the router with a new one ans everything works fine.
      I think the old Router had problems with newer TLS.

      Thanks for reading.

      No one is typing