Re: Spam tagging g in subject doubled up?
On 09.11.2016 20:57, @lbutlr wrote: > On Nov 8, 2016, at 2:49 AM, Tilman Schmidtwrote: >> On 02.11.2016 10:46, Indunil Jayasooriya wrote: >>> >>> pls try below command with less >>> >>> >>> less /etc/amavisd.conf |grep -i sa_spam_subject_tag >> >> Argh. Useless use of less is even worse than useless use of cat. >> Just do >> >> grep -i sa_spam_subject_tag /etc/amavisd.conf > > It is much easier to change the grep terms if you use > > cat | grep > > (up arrow, ^w, type new term) No need to waste a cat for that. (Poor beast.) You can put the search term last on the grep command line. Try grep /etc/amavisd.conf -ie sa_spam_subject_tag > I have no idea why anyone would use less there though. Indeed. Tilman
Re: Spam tagging g in subject doubled up?
On Nov 8, 2016, at 2:49 AM, Tilman Schmidtwrote: > On 02.11.2016 10:46, Indunil Jayasooriya wrote: >> >> pls try below command with less >> >> >> less /etc/amavisd.conf |grep -i sa_spam_subject_tag > > Argh. Useless use of less is even worse than useless use of cat. > Just do > > grep -i sa_spam_subject_tag /etc/amavisd.conf It is much easier to change the grep terms if you use cat | grep (up arrow, ^w, type new term) I have no idea why anyone would use less there though.
Re: Spam tagging g in subject doubled up?
On 02.11.2016 10:46, Indunil Jayasooriya wrote: > > pls try below command with less > > > less /etc/amavisd.conf |grep -i sa_spam_subject_tag Argh. Useless use of less is even worse than useless use of cat. Just do grep -i sa_spam_subject_tag /etc/amavisd.conf HTH Tilman
Re: Spam tagging g in subject doubled up?
pls try below command with less less /etc/amavisd.conf |grep -i sa_spam_subject_tag MYOUTPUT $sa_spam_subject_tag = '***SPAM*** '; On Wed, Nov 2, 2016 at 3:12 PM, Admin Beckspacedwrote: > hello ;) > > not sure how you search things? but whenever i have problems finding > things i do a search on CLI > > first i browse to the directory, e.g. cd /some/dir > > and then do a recursive, case insensitive search via grep > > grep -ri "mysearchpattern" . > > the dot . being the current directory > > or specify a path with the grep command > > grep -ri "mysearchpattern" /path/to/look/in > > this always helped me finding the culprit ;) > > greetings > becki > > > > Am 02.11.2016 um 10:24 schrieb @lbutlr: > >> Anyone? >> >> On Oct 29, 2016, at 10:05 AM, @lbutlr wrote: >> >>> I can’t find where that *Spam* Subject tag is set; I’ve searched every >>> file in and under /usr/local/etc/ & /etc and the only match is in >>> amavisd.cong.sample and that is “***Spam***”. >>> >>> I also cannot find where amavisd’s bayes files are. >>> >>> (I’ve been told they are in /var/spool/amavis/.spamassassin, but these >>> files do not get updated). The user vscan that runs amavis has a home >>> folder at /var/maiad/ but that .spamassassin folder is empty. >>> >> … >> >> >> >> > -- cat /etc/motd Thank you Indunil Jayasooriya http://www.theravadanet.net/ http://www.siyabas.lk/sinhala_how_to_install.html - Download Sinhala Fonts
Re: Spam tagging g in subject doubled up?
On Wed, Nov 2, 2016 at 2:54 PM, @lbutlrwrote: > Anyone? > > On Oct 29, 2016, at 10:05 AM, @lbutlr wrote: > > I can’t find where that *Spam* Subject tag is set; I’ve searched every > file in and under /usr/local/etc/ & /etc and the only match is in > amavisd.cong.sample and that is “***Spam***”. > > in /etc/amavisd.conf (CentOS 6x) $sa_spam_subject_tag = '***SPAM*** '; > > I also cannot find where amavisd’s bayes files are. > > > > (I’ve been told they are in /var/spool/amavis/.spamassassin, but these > files do not get updated). The user vscan that runs amavis has a home > folder at /var/maiad/ but that .spamassassin folder is empty. > > … > > -- cat /etc/motd Thank you Indunil Jayasooriya http://www.theravadanet.net/ http://www.siyabas.lk/sinhala_how_to_install.html - Download Sinhala Fonts
Re: Spam tagging g in subject doubled up?
hello ;) not sure how you search things? but whenever i have problems finding things i do a search on CLI first i browse to the directory, e.g. cd /some/dir and then do a recursive, case insensitive search via grep grep -ri "mysearchpattern" . the dot . being the current directory or specify a path with the grep command grep -ri "mysearchpattern" /path/to/look/in this always helped me finding the culprit ;) greetings becki Am 02.11.2016 um 10:24 schrieb @lbutlr: Anyone? On Oct 29, 2016, at 10:05 AM, @lbutlrwrote: I can’t find where that *Spam* Subject tag is set; I’ve searched every file in and under /usr/local/etc/ & /etc and the only match is in amavisd.cong.sample and that is “***Spam***”. I also cannot find where amavisd’s bayes files are. (I’ve been told they are in /var/spool/amavis/.spamassassin, but these files do not get updated). The user vscan that runs amavis has a home folder at /var/maiad/ but that .spamassassin folder is empty. …
Re: Spam tagging g in subject doubled up?
Anyone? On Oct 29, 2016, at 10:05 AM, @lbutlrwrote: > I can’t find where that *Spam* Subject tag is set; I’ve searched every file > in and under /usr/local/etc/ & /etc and the only match is in > amavisd.cong.sample and that is “***Spam***”. > > I also cannot find where amavisd’s bayes files are. > > (I’ve been told they are in /var/spool/amavis/.spamassassin, but these files > do not get updated). The user vscan that runs amavis has a home folder at > /var/maiad/ but that .spamassassin folder is empty. …
Re: Spam tagging g in subject doubled up?
maybe you just have a typo with the starting and closing sign ' and ‘ are different! have a close look: $sa_spam_subject_tag = '(Spam _SCORE(00)_) ‘; the starting and closing sign don't match up. perhaps this can be the cause? try $sa_spam_subject_tag = '(Spam _SCORE(00)_)'; greetings becki Am 29.10.2016 um 05:25 schrieb @lbutlr: I have: $sa_spam_subject_tag = '(Spam _SCORE(00)_) ‘; and I get spam tagging like this: (Spam? 05.1) *Spam* 5.196:Recent CNN-Report… The string “*Spam” does not appear in my amavisd.conf There are no uncommented lines in /var/spool/amavis/.spamassassin/local.cf Not sure where else to look (and the bases files in /var/spool/amavis/.spamassassin/ are not being updated)