[quote user="lwells"]Strange here too: Not sure what I did to break it?

Mercury v4.62 CPU useage starts out ok then pegs and stays at 99%.

Might be a bad message in the queue or a problem connection with MercuryE for sending mail.  Since you are using MercuryD it also could be a huge message file on the POP3 host.

Mercury is installed on a folder on a Netware 5.1 sp8 server and run from an XP Pro sp2 workstation.
Netware clients tried 4.83sp2 , 4.91 sp4, 4.91 sp5.

2 different workstations running XP pro sp2 become unbearably slow.

1 XP Home seems ok but CPU is still at 99% for Mercury.

XP- home still seems to run ok but CPU =90%

A partial WireShark packet trace (which is over my head) shows some questionable packets: <shapetype id="_x0000_t75" coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"> </shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[   69 08:41:27.729190 192.168.1.68 192.168.1.195 NCP C Search for: Mercury]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"></shapetype>[  <shapetype id="_x0000_t75" coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"> 70 08:41:27.729469 192.168.1.195 192.168.1.68 NCP R <b>No matching files or directories were found</b>]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[  71 08:41:27.729537 192.168.1.68 192.168.1.195 NCP C Search for: Mercury]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[  72 08:41:27.729883 192.168.1.195 192.168.1.68 NCP R OK]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[  93 08:41:27.736452 192.168.1.68 192.168.1.195 NCP C Obtain Info for: APPS/MERCURY/MERCURY.EXE:ZONE.IDENTIFIER]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[  94 08:41:27.736785 192.168.1.195 192.168.1.68 NCP R No matching files or directories were found]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"> </shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">Merury.ini</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[General]<br>myname:          tomcotexas.com    # Canonical name for this server<br>timezone:        -0600    # Time Zone to add to date fields<br>file_api:        1    # Use the file api instead of queues<br>mailqueue:       <a href="file://TOMCO1/SYS/SMTPMAIL" mce_href="file://TOMCO1/SYS/SMTPMAIL">\\TOMCO1\SYS\SMTPMAIL</a>    # Where mail should be put for delivery<br>smtpqueue:       <a href="file://TOMCO1/SYS/SMTPMAIL" mce_href="file://TOMCO1/SYS/SMTPMAIL">\\TOMCO1\SYS\SMTPMAIL</a>    # Where the SMTP client should look for mail<br>secondary_queue: <a href="file://TOMCO1/sys/SMTPMAIL" mce_href="file://TOMCO1/sys/SMTPMAIL">\\TOMCO1\sys\SMTPMAIL</a></shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Protocols]<br>MERCURYS.DLL<br>MERCURYP.DLL<br>MERCURYE.DLL<br># MERCURYC.DLL<br>MERCURYD.DLL<br># MERCURYH.DLL<br># MERCURYF.DLL<br># MERCURYW.DLL<br># MERCURYX.DLL<br># MERCURYI.DLL<br># MERCURYB.DLL</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Mercury]<br>failfile:      <a href="file://tomco1/main/apps/mercury/Mercury/FAILURE.MER" mce_href="file://tomco1/main/apps/mercury/Mercury/FAILURE.MER">\\tomco1\main\apps\mercury\Mercury\FAILURE.MER</a>    # Delivery failure notification template<br>aliasfile:     <a href="file://tomco1/main/apps/mercury/Mercury/ALIAS.MER" mce_href="file://tomco1/main/apps/mercury/Mercury/ALIAS.MER">\\tomco1\main\apps\mercury\Mercury\ALIAS.MER</a>    # System-wide alias file<br>synfile:       <a href="file://tomco1/main/apps/mercury/SYNONYM.MER" mce_href="file://tomco1/main/apps/mercury/SYNONYM.MER">\\tomco1\main\apps\mercury\SYNONYM.MER</a>    # User synonym database<br>listfile:      <a href="file://tomco1/main/apps/mercury/Mercury/LISTS.MER" mce_href="file://tomco1/main/apps/mercury/Mercury/LISTS.MER">\\tomco1\main\apps\mercury\Mercury\LISTS.MER</a>    # List of lists<br>logfile:       <a href="file://tomco1/main/apps/mercury/mercury.log" mce_href="file://tomco1/main/apps/mercury/mercury.log">\\tomco1\main\apps\mercury\mercury.log</a>    # Traffic logging file<br>logwidth:      30    # Width of address fields in logfile<br>retpath:       1    # Do/Don't use 'return-path' for errors<br>maxhops:       15    # Used to detect mailing loops<br>gullible:      0    # If NZ, don't validate 'From' fields<br>poll:          80   # Seconds between queue polling cycles<br>scratch:       <a href="file://tomco1/main/apps/mercury/Scratch" mce_href="file://tomco1/main/apps/mercury/Scratch">\\tomco1\main\apps\mercury\Scratch</a>    # Where we can write temp files</shapetype>

 

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">returnlines:   20    # How many lines of failed messages to return<br>postmaster:    lwells    # NetWare UIC of postmaster<br>broadcast:     0    # Yes, we want broadcast notifications, but<br>receipts:      0    # ... no broadcasts for receipt confirmations<br>PM_notify:     1    # Do/Don't send errors to the postmaster<br>change_owner:  1    # Change message ownership to recipient<br>auto_tzone:    1    # If NZ, obtain timezone information from OS<br>LogLevel:      10    # System message reporting level<br>LogMax:        100    # Maximum number of system messages to store<br>RetryPeriod:   4    # Period between job retries (minutes)<br>MaxRetries:    4    # Maximum number of times a job can fail<br>TwoPasses:     1    # If NZ, process submission queue in 2 passes<br>Autoaddress:   -128    # If NZ, auto-generate user addresses based on name<br>Daily_exit:    1    # If NZ, auto-restart each day after maintenance<br>No_Areply:     1    # If NZ, disable automatic replies system-wide<br>Alt_Forward:   0    # If NZ, allow alternate forwarding specification<br>Maint_hour:    23    # Hour for daily maintenance (24-hour clock)<br>Maint_min:     0    # Minute for daily maintenance<br>Retry_Mode:    0    # If NZ, use progressive backoff for queue retries<br>Local_DSNs:    0    # If NZ generate Delivery Status for local users only<br>DSN_time1:     10800    # Seconds deferred before first DSN is sent<br>DSN_time2:     86400    # Seconds deferred before second DSN is sent<br>DSN_time3:     259200    # Seconds deferred before third DSN is sent<br>Host_in_title: 1    # If NZ, show hostname in system tray and taskbar<br>Lingering:     0    # Enable or disable 'lingering mailboxes'<br>Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down<br>Alert_Host:    notify.pmail.com    # Host to check for licensee advisories<br>Alert_Interval: 720   # Frequency in minutes (min 240) for checks<br>Alert_Flags:   3    # Flags controlling advisory checks</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryC]<br>Host : mail.tomcotexas.com<br>Failfile : <a href="file://tomco1/main/apps/mercury/Mercury/FAILURE.MER" mce_href="file://tomco1/main/apps/mercury/Mercury/FAILURE.MER">\\tomco1\main\apps\mercury\Mercury\FAILURE.MER</a><br>Poll : 120<br>Scratch : <a href="file://tomco1/main/apps/mercury/Mercury" mce_href="file://tomco1/main/apps/mercury/Mercury">\\tomco1\main\apps\mercury\Mercury</a><br>ReturnLines : 15<br>Timeout : 180<br>ESMTP : 1<br>Server_Port : 1025<br>SMTP_Username: <a href="mailto:xxxxxx@tomcotexas.com" mce_href="mailto:xxxxxx@tomcotexas.com">xxxxxx@tomcotexas.com</a><br>SMTP_Password: xxxxxx<br>POP3_Auth : 1<br>POP3_Host : mail.tomcotexas.com<br>POP3_Port : 1025<br>Logfile : MercCLog<br>Log_Verbose : 0<br>Session_logging : c:\temp<br>Session_logmode : 1</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryE]<br>Poll : 15<br>Timeout : 300<br>Nameservers : 68.94.156.1,68.94.157.1<br>Log_Verbose : 1<br>DNS_Timeout : 190<br>DNS_Retries : 5<br>Transcripts : 1<br>MaxThreads : 10</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryD]<br>Scratch : <a href="file://tomco1/main/apps/mercury/Mercury" mce_href="file://tomco1/main/apps/mercury/Mercury">\\tomco1\main\apps\mercury\Mercury</a><br>Timeout : 320<br>Poll : 240<br>Session_logging : c:\mercD.log<br>Session_logmode : 0</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryS]<br>Debug : 1<br>HELO : Mercury<br>Logfile : MercS.log<br>Timeout : 300<br>Relay : 0<br>Strict_Relay : 0<br>Server_Port : 1025<br>Interface : 192.168.1.170<br>Allow_Illegals : 0<br>SMTP_Authentication : 0<br>Auth_File : tomco<br>Session_logging : c:\temp<br>Session_logmode : 1<br>Compliance_Settings : 512<br>Maximum_Failed_Rcpts : 4<br>Max_Relay_Attempts : 4<br>SSL_Mode : 0<br>ST_Blacklisting : 0<br>No_VRFY : 0<br>SMTP_ConnFlags : 0</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryP]<br>Scratch : <a href="file://tomco1/main/apps/mercury/Mercury" mce_href="file://tomco1/main/apps/mercury/Mercury">\\tomco1\main\apps\mercury\Mercury</a><br>Logfile : MercPLog<br>Stack : 32768<br>Mark_Read : 1<br>SSL_Mode : 0<br>Login_Disabled : 0<br>UIDL_nul_list : 1<br>New_UIDs : 0<br>No_NUL_passwords : 1<br>Session_logging : c:\temp<br>Session_logmode : 0<br>Timeout : 180</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryX]<br>Cmd_Delay: 5<br>Cmd_Wait: 1<br>IE4_Dialling: 0<br>Use_ETRN: 0<br>Clients_only: 1<br>Drain_queues: 1<br>Sunday: 0900,1000,720,120,720,120<br>Monday: 0400,1845,0,0,500,30<br>Tuesday: 0440,1800,0,0,500,30<br>Wednesday: 0500,1900,0,0,500,30<br>Thursday: 0500,1745,0,0,500,30<br>Friday: 0500,1800,0,0,500,30<br>Saturday: 0700,1700,0,0,500,30</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Domains]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Maiser]<br>Maiser:          Maiser   # 'Username' of mail server account<br>Helpfile:        <a href="file://tomco1/main/apps/mercury/Mercury/MAISER.HLP" mce_href="file://tomco1/main/apps/mercury/Mercury/MAISER.HLP">\\tomco1\main\apps\mercury\Mercury\MAISER.HLP</a>   # Help sent on failed maiser requests<br>Lookupfile:      <a href="file://tomco1/main/apps/mercury/Mercury/MAISER.LKP" mce_href="file://tomco1/main/apps/mercury/Mercury/MAISER.LKP">\\tomco1\main\apps\mercury\Mercury\MAISER.LKP</a>   # Format file for the 'lookup' command<br>Send_dir:        <a href="file://tomco1/main/apps/mercury/SENDABLE" mce_href="file://tomco1/main/apps/mercury/SENDABLE">\\tomco1\main\apps\mercury\SENDABLE</a>   # Directory for the 'send' command<br>Logfile:         <a href="file://tomco1/main/apps/mercury/Logs/MAISER.LOG" mce_href="file://tomco1/main/apps/mercury/Logs/MAISER.LOG">\\tomco1\main\apps\mercury\Logs\MAISER.LOG</a>   # Mail server log file<br>Notify:          <a href="file://tomco1/main/apps/mercury" mce_href="file://tomco1/main/apps/mercury">\\tomco1\main\apps\mercury</a>   # Dir. for pending 'notify' commands<br>NoList:          Y   # If 'Y', disable the 'list' command<br>Local_only:      N   # If 'Y', local 'notify' commands only</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Groups]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Rewrite]</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[Statistics]<br>StatFlags:    0  # Statistical reporting settings<br>STF_Hours:    24  # How often to write stat log files<br>STM_Hours:    24  # How often to e-mail stat log files</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">[MercuryH]<br>Timeout : 30</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75"><br>I am running out of hammers, and am missing something simple?</shapetype>

<shapetype coordsize="21600,21600" stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75">Larry Wells</shapetype>

<stroke joinstyle="miter"></stroke><formulas><f eqn="if lineDrawn pixelLineWidth 0"></f><f eqn="sum @0 1 0"></f><f eqn="sum 0 0 @1"></f><f eqn="prod @2 1 2"></f><f eqn="prod @3 21600 pixelWidth"></f><f eqn="prod @3 21600 pixelHeight"></f><f eqn="sum @0 0 1"></f><f eqn="prod @6 1 2"></f><f eqn="prod @7 21600 pixelWidth"></f><f eqn="sum @8 21600 0"></f><f eqn="prod @7 21600 pixelHeight"></f><f eqn="sum @10 21600 0"></f></formulas><path o:connecttype="rect" gradientshapeok="t" o:extrusionok="f"></path><lock aspectratio="t" v:ext="edit"></lock>[/quote]

Since a few days I notice that Mercury is constantly taking 99% CPU usage, even without any traffic. I didn't notice this before and I'm wondering if this is normal. I run Mercury 4.62 on a Windows 2003 server, using Firedeamon to have it as a service. I only installed Spamhalter as an extra deamon, removed both Clamav and AVG a couple of weeks ago after having some problems with performance.

Anybody having any clue what might cause this?

 Marko

[quote user="mazeland"]

Since a few days I notice that Mercury is constantly taking 99% CPU usage, even without any traffic. I didn't notice this before and I'm wondering if this is normal. I run Mercury 4.62 on a Windows 2003 server, using Firedeamon to have it as a service. I only installed Spamhalter as an extra daemon, removed both Clamav and AVG a couple of weeks ago after having some problems with performance.

Anybody having any clue what might cause this?

Not at all sure why this is happening. 

What protocols are you running?

What happens when you restart Mercury?[/quote]

Additionally, try starting the program normally without using Firedaemon to make sure it's not related to that. Mercury should use extremely little CPU time when idle.

/Rolf 

Thank you for your answer!

In fact this virtual server does nothing else then handling Mercury. The first 90 seconds after a restart the CPU % is around 0, but the moment the pop3 client starts to pick up mail from various accounts, the CPU % goes to 99%. I checked the and all paths over and over, but with no succes.

I'll give it a try without Firedeamon and see what happens there.

I switched off Firedeamon and started Mercury thru the loader.exe. No difference here, after about 90 secs up to 99% CPU. I did a new install in the current Mercury directory, also no difference. I guess I'm close to the point where I have to start an new fresh Win2K3 server?

Marko

[quote user="mazeland"]

pop3 client starts to pick up mail from various accounts, the CPU % goes to 99%.

[/quote]

I would disable all POP3 accounts in MercD then reenable one at a time to find the one causing the problem.

Turn on session logging for MercD to get a transcript of all traffic. It may be an SSL related issue with one or more accounts.

Even if I swith off MercuryD totally, it doesn't change the situation, so obviously it is not the POP3 Client causing the problem. Anyway, the POP3 logging didn't show any problems.

I did check everything in detail, also all logfiles, but cannot find any clue. I even moved Mercury to a clean Win2K3 server, but still have this 99% CPU.

Would it be clever to move back to a version before 4.62 or is there a newer version that I could try?

[quote user="mazeland"]Even if I swith off MercuryD totally, it doesn't change the situation, so obviously it is not the POP3 Client causing the problem. Anyway, the POP3 logging didn't show any problems.

I did check everything in detail, also all logfiles, but cannot find any clue. I even moved Mercury to a clean Win2K3 server, but still have this 99% CPU.

What happens if you pause all the modules?

Would it be clever to move back to a version before 4.62 or is there a newer version that I could try?

I doubt if this would change anything.  There is something basic wrong in the setup (or the system) that is causing the problem.  Most of the time this is caused by getting Winsock operations blocked but it can be other things as well.

[/quote]

No problem.

Here is my Mercury.Ini:

#  MERCURY.INI generated by Mercury Setup
#
#
#  Sample Bindery Mode MERCURY.INI file (in fact, the one I use on
#  my production server). This one implements most of the possible
#  switches for each module, but you can edit it to do less if you
#  wish. All the fields shown below are described in the file
#  MGUIDE.HLP which is supplied in the Mercury archive.
#
#  Anything after a '#' to the end of the line is a comment and
#  is stripped out before parsing. Trailing and leading whitespace
#  is also stripped before parsing. Many sample commands have been
#  left in this file commented out for reference purposes.
#

[General]
myname:          feif.org    # Canonical name for this server
timezone:        +0100    # Time Zone to add to date fields
file_api:        1    # Use the file api instead of queues
mailqueue:       D:\MERCURY\QUEUE    # Where mail should be put for delivery
smtpqueue:       D:\MERCURY\QUEUE    # Where the SMTP client should look for mail
newmail_path:    D:\MERCURY\MAIL\~N    # Where to find the users' WinPMail mailboxes.

[Protocols]
MERCURYS.DLL
MERCURYP.DLL
# MERCURYE.DLL
MERCURYC.DLL
MERCURYD.DLL
# MERCURYH.DLL
# MERCURYF.DLL
# MERCURYW.DLL
# MERCURYX.DLL
MERCURYI.DLL
# MERCURYB.DLL

[Mercury]
failfile:      D:\MERCURY\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   D:\MERCURY\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     D:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file
synfile:       D:\MERCURY\Mercury\SYNONYM.MER    # User synonym database
listfile:      D:\MERCURY\Mercury\LISTS.MER    # List of lists
logfile:       D:\MERCURY\Logs\System.Log    # Traffic logging file
logwidth:      30    # Width of address fields in logfile
retpath:       1    # Do/Don't use 'return-path' for errors
maxhops:       15    # Used to detect mailing loops
gullible:      0    # If NZ, don't validate 'From' fields
bitnethost:    cunyvm.cuny.edu    # Relay host for '.bitnet' rewrites
poll:          60   # Seconds between queue polling cycles
scratch:       D:\MERCURY\Scratch    # Where we can write temp files
returnlines:   15    # How many lines of failed messages to return
postmaster:    glitnir    # NetWare UIC of postmaster
broadcast:     0    # Yes, we want broadcast notifications, but
receipts:      0    # ... no broadcasts for receipt confirmations
PM_notify:     0    # Do/Don't send errors to the postmaster
change_owner:  0    # Change message ownership to recipient
hard_quit:     49    # If NZ, quit only on Ctrl+File|Exit
auto_tzone:    1    # If NZ, obtain timezone information from OS
LogLevel:      10    # System message reporting level
LogMax:        100    # Maximum number of system messages to store
RetryPeriod:   15    # Period between job retries (minutes)
MaxRetries:    16    # Maximum number of times a job can fail
TwoPasses:     0    # If NZ, process submission queue in 2 passes
Autoaddress:   -128    # If NZ, auto-generate user addresses based on name
Daily_exit:    1    # If NZ, auto-restart each day after maintenance
No_Areply:     0    # If NZ, disable automatic replies system-wide
Alt_Forward:   1    # If NZ, allow alternate forwarding specification
Maint_hour:    2    # Hour for daily maintenance (24-hour clock)
Maint_min:     55    # Minute for daily maintenance
Retry_Mode:    1    # If NZ, use progressive backoff for queue retries
Local_DSNs:    1    # If NZ generate Delivery Status for local users only
DSN_time1:     10800    # Seconds deferred before first DSN is sent
DSN_time2:     86400    # Seconds deferred before second DSN is sent
DSN_time3:     259200    # Seconds deferred before third DSN is sent
Host_in_title: 0    # If NZ, show hostname in system tray and taskbar
Lingering:     0    # Enable or disable 'lingering mailboxes'
Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down
Alert_Host:    notify.pmail.com    # Host to check for licensee advisories
Alert_Interval: 720   # Frequency in minutes (min 240) for checks
Alert_Flags:   3    # Flags controlling advisory checks

[MercuryC]
Host : smtp.xs4all.nl
Failfile : D:\MERCURY\Mercury\FAILURE.MER
Poll : 30
Scratch : D:\MERCURY\Scratch
ReturnLines : 15
Timeout : 60
ESMTP : 1
SMTP_Username: *****
SMTP_Password: ************
POP3_Auth : 0
POP3_Host : pop.xs4all.nl
Logfile : D:\MERCURY\Logs\MERCURYC.LOG
Log_Verbose : 1
Session_logging : D:\MERCURY\LOGS
Session_logmode : 1

[MercuryE]
HELO : mx.glitnir.nl
Session_logging : D:\MERCURY\LOGS
Session_logmode : 1
Poll : 60
Timeout : 30
Nameservers : 195.121.1.34,195.121.1.66
Logfile : smtpe.log
Log_Verbose : 1
DNS_Timeout : 30
DNS_Retries : 4
Transcripts : 1
MaxThreads : 10

[MercuryD]
Scratch : D:\MERCURY\Scratch
Timeout : 30
Poll : 180
Session_logging : D:\Mercury\Logs
Session_logmode : 0

[MercuryS]
Debug : 1
HELO : mx.glitnir.nl
Logfile : D:\MERCURY\Logs\MERCURYS.LOG
Timeout : 30
Relay : 0
Strict_Relay : 1
Alt_Server_Port : 5325
Allow_Illegals : 0
SMTP_Authentication : 3
Auth_File : smtprelay.mer
Session_logging : D:\Mercury\Logs
Session_logmode : 1
Compliance_Settings : 800
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 0
No_VRFY : 0
SMTP_ConnFlags : 0

[MercuryP]
Scratch : D:\MERCURY\Scratch
Logfile : D:\MERCURY\Logs\MERCURYP.LOG
Stack : 32768
Mark_Read : 1
SSL_Mode : 0
Login_Disabled : 0
UIDL_nul_list : 1
New_UIDs : 1
No_NUL_passwords : 1
Session_logging : D:\MERCURY\Logs
Session_logmode : 1
Timeout : 60

[MercuryX]
Cmd_Wait: 1
IE4_Dialling: 0
Use_ETRN: 0
Clients_only: 0
Drain_queues: 1
Sunday: 0000,0000,0,0,0,0
Monday: 0000,0000,0,0,0,0
Tuesday: 0000,0000,0,0,0,0
Wednesday: 0000,0000,0,0,0,0
Thursday: 0000,0000,0,0,0,0
Friday: 0000,0000,0,0,0,0
Saturday: 0000,0000,0,0,0,0

[Domains]
feif: feif.org
feif: feif
glitnir: glitnir.nl
glitnir: glitnir

[Maiser]
Maiser:          mailserver   # 'Username' of mail server account
Helpfile:        D:\MERCURY\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      D:\MERCURY\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        D:\MERCURY\SENDABLE   # Directory for the 'send' command
Logfile:         D:\MERCURY\Logs\MAISER.LOG   # Mail server log file
Notify:          D:\MERCURY\TMP   # Dir. for pending 'notify' commands
NoList:          Y   # If 'Y', disable the 'list' command
Local_only:      Y   # If 'Y', local 'notify' commands only

[MercuryH]
Logfile              :     D:\MERCURY\Logs\MERCURYH.LOG
# Addressbook : \\CLIO\SYS\SYSTEM\MERCURY\PH.PMR
# MOTD : \\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT
# Administrator : postmaster@clio.pmail.gen.nz
Timeout : 30

[MercuryI]
Scratch : D:\MERCURY\SCRATCH
Logfile : D:\MERCURY\Logs\imap4.log
Timeout : 120
Server_Port : 143
Charset : ISO-8859-1
Session_logging : D:\MERCURY\Logs
Session_logmode : 1
Idle_Timeout : 1800
SSL_Mode : 0
Login_Disabled : 0
No_NUL_passwords : 1

[MercuryB]
Scratch : D:\MERCURY\SCRATCH
Logfile : http.log
Timeout : 120
Server_Port : 8080
Idle_Timeout : 1800
URL_Base : glitnir.nl

[Groups]

[Rewrite]

[Statistics]
StatFlags:    19  # Statistical reporting settings
StatFiles:    D:\Mercury\Logs  # Directory to write stat log files
StatMail:     glitnir@glitnir.nl  # Address to send stat log files
STF_Hours:    24  # How often to write stat log files
STM_Hours:    24  # How often to e-mail stat log files

Hi Thomas,

I did upload the Ini file. May I kindly ask you to have a look at it, to see if there are any abnormalities?

Thank you in advance,

Marko

[quote user="mazeland"]Hi Thomas,

I did upload the Ini file.

I got the mercury.ini file via e-mail but when I clicked on the URL it came back with "Forum not found"

May I kindly ask you to have a look at it, to see if there are any abnormalities?

Looks normal to me, I would change the domains section from

[Domains]
feif: feif.org
feif: feif
glitnir: glitnir.nl
glitnir: glitnir

to

[Domains]
feif: feif.org
feif: feif
feif: glitnir.nl
feif: glitnir

since there can only be one server unless running multiple Netware servers.

The only thing that I can see that could cause the 99% would be that one of the connections was hanging.  I would try pausing MercuryD and MercuryC one at a time on start up to see what happens.   If nothing changes then I'd do this with the MercuryI as well.  You really need to see which of these are causing the problem.

Thank you in advance,

Marko[/quote]

Hi Thomas,

I ended up switching off all modules and spamhalter, so only Mercury self would run. The same still happens, 99% cpu. So I guess I'll have to go through the settings of Mercury itself to see what could be changed there. I also did a re-install, no changes there. Any suggestions for a tool I could use to analyse this?

Marko

I ended up switching off all modules and spamhalter, so only Mercury

self would run. The same still happens, 99% cpu.

So I guess I'll have

to go through the settings of Mercury itself to see what could be

changed there. I also did a re-install, no changes there. Any

suggestions for a tool I could use to analyse this?

Hi Thomas,

Finally traced down the problem. As it was clear that it had to do with Mercury.Ece, I checked all folders and file settings in Mercury.Ini once more. What came out is the following:

Helpfile:        D:\MERCURY\MERCURY\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      D:\MERCURY\MERCURY\MAISER.LKP   # Format file for the 'lookup' command
Both files were in D:\MERCURY\ in the past, I moved them to D:\MERCURY\MERCURY\

Couldn't find any remark about this in any log file or event.

Thank you for your support! Hope to give it back tom other users at another moment.

Marko

I have the same problem with Mercury 4.62 (integrated with XAMPP) connecting to google. I checked the config a 100 times, but every time Mercury connects with gmail, it hangs when the STARTTLS session is started.

 The process gets locked and can not be killed.

Session logs show:

21:32:07.727: --- Mon Apr 27 21:32:07 2009 ---
21:32:07.777: Connect to 'smtp.gmail.com', timeout 30.
21:32:08.919: >> 220 mx.google.com ESMTP l12sm293736fgb.24<cr><lf>
21:32:08.919: << EHLO mailaddress@gmail.com<cr><lf>
21:32:08.949: >> 250-mx.google.com at your service, [81.245.201.78]<cr><lf>
21:32:08.949: >> 250-SIZE 35651584<cr><lf>
21:32:08.949: >> 250-8BITMIME<cr><lf>
21:32:08.949: >> 250-STARTTLS<cr><lf>
21:32:08.949: >> 250-ENHANCEDSTATUSCODES<cr><lf>
21:32:08.949: >> 250 PIPELINING<cr><lf>
21:32:08.009: << STARTTLS<cr><lf>
21:32:08.039: >> 220 2.0.0 Ready to start TLS<cr><lf>

 and then the CPU runs between 96 and 98%. The only way to kill it is by rebooting.

Anyone has a helpful suggestion?

TIA,
MM

[quote user="MadMad"]

I have the same problem with Mercury 4.62 (integrated with XAMPP) connecting to google.

Based on what I've seen of the XAMPP install I suspect that there is something not properly configured in Mercury/32.  

I checked the config a 100 times, but every time Mercury connects with gmail, it hangs when the STARTTLS session is started.

I've got a Mercury/32 test setup running here with GMail as the relay host that works quite well.  Either of these should work.

(b) -SMTP STARTTLS -

  Server host name: smtp.gmail.com
  Connection port/type:  587 SSL encryption via STARTTLS command
  Credentials for SMTP Authentication: Login username: GMail username@gmail.com Password: GMail password

(c) - SMTP via SSL -

  Server host name: smtp.gmail.com
  Connection port/type: port: 465   SSL encryption via direct SSL connection
  Credentials for SMTP Authentication: Login username: GMail username@gmail.com Password: GMail password
 
 

 The process gets locked and can not be killed.

 

Session logs show:

21:32:07.727: --- Mon Apr 27 21:32:07 2009 ---
21:32:07.777: Connect to 'smtp.gmail.com', timeout 30.
21:32:08.919: >> 220 mx.google.com ESMTP l12sm293736fgb.24<cr><lf>
21:32:08.919: << EHLO mailaddress@gmail.com<cr><lf>
21:32:08.949: >> 250-mx.google.com at your service, [81.245.201.78]<cr><lf>
21:32:08.949: >> 250-SIZE 35651584<cr><lf>
21:32:08.949: >> 250-8BITMIME<cr><lf>
21:32:08.949: >> 250-STARTTLS<cr><lf>
21:32:08.949: >> 250-ENHANCEDSTATUSCODES<cr><lf>
21:32:08.949: >> 250 PIPELINING<cr><lf>
21:32:08.009: << STARTTLS<cr><lf>
21:32:08.039: >> 220 2.0.0 Ready to start TLS<cr><lf>

 and then the CPU runs between 96 and 98%. The only way to kill it is by rebooting.

 

Anyone has a helpful suggestion?

TIA,
MM

[/quote]

Thanks Thomas.

Those are the same settings as I have.

Then I must have missed something in the .ini file.
Didn't seem anything wrong with the instructions in

http://www.zoe.vc/2008/mercury-mail-transport-system-fur-externe-mail-konfigurieren/?lan=english

TIA,
MM

Thanks Thomas.

Those are the same settings as I have.

Then I must have missed something in the .ini file.

Here's my MercuryC setup with username and password munged.  

[MercuryC]
Host : smtp.gmail.com
Failfile : C:\MERwin\Mercury\FAILURE.MER
Poll : 10
Scratch : C:\MERwin\Mercury
ReturnLines : 15
Timeout : 60
ESMTP : 1
Server_Port : 587
SMTP_Username: ************@gmail.com
SMTP_Password: *********
SMTP_ConnFlags : 4
POP3_Auth : 0
Logfile : c:\merwin\logs\mercuryc\mc~y~m~d.log
Log_Verbose : 1
Session_logging : c:\merwin\logs\mercuryc
Session_logmode : 0

and here's the MercuryC session log with username and password removed.

19:25:36.843: --- Mon Apr 27 19:25:36 2009 ---
19:25:36.859: Connect to 'smtp.gmail.com', timeout 60.
19:25:37.906: >> 220 mx.google.com ESMTP n40sm3193804wag.52<cr><lf>
19:25:37.906: << EHLO merwin.dyndns.org<cr><lf>
19:25:37.953: >> 250-mx.google.com at your service, [209.128.94.2]<cr><lf>
19:25:37.984: >> 250-SIZE 35651584<cr><lf>
19:25:37.984: >> 250-8BITMIME<cr><lf>
19:25:37.984: >> 250-STARTTLS<cr><lf>
19:25:37.000: >> 250-ENHANCEDSTATUSCODES<cr><lf>
19:25:37.000: >> 250 PIPELINING<cr><lf>
19:25:38.015: << STARTTLS<cr><lf>
19:25:38.078: >> 220 2.0.0 Ready to start TLS<cr><lf>
19:25:38.187: [*] SSL/TLS session established: RC4, OFB mode, keysize 128 bits
19:25:38.187: [*] Certificate user is cn=smtp.gmail.com, o=Google Inc, l=Mountain View, sp=California, c=US
19:25:38.218: [*] Certificate is valid from Mon Jul 30 00:00:00 2007 to Thu Jul 29 23:59:59 2010
19:25:38.250: [*] Certificate fingerprint is F1D3DE599D9CE231EAAA2CA0FCAD9A61
19:25:38.250: << EHLO merwin.dyndns.org<cr><lf>
19:25:38.328: >> 250-mx.google.com at your service, [209.128.94.2]<cr><lf>
19:25:38.328: >> 250-SIZE 35651584<cr><lf>
19:25:38.343: >> 250-8BITMIME<cr><lf>
19:25:38.359: >> 250-AUTH LOGIN PLAIN<cr><lf>
19:25:38.390: >> 250-ENHANCEDSTATUSCODES<cr><lf>
19:25:38.421: >> 250 PIPELINING<cr><lf>
19:25:38.437: << AUTH LOGIN<cr><lf>
19:25:38.500: >> 334 VXNlcm5hbWU6<cr><lf>
19:25:38.515: << <base64 encoded username>=<cr><lf>
19:25:38.562: >> 334 UGFzc3dvcmQ6<cr><lf>
19:25:38.578: << <base64 encoded password><cr><lf>
19:25:39.156: >> 235 2.7.0 Accepted<cr><lf>
19:25:39.203: << MAIL FROM:<postmaster@merwin.dyndns.org> SIZE=461<cr><lf>
19:25:39.250: >> 250 2.1.0 OK n40sm3193804wag.52<cr><lf>
19:25:39.265: << RCPT TO:<support@tstephenson.com><cr><lf>
19:25:39.359: >> 250 2.1.5 OK n40sm3193804wag.52<cr><lf>
19:25:39.359: << DATA<cr><lf>
19:25:39.953: >> 354  Go ahead n40sm3193804wag.52<cr><lf>

http://www.zoe.vc/2008/mercury-mail-transport-system-fur-externe-mail-konfigurieren/?lan=english

 These instructions are somewhat valid but they are from someone that really does not understand either Mercury nor the complications of SMTP in the current arena with all of the blocking of servers that do not use a valid host name and IP address. The use of "localhost" for a host name in the EHLO string is the first sign of a spammer.   Note that I am using a valid DynDNS assigned host name with this test setup.

Could it be that there is a very strict firewall blocking all traffic on port 587? I'm not sure why you have put an email address in the "Announce myself as" field (unless that is some special requirement for gmail, of course). Normally this should be a correct hostname (and not localhost as www.zoe.vc suggests).

Settings for other parts of Mercury should have no effect on TLS negotiation in MercuryC.

/Rolf