Thankyou for clarifying my technical ineptitude. But I thought it would have been obvious that I had limited technical knowledge by the content of my message. And rather than flame me, you may have been a little more constructive.
As far as I can make out, postfix can tell the nature of a connection via the PTR (rDNS) record information, although this can be modified on request. It is that information I was eluding to, as postfix does use that information within the relaying_stoplist to prevent just that. So given my secondary (backup) MX server is on one off those types of connection, how do I allow it to connect to my primary server when it returns to service given I have not modified the relaying_stoplist file? Now whilst I may have used some incorrect terms. Think about my puny little brain, and how technically inept you were when you were getting into IT. Regards Fred > On 7/7/2013 4:29 PM, Fred Zinsli wrote: > >> I have primary and secondary MX servers, but my secondary server is on >> cable. My primary server is on the backbone. >> >> How can I configure my primary server to accept connections/mail from >> the >> secondary server but still refuse connections/mail from all other cable >> connections. > > You've said "cable" twice now, plus once in the subject. Postfix > doesn't know what "cable" is. "We" don't know what "cable" is. Do you > actually mean to say "dynamic IP address" here? Likewise, when you say > "backbone" do you simply mean "static IP address"? > > This is a technical mailing list. We can't help you if you don't > provide technically accurate information. If the backup MX indeed has a > dynamic IP address then Wietse's suggestion obviously won't work for you > and a different solution is needed. > > -- > Stan > >
