On Wed, 1 Aug 2018, John Hardin wrote:
On Wed, 1 Aug 2018, Alex wrote:
Aug 1 19:31:42.962 [3586] dbg: rules: ran header rule __HELO_MISC_IP
==> got hit: "[ ip=50.203.126.142
rdns=50-203-126-142-static.hfc.comcastbusiness.net
helo=50-203-126-142-static.hfc.comcastbusiness.net
by=mail01.exa
On Wed, 1 Aug 2018, Alex wrote:
Hi all,
I received an email today from bittitan.com that hit several dynamic
IP rules despite it appearing to have a static IP:
Aug 1 19:31:42.962 [3586] dbg: rules: ran header rule __HELO_MISC_IP
==> got hit: "[ ip=50.203.126.142
rdns=50-203-126-142-static
On Aug 1, 2018, at 6:09 PM, John Hardin wrote:
> Recommendation: download the spamassassin-3.4.1-12 (or later) SRPM from
> Fedora and try building an RPM from it in a Centos 6 dev environment. That's
> what I did for Centos 7 and it works jes' fine.
Kevin Fenzi maintains an SA repo for RHEL/Cen
Hi all,
I received an email today from bittitan.com that hit several dynamic
IP rules despite it appearing to have a static IP:
Aug 1 19:31:42.962 [3586] dbg: rules: ran header rule __HELO_MISC_IP
==> got hit: "[ ip=50.203.126.142
rdns=50-203-126-142-static.hfc.comcastbusiness.net
helo=50-20
On Wed, 1 Aug 2018, Nick Bright wrote:
On 8/1/2018 5:26 PM, Nick Bright wrote:
On 8/1/2018 4:58 PM, Bill Cole wrote:
What version of SpamAssassin are you using? Those line numbers make no
sense with the 3.4.1 release or either current development branch. The
last version it seems to make sens
On 8/1/2018 5:26 PM, Nick Bright wrote:
On 8/1/2018 4:58 PM, Bill Cole wrote:
What version of SpamAssassin are you using? Those line numbers make
no sense with the 3.4.1 release or either current development branch.
The last version it seems to make sense for is 3.3.2, which is antique.
spamas
On 8/1/2018 4:58 PM, Bill Cole wrote:
What version of SpamAssassin are you using? Those line numbers make no
sense with the 3.4.1 release or either current development branch. The
last version it seems to make sense for is 3.3.2, which is antique.
spamassassin-3.3.1-3.el6.x86_64 (CentOS 7 offic
On 1 Aug 2018, at 12:12 (-0400), Nick Bright wrote:
spamd[1833]: plugin: eval failed: error closing socket: Bad file
descriptor at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/DnsResolver.pm line
185, line 156.
What version of SpamAssassin are you using? Those line numbers make no
sense
spamd[1833]: plugin: eval failed: error closing socket: Bad file
descriptor at
/usr/share/perl5/vendor_perl/Mail/SpamAssassin/DnsResolver.pm line 185,
line 156.
I'm sometimes receiving this error in my maillog, certainly not for
every message that gets scanned. It seems to come in bursts.
