On 8/6/2009 12:29 PM, Aaron Wolfe wrote:
address_verify_map = btree:/var/lib/postfix/verify
address_verify_positive_refresh_time = 14d
unverified_recipient_defer_code = 250
>>> You are correct, but this is NOT the recommended way...
>>>
>>> Don't change the unverified_recipient_defe
On Thu, Aug 6, 2009 at 8:39 AM, Charles Marcus wrote:
> On 8/6/2009, Santiago Romero (srom...@servicom2000.com) wrote:
>> By adding the following to my main.cf, I'll check RCPT TO addresses
>> against primary MX, except when PRIMARY MX doesn't answer. In that case,
>> I'll accept any destination fo
On 8/6/2009, Santiago Romero (srom...@servicom2000.com) wrote:
> By adding the following to my main.cf, I'll check RCPT TO addresses
> against primary MX, except when PRIMARY MX doesn't answer. In that case,
> I'll accept any destination for my relay_domains list, just like I was
> doing before add
Yes, that's what the docs say.
450 = default, defer mail if the address can't be verified.
250 = if the address can't be verified, accept it anyway. Not
recommended.
So, summarizing. (And, please, correct me before doing a wrong change
in my config file):
My current server now is a backsc
Charles Marcus wrote:
> On 8/5/2009, Mikael Bak (mik...@t-online.hu) wrote:
>>> So, do you mean that changing this parameter to 250 would make postfix
>>> to accept the email?
>
>> No.
>
> Actually, the answer to his question is yes.
>
>> You should leave this parameter in its default value.
>
On 8/5/2009, Mikael Bak (mik...@t-online.hu) wrote:
>> So, do you mean that changing this parameter to 250 would make postfix
>> to accept the email?
> No.
Actually, the answer to his question is yes.
> You should leave this parameter in its default value.
Correct - but he specifically asked if
Santiago Romero wrote:
Hi,
Quoting the documentation[1]:
"The unverified_recipient_defer_code parameter (default 450) specifies
the numerical Postfix SMTP server reply code when a recipient address
probe fails with some temporary error. Some sites insist on changing
this into 250. NOTE: This
Santiago Romero wrote:
>
>> Hi,
>>
>> Quoting the documentation[1]:
>>
>> "The unverified_recipient_defer_code parameter (default 450) specifies
>> the numerical Postfix SMTP server reply code when a recipient address
>> probe fails with some temporary error. Some sites insist on changing
>> this
Hi,
Quoting the documentation[1]:
"The unverified_recipient_defer_code parameter (default 450) specifies
the numerical Postfix SMTP server reply code when a recipient address
probe fails with some temporary error. Some sites insist on changing
this into 250. NOTE: This change turns MX servers
Brian Evans - Postfix List wrote:
> Mikael Bak wrote:
>> Brian Evans - Postfix List wrote:
>>
>>> Mikael Bak wrote:
>>>
Santiago Romero wrote:
> Really, reject_unverified_recipient feature is very nice, but rejecting
> all mail when primary MX doesn't answer
Mikael Bak wrote:
> Brian Evans - Postfix List wrote:
>
>> Mikael Bak wrote:
>>
>>> Santiago Romero wrote:
>>>
>>>
Really, reject_unverified_recipient feature is very nice, but rejecting
all mail when primary MX doesn't answers breaks it for us :(
Any idea? :?
Brian Evans - Postfix List wrote:
> Mikael Bak wrote:
>> Santiago Romero wrote:
>>
>>> Really, reject_unverified_recipient feature is very nice, but rejecting
>>> all mail when primary MX doesn't answers breaks it for us :(
>>>
>>> Any idea? :?
>>>
>> Hi,
>>
>> Quoting the documentation[1]:
Mikael Bak wrote:
> Santiago Romero wrote:
>
>> Really, reject_unverified_recipient feature is very nice, but rejecting
>> all mail when primary MX doesn't answers breaks it for us :(
>>
>> Any idea? :?
>>
>
> Hi,
>
> Quoting the documentation[1]:
>
> "The unverified_recipient_defer_code pa
Santiago Romero wrote:
>
> Really, reject_unverified_recipient feature is very nice, but rejecting
> all mail when primary MX doesn't answers breaks it for us :(
>
> Any idea? :?
>
Hi,
Quoting the documentation[1]:
"The unverified_recipient_defer_code parameter (default 450) specifies
the num
If you want this behavior, do not use reject_unverified*.
Instead, use a relay_recipient_maps that can be checked locally.
Hi.
This server is a secondary MX server for our customers. Those customers
have their own "private" primary MX servers, so It's not possible for me
to have a local
On 8/3/2009, Santiago Romero (srom...@servicom2000.com) wrote:
> This works nicely when MX1 servers are working and answering RCPT-TO
> checks, but then I asked ... what happens if my server can't reach
> the primary MX (server stopped, misconfiguration, power outage...) ?
>
> In that case my serv
Santiago Romero wrote:
>
> This works nicely when MX1 servers are working and answering RCPT-TO
> checks, but then I asked ... what happens if my server can't reach the
> primary MX (server stopped, misconfiguration, power outage...) ?
>
> In that case my server reacts rejecting ALL email because i
Hi!.
I have a secondary MX server and I'm trying to configure it to "check"
recipient addresses against primary SMTP servers to reject emails
directed to non existing addresses.
I've read the following:
http://www.postfix.org/ADDRESS_VERIFICATION_README.html
So I added this to my main.cf:
18 matches
Mail list logo
