Benches Networking

3

Mail Server Ignoring Incoming One IP

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Very strange... and not even sure it is mail server related...

Incoming SMTP (mail server and direct telnet on port 25) from one public IP address is being totally ignored by the mail server.

Router shows a matching SMTP connection from the IP address. If it was being blocked or refused, the router logs would say so. There is no black-listing feature on router. Router has been restarted.

All other SMTP connections in router logs (around that one IP) are being logged as normal at the mail server (log level: Information). But nothing at all from that one IP. Apart from that, server is not displaying anything untoward.

I'm just about to up the level of server logging but throwing it open for any ideas meantime...

Ta.
-david

3 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Update...

    PacketStream running on the server does not log any SMTP traffic with that IP. All other connections are being logged by PacketStream. Very odd. Looks like router - will concentrate there.

    -david

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    David,

    this sounds definitely like a router/network/firewall issue.
    Assuming the logging level is at lease set to "Information", Postfix would show rejected connections.

    Any PIX routers involved?

    Alex

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Alex,

    Not a PIX, just a plain Netgear DG834N - no blacklisting function. Packet sniffer confirms no SMTP traffic at server with that originating IP but router logs show incoming. Network configuration precludes any further diagnostics (e.g., between server and router (dumb 100M Netgear switch) or before router - but then I'm not really a network level expert anyway so might be missing a trick) and I'm doing this remotely, too. A telnet test from troublesome IP to another (different location) server with same router model connected OK. Very strange but next logical step is just to swap out the router and take it from there. What is it Sherlock Holmes says?... "When you have eliminated the impossible, whatever remains, however improbable, must be the truth."

    Hope everything's hunky-dory with you. I must come visit here more often!

    -david