Corrupted data?

[David Nugent <davidn@sdev.blaze.net.au>]

When I first looked at email today, I was somewhat alarmed to
find over 500 bounce messages in my inbox. :-( Anyway, each and
every one of them were of this kine:


  From postmaster@unique.blaze.net.au Sat Sep 28 14:30:22 1996
  Date: Sat, 28 Sep 1996 12:44:14 +1000
  From: The Post Office <postmaster@unique.blaze.net.au>
  To: CFS-L@LIST.NIH.GOV
  Cc: The Post Office <postoffice@unique.blaze.net.au>
  Subject: Delivery problems with your mail

  A copy of your message is being returned to you due to
  [.. etc ..]
  The following errors occurred during message delivery
  processing:

  <smtp UNIQUE.blaze.net.au inki@UNIQUE.blaze.net.au 65535>:
  Trying to talk with myself!

[ and so on ]

I immediately ran router -i, and found that yes, indeed, any mail
sent to unique.blaze.net.au (this is the hostname of the current
machine) or any of the machine in $MAILVAR/db/localnames was, in
fact, bouncing. Any targets which should have been locally
deliverable were suddenly being resolved to smtp to itself.

I shutdown the mailer and restarted. Same thing.

I shutdown the machine and rebooted. Same thing.

I shutdown zmailer, removed all *.fc files and restarted.
Suddenly things are working again.

The machine had been rebooted early this morning, which is
exactly when the problem started. I can only summise from the
"fix" that the problem was due to one or more corrupted *.fc
files. Searching the log reveals little else by way of
explanation - just a sudden change of behaviour when router
started up after the reboot.

ZMailer version is 2.99.38, running under Linux kernel 2.0.7.


David Nugent, Unique Computing Pty Ltd - Melbourne, Australia
Voice +61-3-791-9547 Data/BBS +61-3-792-3507 3:632/348@fidonet
davidn@blaze.net.au http://www.blaze.net.au/~davidn