I am attempting to configure a Domino R6.01 server to work with Hexamail, a anti-spam filtering product. The configuration should be quite simple: install Hexamail, get Domino to listen on port 2500, get Hexamail to listen on port 25, then get Hexamail to forward internal mail to Domino on port 2500. This all works beautifully.
So that Hexamail can build whitelists of known correspondents from outgoing emails, Hexamail recommend you set up your mail server (Domino) to relay all outgoing mail to the Hexamail server, so I’ve set the “Relay host for messages leaving the local internet domain:” field to its own ip address (10.0.0.2), with no port specified, so you’d think it would assume the default smtp port 25. However, it doesn’t!
This is where it seems to get weird. Is it possible that Domino sees 10.0.0.2 in the relay host field, thinks “Ah, that’s one of my addresses, so I’ll just forward it to myself, on port 2500, as that’s the one I’m listening on”? Weirder still, it doesn’t seem to matter which of the following I put in that field:
10.0.0.2
10.0.0.2:25
10.0.0.2,25
Hexamail (an entry in HOSTS pointing to 10.0.0.2)
(How do you correctly specify a port in the relay host field, if indeed you can?)
In each case, it forwards it to itself on port 2500! Why?
In the case of the host name, does that means it’s actually resolving the name, finding it pointing to one of its own addresses, & therefore ‘knowing better’ & sending it to itself? Who would ever want an smtp server to use itself as a relay?
Can anyone help?