Help I am listed on blacklists
Original Message From: mouss [EMAIL PROTECTED] To: John Hardin [EMAIL PROTECTED] Cc: Lars Ebeling [EMAIL PROTECTED]; users@spamassassin.apache.org Sent: Saturday, November 29, 2008 8:26 PM Subject: Re: Help I am listed on blacklists John Hardin a écrit : On Sat, 29 Nov 2008, Lars Ebeling wrote: Dear all Could someone advice me. I am listed on dun.dnsrbl.net and spam.dnsrbl.net How to get off the lists? Both those lists are dead (since mid-2005?) and appear to be returning 127.0.0.1 for all queries. How did you determine you were listed? saturday guess: he looked up his IP on robtex and found it was listed? Correct. I saw the URL here and tested. But as I understand, I can forget it. Lars
Tagging the mail which already has X-Spam headers
Hello, SpamAssassin tags mail with headers X-Spam- But, what if there were some headers like these, as with mail that already passed someones SpamAssassin and has X-Spam-Score, before being recieved by my server? Will it remove them, replace them or simply add new ones? In the latter case, how do I tell headers, added by my SpamAssassin, from headers, that were there before my mail server?
Re: Tagging the mail which already has X-Spam headers
On Sun, 2008-11-30 at 16:22 +0300, Nikita Kipriyanov wrote: Will it remove them, replace them or simply add new ones? In the latter case, how do I tell headers, added by my SpamAssassin, from headers, that were there before my mail server? SA adds a new set of headers. Look at the X-Spam-Checker-Version header, which shows the name of each host that has run SA against this message. The most recent set of headers is at the top. Martin
Re: Tagging the mail which already has X-Spam headers
Nikita Kipriyanov a écrit : Hello, SpamAssassin tags mail with headers X-Spam- But, what if there were some headers like these, as with mail that already passed someones SpamAssassin and has X-Spam-Score, before being recieved by my server? Will it remove them, replace them or simply add new ones? In the latter case, how do I tell headers, added by my SpamAssassin, from headers, that were there before my mail server? SA will remove such headers. you can preserve them by rewriting them before passing the message to SA. for example, with postfix, you can use header checks: /^(X-Spam-*)/ X-$1 will add an X- to the header names.
Re: Tagging the mail which already has X-Spam headers
On Sunday 30 November 2008 7:22 am, Nikita Kipriyanov wrote: Hello, SpamAssassin tags mail with headers X-Spam- But, what if there were some headers like these, as with mail that already passed someones SpamAssassin and has X-Spam-Score, before being recieved by my server? Will it remove them, replace them or simply add new ones? In the latter case, how do I tell headers, added by my SpamAssassin, from headers, that were there before my mail server? I use procmail and have a formail recipe within my procmail.rc that prepends Old to X-Spam headers from other servers: Tp -i headerfield Same as -A, except that any existing similar fields are renamed by prepending an ``Old-'' prefix. If headerfield consists only of a field-name, it will not be appended. :0Wfh *^To:[EMAIL PROTECTED] | formail -i X-Spam -- Chris KeyID 0xE372A7DA98E6705C pgpep2SfDnnQb.pgp Description: PGP signature
OS Upgrade Broke SpamAssassin; Help Needed to Fix
I (finally) upgraded my main server/workstation from Slackware-11.0 to
-12.0. After rebooting into the newer kernel, the mail system wasn't
working. Postfix was OK, and I traced the problem to SpamAssassin. Version
3.1.7 was installed.
Some perl modules needed to be upgraded, so I did those via CPAN. This did
not fix the problem (memory use about 98%, disk trashing, postfix cleaning
running constantly, MTA connection to localhost (127.0.0.1) being refused,
etc.) so I thought an upgrade of SA was in order.
I tried to upgrade to 3.2.5 via CPAN ('perl -MCPAN -e shell; install
Mail::SpamAssassin'). The above mentioned problems still exist as soon as I
turn on the spam filter in /etc/postfix/master.cf. Turned it off again.
Here are the current versions reported by SA:
[EMAIL PROTECTED] ~]$ /usr/local/bin/spamassassin -V
spamassassin: spamassassin script is v3.001007, but using modules v3.002005
SpamAssassin-3.1.7 is installed in /etc/mail/spamassassin/.
How should I proceed to fix the installation so there's only one copy
(either in /etc/mail/spamassassin or /usr/local/bin) and that's the latest
version? I would like to get this fixed ASAP so I can turn it back on and
still have the MTA working.
TIA,
Rich
--
Richard B. Shepard, Ph.D. | IntegrityCredibility
Applied Ecosystem Services, Inc.|Innovation
http://www.appl-ecosys.com Voice: 503-667-4517 Fax: 503-667-8863
Re: OS Upgrade Broke SpamAssassin; Help Needed to Fix
On Mon, December 1, 2008 01:39, Rich Shepard wrote: still have the MTA working. you have installed 3.2.5 from cpan and 3.1.7 in rpm ? newer install cpan builds when host os is rpm based google cpan2rpm -- Benny Pedersen Need more webspace ? http://www.servage.net/?coupon=cust37098
Re: OS Upgrade Broke SpamAssassin; Help Needed to Fix
On Mon, 1 Dec 2008, Benny Pedersen wrote: you have installed 3.2.5 from cpan and 3.1.7 in rpm ? Benny, Slackware doesn't use rpms. The slack packages end in .tgz and that's what the package tools work with. Rich -- Richard B. Shepard, Ph.D. | IntegrityCredibility Applied Ecosystem Services, Inc.|Innovation http://www.appl-ecosys.com Voice: 503-667-4517 Fax: 503-667-8863
Re: OS Upgrade Broke SpamAssassin; Help Needed to Fix
On Mon, December 1, 2008 02:34, Rich Shepard wrote: On Mon, 1 Dec 2008, Benny Pedersen wrote: you have installed 3.2.5 from cpan and 3.1.7 in rpm ? Slackware doesn't use rpms. The slack packages end in .tgz and that's what the package tools work with. pas then -- Benny Pedersen Need more webspace ? http://www.servage.net/?coupon=cust37098
Re: OS Upgrade Broke SpamAssassin; Help Needed to Fix
On Sun, Nov 30, 2008 at 04:39:49PM -0800, Rich Shepard wrote: [EMAIL PROTECTED] ~]$ /usr/local/bin/spamassassin -V spamassassin: spamassassin script is v3.001007, but using modules v3.002005 How should I proceed to fix the installation so there's only one copy (either in /etc/mail/spamassassin or /usr/local/bin) and that's the latest version? I would like to get this fixed ASAP so I can turn it back on and still have the MTA working. Find all SA-related files and delete them. Then go back and install a fresh version. Make sure to save your own site configs and such, and reinstall them when you're done. -- Randomly Selected Tagline: I cannot have an aide who will not look up. You will be forever walking into things. - Dukhat on Babylon 5 pgpZP1B8RUQQd.pgp Description: PGP signature
Card/Gift/Shopping Spam (or: More Spam Reduction Techniques)
I'm seeing a lot of shopping, gifts, prizes, and cards (ie. credit card, gift card) related spam in the last week or so. (Maybe due to Black Friday?) I'm using Sought, Bayes, and default rules. Is there anything I can do to reduce the amount of spam getting through? I've already knocked the threshold down a little. If it helps, here are some examples: http://dpaste.com/94956/ http://dpaste.com/94957/ http://dpaste.com/94958/ Thanks, Neil.
Spamd and ipv6
Since getting my hosts natively speaking ipv6, I've been seeing a lot of initial timeouts connecting to spamc, because I believe it's apparently trying ipv6 first. spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused However, I cannot get the -A systax for spamd to accept connections from a given address, nor does it appear to be listening on said address: quark# netstat -na | grep LIST | grep 783 tcp4 0 0 *.783 *.*LISTEN I'm running a recent enough version that v6 *should* be supported. Versions: SpamAssassin Server version 3.2.5 running on Perl 5.8.8 with SSL support (IO::Socket::SSL 1.13) with zlib support (Compress::Zlib 2.008) Any ideas? -- I can feel it, comin' back again...Like a rolling thunder chasin' the wind... -Dan Mahoney, JS, JB SL, May 10th, 1997, Approx 1AM Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---
Re: Spamd and ipv6
At 21:45 30-11-2008, Dan Mahoney, System Admin wrote: Since getting my hosts natively speaking ipv6, I've been seeing a lot of initial timeouts connecting to spamc, because I believe it's apparently trying ipv6 first. spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused [snip] However, I cannot get the -A systax for spamd to accept connections from a given address, nor does it appear to be listening on said address: quark# netstat -na | grep LIST | grep 783 tcp4 0 0 *.783 *.*LISTEN Use the -i parameter to specify the IPv6 address. The -A parameter to specify the host which can connect to spamd and not the IP address on which spamd should listen on. Regards, -sm
Re: Tagging the mail which already has X-Spam headers
mouss пишет: you can preserve them by rewriting them before passing the message to SA. for example, with postfix, you can use header checks: /^(X-Spam-*)/ X-$1 will add an X- to the header names. Shouldn't this break some special things like DKIM signatures?
Re: [sa-list] Re: Spamd and ipv6
On Sun, 30 Nov 2008, SM wrote: At 21:45 30-11-2008, Dan Mahoney, System Admin wrote: Since getting my hosts natively speaking ipv6, I've been seeing a lot of initial timeouts connecting to spamc, because I believe it's apparently trying ipv6 first. spamc: connect to spamd on 2001:470:1f07:a7f::1 failed, retrying (#1 of 3): Connection refused [snip] However, I cannot get the -A systax for spamd to accept connections from a given address, nor does it appear to be listening on said address: quark# netstat -na | grep LIST | grep 783 tcp4 0 0 *.783 *.*LISTEN Use the -i parameter to specify the IPv6 address. The -A parameter to specify the host which can connect to spamd and not the IP address on which spamd should listen on. So then, you're saying the behavior for ipv4 and ipv6 is somehow different? I am starting spamd with -i but no ip specified, according to the docs: If you specify no IP address after the switch, spamd will listen on all interfaces. (This is equal to the address 0.0.0.0). All Interfaces != 0.0.0.0 At the very least, this is a docbug and should be amended to say all ipv4 interfaces. No mention is made of whether or not multiple -i arguments can be specified, but from my research, only the first -i is used, and you cannot comma-separate. This is a second docbug, or a functionality that should be added to listen on v4 and v6 simultaneously. Additionally, even when I get this working, I am unable to specify ipv6 addresses to -A, either with or without square brackets. Behaviorally, spamc *tries v6 by default* but spamd requires hoop-jumping. This is a consistency problem and should also be looked into. V6 is coming, fast. Things like this are worth chasing down. Let me know if you need me to run any other debugs or anything. If you need access to my systems, please just say the word. I like having something to offer in the solution of a problem, other than just complaints :) -Dan -- Man, this is such a trip -Dan Mahoney, October 25, 1997 Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---
Re: Tagging the mail which already has X-Spam headers
Nikita Kipriyanov a écrit : mouss пишет: you can preserve them by rewriting them before passing the message to SA. for example, with postfix, you can use header checks: /^(X-Spam-*)/X-$1 argh. I meant /^(X-Spam-*)/REPLACE X-$1 will add an X- to the header names. Shouldn't this break some special things like DKIM signatures? Comment and X-* headers should not be DKIM signed. and anyway, there is no viable alternative, because when you use procmail, maildrop, sieve, ... you cannot specify which X-Spam-* headers you want (and no, the argument if one says it's spam, then it's spam doesn't count. because for one, some people may be looking at /^X-Spam-Flag: No/, but also because just because my friend's ISP is mad doesn't mean I should ignore his mail...).
