[quote user="wolfkin"]the banging on my door is starting to ease up now.... maybe I'll unlock it.[/quote][:)]
Unravelling someone else's undocumented non-standard setup....you should ask for danger money.
Graywall looks like a good solution to the over-abundance of email going through here.
I am using Mercury 4.52 and started up Graywall today.
However, the log file is reporting that everything is coming in through the local IP 127.0.0.1
I am using router forwarding to get email to the Mercury server. Could this be making everything look local?
If not, did I miss something in setup?
All suggestions and ideas are appreciated.
> Graywall looks like a good solution to the over-abundance of email going through here.
> I am using Mercury 4.52 and started up Graywall today.
> However, the log file is reporting that everything is coming in through the local IP 127.0.0.1
> I am using router forwarding to get email to the Mercury server. Could this be making everything look local?
> If not, did I miss something in setup?
> All suggestions and ideas are appreciated.
I suspect that there is something wrong in your router network address translation (NAT) setup that is causing the problem. I use a Linksys router and my NAT of port 25 to host 192.168.1.2 port 25 shows the original IP address of the sending server to both Greywall and the blacklists.
May be something wrong in the Mercury setup....
I am getting double Received: headers. One "by Web1" (name of computer) and one "by FABDOMAIN" (name of Mercury)
SMTP service was turned on ... Turned off Mercury; turned off Service; turned on Mercury ... no activity; turned off Mercury, turned on service, turned on Mercury ... yes activity.
Appears that Mercury will not run while SMTP is on ... there are some IPs being disallowed and the local (127.0.0.1) is allowed. looks like it was setup to bounce off the local SMTP service.
Is there any default values for the IP allow / disallow? I am thinking if I take off all restrictions here, Mercury would start handling the SMTP requests being forwarded by the router.
Does this sound correct?
(( in case you could not tell .. I inherited this and have been tasked with getting it working better ))
Thanks
RESOLVED
Local SMTP service was running. The local service was collecting the email requests and forwarding to Mercury. Mercury was setup to only allow feeds from local (127.0.0.1) and a specific port.
Turned off local service, removed IP restrictions, added port 25 as Alt Port value.
These changes made Mercury the only SMTP service on the station and allowed it to start communicating with the outside world.
Which then passed the proper IP addresses into Graywall.
All up and running now. Thanks for the tidbits. .... the banging on my door is starting to ease up now.... maybe I'll unlock it.
