Am 17.02.2015 um 00:54 schrieb ttgh:
@Antony, I particularly appreciated your response (and the spelling of your
name). To clarify: I am not saying that all messages to ALL ex-staff are
spam, only the messages to specific ex-staff. Also, this email server is
acting as relay/filter for an
not as the primary mail
store.
Thank you for any suggestions!
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/train-filter-based-on-spam-to-ex-employees-tp114546.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
On Monday 16 Feb 2015 at 20:16, ttgh wrote:
i saw last week a mail to our previous front-office which left
the company in 2007 and i know the sender in person - it was not spam,
he just replied to a years old message for whatever reason
Thank you, that's an excellent point. In your
Am 16.02.2015 um 21:16 schrieb ttgh:
i saw last week a mail to our previous front-office which left
the company in 2007 and i know the sender in person - it was not spam,
he just replied to a years old message for whatever reason
Thank you, that's an excellent point. In your example,
On Mon, 16 Feb 2015, ttgh wrote:
Reindl, thank you for the reply but in our situation we have 100% confidence
that these old addressees are spam. In any case, that's our risk to bear.
Can you offer any suggestions on how to use these old addressees as a
'honeypot' or even an outright ban list?
% positive their incoming email is spam...
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/train-filter-based-on-spam-to-ex-employees-tp114546p114558.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Am 16.02.2015 um 20:53 schrieb ttgh:
Also I still don't understand why everyone is so reticent to immediately
black-list messages based on these 100% known-bad addressess. For instance,
is it possible for a bulk spam message to trigger false positives?
because we all may have long years
From: ttgh tony.to...@goldenhour.com
Sent: Monday, February 16, 2015 11:44 AM
To: users@spamassassin.apache.org
Subject: train filter based on spam to ex-employees?
We get 'waves' of spam which are addressed to both long-time employees
(usually executives) as well as long-gone employees. It's
Am 16.02.2015 um 18:44 schrieb ttgh:
We get 'waves' of spam which are addressed to both long-time employees
(usually executives) as well as long-gone employees. It's safe to say that
ANYTHING sent to those ex-employees is spam but how do I use those messages
as an instant filter for the valid
description should be.)
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/train-filter-based-on-spam-to-ex-employees-tp114546p114548.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
-office person was someone tasked with
communicating with outside contacts. Also, that their email was still being
monitored.
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/train-filter-based-on-spam-to-ex-employees-tp114546p114563.html
Sent from the SpamAssassin
Am 16.02.2015 um 19:10 schrieb ttgh:
Reindl, thank you for the reply but in our situation we have 100% confidence
that these old addressees are spam. In any case, that's our risk to bear.
Can you offer any suggestions on how to use these old addressees as a
'honeypot' or even an outright ban
On Mon, 16 Feb 2015, ttgh wrote:
John, by 'spam corpus' are you referring to the 'spam' side of the Bayesian
filter?
Correct.
If we manually delay/review these known-bad accounts are we creating a
window of opportunity for those same messages to pass through to current
users?
To a
On Mon, 16 Feb 2015, ttgh wrote:
i saw last week a mail to our previous front-office which left
the company in 2007 and i know the sender in person - it was not spam,
he just replied to a years old message for whatever reason
Thank you, that's an excellent point. In your example, however, I
the Pyzor 'discover' command
but some of our spam was already being tagged with PYZOR_CHECK=1.985 so I
assumed it was working properly.
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/train-filter-based-on-spam-to-ex-employees-tp114546p114570.html
Sent from
On 16.02.15 10:44, ttgh wrote:
We get 'waves' of spam which are addressed to both long-time employees
(usually executives) as well as long-gone employees. It's safe to say that
ANYTHING sent to those ex-employees is spam but how do I use those messages
as an instant filter for the valid
16 matches
Mail list logo
