.. And here the output from your command below: sa-learn -u vpopmail --force-expire bayes: synced databases from journal in 0 seconds: 1512 unique entries (1901 total entries)
So if my program syncs it in 0 seconds I would assume that spamassassin will take roughly the same time when booting up. Looks like the mail itself is the cause for the hickup? Sebastian PS: Did you have a look at the colored version of qmlog already? I got a patch flying around somewhere still ... Eric Shubert wrote: > FWIW, if you're using spamassassin (along with simscan), you might want > to be sure that you have "bayes_auto_expire 0" in your local.cf file. > This function can take several minutes when it kicks in, and occurs > while the smtp session is still active (possibly resulting in duplicate > messages). You can simply set up a cron job to expire bayes database > entries instead, e.g. (w/ vpopmail as mail user): > > sa-learn -u vpopmail --force-expire > chown vpopmail:vchkpw /home/vpopmail/.spamassassin/bayes_toks > > Sebastian Grewe wrote: > >> .. >> >> Sorry for this but I found the solution here: >> http://www.qmailwiki.org/index.php/Simscan/README#How_to_Disable.2FEnable_simscan_for_smtp_connections_by_IP_ranges >> >> I removed simscan for the know IP's and now mail is coming through. >> Let's hope it's just that one. >> >> Thanks anyway and maybe this information could be useful to someone else >> out there :) >> >> Cheers, >> Sebastian >> >> Sebastian Grewe wrote: >> >>> Hey again, >>> >>> I was a bit quick on the draw there. After some research on our end I >>> noticed that the spam filter needs quite some time to actually scan that >>> mail (>60s) which results in the provider to time us out. So my question >>> is: How can I skip simscan from processing messages from that one >>> provider, given I have their IPs? I would do that until the message >>> comes through and then disable the "whitelist" after that. >>> >>> Cheers, >>> Sebastian >>> >>> Sebastian Grewe wrote: >>> >>> >>>> Hey guys, >>>> >>>> Here an issue we had a long time ago already: >>>> >>>> A mail provider connects to our system to deliver a mail. Spamdyke >>>> accepts the message and sends it over to Simscan. Spamdyke logs a >>>> TIMEOUT error in our Log, right after that Simscan completes the scan. >>>> It looks like it hangs somewhere so Spamdyke, by mistake, sends a >>>> Timeout to the ISP. That one tries to send the same message again which >>>> of course fails again. >>>> >>>> Just wondering, if anyone else had this issue? If not I can post more >>>> details about it. >>>> >>>> Cheers, >>>> Sebastian >>>> _______________________________________________ >>>> 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 >>> >>> > > > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
