On Thu, May 09, 2002 at 01:50:36PM -0400, Dave C. wrote:
> On Wed, 8 May 2002, Matthew Daubenspeck wrote:
>
> > On Wed, May 08, 2002 at 12:11:09PM -0700, Jeremy C. Reed wrote:
> > > On Wed, 8 May 2002, Matthew Daubenspeck wrote:
> > >
> > > > Too many "Received" headers - suspected mail loop
> > >
> > > Look at the mail logs on the other system.
> > >
> > > Does it forward back to the backup system?
> >
> > The original sender's server trys to contact the main server and it
> > fails. It then sucessfully contacts the backup and delivers the
> > message.
> >
> > The backup then tries to contact the main server and fails, then
> > contacts the backup (itself) and delivers the message. Then the new
>
> Thats your problem. The backup isnt recognizing that it should just hold
> on to the message if it cant contact the primary server. How are the MX
> records set up, do they point at the primary hostname of the servers,
> so that the backup server can recognize its own address?
ordeal:/home/mellofone# dig oddprocess.org MX
; <<>> DiG 9.2.0 <<>> oddprocess.org MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55417
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3
;; QUESTION SECTION:
;oddprocess.org. IN MX
;; ANSWER SECTION:
oddprocess.org. 5202 IN MX 0 oddprocess.org.
oddprocess.org. 5202 IN MX 5 daubnet.dns2go.com.
The main server is oddprocess.org, and the backup is
daubnet.dns2go.com.
The backup server /etc/hosts has
192.168.0.4 daubnet.dns2go.com
So it should know its own addresss..
