Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!rex!ames!uhccux!munnari.oz.au!murtoa.cs.mu.oz.au!otc!metro!basser!nuts!cc!sysnet From: SYSNET@cc.nu.oz (David Morrison) Newsgroups: news.software.anu-news Subject: Re: How about making Message-ID:'s more unique? Message-ID: <9081@cc.nu.oz> Date: 31 Aug 89 16:27:57 GMT References: <10147@kuhub.cc.ukans.edu> Organization: University of Newcastle Lines: 23 In article <10147@kuhub.cc.ukans.edu>, SLOANE@kuhub.cc.ukans.edu (Bob Sloane) writes: > Some time ago we had some problems with the disk drive this is used to store > the news database. To make a long story short, we had to restore the disk > from save tapes that were several days old. As a result the Message-ID: > headers for some of the articles we sent out could have been duplicates. I > would like to suggest that the Message-ID: be a little more complicated than > just , perhaps something like , where pid is the > Process ID of the process creating the article. This would tend to make it > VERY unlikely that a job with a duplicate ID would be generated, even if the > NEWS.GROUPS file was restored from a previous time. Some systems use a message ID containing the date and time, eg, 890831112515@cc.nu.oz The only drawback with this is its length and trying to remember it to type to READ/ID=... It could be made more readable by making it a more recognisable form: 89Aug3111:25:15@cc.nu.oz -- David Morrison, Network Manager, Uni of Newcastle, Australia Try sysnet@cc.nu.oz.au or sysnet@cc.nu.oz (mail only) or (VAX PSI) psi%newcastle.edu.au::sysnet or psi%0505249626002::sysnet