Alyssa Ross wrote:
> "@lbutlr" writes:
>
> >> May 21 23:20:56 mail spamd[22787]: spamd: error: Bad arg length for
> >> Socket::unpack_sockaddr_in, length is 28, should be 16 at
> >> /usr/local/lib/perl5/5.28/mach/Socket.pm line 848.
> >> May 21 23:20:56 mail spamd[22787]: , continuing at /usr
Ryan Coleman wrote:
> That’s more information than Dovecot gives for the structure, so that will
> help.
>
> Do you happen to know what the other flags mean?
http://cr.yp.to/proto/maildir.html
My inotify setup posted earlier relies only on the 'S' flag and
alphabetical ordering of flags.
Ryan Coleman wrote:
> Ok so it was established I don’t have a ham scan (correct). So how do
> I do it so that it only scans the read emails in a MAILDIR?
Since 2008, I use inotify (via incrond) on Maildirs:
http://mid.gmane.org/20140822083434.ga8...@dcvr.yhbt.net
Daniel Staal wrote:
> Good points, but inotify might still be overkill. `ls maildir/cur/
> | grep ',.*S` will give you all messages that have been seen in the
> mailbox, so you can run on a periodic schedule fairly easily. I'm
> not sure whether you need the immediate notification inotify gives.
Ian Zimmerman wrote:
> Eric Wong wrote:
>
> Eric> I always thought inotify was an obvious way to train for anybody
> Eric> using Maildirs on Linux, so I set it up for my server and
> Eric> basically forgot about it since it worked well. Fast forward to
> Eric> 2
Hi all, I'm a happy SA user since around 2004/2005.
Since 2008, I've been using Linux inotify (via incron) to do automatic
Bayes training. Previously I did something similar using:
find ... | spamc -L ... via cron.
I also used to run several filters with SA (crm114+dspam), but since
200
