On 10/03/17 12:44, Viktor Dukhovni wrote:
On Mar 9, 2017, at 8:22 PM, MRob wrote:
So is there any restriction that compares the client IP mapping with the HELO
hostname?
Nothing built-in
Is that a bad idea?
Yes.
Unless the system you're receiving email from publishes a CSA record.
You wo
> On Mar 9, 2017, at 8:22 PM, MRob wrote:
>
> So is there any restriction that compares the client IP mapping with the HELO
> hostname?
Nothing built-in
> Is that a bad idea?
Yes.
--
Viktor.
On 2017-03-09 13:41, Noel Jones wrote:
On 3/9/2017 3:16 PM, MRob wrote:
obtained by HELO? Is there something in the tcp connection that
identifies the hostname? Sorry if I misunderstood this part.
The HELO name is not related to and doesn't matter for
reject_unknown_client_hostname. Perhaps
On 2017-03-09 13:41, Noel Jones wrote:
On 3/9/2017 3:16 PM, MRob wrote:
obtained by HELO? Is there something in the tcp connection that
identifies the hostname? Sorry if I misunderstood this part.
The HELO name is not related to and doesn't matter for
reject_unknown_client_hostname. Perhaps
On 3/9/2017 3:16 PM, MRob wrote:
> obtained by HELO? Is there something in the tcp connection that
> identifies the hostname? Sorry if I misunderstood this part.
The HELO name is not related to and doesn't matter for
reject_unknown_client_hostname. Perhaps you were confused by the
different cont
On 2017-03-09 13:06, Noel Jones wrote:
On 3/9/2017 2:58 PM, MRob wrote:
Hello, in Postfix v3.1 I'm having a hard time getting
reject_unknown_client_hostname to bounce test messages.
See the docs for what this rejects.
http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname
Warni
On 3/9/2017 2:58 PM, MRob wrote:
> Hello, in Postfix v3.1 I'm having a hard time getting
> reject_unknown_client_hostname to bounce test messages.
See the docs for what this rejects.
http://www.postfix.org/postconf.5.html#reject_unknown_client_hostname
Warning: this is a very strict test likely t
Hello, in Postfix v3.1 I'm having a hard time getting
reject_unknown_client_hostname to bounce test messages.
I set an external host's Postfix myhostname to be purposefully
incorrect, like nosuchhost.example.com and sent a message to the test
system. If I have reject_unknown_helo_hostname enab
On 7/19/15 10:47 PM, Viktor Dukhovni wrote:
On Sun, Jul 19, 2015 at 10:44:09PM -0500, John Gateley wrote:
However, the question still remains: how can I test this without actually
making one of my domains live?
Define "test".
It will work as documented.
Test: ensuring that my understanding
On Sun, Jul 19, 2015 at 10:44:09PM -0500, John Gateley wrote:
> However, the question still remains: how can I test this without actually
> making one of my domains live?
Define "test".
It will work as documented. If you want to see what it would block
without blocking anything, consider:
On 7/19/15 10:36 PM, Viktor Dukhovni wrote:
On Sun, Jul 19, 2015 at 10:08:07PM -0500, John Gateley wrote:
I have a host running postfix on port 25 (also 12345 for debugging
purposes[*]),
and I want to test the following line in my main.cf:
smtpd_client_restrictions = reject_unknown_client_hos
On Sun, Jul 19, 2015 at 10:08:07PM -0500, John Gateley wrote:
> I have a host running postfix on port 25 (also 12345 for debugging
> purposes[*]),
> and I want to test the following line in my main.cf:
>
> smtpd_client_restrictions = reject_unknown_client_hostname
You can save yourself some time
I have a host running postfix on port 25 (also 12345 for debugging
purposes[*]),
and I want to test the following line in my main.cf:
smtpd_client_restrictions = reject_unknown_client_hostname
The host is on the internet, publicly accessible, but I haven't pointed any
DNS MX records at it.
The
13 matches
Mail list logo
