Hello,

I updated my plesk 9.0.1 to 9.2.1 yesterday.
First, I was really happy as it goes smoothly and everything was up and running after the update!

Then, I realized that greylisting was directly available into Plesk: wonderfull!
So, I removed qgreylist, and enabled the plesk integration.

I can receive my emails, but I noted this error in my maillog:

Apr 29 09:21:22 myhost greylisting filter[5641]: Starting greylisting filter...
Apr 29 09:21:22 myhost qmail-queue-handlers[5640]: handlers_stderr: DEFER
Apr 29 09:21:22 myhost qmail-queue-handlers[5640]: call_handlers: DEFER during call '/usr/local/psa/handlers/info/05-grey-ZDYka8/executable' handler
Apr 29 09:21:22 myhost qmail-queue-handlers[5640]: call_handlers: stop call handlers from dir '/usr/local/psa/handlers/before-queue/global'
Apr 29 09:21:22 myhost X-Qmail-Scanner-2.05st: [myhost.ch12409896827925634] Unable to open pipe to /var/qmail/bin/qmail-queue.orig [61] (#4.3.0) -
Apr 29 09:21:22 myhost X-Qmail-Scanner-2.05st: [myhost.ch12409896827925634] Unable to close pipe to /var/qmail/bin/qmail-queue.orig [61] (#4.3.0) - Illegal seek

Note that I even chmoded /var/qmail/bin/qmail-queue.orig to 777, and even run again qmail-scanner-reconfigure ...
The error still shows up, and it only seems to happen when there is the greylisting filter before.

Any idea?
Thanks!

Any news about this problem?
I noted that after the "DEFER", the concerned mail don't show up again in the maillog... So, it seems that those emails got lost?!

Should I switch back to the usual qgreylist and forget about the greylist plesk integration?

I'm a bit concerned about the mention of /var/qmail/bin/qmail-queue.orig

At a guess I would say that's a backup copy that was made at some point.

But maybe this is normal with qgraylist or something? It just seems very odd.

Faris.

Hello,

same problem here

I personnaly switched off the greylist implementation of Plesk and installed again qgreylist.
It works with no errors and there's much more visibility in the maillogs!

how can I do that ?

Simply uncheck the greylist box in the spam-filter settings (server wide, in Plesk).
After that, do a "yum install qgreylist" (from ART), and you're ready!

thanks I was working hard yesterday and I didn't saw that

It's a good way to maintain qgreylist from ART repo and Spamdyke toghether ?

I never used Spamdyke... But I think that it's not necessary to have both qgreylist and spamdyke installed, as spamdyke include greylisting??!

Yes that's true spamdyke includes qgreylist, so the question is qgreylist or spamdyke ? I like both

I have other problem, my outgoing mails are tagged ar spam or got high SA Scores when they go out ( minimum 4 points ! ):

[root@newlightsystems herramientas]# tail -f /usr/local/psa/var/log/maillog |grep -A 15 -B 15 ppxxx
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: call_handlers: SKIP during call '/usr/local/psa/handlers/info/05-grey-7SSIig/executable' handler
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: call_handlers: call executable = '/usr/local/psa/handlers/info/10-spf-AhwJRQ/executable'
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: No such parameter 'context' for handler '10-spf-AhwJRQ'
May 4 23:48:05 newlightsystems spf filter[30604]: Starting spf filter...
May 4 23:48:05 newlightsystems spf filter[30604]: Some args not defined. Use /usr/local/psa/handlers/info/10-spf-AhwJRQ/executable <FROM> <TO>
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: call_handlers: Error during call '/usr/local/psa/handlers/info/10-spf-AhwJRQ/executable' handler
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: LOG Internal error in handler '10-spf-AhwJRQ'. Skip handler.
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: call_handlers: call executable = '/usr/local/psa/handlers/info/10-spf-UejrXq/executable'
May 4 23:48:05 newlightsystems spf filter[30605]: Starting spf filter...
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: handlers_stderr: SKIP
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: call_handlers: SKIP during call '/usr/local/psa/handlers/info/10-spf-UejrXq/executable' handler
May 4 23:48:05 newlightsystems spamd[27519]: prefork: child states: II
May 4 23:48:05 newlightsystems qmail: 1241473685.680819 new msg 7570037
May 4 23:48:05 newlightsystems qmail: 1241473685.680877 info msg 7570037: bytes 995 from <work@luislorenzo.es> qp 30606 uid 10480
May 4 23:48:05 newlightsystems qmail-queue-handlers[30602]: starter: submitter[30606] exited normally
May 4 23:48:05 newlightsystems qmail-scanner[30587]: Clear:RC:0(83.50.36.229):SA:1(8.8/6.1): 1.06874 534 work@luislorenzo.es crk01@newlightsystems.com ppxxx <49FF6297.301@luislorenzo.es> orig-newlightsystems.com124147368479230587:534 1241473684.30589-0.newlightsystems.com:0
May 4 23:48:05 newlightsystems qmail: 1241473685.744189 starting delivery 11: msg 7570037 to local 137-crk01@newlightsystems.com
May 4 23:48:05 newlightsystems qmail: 1241473685.744223 status: local 1/10 remote 0/20
May 4 23:48:05 newlightsystems qmail-local-handlers[30608]: Handlers Filter before-local for qmail started ...
May 4 23:48:05 newlightsystems qmail-local-handlers[30608]: from=work@luislorenzo.es
May 4 23:48:05 newlightsystems qmail-local-handlers[30608]: to=crk01@newlightsystems.com
May 4 23:48:05 newlightsystems qmail-local-handlers[30608]: mailbox: /var/qmail/mailnames/newlightsystems.com/crk01
May 4 23:48:05 newlightsystems qmail-local-handlers[30608]: hook_dir = '/usr/local/psa/handlers/before-local'
May 4 23:48:05 newlightsystems qmail-local-handlers[30608]: recipient[3] = 'crk01@newlightsystems.com'
May 4 23:48:05 newlightsystems qmail-local-handlers[30608]: handlers dir = '/usr/local/psa/handlers/before-local/recipient/crk01@newlightsystems.com'
May 4 23:48:05 newlightsystems qmail-local-handlers[30608]: call_handlers: call executable = '/usr/local/psa/handlers/info/10-spam-VKgPYw/executable'
May 4 23:48:05 newlightsystems spamd[27522]: spamd: got connection over /tmp/spamd_full.sock
May 4 23:48:05 newlightsystems spamd[27522]: spamd: using default config for crk01@newlightsystems.com: /var/qmail/mailnames/newlightsystems.com/crk01/.spamassassin/user_prefs
May 4 23:48:05 newlightsystems spamd[27522]: spamd: processing message <49FF6297.301@luislorenzo.es> for crk01@newlightsystems.com:110
May 4 23:48:06 newlightsystems spamd[27522]: spamd: clean message (3.9/6.0) for crk01@newlightsystems.com:110 in 0.7 seconds, 995 bytes.
May 4 23:48:06 newlightsystems spamd[27522]: spamd: result: . 3 - AWL,BAYES_50,FH_HOST_EQ_DYNAMICIP,RDNS_DYNAMIC scantime=0.7,size=995,user=crk01@newlightsystems.com,uid=110,required_score=6.0,rhost=localhost,raddr=127.0.0.1,rport=/tmp/spamd_full.sock,mid=<49FF6297.301@luislorenzo.es>,bayes=0.500796,autolearn=no

Hmmm very strange... I don't really know what's going on...
You should check the rules (in the email headers) that get your spam score to 4.
Personnaly, I use the official spamassassin from plesk, and qmail-scanner is only scanning files for viruses with clamd. So, spam checking is not executed on outgoing emails.

The only problem is that I have nothing in my mail headers

I also want that configuration, how are you configured to not filter outgoing mails ?

EDIT:

I reinstall psa-spamassassin, stop the service, do a qmail-scanner-reconfigure , start psa-spamassassin service and that's IT

THe only thing is that in plesk 8.6 I have qmail-scanner-reconfigure with psa-spamassassin and no problems

Yep that's right, you've to execute the qmail-scanner-reconfigure when the spamassassin service is stopped.
Or else, it'll double-check your emails for spam!

perfect that's all , but I remember that in plesk 8.6 I could do a double scan without problems ( qmail-scanner-reconfigure with PSA-SA together )

thanks,