Domain Keys
Hello List, It's me again with another doubt =P I'm stuck in this Domain Keys thing because I don't know how to create a public and a private key for my server. I already read the http://antispam.yahoo.com/domainkeys to understand how Domain Keys work but I can't go on with only this argument. Thanks again,, Jeff
SPF Problems
Hello list, I'm using SPF and if the sender domain have a SPF record, then the header of the message show the SPF_PASS but if doesn't, the header don't show the SPF_FAIL or SOFTFAIL. This thing already happened with someone on the list? Thanks, Jeff
Re: SPF Problems
I'm a little confuse now. When I Get SPF_FAIL? I think that when the domain don't have a SPF record, spamassassin scores the message with FAIL. Theo Van Dinter wrote: On Mon, Apr 24, 2006 at 11:58:00AM -0300, Jeferson Pessoa Santana wrote: I'm using SPF and if the sender domain have a SPF record, then the header of the message show the SPF_PASS but if doesn't, the header don't show the SPF_FAIL or SOFTFAIL. This thing already happened with someone on the list? If the sending domain doesn't have a SPF record, the message can't fail an SPF check. There has to be a record for a check to occur.
Re: SPF and Domain Keys
Jeferson Pessoa Santana wrote: [EMAIL PROTECTED] wrote: Jeferson Pessoa Santana wrote: I'm back with new doubts hehehe. I've been reading a lot of articles and e-mails from the list about SPF and Domain Keys but I don't know how to use they in SpamAssassin. I'm using SpamAssassin 3.1.0 and I already installed the Perl Module Mail::SPF::QUERY. There's a new config lost on my server or I need to put things on the local.cf? SPF: make sure there's a line like loadplugin Mail::SpamAssassin::Plugin::SPF in your init.pre or v310.pre DomainKeys: make sure there's a line like loadplugin Mail::SpamAssassin::Plugin::DomainKeys in your init.pre or v310.pre Also make sure you have Mail::DomainKeys installed There is also a patch you need to make it work with 3.1.0 Thanks Matthew I read documents about this loadplugin feature but I was lost about where to put it. Tks Does anyone have the link of this Domain Keys patch for the version 3.1.0? Doing a Google Search I found some information about this patch but any file or text to create the file.
SPF and Domain Keys
Hello Spamassassin, I'm back with new doubts hehehe. I've been reading a lot of articles and e-mails from the list about SPF and Domain Keys but I don't know how to use they in SpamAssassin. I'm using SpamAssassin 3.1.0 and I already installed the Perl Module Mail::SPF::QUERY. There's a new config lost on my server or I need to put things on the local.cf? Thanks for the attention Jeff
Re: SPF and Domain Keys
[EMAIL PROTECTED] wrote: Jeferson Pessoa Santana wrote: I'm back with new doubts hehehe. I've been reading a lot of articles and e-mails from the list about SPF and Domain Keys but I don't know how to use they in SpamAssassin. I'm using SpamAssassin 3.1.0 and I already installed the Perl Module Mail::SPF::QUERY. There's a new config lost on my server or I need to put things on the local.cf? SPF: make sure there's a line like loadplugin Mail::SpamAssassin::Plugin::SPF in your init.pre or v310.pre DomainKeys: make sure there's a line like loadplugin Mail::SpamAssassin::Plugin::DomainKeys in your init.pre or v310.pre Also make sure you have Mail::DomainKeys installed There is also a patch you need to make it work with 3.1.0 Thanks Matthew I read documents about this loadplugin feature but I was lost about where to put it. Tks
Sender base
Hi guys, Does anyone know how to use Sender Base to check e-mails with SpamAssassin? For those who doesn't know Sender Base : www.senderbase.org. Thanks, Jeff
Re: Sender base
Bret Miller wrote: Not SenderBase specifically, but MXRate is a similar service. See www.mxrate.com for information. Ah, Alligate, the server that "test incoming mail for RFC compliance", but lacks a proper behaviour on RSET. I hope this service is more sane. Anybody with experience with MX? Might be worth a try. I use it or I wouldn't have known how to use it. ;) Like most other DNS blacklists, I wouldn't trust it completely. Whether something is "spam" depends largely on the perception of the person reviewing it. I don't know how you get in one list or another for mxrate, but I do know that a number of messages get flagged somewhat incorrectly at least in my perception of it. So, if you use it, score it where it helps you increase or decrease the score, but realize it will likely flag some real e-mail as "recommend block". It did here. So I treat it as "more likely to be spam" rather than "block this e-mail". Bret Thanks guys. I'm reading the documentation of this MXRATE and it seems to me that this service is better than SenderBase. =D
Re: Problems with the Spamd Daemon
Hy Matthew, I tried to start the daemon in the way that you said in your e-mail but the result are the same. For some reason, the daemon goes back to the command line /usr/bin/spamd -d -u nobody. Thanks anyway for all the help provided by you and the entire list Jeff =) Obs: I'm still looking for the answer hehehe [EMAIL PROTECTED] wrote: Jeferson Pessoa Santana wrote: /usr/bin/spamd -i -d -u nobody --allowed-ips=200.X.X.X,127.0.0.1 Guys, I think that mey e-mail wasn't clearly, sorry. The IP 200.x.x.x means that I'm using 200.189.68.194 for example. And I put the 127.0.0.1 because I have a exim daemon started to relay the incoming e-mails. That was perfectly clear, and I understood that was what you meant. But spamd didn't. Let's assume the IP address you give above is correct... so this is you... http://lacnic.net/cgi-bin/lacnic/whois?query=200.189.68.194 You almost certainly don't want to open your spamd server to the entire LACNIC world: 200.x.x.x AKA 200.0.0.0 - 200.255.255.255 AKA 200.0.0.0/8 AKA 200. You probably meant to open your spamd server only to Digital Express Ltda 200.189.68.192 - 200.189.68.255 AKA 200.189.68.192/26 So you would call spamd as /usr/bin/spamd -d -u nobody --allowed-ips=200.189.68.192/26,127.0.0.1
Re: Problems with the Spamd Daemon
What I'm triyng to do is to monitor the Spamd port with telnet (Ipmonitor is the software that we are using and it's ip is 200.189.68.194. I didn't read the entire spamd man page =-P Thanks Jeff [EMAIL PROTECTED] wrote: Jeferson Pessoa Santana wrote: Hy Matthew, I tried to start the daemon in the way that you said in your e-mail but the result are the same. For some reason, the daemon goes back to the command line /usr/bin/spamd -d -u nobody. Thanks anyway for all the help provided by you and the entire list One last try... you said the command line is /usr/bin/spamd -i -d -u nobody --allowed-ips=200.X.X.X,127.0.0.1 Is it, in fact: /usr/bin/spamd -i -d -u nobody --allowed-ips=200.189.68.248,127.0.0.1 And furthermore, is the IP of the machine 200.189.68.248? If so, then /usr/bin/spamd -d -u nobody makes sense. Why? Because -i is ignored, as it has no interface IP... And --allowed-ips specifies the default IPs anyway. From the man spamd page: By default, connections are only accepted from local host [127.0.0.1]. And of course, the interface IP addresses are all on the local host. So that --allowed-ips, though it is parsed, is just a fancy way of specifying the default anyway.
Re: Problems with the Spamd Daemon
Guys, I think that mey e-mail wasn't clearly, sorry. The IP 200.x.x.x means that I'm using 200.189.68.194 for example. And I put the 127.0.0.1 because I have a exim daemon started to relay the incoming e-mails. [EMAIL PROTECTED] wrote: Jeferson Pessoa Santana wrote: Hi guys, A few hours ago I started my spamassassin with this command line: /usr/bin/spamd -i -d -u nobody --allowed-ips=200.X.X.X,127.0.0.1 And then, for some reason that I don't know yet, wi th the ps ax command, I received this /usr/bin/spamd -d -u nobody Well... -i requires an argument, which you don't supply. So -i is ignored. --allowed-ips takes IP addresses, but not in the format you specify. spamd doesn't understand 200.X.X.X, so --allowed-ips is ignored. Try /usr/bin/spamd -d -u nobody --allowed-ips=200.0.0.0/8,127.0.0.1 or /usr/bin/spamd -i -d -u nobody --allowed-ips=200.,127.0.0.1
Problems with the Spamd Daemon
Hi guys, A few hours ago I started my spamassassin with this command line: /usr/bin/spamd -i -d -u nobody --allowed-ips=200.X.X.X,127.0.0.1 And then, for some reason that I don't know yet, wi th the "ps ax" command, I received this /usr/bin/spamd -d -u nobody I was using this second command line all the time, but when I changed to first, SpamAssassin simply don't accept and back to the "original command line" after some minutes. My logs don't say anything about this. Does anyone knows what's happening? Thanks Jeff "Merry Christmas and a Happy New Year" =P
SpamAssassin: how to generate stats
Hi guys, I'm using SpamAssassin 3.1.0 and I don't know how to generate stats about the number of Spam, Non-Spam received, and Top Rules used. Can you guys know how to do this? Thanks Jeff
Creating Rules for specific domains
Hi People, I'm having some problems with the SpamAssassin Rules. I have to e-mails server (Enchange and Exim) and another server with SpamAssassin and Exim to delivery the messages. In my DNS server, I'd put the mx(10) poiting to the SPamAssassin server and it's delivery the messages to the users mailbox. My problem is, I don't know how to create specific rules for each domain that pass through the SpamAssassin server or maybe set different scores in the existent rules for each domain. Does anyone know how to do this? Thanks Jeff
