> -----Original Message----- > From: Loren Wilton [mailto:[EMAIL PROTECTED] > Sent: Monday, August 13, 2007 8:02 PM > To: users@spamassassin.apache.org > Subject: Re: MS outlook can't read parsed email... HELP!! > > > Sorry for jumping in late to this thread.. But, I currently run > > SA3.18 with a similar yet different Exchange Sink and have no such > > problems as the original poster. > > > Steven > > So which sink do you use? Maybe he should use it instead? > > Loren >
I created it myself.. There's drawbacks to using the SA APIs, like dependencies on the SA version and the functions that need to be called in the various SA verisons (dating back to 2.63 when I built this thing).. So, there's something to be said for calling the bat file, and being done with it! My script is pure perl. P.S. until recently, I hadn't made a change to my sink in over a year, so Chris not updating his in that same time period isn't that unusual. Let me go ahead and put a copy out on the web along with config files and a dependency module that can't be found on the web. Please, no comments about my web design skills (or lack thereof). :) http://www.manross.net/spamassassin/eventsink.txt (rename the eventsink.txt to eventsink.vbs prior to use) http://www.manross.net/spamassassin/sampleini.txt http://www.manross.net/spamassassin/Ini.pm.txt (rename the ini.pm.txt to ini.pm and place in the C:\Perl\Site\lib\SRM folder -- create if necessary) This code is purely for the interested. Any suggestions for code improvements would be greatly appreciated (please reply offlist, since Exchange is not a buzzword that happens too often on this list). But, to reiterate, I don't think Chris' sink is to blame here. I think the text file is messed up prior to reimporting it (because Chris and I are doing the same ADODB code to reimport the text file). As well, I've gotten confirmation that the original poster is trying to install another version (SA3.23) just to make sure nothing's messed up in the sa install. I do a lot of very custom things in my sink (but a lot of it is configurable to turn on/off): --like an RBL check that requires 2 or more hits prior to discarding a message (configurable) as my wife doesn't think that someone's server getting blacklisted is a valid reason not to accept mail from xyzreallybigisp.com, so I require 2 listings (hopefully the chance of xyzreallybigisp.com getting listed by two separate DNSBL servers by accident is much harder). --custom logging for each mail message and it's disposition (as well as SA Debug logging) --maintaining an MS SQL server list of IPs that have been checked against blocklists in the last 24 hours and importing DNSBL positive IPs into the IIS (Exchange) Connection Deny list using a Perl Module (available on CPAN -- Win32::Exchange::SMTP::Security) for the next 24 hours. --attachment stripping (based on file extension) --sql message disposition logging so I can track and chart mail load based on SA category (Real Mail, SPAM, NDR,DNSBL,Outgoing, etc). --dropping messages that have encoded subjects, tos, froms, etc.. (that's probably not RFC, but I don't deal with mailing regions that encode those fields on a regular basis, so I can get away with it. I will admit that my script isn't the best, since I believe there's a memory leak in the code (or in Activestate's OLE implementation) that I've never been able to nail down. :( But, I deal with it, and by mail traffic is somewhat lite (except for all the SPAM, and, of course the traffic from this list... HAHA). Steven
