Bug 1115656 - Spamd, problem com DnsResolver.pm
Summary: Spamd, problem com DnsResolver.pm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: spamassassin
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-02 20:34 UTC by volnei
Modified: 2014-07-07 11:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-02 20:41:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description volnei 2014-07-02 20:34:55 UTC
Description of problem:

Hi,

I don't know why this message is shown below.
But since she started, I realized that there are problems
with spam detection
I wish, if possible, which will assist me with this issue

Jul  2 17:26:49 deimos spamd[2560]: Use of uninitialized value $ns in pattern match (m//) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/DnsResolver.pm line 201.

Version-Release number of selected component (if applicable):
spamassassin-3.3.2-15.fc19.x86_64

Thank you

Comment 1 Kevin Fenzi 2014-07-02 20:41:46 UTC
Please update to https://admin.fedoraproject.org/updates/FEDORA-2014-7658/spamassassin-3.4.0-7.fc19 which is even now being pushed to stable updates. ;)

Comment 2 William H. Haller 2014-07-06 21:38:48 UTC
Version 3.4.0-7 upgrade gives spamassassin.service holdoff time over, scheduling restart every few seconds but doesn't report the $ns error anymore. Of course the $ns error was just during processing in the maillog and the other error is repeating in the messages log, I can't say it's a good tradeoff, but...

Comment 3 Kevin Fenzi 2014-07-06 21:41:03 UTC
(In reply to William H. Haller from comment #2)
> Version 3.4.0-7 upgrade gives spamassassin.service holdoff time over,
> scheduling restart every few seconds but doesn't report the $ns error
> anymore. Of course the $ns error was just during processing in the maillog
> and the other error is repeating in the messages log, I can't say it's a
> good tradeoff, but...

This is due to your editing the /etc/sysconfig/spamassassin file and not merging in the changes from the new version. In particular, remove '-d' from your /etc/sysconfig/spamassassin file and restart. 

See the /usr/share/doc/spamassassin/README.RHEL.Fedora file: 

"Note about -d option
====================

With spamassassin 3.4.0, this package has switched the way spamd is started.·
You should no longer use the '-d' option in /etc/sysconfig/spamassassin. Doing·
so will result in spamd starting and stopping in a loop. The default·
/etc/sysconfig/spamassassin file has been adjusted for this, please merge·
this change into that file if you have made any changes to it."

Comment 4 William H. Haller 2014-07-06 22:49:35 UTC
Thanks. I still had a spamassassin.rpmnew from my F19 upgrade and the new file didn't overwrite it so I saw no options difference. Apologies...

Comment 5 Kevin Fenzi 2014-07-07 00:19:30 UTC
No worries. ;( Sorry this change got merged in f19/f20... it was not planned. ;(

Comment 6 volnei 2014-07-07 11:26:42 UTC
Hi,

I updated to version spamassassin-3.4.0-7.fc19.x86_64 and now everything is working correctly. The problem with the DNSResolver was solved


Thank you


Note You need to log in before you can comment on or make changes to this bug.