Message rejected by server filters

[eof]

[<02>] The reason of the delivery failure was:

Message rejected by server filters


What is it? Where should I fix the problem??? My mail server rejected this message. And there is no any other problems with any other messages! The remote server was Microsoft Exchange. Or where can I get more info about what has happened with this email?

[hschneider]

Who produced this error message? XMail or Exchange ?



Bye,
Harald

[hschneider]

Hi,

as you see at
http://xmailserver.org/Errors.html

XMail uses negative numbers as error codes. Please give more precised information, where this message is from ...



Bye,
Harald

[eof]

And where can I look for this negative number generated by XMail? There is no any Error code in the message which came to my admin account about failed delivery! This error message was produced by my XMail server. The mail was incoming.

[hschneider]

Incoming or coming back ?
Since XMail does no outbound filtering, the prob might be Exchange server of the recipient.

Thanks for forwarding the mail:
*** maybe *** you or the recipient (more precised some filter-tools)
have problems with the cyrillic chars in the subject:
Subject: =?koi8-r?B?IOTM0SD0LiDwzM/UzsnLz9fPyg==?=

The mail appears corrupted and is rejected.

Can you test the same mail with a non-cyrillic subject ?

Let me know the result.

Bye,
Harald

[eof]

Harald, here in Russia we always have cylillic subjects and no problem with it.

The mail was incoming. I mean that someone composed the message and sent it to us. But I found one thing that can help us. The message had rather huge size. Does XMail generate such report if the message's size is grater than MaxMessageSize variable?

[hschneider]

NOPe. This would look like this:

552 Message exceeds fixed maximum message size

Errors coming from the SMTP negotiation between the both SMTP servers always have a value > 300 ...

Errorcode #2 seems to be rather strange ...






Bye,
Harald

[hschneider]

I scanned the xmail.exe binary for the 'rejected by server filters' message and it's there. So it is definately a message produced by XMail. Further it must be an internal message, since it is not a SMTP protocol errcode. Unfortunately it is not documented ...

Can you please check all tabs, that concern filtering or spam blocking on your system ?

These are
spam*.tab
*redir*.tab

... and files in
/custdomains
/filters




Are there any entries in some of these files ?


Bye,
Harald

[hschneider]

Me again ...

I digged into the source code of XMail:
Err #2 is produced in only one certain situation, exactly when a domain message filter returns an errcode of #99. See manual:

----
Part 13 Domain message filters

This feature offer the way to filter out messages by providing the ability to
execute external programs, such as scripts or real executables, that examines
( modify or both ) the message and gives its response with its return value.
This feature offer the ability to inspect and modify messages, giving a way
to reject messages based on its content, alter messages ( address rewriting )
and so on.
If this filters returns 97, 98 or 99 means that the message is rejected and
must be stopped in its travel.
[...]
---

Please check, if you have set any of these filters ...



Bye,
Harald

[eof]

How could I forget!!!

Yes, I have the antivirus filter! It is clear that this filter could not to check such huge attached file and could return such error code. I thing it's not a bug or something in XMail, this is the problem of antivirus filter.

I'm using f-prot filter 'cause I haven't found enything better for Win32. The AVG filter makes system much more slower!!!

[hschneider]

Oh ... I'm here to remind you -)

OK .. as you know, AV tools often claim detecting a virus even if the msg is clean. Or maybe it was indeed infected.

So the prob is solved and we have successfully resolved the mystery of errcode #2 ... :)



Bye,
Harald

[eof]

No! When AV filter finds a virus it does'n behave so! And that file couldn't be infected! I am sure that AV filter just can't work with such huge file. Especially because it works in console mode.

[hschneider]

You are right: Seems NOT to be a prob of the AV filter:

XMail tries to process the message, even it is still in the filter!
See this extract from the newsgroup:

---
On Sun, 1 Sep 2002, Theo Rosbag wrote:

>
> Hello,
> I'm using a viruscheck filter (viruscheck.pl from P Lindeman) to check
> incoming/outgoing mail for virusses .
> All went well until i try to send a very big attachement (about 550MB) .
> Xmail seems to try to send the message during the virusscan , and after
> a while it returns the following errorlog in the spool directory :
>
> [Start Log]
> [PeekTime] 1030836324 : Sun, 01 Sep 2002 01:25:24 +0200
> <<
> ErrCode = -5
> ErrString = Timeout error
> Filter error for domain "xxxxx.nl" (/var/MailRoot/filters/checkvirus.pl)
> >>
> <<
> ErrCode = -162
> ErrString = End of socket stream data
> SMAIL SMTP-Send RLYS = "xxxxx.nl" SMTP = "xxxxx" From = xx@xxxx.com" To
> = "xxxxx@xxxxxx.nl" Failed !
> [/end Log]
>
> In my opinion Xmail should wait for an exit code from the script before
> sending the message or am i getting wrong?

yes, it is possible. to prevent the SMAIL thread to get stuck forever
there's an hard-coded timeout of 60 secs. this is the time XMail will wait
for the filter command to complete. i'll make this configurable from the
command line.



- Davide

---

So if filtering takes longer than 60 sec, the filter get cannot process the message anymore (cause it is locked or removed by XMail) and produces an error code ...


Bye,
Harald

-- Visit the home of XMail Queue Manager: http://xmail.marketmix.com