Thank you. I didn't know that.

Hello everyone.

Two days ago we installed for testing purposes a second mail server on the same machine as mercury. 

Three users are now mailing through the new mail server, the other (about 20) are still using mercury.

The other mail server has a feature, that allows to define SMTP-routing for a whole domain or specific adresses.  

We use this feature to send mails from the local users on the new mail-server directly to the local users still using

mercury. A kind of "SMTP-forwarding". So the local mails are not taking the long way through the provider.

One mail-server forwards the internal mails directly to the other on the same machine.

Simply sending mails over this way is working fine. But when mails are forwarded, mercury deletes this mails

with the message "killed by global spam processor".  

What can I do to avoid this? No need to say, it's quite urgent!

Thanks for any help. 

Edit:  

 Further investigation showed, that it's NOT a global problem, only one of the three "test-users" is affected, but for this user it's absolutely reproducable: Sending mails works fine, forwarded messages are all "killed by global spam processor".
Is there any possibility to disable spam processing for either a specific user, an email-adress, an ip-adress or an ip-adress-range?

The "killed by global spam processor" happens when mail addressed to the Spamhalter SPAM or NOSPAM user comes into the system.  I suspect this one user matches one of these users.

My first thought was, that this has something to do with spam halter. But when I disabled spam halter for testing, the problem still exists.

Are you sure it's disabled?  You'll never get a message talking about the global spam processor unless you have some daemon running.

Thank you ,Thomas. No Need to torture your brain with this problem any longer. We found the (weird) reason.

This was the only user who forwarded mail by attachments. Setting the forwarding option in the mail-client to "inline" solved

the problem.  

In the moment I have no explanation for this.  

Your "List of banned attachments" will include '.eml' so they will be killed.

Yes, I am sure. Or do I have to restart mercury to activate this setting?

 Edit: For Thomas...
 

To dilberts_left_nut: 

This would be an explanation for this. But I don't find a "List of banned attachments" anywhere. Nor in SpamHalter, neither in Mercury...

Sorry, was going by memory (must be a stuck bit somewhere [:)]), the list of banned attachments is a Clamwall setting "Basic Settings" tab.

You have to restart Mercury to en/dis-able a daemon.