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 <maik.linnem...@provit.info> 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 <dbfunk (at) engineering.uiowa.edu> College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include <std_disclaimer.h> Better is not better, 'standard' is better. B{
