|Main Archive Page > Month Archives > postfix-users archives|
OT response and the only one.
Saturday, April 30, 2011, 9:23:14 PM, Michael wrote:
> Just a small follow-up. Using SquirrelMail running on the mail server
> I have since successfully emailed the customer that previously
> rejected a conventional ESMTP message. Note that SquirrelMail also
> includes the remote IP in the Received header (which so happens is the
> exact same dynamic IP used for the previously rejected message):
> Received: from 126.96.36.199
> (SquirrelMail authenticated user whomever)
> by www.busicorp.com with HTTP;
> Fri, 29 Apr 2011 23:08:43 -0400 (EDT)
> Message-ID: <email@example.com>
> Date: Fri, 29 Apr 2011 23:08:43 -0400 (EDT)
> User-Agent: SquirrelMail/1.4.8-5.el5.centos.10
> So apparently whatever filtering they're doing isn't as simple as
> doing an RBL lookup on any IP found in Received headers. Maybe the
> filter is picking up on some part of the
> "pool-98-190-153-84.nwrknj.fios.verizon.net" like the "pool-" bit.
Results from a local name server here:
[duane@fc58] ~> host 188.8.131.52
184.108.40.206.in-addr.arpa domain name pointer wsip-98-190-153-84.ph.ph.cox.net.
[duane@fc58] ~> host wsip-98-190-153-84.ph.ph.cox.net
wsip-98-190-153-84.ph.ph.cox.net has address 220.127.116.11
There is no mention of 'pool-' anything above. Is it Cox or Verizon?
From this angle, it's Cox.
This does not resolve:
[duane@fc58] ~> host pool-98-190-153-84.nwrknj.fios.verizon.net
Host pool-98-190-153-84.nwrknj.fios.verizon.net not found: 3(NXDOMAIN)