require_helo issue

[andi]

hello,

i have in my maiEnable SMTP-log lines as follows:

01/11/11 12:54:21 SMTP-IN 403692EAA54F4DA08F61D3D597275E2F.MAI 1636 195.186.19.70 EHLO EHLO mail30.bluewin.ch 250-server45.hostfactory.ch [195.186.19.70], this server offers 4 extensions 132 24
01/11/11 12:54:21 SMTP-IN 403692EAA54F4DA08F61D3D597275E2F.MAI 1636 195.186.19.70 MAIL MAIL FROM:<***@***.***> 250 Requested mail action okay, completed 43 38

magicSpam for ME v1.0.5-2 is installed and 'resolve_helo_domain'-rule is activated. but why do i get here:

2011-01-11 12:54:22 SPAM[require_helo] no 195.186.19.70 mail30.bluewin.ch (null) ***@***.*** ***@***.***


thank you,
andi

[magicspam]

Hello Andi,

Would you please be able to post the matching log entry (obfuscated or otherwise) in your MagicSpam logs?

[andi]

hello,

the last line in my previous post was from magicSpam 'logtail.php'. now, i copied the requested line from C:\magicspam\log\mslog, once again:

2011-01-11 12:54:21 magicspam-mailenable[16328]: SPAM[require_helo]: mua=0,ip=[195.186.19.70:mail30.bluewin.ch],helo=<(null)>,from=<xxx@bluewin.ch>,rcpt=<xxx@xxx.com>

thank you,
andi

[magicspam]

Thanks for providing and clarifying that Andi.

We have been running through testing and have not been able to replicate the issue as reported. For some reason the MailEnable SMTP process is passing the HELO argument (or in this case EHLO) as NULL - which seems to indicate to me that there is likely something incorrect in the argument or the argument processing taking place within that session.

Can you please confirm - from your last post you had reverted to MagicSpam 1.0.5-1 - have you upgraded to 1.0.5-2 yet?

[magicspam]

Ok.. seeing another post from you it would appear you have upgraded to 1.0.5-2.

We will be running through some additional testing to see if some fundamental elements of the MESMTPC.exe binary has changed in the latest Mail Enable release... we will post back shortly with our results and hopefully a resolution.

One thing you can try though in the meantime is:

Stop MailEnable SMTP Connector service
Make a back up copy of %PROGRAM FILES%\Mail Enable\Bin\MESMTPC.exe
copy over c:\magicspam\me\MESMTPC.exe to replace (at least temporarily)
Start MailEnable SMTP Connector service

This should help to determine if there was a change upstream with MailEnable that will need to be addressed .

Thanks!

[andi]

hello,
thank you for reply.

well,
my ME-installation is integraded in plesk for windows 9.5.4, so i had to copy MESMTPC.exe to '...\Plesk\Mail Servers\Mail Enable\Bin\'. here, i have 3 MESMTPC-files right now:

MESMTPC.exe (497KB), copied from c:\magicspam\me\MESMTPC.exe
MESMTPC.exe.backup (492KB), original from ME-installation
MESMTPC.exe.magicspam (470KB)

if this did help to resolve deh EHLO-issue, i cannot say, yet: i was only able to face the issue with one single sender adress, so i have to wait for another try, but i will let you know.

besides:
after ME-update to version 5.0.3 and magicSpam update to v 1.5.0-2, i was facing some performance issues on this reuqested node, which seems to be resolved since changing MESMTPC.exe.

regards,
andi