[162918] in North American Network Operators' Group
Re: NANOG58 bad helo for hotel reservation emails
daemon@ATHENA.MIT.EDU (Suresh Ramasubramanian)
Tue May 7 20:19:47 2013
In-Reply-To: <518994A0.9040400@direcpath.com>
Date: Wed, 8 May 2013 05:49:36 +0530
From: Suresh Ramasubramanian <ops.lists@gmail.com>
To: Robert Drake <rdrake@direcpath.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Checking for a non resolvable HELO will get you significant fps. There are
plenty of HELO patterns that can and must be filtered but not this one.
On Wednesday, May 8, 2013, Robert Drake wrote:
> Sorry for the noise, but I thought this might be of interest to anyone
> waiting for their hotel confirmation:
>
> NOQUEUE: reject: RCPT from feport01.hiltonhhonors.net[63.**122.201.171]:
> 450 4.7.1 <ironport.hhonorscrm.net>: Helo command rejected: Host not
> found; from=<waldorfastoriahotels&resorts@res.hilton.com> to=<excised>
> proto=ESMTP helo=<ironport.hhonorscrm.net>
>
> So if you run your own server and/or are capable of compensating for a
> misconfigured MTA, you should add an exception for
> feport01.hiltonhhonors.net.
>
>
>
>
>
--
--srs (iPad)
