Re: --virtual-config-dir=pattern is not substituted
Strange, I am missing that configuration in /etc/postfix/master.cf. Will add them. Am Donnerstag, 29. November 2018, 01:15:39 CET schrieb Bill Cole: > On 28 Nov 2018, at 17:53, Eggert Ehmke wrote: > > Do you mean the --username option in /etc/default/spamassassin? > > No. Postfix is running the 'spamc' program in some fashion, usually via > a pipe transport configured in master.cf. That transport (typically an > intermediary script) needs to be passed the recipient address by Postfix > and may need to transform it in some fashion (e.g. strip the domain > maybe) to use it as the argument to the '-u' option in an invocation of > spamc. > > > It is set to the generic user --username=debian-spamd > > > > > > Thank you > > > > Am Mittwoch, 28. November 2018, 22:41:38 CET schrieb RW: > >> On Tue, 27 Nov 2018 18:01:04 +0100 > >> > >> Eggert Ehmke wrote: > >>> I have Spamassassin running on Debian with Postfix, Dovecot etc. It > >>> seems to work, Spam is filtered to my Quarantine. I have some > >>> virtual > >>> mailboxes in /var/mail/vhosts and have set up the Option > >>> > >>> -x --virtual-config-dir=/var/mail/vhosts/%d/%l/spamassassin > >>> This does not work, in the log file /var/log/spamassassin/spamd.log > >>> > >>> I find these lines: > >>> > >>> warn: plugin: eval failed: bayes: (in learn) locker: safe_lock: > >>> cannot create tmp lockfile /var/ > >>> mail/vhosts///spamassassin/bayes.lock.domain.de.3653 > >>> for /var/mail/vhosts///spa > >>> > >>> > >>> So the user name and the domain are not replaced in the pattern. > >>> What may be wrong?? > >> > >> Are you sure the recipient address is being passed to spamc via the > >> -u > >> option?
Re: --virtual-config-dir=pattern is not substituted
Do you mean the --username option in /etc/default/spamassassin? It is set to the generic user --username=debian-spamd Thank you Am Mittwoch, 28. November 2018, 22:41:38 CET schrieb RW: > On Tue, 27 Nov 2018 18:01:04 +0100 > > Eggert Ehmke wrote: > > I have Spamassassin running on Debian with Postfix, Dovecot etc. It > > seems to work, Spam is filtered to my Quarantine. I have some virtual > > mailboxes in /var/mail/vhosts and have set up the Option > > > > -x --virtual-config-dir=/var/mail/vhosts/%d/%l/spamassassin > > This does not work, in the log file /var/log/spamassassin/spamd.log > > > > I find these lines: > > > > warn: plugin: eval failed: bayes: (in learn) locker: safe_lock: > > cannot create tmp lockfile /var/ > > mail/vhosts///spamassassin/bayes.lock.domain.de.3653 > > for /var/mail/vhosts///spa > > > > > > So the user name and the domain are not replaced in the pattern. > > What may be wrong?? > > Are you sure the recipient address is being passed to spamc via the -u > option?
--virtual-config-dir=pattern is not substituted
I have Spamassassin running on Debian with Postfix, Dovecot etc. It seems to work, Spam is filtered to my Quarantine. I have some virtual mailboxes in /var/mail/vhosts and have set up the Option -x --virtual-config-dir=/var/mail/vhosts/%d/%l/spamassassin This does not work, in the log file /var/log/spamassassin/spamd.log I find these lines: warn: plugin: eval failed: bayes: (in learn) locker: safe_lock: cannot create tmp lockfile /var/ mail/vhosts///spamassassin/bayes.lock.domain.de.3653 for /var/mail/vhosts///spa So the user name and the domain are not replaced in the pattern. What may be wrong?? Cheers, Eggert
unsubscribe
Re: Mysterious false positives in inbox
Perhaps this is a misunderstanding. By "same" I mean "this server". The mail was originally received by my server via TLS, processed by mailman and then delivered with the ***SPAM*** subject line to the recipients of the mailing list, but not to the Quarantine. One of the recipients is my own mailbox. So in any case, the poorly configured server is my own. Am Mittwoch, 9. Mai 2018, 10:35:34 CEST schrieb Ian Zimmerman: > On 2018-05-09 13:08, Eggert Ehmke wrote: > > > Wild stab - maybe they're entering the system already with > > > ***SPAM*** in the subject? > > > > The mail also originated from the same server. > > All the more reason to suspect the "wild stab" is correct. > > In my experience this is quite common on some poorly configured mailing > list servers.
Re: Mysterious false positives in inbox
The mail also originated from the same server. Ok, I look into the amavisd config. Thanks, Eggert Am Mittwoch, 9. Mai 2018, 14:06:08 CEST schrieb Reio Remma: > Wild stab - maybe they're entering the system already with ***SPAM*** in > the subject? > > With amavisd-new it's amavisd that modifies the subject, local.cf > shouldn't have an effect on that. > > Good luck, > Reio > > On 09.05.18 14:02, Eggert Ehmke wrote: > > Hello, > > > > I have spamassassin 3.4.1 / amavisd / postfix / dovecot installed on > > my Debian 9.4 server. I also run a mailman mailing list. Most of the > > time, all runs very well, but occasionally I get mails marked > > ***SPAM*** in my inbox. These are indeed no spam, but valid mails > > forwarded by mailman. Training seems to have no effect. > > > > The mails in question have those header entries: > > > > X-Virus-Scanned: Debian amavisd-new at > > > > X-Spam-Flag: NO > > > > X-Spam-Score: -1 > > > > X-Spam-Level: > > > > X-Spam-Status: No, score=-1 tagged_above=-999 required=3 > > tests=[ALL_TRUSTED=-1, SHORTCIRCUIT=-0.0001] autolearn=disabled > > > > With those entries, why is the ***SPAM*** put into the subject line?? > > > > In /etc/spamassassin/local.cf are these entries: > > > > rewrite_header Subject ***SPAM*** report_safe 0 trusted_networks > of my other server> required_score 2.0 use_bayes 1 bayes_auto_learn 1 > > ifplugin Mail::SpamAssassin::Plugin::Shortcircuit shortcircuit > > ALL_TRUSTED on endif # > > Mail::SpamAssassin::Plugin::Shortcircuit Any idea? > > > > Eggert
Mysterious false positives in inbox
Hello, I have spamassassin 3.4.1 / amavisd / postfix / dovecot installed on my Debian 9.4 server. I also run a mailman mailing list. Most of the time, all runs very well, but occasionally I get mails marked ***SPAM*** in my inbox. These are indeed no spam, but valid mails forwarded by mailman. Training seems to have no effect. The mails in question have those header entries: X-Virus-Scanned: Debian amavisd-new at X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=3 tests=[ALL_TRUSTED=-1, SHORTCIRCUIT=-0.0001] autolearn=disabled With those entries, why is the ***SPAM*** put into the subject line?? In /etc/spamassassin/local.cf are these entries: rewrite_header Subject ***SPAM*** Eggert
