This is the area for a general support questions, discussions and information that you can read and share. Post your experiences, stats and tricks and tips that are not covered elsewhere. Remember, for questions please search the FAQ first, as your question may already be answered.

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?

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?

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?

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:

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.