Den 2012-02-06 14:36, James Day skrev:
> My current line of
thought is to use a check_helo_access map to make exceptions on a per
server basis, is there a better way?
> write to
postmas...@senderdomain.example.org perfectly done by users that
complain :-)
Hi, James. I use this here, but mine is a small server. When I see what looks
like a real message that was blocked, I usually email the postmaster of the
other system with a canned letter advising them of the issue and how to fix it.
It's usually just a line in their config that sets the helo
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Noel Jones
Sent: 06 February 2012 14:19
To: postfix-users@postfix.org
Subject: Re: reject unknown helo hostname
On 2/6/2012 7:36 AM, James Day wrote:
> Just wanted to get pub
On 2/6/2012 7:36 AM, James Day wrote:
> Just wanted to get public opinion on this one.
>
> reject_unknown_helo_hostname
I don't use that restriction because there seem to be too many legit
hosts that fail, and not enough bad ones that do.
Don't forget you can use a restriction with warn_if_rej
On Mon, Feb 06, 2012 at 01:36:09PM +, James Day wrote:
> reject_unknown_helo_hostname
Not safe for most use.
> My understanding is that to be RFC compliant your HELO greeting
> must be a valid hostname (ie there is a public A record).
Right.
> However since implementing this restriction un
Just wanted to get public opinion on this one.
reject_unknown_helo_hostname
My understanding is that to be RFC compliant your HELO greeting must be a valid
hostname (ie there is a public A record).
However since implementing this restriction under smtpd_helo_restrictions I
have had nothing but
