Wietse Venema:
> varad gupta:
> > Dec 9 13:24:25 ms1 postfix/smtpd[6462]: B082DCCEB6:
> > client=unknown[192.168.x.x], sasl_method=LOGIN,
> > sasl_username=x...@domain.tld
> > Dec 9 13:24:25 ms1 postfix/cleanup[24260]: B082DCCEB6:
> > message-id=<004801ccb647$d6a829e0$83f87da0$@domain.tld>
> > Dec 9 13:24:25 ms1 postfix/qmgr[21077]: B082DCCEB6:
> > from=<x...@domain.tld>, size=11809, nrcpt=2 (queue active)
> > Dec 9 13:53:15 ms1 postfix/lmtp[20066]: warning: open active
> > B082DCCEB6: No such file or directory
>
> The LMTP client was unable to open the queue file. This means
> one of the following:
>
> a) Someone was running "postfix reload". This runs "postsuper" which
> renames files whose name doesn't match their inode number. Such
> discrepancies happen when non-Postfix software creates queue
> files, or when files are copied from a different mail queue.
>
> Postfix requires that file names match inode numbers to avoid
> loss of email.
>
> I suggest you search the logfile for "reload" and "postsuper".
>
> b) You have file system corruption. Take the system to single-user
> mode and run FSCK or equivalent until there are no more errors.
c) Your inode numbers change when a file is renamed from incoming/foo
to active/foo.
Non-fixed inode numbers would explain why postsuper would want to
change the name of the file. For example, AFS file systems have
inode numbers that depend on how you reach a file.
Postfix safety (against loss of mail) requires that the inode number
does not change when a file is renamed to directory in the same
file system.
Wietse
> > # cat maillog | grep B082DA4218
> > Dec 10 11:59:27 ms1 postfix/qmgr[12420]: B082DA4218:
> > from=<x...@domain.tld>, size=11809, nrcpt=2 (queue active)
> > Dec 10 12:03:59 ms1 postfix/lmtp[30172]: B082DA4218:
> > to=<y...@domain.tld>, relay=[relay-ip], conn_use=551, delay=81573,
> > delays=81302/272/0/0.19, dsn=2.0.0, status=sent (250 2.0.0 Ok,
> > id=31000-14-551, from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as
> > 9C664165F6F)
>
> That is a file with a different name, with the same size and
> recipients, and it arrived 22 hours, 39 minutes and 33 seconds
> earlier, i.e. 13:24:26. That's close enough.
>
> Something caused the file name B082DA4218 to be changed into
> B082DCCEB6. The first five characters (B082D) of the name did not
> change: these are the time in microseconds. All characters in the
> rest of the name were changed: this is the file inode number. Most
> likely, the postsuper command (perhaps after "postfix reload")
> renamed the file to match the file inode number.
>
> Wietse
>
