From 52c60d1c3e6ff0477e5917c3a6981217cb217c8d Mon Sep 17 00:00:00 2001
From: Matthias Andree
O12. Fetchmail no longer expunges mail on a 451 SMTP response.
O13. I want timestamp information in my fetchmail logs.
O14. Fetchmail no longer deletes oversized mails with
---flush.
+ --flush.
+O15. Fetchmail always retains the first message in the
+ mailbox.
Answers:
@@ -3588,6 +3590,41 @@ oversized mails or both when a user specifies both
--limitflush
has been added to resolve the ambiguity.
This happens when fetchmail sees an "X-IMAP:" header in the very +first message in your mailbox. This usually stems from a message like +the one shown below, which is automatically created on your server. This +message shows up if the University of Washington IMAP or PINE software +is used on the server together with a POP2 or POP3 daemon that is not +aware of these messages, such as some versions of Qualcomm Popper +(QPOP):
+ +++ ++From MAILER-DAEMON Wed Nov 23 11:38:42 2005 +Date: 23 Nov 2005 11:38:42 +0100 +From: Mail System Internal Data <MAILER-DAEMON@imap.example.org> +Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA +Message-ID: <1132742322@imap.example.org> +X-IMAP: 1132742306 0000000001 +Status: RO + +This text is part of the internal format of your mail folder, and is not +a real message. It is created automatically by the mail system software. +If deleted, important folder data will be lost, and it will be re-created +with the data reset to initial values. ++
As this message does not contain useful information, fetchmail is not +retrieving it. And deleting it might slow down the server if you are +keeping messages on the server, and the server would recreate it +anyways, that's why fetchmail does not bother to delete it either.
+ +Back to Fetchmail Home -- cgit v1.2.3 |