Symantec Premium Antispam & Domino

HCL Domino Domino Forum
1

We’re running Domino 8.01 with Symantec’s Premium Antispam filtering service - which does work pretty well. I’m not even sure the issue I’m about to describe has anything to do with the spam filter. However, following is a typical mail routing event on our server, as regards outbound mail. Can anyone explain why this happens, and is there a better way to configure the server to avoid it?

06/18/2008 02:42:52 PM Router: No messages transferred to NATIONWIDE.COM (host nefastis.NATIONWIDE.COM) via SMTP: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.

06/18/2008 02:42:57 PM Router: No messages transferred to NATIONWIDE.COM (host mucho.NATIONWIDE.COM) via SMTP: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.

06/18/2008 02:43:02 PM Router: [0000000B] Transferring mail to domain NATIONWIDE.COM (host mucho.NATIONWIDE.COM [155.188.168.11]) via SMTP

06/18/2008 02:43:02 PM Router: Transferred 1 messages to NATIONWIDE.COM (host mucho.NATIONWIDE.COM) via SMTP

06/18/2008 02:43:03 PM Router: Message 006C3232 transferred to mucho.NATIONWIDE.COM for recipient@nationwide.com from Sender/ourdomain Size: 2K via SMTP

2

Subject: SMTP routing

I would be tempted to believe the message. There is a 10 second delay between the messages saying couldn’t and could send the email, this looks like a re-try, ie there was no response to the smtp Helo first time, so the server waited and tried again, this time successfully. I ran SAVDOM for many years as our spam system, without any delay such as this (except for the great “Filter-Hub” debacle). However, it looks as though this server of yours is internet facing, we passed email onto an smtp (symantec again) server beyond the firewall. You could try pinging nationwide.com from the domino server and see if there is any significant delay, if so, it could be with dns resolution, firewall or just plain busy network.

Pete