Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Shut down after relay attempts

Status
Not open for further replies.

gbaker

MIS
Nov 27, 2001
77
US
Every few days my Mercury server shuts down with a Dr. Watson error: "he application, , generated an application error The error occurred on 10/24/2002 @ 18:10:43.295 The exception generated was c0000005 at address 004534A7 (__unlockDebuggerData$qv) "
Going through the Mercury logs, this coincides with rather large relay attempts. I have the server set so that only authenticated users may relay mail, and a killfile for senders that I've found. It seems that the server is just getting overwhelmed by the relay attempts and says 'nuff's 'nuff, I'm outta here.
Does anyone have similar experiences with this, and if so, any workarounds?
 
gbaker

I'm experiencing relay attempts almost every day in large numbers (>100 per night) but never had a crash because of that.
Which version of Mercury are you running?
How did you set up Mercury to prevent relaying?
Do you have users outside of your network that must use MercuryS?

SteelBurner
 
SteelBurner,

I'm using ver. 3.32 and restricting relaying by 'Only Authenticated Users May Relay Mail' as well as adding SPAMMERS to the killfile, which doesn't even start to process the message, just bounces it.
Yes, I have users outside of the network that need access to this (~50).
I'm almost at the point of running a daemon to check if it's still running.
 
gbaker,

Your "outside" users have static IPs or do they get their IP when dialing in to the ISP?

You might look for an entry like "allow 0.0.0.0" in MercuryS - remove it. How about cutting and pasting the [MercuryS] section of your MERCURY.INI?

SteelBurner
 
gbaker,

in MercuryS on the Compliance tab you can set Limit maximum number of failed RCPT commands to 4 and Limit maximum number of relay attempts to 4. This will keep relaying attempts out of the Mercury processing queue.

These are some of the settings I use on many of our Mercury installations.

SteelBurner
 
Thanks for the advice. Here's the MercuryS section of the .ini file:

Debug : 1
Logfile : D:\MERCURY\Logs\MERCURYS.LOG
Timeout : 30
Relay : 0
Strict_Relay : 1
Allow_Illegals : 0
SMTP_Authentication : 3
Auth_File : auth.mer
Killfile : killfile.txt
Session_logging : D:\mercury\logs\sessionlogs
Session_logmode : 0
Compliance_Settings : 128
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4

I believe this should do the job.
Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top