Hi All, Just had an interesting conversation with another hosting provider trying to track down the cause a message marked as spam. Turns out the issue is that my clients home IP address is on a spam list, this address is out of my control, belongs to their ISP and is notoriously spammy. This client sends mail by connecting to our POP3 service. Our servers IP addresses are not in any spam lists, but the IP of their home router is. My Q is: Does anyone know how to strip out the headers from these POP3 connections so the originating machine headers are not included in what is sent along with the message. It would be fine if the originating server were just our servers IP address. Ideally of course, I would like to make sure that at some point we log the incoming headers, but don't forward them along. Here is a sample of what is being blocked (somewhat redacted for client privacy) > Return-Path: <xyz@mycustomersdomain> > Received: (qmail 31469 invoked by uid 10063); 10 Oct 2011 09:02:47 > -0500 > Received: from 174-124-66-132.dyn.centurytel.net by ss4.site-hosts.com > (envelope-from <xyz@mycustomersdomain>, uid 2020) with > qmail-scanner-2.08st > (clamdscan: 0.97.2/13776. spamassassin: 3.2.5. perlscan: 2.08st. > Clear:RC:0(184.108.40.206):SA:0(-101.9/2.4):. > Processed in 1.138433 secs); 10 Oct 2011 14:02:47 -0000 > X-Spam-Status: No, hits=-101.9 required=2.4 > Received: from 174-124-66-132.dyn.centurytel.net (HELO ?192.168.0.3?) > (220.127.116.11) > by ss4.site-hosts.com with SMTP; 10 Oct 2011 09:02:46 -0500 In this case the IP address 18.104.22.168 is on a couple of block lists and belongs to centurytel. However my server ss4.site-hosts is clean and clear. We whitelisted her IP so that she can send, but these headers are forwarded in the message and we get lots of clients asking why they are blocked. Any ideas on how to strip this stuff out? Our config is qmail - qmail-scanner - clamav - spamassassin.