Wizard IT Products

Hello,

We have installed Magicspam for Mailenable Professional version in our windows 2008 server. We are facing a issue while trying to send mail through Horde webmail and we are receiving an error as below:

There was an error sending your message: unable to add recipient [xyz@test.com]: Invalid response code received from server.

This is happening for any email id may be its local or outside domains. When we are disabling the Magicspam protection everything is working fine. The Best practice rule settings are:


Best Practice Rule Status
(?) Block messages from IP (no domain)
(Rule name: block_ip_in_addr) Enabled
(?) Block Mail Servers on Dynamic/Dial-up Addresses
(Rule name: check_dynamic_reverse_dns) Enabled
(?) Perform reverse lookup check
(Rule name: check_ip_reverse_dns) Disabled
(?) Block Mail Servers reported as Spam Source
(Rule name: check_reverse_dns_list) Enabled
(?) Confirm Server Identification Resolves (HELO)
(Rule name: resolve_helo_domain) Disabled
(?) Strict address parsing
(Rule name: require_full_addr) Enabled
(?) Sending server must identify itself (HELO)
(Rule name: require_helo) Enabled
(?) Valid FROM domain
(Rule name: valid_from_domain) Disabled
(?) Server Identification must be valid (HELO)
(Rule name: valid_helo_domain) Enabled

The IP reputation settings are as below:


List Name Status
(?) UCEPROTECT-1
(List ID: 4) Disabled
(?) UCEPROTECT-2
(List ID: 5) Disabled
(?) UCEPROTECT-3
(List ID: 6) Disabled
(?) PSBL
(List ID: 13) Enabled
(?) SORBS-DUL
(List ID: 23) Enabled
(?) MIPSPACE
(List ID: 35) Disabled
(?) RATS-DYNA
(List ID: 36) Enabled
(?) RATS-NOPTR
(List ID: 37) Enabled
(?) RATS-SPAM
(List ID: 38) Enabled


Please suggest as soon as possible what needs to be done to rectify the problem.

Regards,
Diadem

Are you able to track down any log entries regarding the email address you're trying to send to when you get the error message? We suggest looking through the logs to see if there are any spam rules triggered when trying to send to that address.

We haven't heard anything more from you regarding this. Did you manage to get everything sorted out?

Yes we added 127.0.0.1 in the whitelist and everything worked fine.

We're glad to hear that you managed to get it working!

Hello;

Has spent time of this problem, but it is happening to me now and we can not add the IP address 127.0.0.1 to whitelist. MagicSpam now does not allow it.

The operating system is Windows Server 2008 SP1 64bit.
The version of Mail Enable Standar is v8.02 with Parallels Plesk Panel 11.5.30.
Horde v5.1.5.
MagicSpam v1.0.6-1.3.

There was an error sending your message: Mailbox unavailable. <---------- Sending a local address in same email server.

There was an error sending your message: This mail server requires authentication whe attempting to send to a non-local e-mail address. Please check your mail cliente settings or contac your administrator to verify that the domain or address is defined for this server. <------------- Sending a external address out of email server.

The errors.... we believe that the Horde misinterprets the errors, because MagicSpam stops emails and do not reach MailEnable. With MagicSpam deactivated working properly. The emails is sent.

In log of MagicSpam:
Type: SPAM[valid_helo_domain]
Mua: no
Address: 127.0.0.1
Hostname: mewebmail.localhost <-------------- We believe the error occurs here.
Helo: SERVER <-------- Same name that name of PC.
Sender: xxxxx@xxxxxx.com
Recipient: xxxxx@xxxxx.com

We can not add to whitelist SENDER because they would be all email addresses of mail server.

Help! Regars.

Hello,

Thank you for the post.

Based on the log provided, it looks that your Horde installation does not have the support for SMTP Authentication enabled. Please look into enabling SMTP Authentication in Horde's settings. Once Horde performs SMTP Authentication with the sender's email address when sending emails, the rule "valid_helo_domain" would not be applied and cause the message to be rejected.

In addition, please look into updating your server's hostname to a FQDN, e.g. "mewebmail.blancatel.com". Having a FQDN for your mail server is of Best Practices and would eliminate email delivery issues related to hostname verifications.

Please let us know if you have any further questions.

-- MagicSpam Support Team --