Which Setting Caused This?

A client received this from Yahoo:


Last Bounced Message
Remote host said: 550 Your ip does not have a name
associated with it 
(209.131.38.236)
[RCPT_TO]

This was identified as a hard bounce.

The only things I changed lately are:

g_verify_helo - Verify helo name translates to same network
as sending system.

Syntax: g_verify_helo "true/false"

It will skip this check for any trusted connection (smtp 
authenticated, or any ip it would allow to forward)

It adds this header:
X-Verify-Helo

It simply takes the helo name, and turns it into a number
a.b.c.d, 
then it checks that the connection is coming from 'a.b.*.*'
if it isn't it adds a header saying as much.

Syntax: g_verify_helo bool

	and

g_lookup_names - Lookup names for connecting IP addresses

This is one of those things that you very likely do not want
to turn 
on. It makes the mail server lookup the IP name of any
connecting 
user, however lookups can take 30-90 seconds so it can
negatively 
impact apparent performance. Most of the access rules in the
server 
can accept IP names if this setting is enabled, e.g. instead
of 
specifying local users are 153.2.3.* you can say
'*.netwinsite.com"

Syntax: g_lookup_names bool

Neither of these say anything about bouncing or rejecting
mail with a 
"Your ip does not have a name associated with it"
message.

Is one of these the responsible setting?

MOST email from Yahoo is received just fine. Apparently, the

occasional lookup fails, rendering these settings unsafe to
use.

Warren Michelsen wrote:
> A client received this from Yahoo:
> 
> 
> Last Bounced Message
> Remote host said: 550 Your ip does not have a name
associated with it 
> (209.131.38.236)
> [RCPT_TO]
> 
> This was identified as a hard bounce.
> 
> The only things I changed lately are:
> 
> g_verify_helo - Verify helo name translates to same
network as sending 
> system.
> 
> Syntax: g_verify_helo "true/false"
> 
> It will skip this check for any trusted connection
(smtp authenticated, 
> or any ip it would allow to forward)
> 
> It adds this header:
> X-Verify-Helo
> 
> It simply takes the helo name, and turns it into a
number a.b.c.d, then 
> it checks that the connection is coming from 'a.b.*.*'
> if it isn't it adds a header saying as much.
> 
> Syntax: g_verify_helo bool
> 
>     and
> 
> g_lookup_names - Lookup names for connecting IP
addresses
> 
> This is one of those things that you very likely do not
want to turn on. 
> It makes the mail server lookup the IP name of any
connecting user, 
> however lookups can take 30-90 seconds so it can
negatively impact 
> apparent performance. Most of the access rules in the
server can accept 
> IP names if this setting is enabled, e.g. instead of
specifying local 
> users are 153.2.3.* you can say
'*.netwinsite.com"
> 
> Syntax: g_lookup_names bool
> 
> Neither of these say anything about bouncing or
rejecting mail with a 
> "Your ip does not have a name associated with
it" message.
> 
> Is one of these the responsible setting?
> 
> MOST email from Yahoo is received just fine.
Apparently, the occasional 
> lookup fails, rendering these settings unsafe to use.
> 
> 
> 
Please send your surgemail.ini to surgemail-support

Regards,
Stuart

> 
> 


-- 
When replying please quote original message to save time and
always let
us know what OS and version of SurgeMail you are using.

************************************************************
****************
If you wish to communicate with other users and talk about
SurgeMail and
also get news about updates etc then join the SurgeMail
List.
Send an email to surgemail-list-requestnetwinsite.com with only 
"subscribe" in the message body

FAQ - http
://www.netwinsite.com/surgemail/help/faq.htm
************************************************************
****************