|
|
Browse by Tags
All Tags » MercuryS » spam » mercury/32 (RSS)
-
Can't connect to 213.180.114.52 on port 25: Timed out
Firewall? TCP port 25 incoming needs to be opened. Check your router. Check your software firewall configuration. In the Windows firewall, allow mercury.exe.
Tip: if you only have one mail server, it is easy to do away with a large volume of ...
-
Greenman:
I don't understand how Mercury was able to accept the mail from 61.145.143.171 when it is outside the allowed range of IP addresses. Am I missing something here?
Is there any further configuration I need to carry out to ensure that Mercury only accepts SMTP connections from the allowed ranges?
It's not clear ...
-
There is absolutely no necessity to get complicated. The more complicated the solution, the more difficult it is to implement. And few of the ''anti-spam technologies'' tackle the problem where it occurs, which is actually where it must be tackled. Once it gets past the SMTP layer, i.e. at the mail clients, all the ''anti-spam technologies'' are ...
-
Hi all !
I'm evaluating SpamHalter 4.3.1.383 with Mercury/32 4.52.
I'm experiencing some problems with the ''Is SPAM without classification'' settings.
1) Block messages with headers
MercuryS in configured for quering an RBL server and tag matched messages, and this works (it adds ''X-Blocked: ...'' to matched messages).
SpamHalter is ...
|
|
|