I went in and examined these messages. They both actually *do* have
Message-Id's -- which is why IMPORT evidently didn't reject them,
however EXPIRE doesn't seem to be as smart as IMPORT at recognising
ID's...
The common unusual thing about these two messages is they both had
extremely long ID strings. So whatever software sent them decided,
when formatting the header, to put the ID value on a new line. SO the
header looks like this (an actual example from my news.dat):
Message-id:
<c=US%a=_%p=Schwab%l=N1006SMX-970417210531Z-26548@n2100pmx.nt.schwab.com>
EXPIRE doesn't seem to recognise the above as being an ID, while
import must have (since the message wasn't rejected in the first
place).
This is a definite bug meaning that EXPIRE -o will never expire these
articles (because it won't be able to match the ID with the one stored
in the history.pag which contains the expirey dates) I think?
EXPIRE -r should (i haven't actually tried yet) still kill them (if
they are marked READ), and that's what I'll do to kill them (both
messages -- an unrelated coincidence -- happened to be in my
"procmail" pseudo newsgroup -- so easy to just expire -r that
newsgroup). However, I wanted to report the bug as related to EXPIRE
-o...
Although it's irrelevant, here's an example of the message EXPIRE gave
me...
---snip---
alt.aldus.pagemaker 108 expired
comp.graphics.apps.pagemaker 98 expired
1009
Article at offset 6814950 has no Message-ID.
2374
Article at offset 14237352 has no Message-ID.
2599 articles (5900116 bytes) deleted
--
.._,.,._.,.,.,_,._,,,.,_,.,_,..,..,_..,.,.,_,,.,.,_._.,_.,.._,.,_..,.
Tim Moddletun =-=-= with love and a banana fish =-=-= x @ veX . net
-=-=- brace yourself and read The Idiot by Fyodor Dostoyevsky -=-=-
^`~^"^`~^"^`~^"^`~^"^`~^"^`~^"^`~^"^`~^"^`~^"^`~^"^`~^"^`~^"^`~^"^`~^
Yarn/2 Bells & Whistles Page: http://www.vex.net/~x/bells2.phtml
* April 22nd * International Day of the Noble Parasite