Hello Uwe,
On 2015-05-07 08:00, Uwe Eischens wrote:
very cool thing! The script works flawlessly and the mails are stored in /var/piler/imap on the fly. Thank you very much!
ok, then I put this script to the contrib directory.
May 7 07:34:44 nexus pilter[6196]: message-id=<[email protected]>, fname=1430976883-949924-6196-W4MYEUPC, size=1211 Next step will be thinking about pilerimport. As far as I understand the docs, no files are deleted during the import. So I have to ensure
by default no. However you may use the -r option which says remove after importing.
that the files in /var/piler/imap keep consistent, means deleting the whole content after a cron-controlled import could be a bit tricky, if there are new mails arriving while the import is running which are not
that's why you have 2 dirs under /var/piler/imap: "cur" and "new". I tried to imitate how mail servers handle the Maildir structure. So pilter.pl writes files to "new", and after the files is written, and the file handle is closed, then it relocates (ie. rename) the file to "cur". So you should process only
the cur directory with pilerimport.
yet detected by pilerimport. Does pilerimport performing any duplicate-detection? If so, deleting would be obsolete, which would make the process easier to control.
yes, piler discards duplicates. Janos
