ictions = permit_mynetworks permit_sasl_authenticated
> reject_unauth_destination
>
> in main.conf.
>
> In several places in main.cf I have permit_sasl_authenticated. Should I only
> have that in master.cf under submission?
>
Since you don't have AUTH enabled on port 25,
permit_s
On 31 Aug 2013, at 10:20 , Noel Jones wrote:
> reject_unauth_destination is what keeps you from being an open
> relay, and is required in either smtpd_recipient_restrictions or
> (postfix 2.10 and newer) smtpd_relay_restrictions.
Hmm. I did run several tests on the "are you
On 8/31/2013 2:55 AM, LuKreme wrote:
> Is there any downside to using reject_unauth_destination? I had it commented
> out but I did not have a note on why it was disabled. Reading the
> description, it seems like it should always be turned on (or at least that it
> couldn
!-- On Sat 31.Aug'13 at 8:55:34 BST, LuKreme (krem...@kreme.com), wrote:
> Is there any downside to using reject_unauth_destination? I had it commented
> out but I did not have a note on why it was disabled. Reading the
> description, it seems like it should always be turned o
Is there any downside to using reject_unauth_destination? I had it commented
out but I did not have a note on why it was disabled. Reading the description,
it seems like it should always be turned on (or at least that it couldn't
possibly hurt)?
<http://www.postfix.org/postcon
IP address.
(Clearly you are not in that situation, because DNSBL lookups would
be meaningless.)
> Now I understand why this is failing. I guess I'm going to need to
> do something different with my SMTPD restrictions -- possibly move
> all my existing client restrictions to be
after reject_unauth_destination).
Rich Wales
ri...@richw.org
It's often recommended to put all restrictions under
smtpd_recipient_restrictions to keep life simpler.
Basic format...
smtpd_recipient_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unauth_destination
... white
> That is ignored in the context of a "RCPT TO" command (thus in all of
> the top-level restriction classes when smtpd_delay_reject = yes) for
> a recipient that would fail "reject_unauth_destination". For such a
> recipient do you really need DNSWL whitelisting
On Fri, Jun 24, 2011 at 08:12:28PM -0700, Rich Wales wrote:
> In http://www.postfix.org/postconf.5.html#smtpd_client_restrictions, I
> read that "for safety", permit_dnswl_client and permit_rhswl_client are
> silently ignored when they would override reject_unauth_destination.
te in the various restriction lists).
In http://www.postfix.org/postconf.5.html#smtpd_client_restrictions, I
read that "for safety", permit_dnswl_client and permit_rhswl_client are
silently ignored when they would override reject_unauth_destination.
I understand why this is a good idea w
Le 20/11/2010 20:55, Victor Duchovni a écrit :
On Sat, Nov 20, 2010 at 07:45:41PM +0100, Ben wrote:
Thank you for your help ! The recipient domain should be configured as
final, but is not. I think that's the problem.
I joined the information you asked to avoid line breaking.
Turn off verbos
On Sat, Nov 20, 2010 at 07:45:41PM +0100, Ben wrote:
> Thank you for your help ! The recipient domain should be configured as
> final, but is not. I think that's the problem.
>
> I joined the information you asked to avoid line breaking.
Turn off verbose logging, it is not needed, and obscures t
4:50 kappa postfix/smtpd[23554]: reject_unauth_pipelining: RCPT
Nov 19 17:34:50 kappa postfix/smtpd[23554]: generic_checks: name=reject_unauth_pipelining status=0
Nov 19 17:34:50 kappa postfix/smtpd[23554]: generic_checks: name=reject_unauth_destination
Nov 19 17:34:50 kappa postfix/smtpd[23554]
On Sat, Nov 20, 2010 at 06:49:52PM +0100, Ben wrote:
>>> I have a problem of relay access denied with postfix to deliver a mail
>>> to one domain (only one, all other domains are ok). I ran smtpd in
>>
>> Does the domain name match mydestination? If yes, show evidence.
>>
>> Does the domain name m
[23554]: generic_checks: name=reject_unauth_destination
Nov 19 17:34:50 kappa postfix/smtpd[23554]: reject_unauth_destination: i...@test-and-test.com
Nov 19 17:34:50 kappa postfix/smtpd[23554]: permit_auth_destination: i...@test-and-test.com
Nov 19 17:34:50 kappa postfix/smtpd[23554]: ctable_locate: l
Le 20/11/2010 18:26, Wietse Venema a écrit :
Ben:
Hello,
I have a problem of relay access denied with postfix to deliver a mail
to one domain (only one, all other domains are ok). I ran smtpd in
Does the domain name match mydestination? If yes, show evidence.
Does the domain name match virtu
Ben:
> Hello,
>
> I have a problem of relay access denied with postfix to deliver a mail
> to one domain (only one, all other domains are ok). I ran smtpd in
Does the domain name match mydestination? If yes, show evidence.
Does the domain name match virtual_alias_domains? If yes, show evidence
Hello,
I have a problem of relay access denied with postfix to deliver a mail
to one domain (only one, all other domains are ok). I ran smtpd in
verbose mode and I can see that it's the reject_unauth_destination
generic check that reply with status 2, so postfix reject the mail.
18 matches
Mail list logo
