the sort I needed. I need to look at headers and dates in the short term to
expire older messages in some mailboxes that accumulate messages rapidly by
day.
One thing I note -- is that Outlook -- no matter how many times I'd have to
delete it's account stash (before I gave up on it after a mandatory windows
security fix disabled IMAP), when I resubb'ed to the IMAP server, it always
would know which mailboxes were subscribed to and which were not -- I take it
that this was a function of the IMAP server and not something included in the
Mailboxes them selves?
The reason I ask is that Netscape on IRIX used to be able to recover the
information about which files were active mailboxes and which were not,
somehow, when they were mbox format and not accessed through IMAP. But when
using remote servers, I implemented IMAP for remote access and it still seemed
to know which folders were real mailboxes and which were not (or maybe I just
remember it that way and made sure all other files were compressed or not in
the same dir -- been a while). When I got a windows client outlook seemed to
know which files were valid subscribed-to folders and which were not. Other
Windows based clients like Netscape also could tell which were valid folders
and not. Now, with mozilla and thunderbird, they allow me to see all files in
the directory when I am subscribing including hidden indexing files like
".<box>.index" and ".<box>.index.ids." I'm not sure which client creates those
-- it appears to be a netscape-mozilla-thunderbird-"ism". Whatever -- but
oddly enough the first time I remember going through Mozilla, I thought it
picked out the right folders to subscribe to (maybe it picked the folders out
of Outlook's format or maybe vice versa depending on which client had IMAP
support first.
Now with the Box library...it's going through all valid mbox folders which is
"ok" (would be nice if it magically knew which I was subscribed to, but since I
don't know how any of the other clients did it I'm not going to worry too much
about it). However, when I iterate through all subfolders of my mail dir
(check=>true, skip_empty=>true), I then loop through each name and ask for it's
organization, size and #messages.:
<>@names=$folder->listSubFolders(check=>True,skip_empty=>True); <>@nnames=sort @names; @[EMAIL PROTECTED];$#nnames=-1; foreach(@names) { print; flush STDOUT; $subf=$folder->openSubFolder($_); print ", org=".$subf->organization,", "; print "size=".$subf->size.", "; print "#msgs=".$subf->messages; print "\n"; }
I get a few errors, a couple "annoying", and 1 fatal:
...
SuSE-Security, org=FILE, size=5496706, #msgs=1130
archive, org=FILE, size=1240, #msgs=0 << directory
bind, org=FILE, size=8039283, #msgs=1487
firewallsUnexpected end of header (C parser): << parser error
especially with government agencies, especially in the UK where it started
, org=FILE, size=5034191, #msgs=801 << count 1 greater than IMAP
no dummy msg at beginning of mbox
general, org=FILE, size=38062, #msgs=5
...
ipsecUnexpected end of header (C parser): << another parser error
A Proposed Standard specification is generally stable, has resolved
, org=FILE, size=907563, #msgs=212 << count 1 greater than # in IMAP
but has dummy message at beginning
...
Then the fatal: on a directory named "old"...it's odd, but somehow "old"
got mangled into a "o", but I have no file or dir in the directory named "o"
oWARNING: Folder does not exist, failed opening mbox folder /home/law/mail/o.
Can't call method "organization" on an undefined value at ./x.pl line 26.
I added a line to print out all the sorted values before I entered this loop and the line "o" is on was: ... mail_problems, net-traffic-logs, noflushd, o, openssh, perl, perl-mods,
Indeed, in the list of subfolders, "old/" is missing and "o" is present. I'm
not sure why or how "old/" got translated into "o".
1) In looking at firewalls, there seems to be a text line starting with
From as the first line after the header which is the bit of text printed
out in the error message:
"Status: RO
X-Status:
X-Keywords: NonJunk X-UID: 485
From my understanding ISO 17799 receives a lot of focus in Europe, especially with government agencies, especially in the UK where it started"
In "ipsec,", the From is in the middle of
the message and on a separate line from the text spit out in the error message:
"But at the end of the day there has to be one interpretation and that means that someone has to change.
From RFC 2026: A Proposed Standard specification is generally stable, has resolved"
2) As for the "old"->(transmute)->"o", I'm clueless...any ideas?
Thanks, -linda
