On 25/10/12 21:13, Bradley Rintoul wrote:
This could be good. I'd never looked into the LDA - I will study up on it.
Someone else was helping out here and I thought I'd shed some more light on what I'm doing here...
Let's say someone has an account with Yahoo, for example. My Python code is
fetching email from the user's Yahoo! account and placing it into the Dovecot Maildir storage for a particular user. Now when the user retrieves their mail, they are doing so using my Dovecot - my Dovecot instance is acting as a proxy, of sorts...
I'm intrigued by this. Why are you using some self-baked(?) python script to fetch the mail in stead of using ready-made components like fetchmail?
Unless there's a special reason not to, try using the LDA (and fetchmail/getmail for that matter).
This sounds exactly what you want: http://pyropus.ca/software/getmail/configuration.html#destination-mdaexterna...
-- Tom
Thanks for the responses!
(Is there an IRC channel?)
From: Sven Hartge sven@svenhartge.de To: dovecot@dovecot.org Sent: Thu, October 25, 2012 11:07:26 AM Subject: Re: [Dovecot] Creating Maildir and populating with emails via external Python process
Bradley Rintoul brintoul@sbcglobal.net wrote:
I'm using Dovecot to provide IMAP services for Thunderbird clients. The user's mail is stored in Maildir format and the individual emails which the user "receives" are actually downloaded and put into the Maildir "repository" using a Python email client (POP3 client).
I am trying to create the dovecot-uidlist file and maintain the "next UID" value within it, but I am having trouble with the UIDVALIDITY and the 128 bit mailbox global UID among other things. How can I "seed" a dovecot-uidlist file with these values..?
Sorry if the information is not much to go on, please let me know what more information you might need to help point me in the right direction.
How about injecting the mails into the LDA. It will take care of proper delivery without the need for your programm to know the internal workings of dovecot.
S°