On 04/27/2011 10:16 PM, Michael B Allen wrote: > Hi, > > When I send email from home through my Postfix server my home dynamic > IP is included in the Received header: > > Received: from nano.foo.net > (pool-98-190-153-84.nwrknj.fios.verizon.net [98.190.153.84]) > (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) > (No client certificate requested) > (Authenticated sender: whomever) > by mail.ioplex.com (Postfix) with ESMTP id 13CC658010; > Wed, 27 Apr 2011 20:25:20 -0400 (EDT) > > Someone actually just outright rejected a message because of this. > Meaning even though the message was sent from a squeaky clean fixed IP > server on the Internet (mail.ioplex.com), their filter walked back > through the Received hosts and totally rejected the message because it > originated from a dynamic IP. > > Is there any way to configure my mail.ioplex.com postfix install to > leave out this part of the Received header or rewrite it so that it > looks like the message is simply coming from mail.ioplex.com such as > if I used webmail? > > Also, how common is this level of filtering? It seems excessive to me > but I have to wonder how much of my emails sent from home are ending > up at the very least flagged as SPAM. > > Mike
There is a setting on some Barracuda appliances called "deep header inspection" or "deep header parsing" that does this. Nobody who understood it would ever turn it on. Nevertheless, it sounds good, right? If you put the box there, somebody will check it.
