Debian bug report logs - #1481
smail paniclog suggestion

Message received at debian-bugs:

From cus.cam.ac.uk!iwj10 Tue Sep 26 05:14:30 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sxYu5-000GYrC; Tue, 26 Sep 95 05:14 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA14933
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Tue, 26 Sep 1995 05:14:08 -0700
Received: by bootes.cus.cam.ac.uk 
	(Smail-3.1.29.0 #36) id m0sxYVf-000C0ZC; Tue, 26 Sep 95 12:49 BST
Received: by chiark
	id <m0sxXNi-0002ZwZ@chiark.al.cl.cam.ac.uk>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Tue, 26 Sep 95 11:36 BST
Message-Id: <m0sxXNi-0002ZwZ@chiark.al.cl.cam.ac.uk>
Date: Tue, 26 Sep 95 11:36 BST
From: Ian Jackson <iwj10@cus.cam.ac.uk>
To: debian-bugs@pixar.com
X-Debian-Pr: quiet
Subject: Re: smail paniclog suggestion

Package: smail
Version: 3.1.29.1

Bernd S. Brentrup writes ("smail paniclog suggestion"):
> I'm not sure whether to report this as a bug
> 
> bora:~$ dpkg --status smail | egrep 'Package|Version|Revision|Maintainer'
> Package: smail
> Maintainer: Ian Jackson <iwj10@cus.cam.ac.uk>
> Version: 3.1.29.1
> Revision: 13
> 
> After recovering from a hardware failure while fetching mail from my pop3
> server, I had a hard time to figure out that popclient probably did not
> delete the failed message, I have no proof though.
> 
> When logging a serious error in paniclog, smail uses its internally generated
> message id for identification, this id doesn't occur anywhere else, so it was
> completely useless in this situation.
> 
> Including the orig-id - which is listed for successfully received messages in
> logfile - would make it a lot easier to check whether mail has been lost.
> 
> I'm no smail guru and don't have enough time to look into the smail docs now.
> As a workaround I'll setup procmail on my upstream account to log incoming
> message ids, no need for cooperation from the postmaster.
> 
> Greetings
> -- Siggy
>