Hi Janos,
very cool thing! The script works flawlessly and the mails are stored in
/var/piler/imap on the fly. Thank you very much!
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 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 yet
detected by pilerimport. Does pilerimport performing any
duplicate-detection? If so, deleting would be obsolete, which would make
the process easier to control.
Uwe
From: Janos SUTO <[email protected]>
Sent: 6.5.2015 22:22:12
To: Piler User
Subject: Re: Implementing a Milter port
So, here's a quick and dirty 1.0 beta solution.
You may edit the following variables, then ready to go:
my $savedir = "/var/piler/imap";
my $username = 'piler';
my $conn = 'inet:[email protected]';
It will save emails to $savedir/cur
Then you may process emails with pilerimport. Let me know
how it works.
Janos
--
Diese E-Mail koennte vertrauliche und/oder rechtlich geschuetzte Informationen
enthalten. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtuemlich erhalten haben, informieren Sie bitte den Absender und vernichten
Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
Mail sind nicht gestattet.
