listed only on 1 RBL. The RBL offers
no proof of the email which triggered the listing. You're just there!
I call this lone RBL a heckler RBL. It is the only RBL out there
which is causing a handful of recipients to not receive email. Why
sysadmins only trust 0 RBLs, I don't know.
--
*Eric
Is there a website or repository where I can yum upgrade to the latest
spamassassin from, say, a FC6 system?
-eric wood
- Original Message -
From: Joe Zitnik
I'd like to write a custom rule that would allow e-mail in from users that
have an attachment
with a weird in house extension like foo.bar . How would I do this?
How about delivering it before spamassassin sees it in procmail?:
:0
*
updating a particular perl module. I did it for the
first time yesterday on two FC1 systems. Then use a spamassassin 3.x.x. rpm
to install the main program and restart the daemon. It's documented in the
middle of the INSTALL file.
-eric wood
the man Ed!
Thanks,
-eric wood
)
doesn't really check for specific perl modules. Maybe the spamassassin
package maintainers might need to be informed.
I seem to be working fine now.
-eric wood
