Pyzor problems:
http://www.atomicorp.com/wiki/index.php/Pyzor
SA_DELETE not working
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
Do you need to change /etc/sysconfig/spamassassin on all Project Gamera installs or are there special configurations that need the altered SPAMDOPTIONS line?
Lemonbit Internet Dedicated Server Management
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
I just want to know if one needs to change anything on a vanilla Project Gamera install to get pyzor to work normally. Is that the case or isn't that the case?
Lemonbit Internet Dedicated Server Management
kudos scott. It all seems to be working without a hitch now.
For those following along, the major issue for me seemed to be a conflict in how spamassassin and psa-spamassassin worked (or didn't work) together. So in the end I Uninstalled psa-spamassassin, installed the latest version of SpamAssassin from the ART repos, then manually re-installed psa-spamassassin from the ART repos. I ran qmail-scanner-reconfigure after each step to make sure, not sure if that's technically necessary or not.
My fix for pyzor was a simple one. In its /root/.pyzor/servers file it listed a specific IP number and port to use for connection. I had the port blocked in my firewall, of course. So opening that port up for UDP Out got it working.
At the end of the day it looks like everything is working as hoped. Plus with psa-spamassassin installed again users can set their own hit limit, with the automatic delete feeding off of the number they enter.
The only other tweak I made was to include the QS_SPAMASSASSIN-"on" line to smtp_psa and smtps_psa files in /etc/xinetd.d/ to have SA score those emails.
I've gotta do this on a brand new RHEL server in a few days. I think I'll start that out by removing psa-spamassassin before I do anything else. Hopefully that'll get it working right from the get go.
For those following along, the major issue for me seemed to be a conflict in how spamassassin and psa-spamassassin worked (or didn't work) together. So in the end I Uninstalled psa-spamassassin, installed the latest version of SpamAssassin from the ART repos, then manually re-installed psa-spamassassin from the ART repos. I ran qmail-scanner-reconfigure after each step to make sure, not sure if that's technically necessary or not.
My fix for pyzor was a simple one. In its /root/.pyzor/servers file it listed a specific IP number and port to use for connection. I had the port blocked in my firewall, of course. So opening that port up for UDP Out got it working.
At the end of the day it looks like everything is working as hoped. Plus with psa-spamassassin installed again users can set their own hit limit, with the automatic delete feeding off of the number they enter.
The only other tweak I made was to include the QS_SPAMASSASSIN-"on" line to smtp_psa and smtps_psa files in /etc/xinetd.d/ to have SA score those emails.
I've gotta do this on a brand new RHEL server in a few days. I think I'll start that out by removing psa-spamassassin before I do anything else. Hopefully that'll get it working right from the get go.