Matt Kettler wrote: > Bob Proulx wrote: > > -4.0 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, > > medium trust > > [128.30.16.9 listed in list.dnswl.org]
> Yes, you're right, GNU is only in DNSWL LOW, and this message *SHOULD* > have matched that, not med.. Uhm, no... lists.gnu.org is in my trust path. For all intents and purposes of running this mail through spamassassin the machine is virtually there. It's not but it acts that way. > One MAJOR problem you have is your mailserver isn't generating Received: > headers. It's not a complete solve for your problem, but it's a source > of dozens of problems your system is currently suffering. Pretty much > every DNSBL test isn't working correctly.. Second uhm... What has led you to believe that something is not working correctly? Things are all working fine. Normally your advice is excellent and I have great respect for it. You give untiring assistance to many people asking questions on the list. Let me thank you for that right now. It is awesome. But I think my message has simply confused you very much today. I apologize for that but I didn't think reporting that I am getting spam from a host in the RCVD_IN_DNSWL_MED and posting an example needed all of the background that didn't seem to be related. I mean *I* knew how the system was working. :-) My mailserver isn't in the mail path through lists.gnu.org. My compute server is simply a spamassassin cpu work farm server for it. It has a spamd running on it and messages are run through it to be classified by spamassassin. The messages are teleported magically to it and therefore don't have received headers. These are extracted from the Mailman moderator approval messages that are generated by Mailman when a message is held for review in the Mailman hold queue. > Since your network never generated a Received: header, SpamAssassin > concludes that lists.gnu.org is your network, because clearly the most > recent Received: header needs to have been generated by your network. Not in this case. This is simply a remote compute server. I am one of the volunteers that attempts to keep spam off of the mailing lists and I volunteer cpu time on my compute servers to do it. The machine regret.proulx.com isn't even on a public network and so trying to analyze where it fits into the world network isn't really possible. > since email can't teleport magically, and all hosts that receive a > message over SMTP must generate a Received header, by RFC spec this > needs to be true. Actually it *can* teleport magically. Any sufficiently advanced technology is indistinguishable from magic. Anything else is simply insufficiently advanced! Bob
