spamass-milter isn't part of the Spamassassin project and is unmaintained by
its upstream [https://github.com/andybalholm/spamass-milter], so you may have
limited support opportunities here.
What you're seeing here is that the Fedora/EPEL "spamass-milter" package has a
strong dependency on t
> I don't know if it would work in your scenario or not, but it might work
> to have the upstream system send to the downstream mailhub on a
> different IP+port pair wherein SpamAssassin is not integrated. In
> Sendmail, this could be as simple as an additional DaemonPort that
> doesn't include
I have an upstream mail server running spamassassin as part of a relatively
complex mail flow. This server will flag mail identified as spam with
X-Spam-Flag: YES (among other standard headers).
Some of this mail gets forwarded to another organization (also partially under
my control) which h
- On Aug 22, 2020, at 3:35 PM, Kenneth Porter sh...@sewingwitch.com wrote:
>> Like most ISPs, they have a feedback loop to remove malicious users. I
>> assume it is too slow, so a SendGrid account ID RBL would provide
>> meaningful value.
>
> Would not Pyzor accomplish the same thing? Sub
- On Aug 21, 2020, at 10:37 PM, Philip Prindeville
philipp_s...@redfish-solutions.com wrote:
> I fail to see the point: that we do the work that sendgrid should be doing,
> but
> on a duplicative scale?
>
> Why don’t they police themselves?
Presumably for the same reasons we filter spam
}\b/i
> #skelaxin
> body __DRUGS_MUSCLE5 /\bskelaxin\b/i
> meta DRUGS_MUSCLE (__DRUGS_MUSCLE2 || __DRUGS_MUSCLE3 || __DRUGS_MUSCLE4
> ||__DRUGS_MUSCLE5 )
> describe DRUGS_MUSCLE Refers to a muscle relaxant
>
> Thank you.
>
>
> Best regards,
> Henrik
Henrik,
The applicable rules file can be found here:
http://svn.apache.org/repos/asf/spamassassin/trunk/rules/20_drugs.cf
The file notes:
# This ruleset is intended to detect common "pill spam" however, it is not
# appropriate for all environments. It may not be appropriate for a medical or
ebian.org/ jessie/updates main
> # jessie-updates, previously known as 'volatile'
> deb http://ftp.de.debian.org/debian/ jessie-updates main
> deb-src http://ftp.de.debian.org/debian/ jessie-updates main
> Regards
> Maurizio
> Von: Jered Floyd [mailto:je...@convivian.
Hi Maurizio,
What version of Debian are you running, and which spamassassin package do you
have installed?
Useful commands:
# cat /etc/debian_version
# dpkg -l spamassassin
If you have mixed releases installed, please also provide the contents of
/etc/apt/sources.list.
Regards,
--Jered
-perl-xml-sax-expat
zimbra-perl-xml-simple
zimbra-perl-zmq-constants
zimbra-perl-zmq-libzmq3
zimbra-spamassassin-rules
Regards,
--Jered
- On Feb 26, 2017, at 10:22 AM, Matus UHLAR - fantomas uh...@fantomas.sk
wrote:
> On 26.02.17 10:12, Jered Floyd wrote:
>>It may be more effective
Matus,
It may be more effective to pursue this in a Zimbra support forum.
If you are running the OSS version (as am I!), you may have good luck here:
https://forums.zimbra.org/
Unfortunately I run SpamAssassin on my mailhub prior to Zimbra so can't help on
this one.
--Jered
- On Feb 26,
I personally consider stuff like this spam, but unfortunately the world at
large (and spam filtering software) doesn't -- and I'm not sure it's possible
to sufficiently train to block it. I would love a solution, but I don't know
what it is, beyond blocking all "legitimate" bulk commercial ema
Hi Marc,
I can't commit to providing a timely review of your idea (although I'm happy to
keep any communication in confidence if you would like to share), but I think I
can point out a very likely weakness that you should consider.
The biggest challenge with SA is that it is so widely deployed
Wrolf,
Facebook (et al.) already have extremely powerful engines and many engineers
working on anti-spam/anti-fraud technologies. They're quite good at keeping
most of the spam out of your Timeline. They don't need "our" help.
The same techniques could plausibly be used to block ISIS propagan
It's a brain dead forwarder that does that, but most forwarders are brain dead.
"aliases" and ".forward" are the most common things out there.
--Jered
- On Oct 6, 2015, at 7:06 PM, Benny Pedersen m...@junc.eu wrote:
> David B Funk skrev den 2015-10-06 22:33:
>
>> So that explicit forward
>> Can we temper this rule with a check to see if the mail indeed did pass
>> through
>> a fb server? You're checking the From: header, which can obviously be easily
>> spoofed, but perhaps if it originated from a facebook server?
This would be of limited value. As an MTA, you can only believe th
prevent it.
DKIM and SPF are both valuable tools in our arsenal, and SPF fail isn't enough
to reject mail.
--Jered
- On Oct 6, 2015, at 5:05 PM, Kevin A. McGrail wrote:
> On 10/6/2015 5:01 PM, Jered Floyd wrote:
>> Ah; good eyes!
>> That KAM_FACEBOOK rule
Ah; good eyes!
That KAM_FACEBOOK rule is dangerous.
--Jered
- On Oct 6, 2015, at 4:33 PM, David B Funk dbf...@engineering.uiowa.edu
wrote:
> On Tue, 6 Oct 2015, Alex wrote:
>
>> Hi,
>>
>> I've received a handful of messages that appear to be facebook
>> notifications, but fail SPF. They
Are you operating a backup MX at the cox.net address? If messages are delayed
and retried to your backup MX, this would explain the SPF failures.
--Jered
- On Oct 6, 2015, at 1:38 PM, Alex mysqlstud...@gmail.com wrote:
> Hi,
>
> I've received a handful of messages that appear to be faceb
>> The form does seem to have worked, and I'm not currently on the BRBL,
>> although
>> this morning I got bounces from a Barracuda customer for a very benign
>> message
>> with "rejected due to spam content," so who knows. I wish there was better
>> visibility into the process.
>
> then it w
them you want a block they will SWIP to you. I
> realize this may cost you some more money. But email is not one of
> those things you can do well on the cheap.
>
> Ted
>
>
> On 6/20/2015 8:38 AM, Jered Floyd wrote:
>>
>> Hello SA-users,
>>
>> I have
EmailReg.org operates a whitelist, so you pay to get listed there. The site
doesn't say much at all about what sort of verification or later delisting for
spam they might do.
However, they are promoted directly on the "Sorry, your email was blocked" page
for Barracuda Reputation, and the page
Richard,
> The BRBL may have listed the entire /24 that includes your sending IPs.
> Painful experience has shown that Barracuda won't hear your requests for
> delisting, and the listing may never go away.
I believe you've got it in one. I heard back from a colleague on the same /24
(though n
Harald,
> no you don't understand how a Barracuda appliance works
> emailreg.org is a whitelist like the ones spamassassin is using
>
> in case of a barracuda appliance it overrides the RBL
It's a whitelist that appears to be based solely on paying Barracuda a fee.
That doesn't sound like a v
Hello SA-users,
I have a question on the other side of things: outgoing mail. I know this is
off-topic but this seems to the only venue where there might be knowledge of
the problem, and the offender is a spamassassin "customer".
(I operate an MTA host on which I run SpamAssassin -- it works
25 matches
Mail list logo
