SMTP-issues since magicSpam 1.0.5-3

[andi]

hello,

since upgrading magicSpam for mailEnable to the latest version 1.0.5-3, it seems that SMTP of ME 5.0.3 prof. edit. stops to be available from time to time. i get only some notifications from our survey-software, that SMTP did not answer and have been restarted through plesk-api - in SMTP-logs, i was not able to find any further informations about this.

the issue occurs exactly since upgrading to magicSpam 1.0.5-3, last week. we face the issue on severall ME-servers (v. 4.x and 5.x),

does anybody face similar issues?
does anybody know the reason for this behaviour?

regards,
andi

[magicspam]

Hello Andi, that is indeed odd.. are there particular times that this happens at that you have noticed? If for example this is happening during scheduled update periods then we would of course want to review what is happening there.

As a curiosity question, what kind of resources do the effected servers have (ie: CPU(s), RAM, disk types) and also, were these servers upgraded from 1.0.5-2 or an earlier release?

Thank you for any information you may be able to provide!

[andi]

it happens at different times. last issues, i faced were on different nodes at 23:28h, 23:36h, 23:50h, 00:04h, 00:05h

on all this servers, i performed upgrade from 1.0.5-2 to 1.0.5-3.
on all servers, plesk 9.x and mailEnable 4.x or 5.x professional is installed.
hardware an os is different: some windows 2003 servers, some windows 2008; some 32bit, some 64bit. also CPU and RAM differs.

we are checking uptime of SMTP over PLESK's API: if plesk shows MESMTPCS as down, we perform a restart of the service.

i really do not know, which kind of information i could provide additionally..?!

is there a way to downgrade from 1.0.5-2 to 1.0.5-3? may i just uninstall 1.0.5-3 and reinstall 1.0.5-2 till we were able to figure out why this happens?

regards,
andi

[magicspam]

Hello Andi,

Before you downgrade the software, could you please post the output of the following command (while MagicSpam is enabled) on one of your MailEnable 4.x servers and one of your MailEnable 5.x servers respectively:

c:\magicspam\bin\md5sums.exe %PROGRAM FILES%\Mail Enable\Bin\MESMTPC.exe

This is rather baffling as there were no fundamental changes in the underlying code that should have affected the stability of the integration...

and just so you know, yes.. you can un-install and use the previous 1.0.5-2 installer to downgrade.

[andi]

hello,

i did allready perform some downgrades, but not on every server. so i can provide you the results of 'c:\magicspam\bin\md5sums.exe %PROGRAM FILES%\Mail Enable\Bin\MESMTPC.exe':

w2k3 server 64bit, ME 4.17 prof., magicSpam 1.0.5-3, plesk for windows 9.5.3:

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type c:\magicspam\bin\md5sums.exe -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[D:\parallels\plesk\mail servers\Mail Enable\Bin\]
MESMTPC.exe 6f3efae582a6a70249b92278d1ddc238





w2k8 server 64bit, ME 5.02 prof., magicSpam 1.0.5-3, plesk for windows 9.5.4:

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type c:\magicspam\bin\md5sums.exe -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[D:\parallels\plesk\mail servers\Mail Enable\Bin\]
MESMTPC.exe fd5320aa01eed9b729f0d2a8bbf264c0



thank you,
andi

[isaak]

I am having the exact same issue.
SMTP fails every now and then. And when it occurs, during the time frame, it stops every 10 or 15 min.

This is what came out when I used the command you posted before:

Code: Select all

C:\Documents and Settings\Administrator>c:\magicspam\bin\md5sums.exe "C:\Program
 Files (x86)\Mail Enable\bin\MESMTPC.exe"

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type c:\magicspam\bin\md5sums.exe -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[C:\Program Files (x86)\Mail Enable\bin\]
MESMTPC.exe                                    dbf00873cebbffd7cd49ebdb19e61752

This is what I found in the Windows Event about MagicSpam making SMTP fail:

Code: Select all

Faulting application MESMTPC.exe, version 1.0.0.59, faulting module magicspam.dll, version 0.0.0.0, fault address 0x00004a4a.

So far we have disabled magicspam protection and SMTP is running perfectly.
Running MagicSpam 1.0.5-3, on Windows 2003 and ME Premium 5.10 on a 64bit platform (which the problem might reside).

Regards,

[isaak]

I am having the exact same issue.
SMTP fails every now and then. And when it occurs, during the time frame, it stops every 10 or 15 min.

This is what came out when I used the command you posted before:

Code: Select all

C:\Documents and Settings\Administrator>c:\magicspam\bin\md5sums.exe "C:\Program
 Files (x86)\Mail Enable\bin\MESMTPC.exe"

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type c:\magicspam\bin\md5sums.exe -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[C:\Program Files (x86)\Mail Enable\bin\]
MESMTPC.exe                                    dbf00873cebbffd7cd49ebdb19e61752

This is what I found in the Windows Event about MagicSpam making SMTP fail:

Code: Select all

Faulting application MESMTPC.exe, version 1.0.0.59, faulting module magicspam.dll, version 0.0.0.0, fault address 0x00004a4a.

So far we have disabled magicspam protection and SMTP is running perfectly.
Running MagicSpam 1.0.5-3, on Windows 2003 and ME Premium 5.10 on a 64bit platform (which the problem might reside).

Regards,

[magicspam]

That certainly sheds some light on the issue, thank you for posting Isaak.

Do you happen to have the MailEnable SMTP activity log portions surrounding the time frame of the recorded fault event along with the time stamp of the recorded event? It would be very beneficial to determine if this is a result of a particular type of message / message data triggering this.

If you would like, please feel free to contact support [at] magicspam.com to arrange direct contact for testing this bug.

Thanks!

[isaak]

Thank you, I have just sent the email with the information requested.

Hope it helps to find a solution.

Please keep us informed.

Regards,


Isaak Mancia
Web-e-volution

[magicspam]

This issue has now been resolved with newly released package 1.0.5-3.3 for MailEnable. Thank you all for your patience as we worked through with an active participating customer and squashed this bug.