On 2010-12-20 2:03 AM, Ramesh wrote:
> I am planning to configure backup MX for primary MX. i have few
> queries..
> Please send suggestion's or URL to know more about this.
Don't bother... backup MX's should only be implemented by those who have
a very good reason for doing so, and are a total
On Mon, 2010-12-20 at 07:03 +, Ramesh wrote:
> HI All,
>
> I am planning to configure backup MX for primary MX. i have few queries..
>
> All email id's in primary MX need to be same in secondary MX?
> Is it possible to configure separate email clients to receive and send for
> both mail serv
Le 20/12/2010 08:03, Ramesh a écrit :
HI All,
I am planning to configure backup MX for primary MX. i have few queries..
All email id's in primary MX need to be same in secondary MX?
yes. and all checks done on the primary should be done on the secondary
as well.
also, if the secondary pas
HI All,
I am planning to configure backup MX for primary MX. i have few queries..
All email id's in primary MX need to be same in secondary MX?
Is it possible to configure separate email clients to receive and send for both
mail server's, in case primary MX is down?
Please send suggestion's or
7064]: 523FD1C11A:
>> to=, relay=none, delay=1264, delays=1264/0.01/0/0,
>> dsn=5.4.6, status=bounced (mail for mx2.youngguns.nl loops back to
>> myself)
>> Jan 21 17:23:02 marcus postfix/bounce[17065]: 523FD1C11A: sender
>> non-delivery notification: B15A81C76E
>
postfix/qmgr[16900]: 523FD1C11A:
> from=, size=650750, nrcpt=1 (queue active)
> Jan 21 17:23:02 marcus postfix/smtp[17064]: 523FD1C11A:
> to=, relay=none, delay=1264, delays=1264/0.01/0/0,
> dsn=5.4.6, status=bounced (mail for mx2.youngguns.nl loops back to myself)
> Jan 21 17:23:02
Hi list,
I had a problem with my primary mailserver which was not able to deliver
mail to some remote mx's. One of the mx's that we couldn't deliver to was
mx-cluster[1-2].one.com. After I modified the transport maps on
mx1.youngguns.nl (stevie.youngguns.nl) the message now is
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
able to force postfix to accept the incoming emails when
the dest address cannot be validated...
Unless you have a really good reason, you'd be much better off just
losing the MX2,
Customers paying for "MX BACKUP SERVER" service is a good reason to not loose
MX2 :-)
Really
> In that case my server reacts rejecting ALL email because if cannot
> be verified with "Recipient address rejected: unverified address:
> Address verification in progress".
Unless you have a really good reason, you'd be much better off just
losing the MX2, and let smtp work as
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:
25 matches
Mail list logo
