Re: mynetworks=<empty> vs mynetworks=<default> (via mynetworks_style)

2 msg	2 postfix server on the same domain in differen...
3 msg	mailer-deamon sends error messages to: question
3 msg	Procmail
15 msg	MAIL FROM timeout with ciphers=high
2 msg	milter, broken pipe
17 msg	How to listen on 587 as well as 25?
6 msg	reject_sender_login_mismatch doesnt work
2 msg	smtp auth
4 msg	Postfix with MYSQL compile error

mynetworks=<empty> vs mynetworks=<defa...
\ Alain Spineux (29 Nov 2007)
. \ (Wietse Venema) (29 Nov 2007)
. . \ Alain Spineux (29 Nov 2007)
. . . \ (Wietse Venema) (29 Nov 2007)
. . . . \ Bill Cole (29 Nov 2007)
. . . . \ Alain Spineux (29 Nov 2007)
. . . . . \ (Wietse Venema) (29 Nov 2007)
. . . \ Blake Hudson (30 Nov 2007)

3 msg	message_size_limit with ldap search parameter
2 msg	Pipe debugging
12 msg	destination_concurrency_limit not respected ?
13 msg	Virtual spam forwarding issues
2 msg	cleaning up deferred queue
2 msg	static nexthop per domain
2 msg	Simple postmap question
9 msg	Issues with Recipient_Canonical mapping
3 msg	Mail server reboot after got flood
3 msg	can't create a virtual domain

Subject:	Re: mynetworks=<empty> vs mynetworks=<default> (via mynetworks_style)
Group:	Postfix-users
From:	Blake Hudson
Date:	30 Nov 2007

Alain Spineux wrote:
> On Nov 29, 2007 8:09 PM, Wietse Venema <wietse> wrote:
>
>> Alain Spineux:
>>
>>> Hi
>>>
>>> I want to have mynetworks=<empty>
>>> I mean no host taking advantage of the "mynetworks" advantage,
>>> including 127.0.0.1 !
>>>
>>> If a set "mynetworks="
>>> then, postfix use the default from mynetworks_style!
>>>
>> No it doesn't.
>>
>
> How can I not trust you!
> Then my problem is somewhere else,
> and goes away if a set mynetworks to 0.0.0.0 !
>
> I have
>
> smtpd_sender_restrictions =
> permit_mynetworks,
> # permit_sasl_authenticated,
> # this policy verify sender=username and more
> check_policy_service unix:private/egpolicy,
> reject_non_fqdn_sender,
> reject_unknown_sender_domain,
> permit
>
> and
>
Why do you use permit_my networks in your recipient restrictions if you
don't want to permit any hosts with it? Why not remove it from your
restrictions? What other advantages (that are important to you) does a
host get by being in that list?

-Blake