Ok.... Well, that explains it. :-) I'm going to pass on the patch, although I appreciate the effort. I'm not comfortable enough with Linux to patch stuff, at least not without some pretty good instructions and I'm trying to move away from having to patch new servers when I deploy them, thus the move to QMT from QMR. It just makes like easier.
I may put together a Virtual Machine and try it on there though, when I get some time. In the mean time, I'll just find a way to work around the issue...Probably just put them in tcp.smtp and turn off the option in SpamDyke. Thanks again for the response Sam! You put an end to a couple day head bashing session. :-) Michael J. Colvin NorCal Internet Services www.norcalisp.com > -----Original Message----- > From: [email protected] [mailto:spamdyke-users- > [email protected]] On Behalf Of Sam Clippinger > Sent: Wednesday, January 12, 2011 3:57 PM > To: spamdyke users > Subject: Re: [spamdyke-users] SpamAssassin not getting Invoked > > We've seen this before: > http://www.mail-archive.com/[email protected]/msg02032.html > Unfortunately there doesn't seem to be a good solution. spamdyke has to > set the RELAYCLIENT variable in order to control relaying without > interference from downstream filters, but simscan won't scan any > messages when that variable is set. > > I pulled down the source code for the latest simscan and created a patch > (attached) to make it ignore the RELAYCLIENT variable and scan all email > regardless of origin or authentication. You're welcome to try it but be > warned: I haven't tested it at all, I haven't even tried to compile it > (I don't have a simscan environment set up). > > -- Sam Clippinger > > On 1/12/11 3:39 PM, Michael Colvin wrote: > > > > I cant believe I sent the last message w/o a subject Here it is > > again so the thread can be followed > > > > Hey Sam Im experiencing something weird, and am hoping you can > > straighten me out. J > > > > Running QmailToaster, which uses SimScan to scan mail, SpamAssassin is > > not being invoked. > > > > Through trial and error, weve narrowed it down to the > > access-file=/var/qmail/control/relay call in my spamdyke.conf file. > > If I comment this line out, SpamAssassin is called, mail is scored, > > and all works as expected. We are guessing that SpamDyke is passing > > the RELAYCLIENT value back, causing simscan to not send to > spamassassin. > > > > So, thinking that something was wrong in my relay file, I started > > looking there. Initially, I had simply IP addresses listed of hosts > > I needed to allow to relay. Example: > > > > 192.168.100. > > > > 69.224.221.10 > > > > Eric Shubert pointed out that the docs show a different syntax Not > > sure where I got just using the IPs from Anyway, I updated the file to: > > > > 192.168.100.:allow > > > > 69.224.211.10:allow > > > > But still, SpamAssassin wasnt being called. So, I commented out the > > lines in the relay file using # (Obviously w/o the quotes). Still > > no invocation of SpamAssassin > > > > So, Im wondering if Im still using the wrong syntax in that file? > > Does commenting out everything in that file, essentially making it > > empty, cause prolems? (Calling an empty file) Does simply utilizing > > the access-file option do something to set the RELAYCLIENT > > variable? Am I missing something else? > > > > Heres my spamdyke.conf: > > > > log-level=info > > > > access-file=/var/qmail/control/relay > > > > local-domains-file=/var/qmail/control/rcpthosts > > > > max-recipients=20 > > > > idle-timeout-secs=180 > > > > greeting-delay-secs=0 > > > > graylist-level=always > > > > graylist-dir=/var/spamdyke/graylist > > > > graylist-min-secs=300 > > > > graylist-max-secs=1814400 > > > > #policy-url=http://www.norcalisp.com/nospam?reason= > > > > sender-blacklist-file=/etc/spamdyke/blacklist_senders > > > > sender-whitelist-file=/etc/spamdyke/whitelist_senders > > > > ip-whitelist-file=/etc/spamdyke/whitelist_ip > > > > rdns-whitelist-file=/etc/spamdyke/whitelist_rdns > > > > reject-missing-sender-mx > > > > reject-ip-in-cc-rdns > > > > ip-blacklist-file=/etc/spamdyke/blacklist_ip > > > > recipient-blacklist-file=/etc/spamdyke/blacklist_recipients > > > > #ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords > > > > #rdns-blacklist-dir=/etc/spamdyke/blacklist_rdns.d > > > > reject-empty-rdns > > > > #reject-unresolvable-rdns > > > > dns-blacklist-entry=zen.spamhaus.org > > > > dns-blacklist-entry=b.barracudacentral.org > > > > dns-blacklist-entry=cbl.abuseat.org > > > > dns-blacklist-entry=list.dsbl.org > > > > dns-blacklist-entry=bl.spamcop.net > > > > dns-blacklist-entry=bogons.cymru.com > > > > # > > > > tls-certificate-file=/var/qmail/control/servercert.pem > > > > tls-level=smtp > > > > All of the whitelist_ files are empty, and, as I said initially, > > remarking out the access-file line causes SpamAssassin to be invoked. > > > > Any ideas? > > > > Thanks in advance! > > > > **Michael J. Colvin** > > > > **NorCal Internet Services** > > > > **//www.norcalisp.com// <http://www.norcalisp.com/>****** > > > > **(916) 864-1111** > > > > > > _______________________________________________ > > spamdyke-users mailing list > > [email protected] > > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
