Application Development Software

I'm currently evaluating the proofpoint anti-spam product. I'm using it via milter and it's setup and doing it's thing filtering messages. However, I had noticed several false positives so I went ahead and submitted them. What I got back from them was the following:

The null byte at the end of the message is raising the score enough to just cross the spam threshold. Perhaps check with Sun to see if it's possible to disable sending a null at the end of the MILTER data?

Example octal character dump illustrating this:

0004240 . I f y o u n e e d a n
0004260 y \n i m m e d i a t e i n f o
0004300 r m a t i o n r e g a r d i n
0004320 g a p a r t i c u l a r g
0004340 r o u p t h a t ' s t h e
0004360 p e r s o n t o \n l o o k t
0004400 o o . H a v e a g o o d
0004420 w e e k e n d . \n \n J o r d a n
0004440 \n \n \0
0004443
note the null byte^

I've done some googling but, have not found anything useful. I've also had a look at the admin reference and any possible channel keywords, option.dat options, or tcp channel options but, found none.

Has anyone else run into this and if so how did you resolve it?

[smtpin121:...sbin] root[202]# ./imsimta version
Sun Java(tm) System Messaging Server 6.3-7.02 (built Jun 27 2008; 32bit)
libimta.so 6.3-7.02 (built 17:20:56, Jun 27 2008; 32bit)
SunOS smtpin121 5.10 Generic_127111-02 sun4v sparc SUNW,Sun-Fire-T1000

Edited by: cvervais on Sep 19, 2008 7:48 PM