Style Gibberish spammers are one step ahead of me !!!!
No sooner did I complete a small python filter to divert untrapped style gibberish spams than I started getting these without the
Re: cron sa-update with multipe channels
On Sat, 2016-09-17 at 19:20 +0100, RW wrote: > On Sat, 17 Sep 2016 11:52:16 +0200 > Marcus Schopen wrote: > > > > > > Thanks! But then in sa-update-hock.d dir in my case mimedefang > > would > > be reloaded after each channel update instead of one recompile and > > one > > reload after all updates finished. > I think you'd have to write your own script. Just keep track of > the return codes from the various invocations of sa-update and > recompile/restart at the end of the script. > The OP could also run the various updates as separate cronjobs. Each would set a flag, i.e. create a file to indicate a successful update, on completion. If the flag is already set it would not touch it. A final cronjob, timed for 30 mins or so later, would do the recompile and restart if the flag was set and then unset it. That should keep the scripts simple (only one task per script) while still only doing a single recompile/restart if at least one update was successful. Martin
Re: cron sa-update with multipe channels
On Sat, 17 Sep 2016 11:52:16 +0200 Marcus Schopen wrote: > Thanks! But then in sa-update-hock.d dir in my case mimedefang would > be reloaded after each channel update instead of one recompile and one > reload after all updates finished. I think you'd have to write your own script. Just keep track of the return codes from the various invocations of sa-update and recompile/restart at the end of the script. I'm curious about what all these channels are. Are they something private?
AW: AW: X-Spam Tagging - Spam Status YESNO Flags - Sometimes not appended...
Thanks! I checked that and it gave me a direction. Log says that messages skipped because of size limit which i haven't set and is still default (512000 bytes). On the other site I checked the messages that are not tagged and not all of them are bigger than 512kb. Anyway most of them are! I tried to set the -s option in /etc/default/spamassassin on debian to 1024000 for a test, with no effect. Log still says its skipping due to the limit of 512000. Does anyone have a clue what needs to be done in debian?! -Ursprüngliche Nachricht- Von: David B Funk [mailto:dbf...@engineering.uiowa.edu] Gesendet: Freitag, 16. September 2016 18:18 An: Maik Linnemann Cc: users@spamassassin.apache.org Betreff: Re: AW: X-Spam Tagging - Spam Status YESNO Flags - Sometimes not appended... What do you see in your syslog reports from spamc? Is it reporting any errors? Please note the 'max-size' parameter for spamc: -s max_size, --max-size=max_size Set the maximum message size which will be sent to spamd -- any bigger than this threshold and the message will be returned unprocessed (default: 500 KB). If spamc gets handed a message bigger than this, it won't be passed to spamd. The maximum message size is 256 MB. So any message larger than that parameter (default 500KB) will be silently bypassed as far as spamd processing is concerned. Note, do not make that a large number in an attempt to process -everything- unless you have a beefy (lots of RAM & CPU) machine for your spamd processing. On Fri, 16 Sep 2016, Maik Linnemann wrote: > SA is integrated into postix via master.cf like: > > == > # service type private unpriv chroot wakeup maxproc command + args > # (yes) (yes) (yes) (never) (100) > # == > smtp inet n - - - - smtpd > -o content_filter=spamassassin > > spamassassin unix - n n - - pipe > user=nobody argv=/usr/bin/spamc -f -e /usr/sbin/sendmail -oi -f > ${sender} ${recipient} > > i dont have milter or amavis in place. av scanning is done in the backend, > where i would say the tagging should already be done (and mostly its the > case!) > > > Von: li...@rhsoft.net [li...@rhsoft.net] > Gesendet: Freitag, 16. September 2016 15:52 > An: users@spamassassin.apache.org > Betreff: Re: X-Spam Tagging - Spam Status YESNO Flags - Sometimes not > appended... > > Am 16.09.2016 um 14:49 schrieb Maik Linnemann: >> So far so good. The concept works like it should with only one >> exception: Some mails are not tagged by spamassassin and i dont have a >> clue why. Viscerally i would say its about 20% of all mails that arent >> tagged by spamassassin -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_adminIowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{
Re: cron sa-update with multipe channels
Am Samstag, den 17.09.2016, 11:46 +0200 schrieb Axb: > On 09/17/2016 11:35 AM, Marcus Schopen wrote: > > Am Samstag, den 17.09.2016, 10:36 +0200 schrieb Axb: > >> On 09/17/2016 10:17 AM, Marcus Schopen wrote: > >>> Hi, > >>> > >>> is there a concept for updating from multiple channels > >>> in /etc/cron.daily/spamassassin so that sa-compile is called only if one > >>> channel got updates? > >> > >> > >> /etc/cron.daily/spamassassin is not part of the SA project. It's usually > >> something added by a distro maintainer > >> > >> just add conjobs for the "other" channels as per sa-update docs > >> > >> (http://spamassassin.apache.org/full/3.4.x/doc/sa-update.txt) > > > > Ah, understand. Thanks. > > > > If I use --channelfile to list all update servers in one file, I have a > > problem to mix servers with gpgkey and without. Do I need to use > > --channel for each server instead of --channelfile to be able to specify > > --gpgkey or --nogpg or how can I mix that? > > > > I've never used --channelfile so I can't tell. > > as different channels may require different update frequency, etc, I've > always chosen to us one cronjob per channel and/or server. > Makes it easier to track and debug. > > Maybe someone else can answer your question. Thanks! But then in sa-update-hock.d dir in my case mimedefang would be reloaded after each channel update instead of one recompile and one reload after all updates finished. Ciao!
Re: cron sa-update with multipe channels
On 09/17/2016 11:35 AM, Marcus Schopen wrote: Am Samstag, den 17.09.2016, 10:36 +0200 schrieb Axb: On 09/17/2016 10:17 AM, Marcus Schopen wrote: Hi, is there a concept for updating from multiple channels in /etc/cron.daily/spamassassin so that sa-compile is called only if one channel got updates? /etc/cron.daily/spamassassin is not part of the SA project. It's usually something added by a distro maintainer just add conjobs for the "other" channels as per sa-update docs (http://spamassassin.apache.org/full/3.4.x/doc/sa-update.txt) Ah, understand. Thanks. If I use --channelfile to list all update servers in one file, I have a problem to mix servers with gpgkey and without. Do I need to use --channel for each server instead of --channelfile to be able to specify --gpgkey or --nogpg or how can I mix that? I've never used --channelfile so I can't tell. as different channels may require different update frequency, etc, I've always chosen to us one cronjob per channel and/or server. Makes it easier to track and debug. Maybe someone else can answer your question.
Re: cron sa-update with multipe channels
Am Samstag, den 17.09.2016, 10:36 +0200 schrieb Axb: > On 09/17/2016 10:17 AM, Marcus Schopen wrote: > > Hi, > > > > is there a concept for updating from multiple channels > > in /etc/cron.daily/spamassassin so that sa-compile is called only if one > > channel got updates? > > > /etc/cron.daily/spamassassin is not part of the SA project. It's usually > something added by a distro maintainer > > just add conjobs for the "other" channels as per sa-update docs > > (http://spamassassin.apache.org/full/3.4.x/doc/sa-update.txt) Ah, understand. Thanks. If I use --channelfile to list all update servers in one file, I have a problem to mix servers with gpgkey and without. Do I need to use --channel for each server instead of --channelfile to be able to specify --gpgkey or --nogpg or how can I mix that? Ciao Marcus
Re: cron sa-update with multipe channels
On 09/17/2016 10:17 AM, Marcus Schopen wrote: Hi, is there a concept for updating from multiple channels in /etc/cron.daily/spamassassin so that sa-compile is called only if one channel got updates? /etc/cron.daily/spamassassin is not part of the SA project. It's usually something added by a distro maintainer just add conjobs for the "other" channels as per sa-update docs (http://spamassassin.apache.org/full/3.4.x/doc/sa-update.txt)
cron sa-update with multipe channels
Hi, is there a concept for updating from multiple channels in /etc/cron.daily/spamassassin so that sa-compile is called only if one channel got updates? Ciao Marcus