hip were set so as to prevent it from working.
Broken! :-(
Bob
7;s also a feature that casual users often point to as a reason not
to use the mailing list header fields for filing and instead request
subject tags to use for filing. However subject tags break DKIM
signatures.
Bob
@lbutlr wrote:
> On 20 Apr 2021, at 18:29, Bob Proulx wrote:
> > Hmm... No. I disagree. It's not if-one-then-the-other. All that is
> > needed to disprove it is one example. And as it happens I can list
> > two immediately.
>
> Which does nothing to dis
Antony Stone wrote:
> Bob Proulx wrote:
> > I was not aware that this mailing list requires one to be subscribed
> > to post to it. Does it? It's not necessary on most technical mailing
> > lists.
>
> I would in fact say the exact opposite: most mailing lists do
chive without mangling then they have their
answer. If they find a bad archive that mangles then they are left
still looking. However in this case, hopefully, my answer is still
useful to them even on a bad archive as they can assemble it
themselves.
https://xkcd.com/979/
Hopefully that explains what I meant there! :-)
Bob
add
themselves to the "allow" database in the same way. This is
documented only briefly in the USER'S manual.
Archive access may also be restricted to subscribers. Like
subscribers of the list or the digest list, addresses in the
"allow"
che DOT org
For general information about the mailing lists:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/MailingLists
Bob
will hit on
the this rule.
5.0 KAM_SOMETLD_ARE_BAD_TLD ...
I downgraded the score to 0.01 so I could track it but it is obviously
too agressive of a test at a full 5 points if it is hitting on data
in attachments.
Enjoy! :-)
Bob
Bill Cole wrote:
> Bob Proulx wrote:
> > Only if you have upgraded to an Ubuntu nightly or installing a
> > backport would you get 3.4.5.
>
> Also required: a time machine.
>
> 3.4.5 is not yet released. There have been substantial fixes made to the 3.4
> bra
vely I
know. Because then merges will be required upon package upgrades.
Instead I recommend using a local-local.cf file to be your "really
local" changes. Since that is not packaged as a "conffile" it will
never require merges. However if syntax changes then it will of
course need to be updated to match the new syntax.
I know, I know... Too much information! But you are doing system
administration and this is what you need to know to be doing it
successfully.
Bob
pon rolling releases such as Gentoo, Arch, Void, and
others. Therefore people should choose the one they want. It's a big
universe. I prefer the Stable release model.
Bob
from the correspondent list
> because spamming addresses can creep onto the list, but its very
> infrequently needed.
It is a clever idea! I might add something similar to my own setup. :-)
Bob
sing the check-a...@verifier.port25.com automated test
facility to report on configurations. Send a mail there and an
automated report will be returned.
Bob
On 7/14/20 8:15 AM, Kevin A. McGrail wrote:
The only change is that in 2009, they asked us to standardize on
referring to them as the /*_Apache Nation_*/ but otherwise, there are
no issues with the Apache name. We are proud to use the name Apache
and hope that our great work as a foundation br
se? Is it possible that this process
could be made a bit easier for 'stupid idiots' like me? :-)
What's the saying about assume ? #;)
Linux easy ?? "Tosten en Strudel ? Ha Ha Ha Ha"
Thanks so much. I could NOT have done without your help.
Jerry
On 11/23/201
On 11/23/19 1:07 PM, Jerry Malcolm wrote:
Bob & John Thanks so much for the info. But as if I wasn't dazed
& confused enough already, I have discovered a new variable to the
whole thing. I have set up a couple of sandbox EC2 instances just to
play. I didn't realiz
.
(nightmare)
It is sytemd however, it retains duplicate systemv and is supposed to be
compatible. The same is true with the latest Ubuntu's.
Amazon's systemd apparently is not backwards compatible.
On 11/23/19 2:02 PM, Martin Gregorie wrote:
On Sat, 2019-11-23 at 13:07 -0600, Je
Jerry,
Let's back up a bit.
Let us see your distro via the command lsb_release -a
Also the version via uname -r
Additionally, how did you install spamassassin please ?
On 11/23/19 1:07 PM, Jerry Malcolm wrote:
Bob & John Thanks so much for the info. But as if I was
This may help,
https://cwiki.apache.org/confluence/display/spamassassin/SiteWideBayesSetup
On 11/23/19 10:25 AM, Jerry Malcolm wrote:
Thank you for the information. I apologize for taking the bait. It
just totally blindsided me that anyone here would initiate such a
vicious personal attack.
client to spamd the daemon) and does so using the user
amavis.
Amavis runs tend to run seperately from the normal spamassassin run
structure and can be difficult at best to follow/troubleshoot.
Clear as mud ?
Regards
Bob
On 11/23/19 11:09 AM, Jerry Malcolm wrote:
Meanwhile, back at the ranch
est fqdn it Will be your problem
> :)
I have often done similar by sending the email to nobody@theirdomain
where theirdomain is the sites fqdn. I am often surprised at how
often it is rejected as already in use by another account! Someone
else has beat me to it!
Bob
I would like to thank everyone for your responses, they have been great.
This maillist has not failed to help me improve things everytime I use it.
So this particular server has virtual domains and virtual users in a
folder hierarchy there under all owned by 'vmail' user.
I have done the follow
Well, now I am more thoroughly confused than usual. #:)
On 4/15/18 2:04 PM, RW wrote:
On Sun, 15 Apr 2018 13:39:31 -0500
Computer Bob wrote:
Update:
For this location, it is ok to have a central bayes database, so I
turned off AWL, adjusted local.cf to contain:
bayes_path /Central_Path
Here is a root scan: https://pastebin.com/qdXMRzKb
Here is the same run under spamd: https://pastebin.com/SvvYptYv
On 4/15/18 11:34 AM, Computer Bob wrote:
Greeting all, *
*I have had some issues with spam getting low scores and in
troubleshooting I have found that if I run a command line
Greeting all, *
*I have had some issues with spam getting low scores and in
troubleshooting I have found that if I run a command line check with
"spamassassin -D -x < test" on a mail in question, I get a very high
score when run under user root. When run under user spamd it gets a low
passing
Thank you,
Yes, DCC Razor and Pyzor are installed and running.
I will look into your other suggestions and let you know.
On 1/30/18 1:37 PM, David Jones wrote:
On 01/30/2018 11:47 AM, Computer Bob wrote:
Also:
I modified the following SA local.cf items
massassin folder.
Any further suggestions ?
On 1/30/18 11:31 AM, Computer Bob wrote:
Follow-up,
I did a dist-upgrade to Ubuntu 16.04 LTS and the process whacked the
SA bad.
Removal and purging of SA was necessary and a fresh reinstall brought
it back.
It is currently "factory fresh".
Follow-up,
I did a dist-upgrade to Ubuntu 16.04 LTS and the process whacked the SA bad.
Removal and purging of SA was necessary and a fresh reinstall brought it
back.
It is currently "factory fresh".
Still my problems persist, I am pursuing this via the Amavis mail list
as command line calls
-Spam-Status: Yes, score=23.0 required=4.0 tests=DKIM_SIGNED,
RAZOR2_CF_RANGE_51_100,RAZOR2_CHECK,RCVD_IN_SBL_CSS,RDNS_NONE,T_DKIM_INVALID,
URIBL_ABUSE_SURBL,URIBL_BLACK,URIBL_DBL_SPAM autolearn=no
autolearn_force=no
version=3.4.0
MIME-Version: 1.0
Bob
RAZOR and URIBL hits.
Is
=3.4.0
MIME-Version: 1.0
Bob
RAZOR and URIBL hits.
Is amavis perhaps configured to disable network tests?
On 1/26/18 2:48 PM, David Jones wrote:
On 01/26/2018 02:39 PM, b...@inter-control.com wrote:
The headers that get through are usually along the lines of:
X-Spam-Flag: NO
X-Spam-Score
autolearn_force=no
version=3.4.0
MIME-Version: 1.0
Bob
RAZOR and URIBL hits.
Is amavis perhaps configured to disable network tests?
On 1/26/18 2:48 PM, David Jones wrote:
On 01/26/2018 02:39 PM, b...@inter-control.com wrote:
The headers that get through are usually along the lines of
which then creates /var/lib/spamassassin as root. Once that
happens the non-root debian-spamd is locked out.
To restore permissions:
chown -R debian-spamd:debian-spamd /var/lib/spamassassin
And in the future avoid running it as root manually. With great power
comes great responsibility. :-)
Bob
ng local env sets before the command.
I will just jump in her long enough to say that using 'env' like that
is the idiomatic way to avoid differences in shells between sh and csh
(and therefore between bash, dash, posh, ash, ksh, mksh, zsh, and I
think you get the idea). It is a way to guarentee the ability to set
variables regardless of shell. This make documenting things easier.
Bob
-spam" for Bayes training.
Bob
cist
usage of tarbaby is of a problem that gets worse trying to solve it.
(However if you really do mean to add MX of valid domains then that is
correct slang for it.) The racist interpretation is best avoided too.
Bob
John Hardin wrote:
> Bob Proulx wrote:
> > John Hardin wrote:
> > > Bob Proulx wrote:
> > > > And that is also why I don't understand the move from /bin/* to
> > > > /usr/bin/* and the same for lib and others. That makes the "usr" par
Reindl Harald wrote:
> schrieb Bob Proulx:
> >They are producing gratuitous system differences for no good reason.
>
> not true - hence the symlink and "they" are in the meantime not only fedora,
> google will show
>
> >And that is also why I don't
John Hardin wrote:
> Bob Proulx wrote:
> > And that is also why I don't understand the move from /bin/* to
> > /usr/bin/* and the same for lib and others. That makes the "usr" part
> > completely useless. It would be better to move everything from
> > /u
Reindl Harald wrote:
> schrieb Bob Proulx:
> > Seeing SHELL=/usr/bin/bash I must comment that the setting is quite
> > unusual. It would normally be /bin/sh. Or on some systems be
> > /bin/bash. It is quite unusual to see /usr/bin/bash there
>
> it was /bin/bash i
Reindl Harald wrote:
>
> schrieb LuKreme:
> >Bob Proulx wrote:
> > > The syntax "variable=value command" is a /bin/sh syntax which sets the
> > > variable for just that command. In the above sa-update would get the
> > > PATH setting. But then
LuKreme wrote:
> Bob Proulx wrote:
> > The syntax "variable=value command" is a /bin/sh syntax which sets the
> > variable for just that command. In the above sa-update would get the
> > PATH setting. But then && terminates that command.
>
> I’m
mands started from that crontab.
Personally I prefer to use a file /etc/cron.daily/spamassassin which
then calls all of the individual programs. The /etc/cron.daily is a
directory of scripts (not crontabs) where each script is run once
daily one after the other. Since that is a script you can set PATH in
that script and again it would be set for all subsequent invocations.
Bob
Reindl Harald wrote:
> schrieb Bob Proulx:
> >Reindl, Please play nice. Dave was exactly correct and friendly with
> >his response to you. Liberty, tolerance and respect are not zero sum
> >concepts. (Stealing the excellent phrase from Judge Robert Hinkle.)
>
> frien
ray value.
To be a literal at sign in the string it needs "\@array" and that is
the Perl syntax.
http://perldoc.perl.org/perldata.html
Bob
rated rule set / sa-update channel going.
Good poke! And I will leave this to the list to show further
enthusiasm for the project instead of simply promising time off list.
Bob
the html alternative and would have read all of the text in
the font of your choice. Plain text is for me the most accessible.
Bob
John Hardin wrote:
> Bob Proulx wrote:
> >But, but, but... It also failed lint and produced cron noise on my
> >perl 5.20.1 system too. Running spamassassin 3.4.0. That is later
> >than perl 5.18 and it definitely produced the warning message.
>
> That's two s
John Hardin wrote:
> Bob Proulx wrote:
> > There have been multiple facets to this problem. The first was a rule
> > update that produced warnings that produced email from every cron run
> > sa-update / sa-learn run if run on recent released spamassassin 3.4.0
> > bu
the dynamic rule update
emitted that warning for you too. But the new suggested rule using
the improved if expression gating syntax will work okay for you.
Hope that helps,
Bob
jdow wrote:
> John Hardin wrote:
> > Bob Proulx wrote:
> > > I am hoping this won't make you gun-shy from continuing your fine
> > > work on the project. Please don't let this minor bump in the road
> > > discourage you from future work. That would
&& perl_version >= 5.01
header __PDS_FROM_2_EMAILS From =~
/^\W+([\w+.-]+\@[\w.-]+\.\w\w++)(?:[^\n\w<]{0,80})?<(?!\1)[^\n\s]*\@/i
endif
This produced no lint warnings with the above combination. I am
missing why it is causing problems in Burnie's configuration. Is
3.3.1 really that different here from 3.3.2 which is silent?
Bob
security is the one feature of the system that by design
makes it harder to use.
Bob
discourage you from future work. That would be a tragedy for
the project and for the users.
Please keep up the good work!
Bob
Chris wrote:
> Bob Proulx wrote:
> > The -D option takes an argument. If there is an argument following -D
> > then it becomes the argument to -D. In the above the argument to -D
> > is -t due to it being positioned after -D. That is not what you want.
>
> Sorry f
#x27;t really needed with -t. But it is a valid combination.
AIUI the -d removes markup while the -t ignores any existing markup.
So with -t it doesn't matter but it is a valid combination. In any
case my standard scripts have -d -t all of the time with no problems.
Bob
o become involved.
> This is initial "brainstorming"...
Thank you very much for raising this topic for discussion. If these
were available I would use them. If there is some way that I could
help I would be very happy to do so.
Bob
arn (or spamc -L) procmail recipe that has a
> serialization lock.
I run sa-learn --expire from cron. I run spamc --learntype=spam
otherwise using a different invocation not involving procmail.
Bob
Give it a try and monitor system resource utilization. Start
tuning at spamd. Tune other things as needed afterward.
:0fw
| spamc -x
:0e
{
EXITCODE=$?
}
Bob
ject =~ /^(Annual|Perpetual) license key
> generated for/ && mail_for(qr/provision_request/);
> accept_mail("Buildbot") if $m->subject =~ /^buildbot success/;
> accept_mail("Buildbot") if $m->subject =~ /^buildbot failure/;
>
> $m->accept("$p/Received-Archive/$REC");
>
> which I find far more readable than .procmailrc recipes.
I think this proves that beauty is in the eye of the beholder.
:-)
Bob
ache.org/spamassassin/MailingLists
If you are having trouble unsubscribing and need human assistance then
send a message to the mailing list owner at the -owner address. The
mailing list owner address is .
Bob
apache.org mailing list expert. Great stuff!
http://untroubled.org/ezmlm/manual/
The most important takeaway is that if you have problems with a
mailing list then contact the mailing list owner at the -owner
address.
http://untroubled.org/ezmlm/manual/Contacting-the-Owner.html#Contacting-the-Owner
Hope that helps someone!
Bob
Jari Fredriksson wrote:
> haproxy is just a small app capable of working as a proxy for http
> or plain tcp connections. HA.
What are you using for the Bayes database on the distributed compute
farm? (Just curious...)
Bob
needs no file
locking support in Postfix or in other mail software.
> ...Great, now I'm paranoid. Thanks, Ian. ;-) I guess I can go back and
> force the exports to ne NFS3 instead of NFS4 so I can explicitly state the
> nolocks option
Paranoia is good. But using Maildir format would also be okay too.
Bob
John Hardin wrote:
> Bob Proulx wrote:
> >Is there a way to use this to create a SpamAssassin rule to try to
> >catch this type of spam?
>
> Grab the RAND_HEADER rules (there are several related, get them all) from my
> sandbox and score as you see fit.
Ah... Already d
://pastebin.com/0Ga7g0UX
Looking at the headers by eye and flipping from message to message it
is pretty easy to visually see the pattern that is created.
Is there a way to use this to create a SpamAssassin rule to try to
catch this type of spam?
Thanks,
Bob
P.S. Note that if I run these thro
Reindl Harald wrote:
> schrieb Bob Proulx:
> > Being able to undeliver spam after it has been detected later and if
> > it is as yet unread is none of those bad things. This is a positive
> > anti-spam feature in the core feature set of an email provider.
>
> honestl
Reindl Harald wrote:
> schrieb Bob Proulx:
> > Ted Mittelstaedt wrote:
> >> Bob Proulx wrote:
> >>> Plus Google can "undeliver" a message from your Inbox if you have not
> >>> read it yet. Say a spammer slowly sends sneaky spam to 10,000 peopl
Ted Mittelstaedt wrote:
> Bob Proulx wrote:
> >Plus Google can "undeliver" a message from your Inbox if you have not
> >read it yet. Say a spammer slowly sends sneaky spam to 10,000 people.
> >After the first dozen report the message as spam then the next 9988
>
neaky spam to 10,000 people.
After the first dozen report the message as spam then the next 9988
have the message undelivered from their Inbox over to the Junk folder.
That is a powerful feature but one I have never implemented for
myself.
Bob
Ted Mittelstaedt wrote:
> Bob Proulx wrote:
> >Ted Mittelstaedt wrote:
> > > What do other people do? Or are we just going to end up with an
> > > Internet in about 10 years where every single email box is either
> > > on Microsoft 365 or Gmail and the NSA ha
ld has trouble reacting to a
quickly changing environment.
Bob
/ with updated rules by
cron. Does your version do this? I think it likely that those rules
are only missing until sa-update has been run successfully. Perhaps
you system has a cron script and it simply needs to be enabled?
Bob
ot to be wearing a target around me. Instead by not
being pinned between the gorillas I could concentrate on adding value
in other places. The job mutates and is different but still
continues.
Bob
Expecially on a busy mail server the load from
DNS can be appreciable.
I would enjoy reading any comments you might have on optimum DNSBL
anti-spam usage.
Bob
ct_non_fqdn_helo_hostname,
reject_invalid_helo_hostname,
reject_unauth_destination,
reject_invalid_hostname,
reject_non_fqdn_hostname,
reject_non_fqdn_sender,
reject_non_fqdn_recipient,
reject_unknown_sender_domain,
reject_unknown_recipient_domain,
reject_rbl_client zen.spamhaus.org,
permit
Hope that helps and good luck!
Bob
any people
routinely send mail forging their receive address. Therefore while
the above suggestion is perfectly valid I tend to do nothing with
domains. Instead I tend to blacklist or whitelist only client host IP
addresses. However there is no single way. It takes a combined arms
strategy of many different things in order to effectively deal with
spammers. I say, do them all to some extent and then you will be
mostly covered. :-)
Bob
your anti-spam efforts. I highly
recommend doing at least this in smtpd_recipient_restrictions:
reject_rbl_client zen.spamhaus.org
You can read about the zen DNSBL here:
http://www.spamhaus.org/zen/
Bob
meone could
explain that in better detail.
> I added CRM114 and BOGOFILTER plugins as a "balance of power" to
> Bayesian and it's working very well again.
Both of those are good learning Bayes engines on their own.
Bob
RW wrote:
> Bob Proulx wrote:
> > The script is looping through mail files in a maildir and processing
> > them remotely on the server through sa-learn. After processing the
> > messages it is moving the messages to mark them as having been read.
>
> No, the Maildir s
case that is doing other things. It would
need a little work. But it might give some ideas.
Bob
ed into the spam mailbox through to sa-learn --spam
on the server training the SpamAssasin Bayes engine on the message.
And the opposite for non-spam for misclassified messages. For the end
mail reading user no command line knowledge is needed. They simply
need to be able to save email into mail folders. Simple for them.
All of the effort is in the backend on the mail server. Would work
for a large number of users.
Bob
Wolfgang Zeikat wrote:
> Bob Proulx wrote:
> > spamassassin -d -t -D < mail.file | less
>
> Note: in the above command you did _not_ redirect STDERR to STDOUT
Oops. My bad. I should have shown that. I was concentrating on the
options and neglected the right hand side.
>
Kevin A. McGrail wrote:
> Bob Proulx wrote:
> >It looks to me that -D now disables Bayes as a regression in 3.4.0.
>
> Can't recreate and can't see how that's possible. -D turns on debug
> output and I don't see any references to the config option in the
>
BAYES_* scoring is seen. Neither is it enabled even when
debugging "bayes" specifically. Making that feature rather hard to
use now. :-(
spamassassin -d -t -D bayes < mail.file | less
It looks to me that -D now disables Bayes as a regression in 3.4.0.
Thanks,
Bob
gt; rules.
This appears to be working now. I can run sa-update and all appears
to be working.
Thank you for trying not to dump the 3.3.x rules. Those are still
going to be in use for a while.
Thanks!
Bob
Kris Deugau wrote:
> Bob Proulx wrote:
> > How hard would it be to use SpamAssassin's mail handling routines to
> > extract the Received: IP address header chain using the already
> > configured trusted_networks configuration? Does anyone have any hints
> > on how
Karsten Bräckelmann wrote:
> Bob Proulx wrote:
> > How hard would it be to use SpamAssassin's mail handling routines to
> > extract the Received: IP address header chain using the already
> > configured trusted_networks configuration?
>
> How hard? Depends... A
ation
into my own Perl script then I would be able to do some exploration of
a few ideas.
Thanks,
Bob
me glitches along the way when it hasn't been
done for a while. Thanks for your work on this!
Bob
$ dig 2.3.3.updates.spamassassin.org +short txt
"1568594"
Unfortunately the mirrors are configured such that it isn't possible
to list what files are actually there so I can't tell anything
further. Any ideas?
Bob
as asking why the score for BAYES_999 is separate from
the other BAYES_* scores. And why the default is lower than BAYES_99.
BAYES_999 seems uniquely different from the rest. A wiki page
describing it would be a perfect and would keep the noise from people
like me off the mailing list. :-)
Bob
David F. Skoll wrote:
> Bob Proulx wrote:
> > And would you suggest distributing your well-averaged database to
> > people who install SpamAssassin to as to seed their Bayes?
>
> We have a distribution mechanism built into our software.
>
> > I think having users sta
kes the most sense. And users can always
learn from their current mailbox of past messages so it isn't much
hardship.
Bob
en it will immediately start learning. Learning is
not limited by having an empty database. Only classification is
limited until learning has occurred.
Bob
Axel Werner wrote:
> unsubscribe
list-help: <mailto:users-h...@spamassassin.apache.org>
list-unsubscribe: <mailto:users-unsubscr...@spamassassin.apache.org>
List-Post: <mailto:users@spamassassin.apache.org>
List-Id:
https://wiki.apache.org/spamassassin/MailingLists
--
Bob
Karsten Bräckelmann wrote:
> Bob Proulx wrote:
> > * ^X-Spam-Level: \*{10}
>
> Unfortunately, no. While procmail implements some flavor of "extended"
> Regular Expressions, there are still quite some differences to other
> regex engines, like egrep's o
whatever you feel is reasonable.
I would probably say ten days. That way if I need to go looking for a
potentially very spammy message I could still find it within the time
window. I would run this daily from cron.
find $HOME/Mail/devnull -type f -mtime +10 -delete
HTH,
Bob
again. If it does then I suspect some rollover problem. If it does
not then I suspect a transient file lock glitch of some sort.
Bob
make them available
directly to anyone who wished to peek at them to get a better idea of
what is happening.
> If you learn some spam/ham by hand do the nspam/nham counters go up?
Yes. I just did a test to verify. One ham, checked, incremented nham
counter, one spam, checked, incremented nspam counter.
Thanks!
Bob
would a token hang around in the database assuming that no new message
token "refreshes" it?
Thanks,
Bob
Various details:
$ ll -hog .spamassassin/bayes_*
-rw--- 1 12K Feb 7 16:30 .spamassassin/bayes_journal
-rw--- 1 75M Feb 7 16:29 .spamassassin/bayes_seen
-rw--- 1 5
1 - 100 of 550 matches
Mail list logo
