I am open to modifying my rules as needed. Send spamples via pastebin or
see the instructions in KAM.cf.
On Mon, Apr 9, 2018, 21:40 Alex Regan wrote:
> Hi,
>
> What's the best way to add a URL shortener to the current list? Would I
> have to rewrite __URL_SHORTENER? I also notice this subrule d
Hi,
What's the best way to add a URL shortener to the current list? Would I
have to rewrite __URL_SHORTENER? I also notice this subrule doesn't
account for the https version of the list. Is that intentional?
More specifically, we've received some spam from back.ly. I could reject
it outright
On 09/04/18 15:24, David Jones wrote:
I was wondering if anyone knows of an SA plugin or another method to
determine if the envelope-from domain has a valid MX record that is
listening on TCP port 25. I don't think it would be a major scorer but
it could be useful in meta rules.
This might
formail so far is working exactly as I need.
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Mon, Apr 9, 2018 at 1:59 PM, RW wrote:
> On Mon, 9 Apr 2018 10:48:31 -0
On Mon, 9 Apr 2018 10:48:31 -0400
Kevin A. McGrail wrote:
> Hi All,
>
> I get a lot of spamples submitted to me and it would be nice if there
> was an automated way to synthesize the mbox separator. Looking to
> see if there is an existing process before I reinvent the wheel.
And it's quite eas
On Mon, 9 Apr 2018 09:24:23 -0500
David Jones wrote:
> I was wondering if anyone knows of an SA plugin or another method to
> determine if the envelope-from domain has a valid MX record that is
> listening on TCP port 25. I don't think it would be a major scorer
> but it could be useful in meta
On Sun, 8 Apr 2018 07:41:50 -0500
David Jones wrote:
> On 04/07/2018 10:42 AM, Sebastian Arcus wrote:
> > I've enclosed one of the messages received here:
> >
> > https://pastebin.com/9Bmu3pj1
>
> I added this to the 60_whitelist_auth.cf to trust this sender:
>
> def_whitelist_auth *@*.tpr.g
Hello, thanks for the reply. I use one database bayes for all email accounts
(not sites, sorry for the error)
here i show some spamassassin configuration
local.cf
bayes_expiry_max_db_size 15
bayes_learn_to_journal 1
bayes_auto_learn 0
include custom_rules
include whitelist
include black
On 09.04.18 11:01, Emanuel Gonzalez wrote:
I use one bayes database to all sites in my server.
sites? afaik spamd and MTAs differ between mailboxes, not sites.
What would be the best way to avoid my problem?? create a database of bayes
by email account? Or create a unique database of bayes f
I'm receiving attachments from webforms primarily that are just the message
headers & body but missing the mbox separator. However, most of my tooling
is designed for mbox. I'll try the formail idea, thanks!
--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair E
Kevin A. McGrail skrev den 2018-04-09 16:46:
If you are interested, let me know.
i am interested to learn how to setup mimedefang, not how to test mx :=)
that will always be a job for mta to make sure this is valid
Kevin A. McGrail wrote:
Hi All,
I get a lot of spamples submitted to me and it would be nice if there
was an automated way to synthesize the mbox separator. Looking to see
if there is an existing process before I reinvent the wheel.
formail < messagefile >> mboxfile
However, whatever magic
David Jones skrev den 2018-04-09 16:24:
I was wondering if anyone knows of an SA plugin or another method to
determine if the envelope-from domain has a valid MX record that is
listening on TCP port 25. I don't think it would be a major scorer
but it could be useful in meta rules.
thats a job
On 09/04/2018 16:24, David Jones wrote:
Been playing around with rspamd over the weekend to see how it
compares and so far not that impressed. It has a few features that
are interesting like the MX check but other than that it's not as
impressive as the author makes it out to be on the webs
Well, here's the code I use in filter_sender in MD to check for a validMX.
The module needs a public release with some updates and doesn't work great
with IPv6 but the code is solid and been in use for a long time at my firm.
#IF NOT A BOUNCE, THEN CHECK VALID MX RECORDS
if ($sender ne '<>') {
On 04/09/2018 09:58 AM, Dianne Skoll wrote:
On Mon, 9 Apr 2018 09:56:20 -0500
David Jones wrote:
On 04/09/2018 09:44 AM, Reindl Harald wrote:
you simply don't want connect to every innocent MX which inbound
mail is forged because for the sake of god you are attacking the
victim of spoofed mai
On Mon, 9 Apr 2018 09:56:20 -0500
David Jones wrote:
> On 04/09/2018 09:44 AM, Reindl Harald wrote:
> > you simply don't want connect to every innocent MX which inbound
> > mail is forged because for the sake of god you are attacking the
> > victim of spoofed mails and you are easily part of a di
On 04/09/2018 09:46 AM, Kevin A. McGrail wrote:
Hi Dave,
I do similar work in MIMEDefang using the a redis backend for caching
valid recipients combined with Net::validMX that can check to see if a
sender has valid MX before sending. I have a release of Net::validMX
I'm about to post this we
On 04/09/2018 09:44 AM, Reindl Harald wrote:
Am 09.04.2018 um 16:24 schrieb David Jones:
I was wondering if anyone knows of an SA plugin or another method to
determine if the envelope-from domain has a valid MX record that is
listening on TCP port 25. I don't think it would be a major scorer
Hi All,
I get a lot of spamples submitted to me and it would be nice if there was
an automated way to synthesize the mbox separator. Looking to see if there
is an existing process before I reinvent the wheel.
Regards,
KAM
Hi Dave,
I do similar work in MIMEDefang using the a redis backend for caching valid
recipients combined with Net::validMX that can check to see if a sender has
valid MX before sending. I have a release of Net::validMX I'm about to
post this week in fact.
If you are interested, let me know.
Reg
I was wondering if anyone knows of an SA plugin or another method to
determine if the envelope-from domain has a valid MX record that is
listening on TCP port 25. I don't think it would be a major scorer but
it could be useful in meta rules.
Been playing around with rspamd over the weekend to
Hello, thans for the reply.
I use one bayes database to all sites in my server.
What would be the best way to avoid my problem?? create a database of bayes by
email account? Or create a unique database of bayes for all email accounts?
Thanks,
De: Pedro David M
On 08/04/18 13:41, David Jones wrote:
On 04/07/2018 10:42 AM, Sebastian Arcus wrote:
I'm not entirely sure what is the cause of this - notification emails
from The Pension Regulator in UK (a government body overseeing
pensions) have the destination email in upper case as part of the
Message-I
24 matches
Mail list logo