In article <2fe86b1946b5c80d42eb685204fa0dfe@xxxxxxxxxxxxxxxxxxxx>,
Jeremy Nicoll - freelists <jn.fr.lsts.74@xxxxxxxxxxxxxxxxxxxx> wrote:
I thought I'd re-read the original mail at the start of this discussion.
On 2019-09-20 10:16, Rod at Orpheusmail wrote:
I use !AntiSpam, !POPstar and !Pluto and have been for years and I've
always had a problem with "defaulted", "deleted" and "diverted"
files/logs. I have never been sure what "defaulted" does and "deleted"
works as expected; leaving a list of headers in the file
'<SysLog$LogDir>.deleted'.
What?I suppose my lack of understanding was because I haven't read the manual
(I've lost a few emails I wanted to keep on the way, though!).
-- as an aside, not really relevant here - did you mean because your ASBecause the AS rules I added caught something they were not intended to
rules told it to delete things because the rules were not adequate for your
needs, or do you mena something else?
Diverted however, I've never been able to get working as I wanted it to
work. I get the headers in the '<SysLog$LogDir>.diverted' log file but
have never been able to save the emails in '<SysLog$LogDir>.DivertTo'.
What?If an email is caught by a 'divert' rule the it is recorded in the log file
When I read this before I thought it was weird but because the Divert option
was something Frank added, I didn't pay much attention, esspecially to the
second instance.
But I would have expected that content written to a <SysLog$LogDir>.I agree, but, although the log file contained the details of diverted files,
anything file would be a LOG - a record of processing done somewhere else.
So I would expect <SysLog$LogDir>.deleted to contain partial information
about the headers seen in emails that AS has deleted, and I would expect
<SysLog$LogDir> .DivertTo to contain partial logging info about emails that
have been diverted. I wouldn't expect either file to contain whole emails.
/If/ entire emails can correctly be written to a log file (in essence as a
very detailed logging of what was done with the emails themselves) they
will possibly not have the line-endings that an email client will expect to
see.
Surely, SURELY, the emails themselves were 'diverted' to some other folder,Yes, I think they were. When I was looking for lost emails I found two files
and written to this other place in the format that Pluto expects?
Do you really mean that you've cut & pasted sections of log files into otherNo.
places and then tried to debatch those?
The other day, however, I found some very large files located in
!AntiSpam - !AntiSpam.Defaulted and !AntiSpam.DefaultTo.
- this time did you really mean these locations, instead of the Syslog ones?Yes, see above.
While trying to recover some of these emails (by dropping them in
'!POPstar.MailDir.spool.mail.text'). I ran into a problem.
After debatching and opening the relevant !Pluto Boxes list the emails in
question were present but greyed out. Opening them revealed no body text
but an attachment. Opening the attachment revealed nothing, it appeared to
be empty. But opening the header view revealed the body of the email
incorporated into the header. So what is happening here?
It was possible to extract the email by saving it from the header view and
extracting the header manually; so all was not lost.
I don't know what "the header view" means, but if you saved content fromIn Pluto's Article Viewer menu bar the 4th from the right is up arrow over a
that, perhaps it is not saved with the line-endings that should be there
for a mail transport file, but instead just a normal text file?
