now this is odd - and I must be real stupid so bear with me...if I whitelist the address that attaches to my mail server as below the rest of the message gets skipped - so my customers who I've told they can forward mail into this system, and it will catch spam are in trouble... i.e.
[EMAIL PROTECTED] wants to block spam 2.they also have a [EMAIL PROTECTED] 3.I tell them they can forward mail to [EMAIL PROTECTED] from that maine.rr.com account and it will mark spam. 4.Things are working dandy... 5.spamcop gets wind of a spam that seems to increminate a server in the roadrunner system - one in NYC. 6.spamcop starts hitting in that server using the HOPS we have 7.suddenly all mail forwarded through maine.rr.com is tagged as spam. 8.I whitelist the IP that touches our server and suddenly all mail from maine.rr.com is never spam. Is there any way to just IGNORE IP 24.29.99.40 in the hops check and continue down the hops / without breaking something else... FYI the dirty server is in NYC or someplace, and appears to be a sorting gatway for roadrunner in the NE area - it's IP is 24.29.99.40. the server in Maine that delivers the mail is 24.93.159.132 - clean. thanks, Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry Sent: Thursday, May 02, 2002 10:39 PM To: [EMAIL PROTECTED] Subject: RE: [Declude.JunkMail] whitelisting >okay - but it is the 24.29.99.40 I am trying to whitelist...spamcop is >marking it, but I don't want it to get tagged I put the WHITELIST IP >24.29.99.40 in global.cfg but it still tags it - That's because the "WHITELIST IP" only works with the IP address of the remote mailserver (the one connecting to yours), not other mailservers that may have handled the E-mail. >... or do I whitelist the one above it, so the rest of the chain gets skipped? That's exactly what I would recommend. >The one above it (24.93.159.132) would >handle the majority of the problem, but if I get some legit email that >touches this gateway ip (24.29.99.40) without hitting 24.93.159.132 I would >still want the mail... Unfortunately, there isn't a way to handle that situation (whitelist an IP other than the one that connects directly to yours). However, legitimate E-mail leaving 24.29.99.40 should always take the same path to your server (unless 24.29.99.40 gets changed to use a gateway, or some other configuration change). > -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com . --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
