Re: destination/maildir: Manuals seem to use different standards / how to configure correctly?

Hi Larry,

looking at the docs a second time (especially 
https://wiki2.dovecot.org/HowTo/TriggerGetmailOnIMAPAccess), it seems 
getmail doesn't use the maildir at all - it uses a script (probably sth. 
like a pipe function) to deliver the mail directly to dovecot, so mail 
will only be stored in the maildir folder by dovecot, I guess. Probably 
time to just be happy.  ;-)

Regards

Peter


Am 08.07.2018 um 13:03 schrieb Larry Fahnoe:
> Hi Peter,
>
> Yes, if you have delete = false you can make many different test runs
> without making any changes to the source IMAP server. For your initial
> tests, use something like:
>
> message_log_verbose = true
> verbose = 2
> message_log = ~/.getmail/log
>
> max_messages_per_session = 10
>
> delete = false
> read_all = true
>
>
> Once you're happy with the way getmail/dovecot_lda/sieve is working, turn
> down the logging, remove max_messages_per_session and set delete = true.
> Takes a few reads of the various bits of documentation, but these tools
> work really well together.
>
> --Larry
>
>
> On Sun, Jul 8, 2018 at 4:34 AM, Peter Nabbefeld <[email protected]>
> wrote:
>
>> Hi,
>>
>> syncing isn't a solution, as I want to remove all my messages from the
>> provider's server, when I'm ready, so offlineimap and imapsync won't help.
>> getmail's maildir shall be used by dovecot as "mail buffer".
>>
>> I've noticed the following two options:
>> * read_all (boolean) — if set, getmail retrieves all available messages.
>> If unset, getmail only retrieves messages it has not seen before. Default:
>> True.
>> * delete (boolean) — if set, getmail will delete messages after retrieving
>> and successfully delivering them. If unset, getmail will leave messages on
>> the server after retrieving them. Default: False.
>>
>> If I understand that correctly, this is exactly what I'd expect for a "dry
>> run", when using defaults: Just copy but change nothing (with the exception
>> of some headers after receiving).
>>
>> Kind regards
>>
>> Peter
>>
>>
>>
>>
>> Am 07.07.2018 um 15:05 schrieb RW:
>>
>>> On Sat, 7 Jul 2018 09:44:42 +0200
>>> Peter Nabbefeld wrote:
>>>
>>> Hello,
>>>> I'm trying to setup a dovecot installation with getmail and found
>>>> these instructions:
>>>>
>>>> 1.
>>>> http://pyropus.ca/software/getmail/configuration.html#destin
>>>> ation-maildir
>>>> using "~/Maildir/"
>>>>
>>>> 2. https://wiki2.dovecot.org/HowTo/TriggerGetmailOnIMAPAccess
>>>>       using "~/.maildir"
>>>>
>>>> 3. Using Arch Linux, I've set "mail_location = maildir:~/Maildir" in
>>>> "/etc/dovecot/conf.d/10-mail.conf" as advised in their wiki.
>>>>
>>>> As these folder names seem having to do with storage format, I don't
>>>> want just to guess, so which variant would be correct?
>>>>
>>> It doesn't matter, unless there's something else that cares.
>>>
>>>
>>> Just to make sure, I'm using the correct toolset:
>>>> I want to move all my mail documents off of my provider (GMX), and I
>>>> want everything to be stored locally. So I want getmail to fetch
>>>> everything, including folder structure
>>>>
>>> getmail doesn't do that itself, but you might be able to get
>>> dovecot sieve to read the folder name from the
>>> X-getmail-retrieved-from-mailbox header and file automatically
>>> creating missing folders as it goes. It would rely on some sieve
>>> extensions that I don't use, so I'm not sure.
>>>
>>> Alternately there are IMAP syncing programs, such as offlineimap and
>>> imapsync, that can sync directly to the maildir folders or through imap.
>>> Note that there is no standard for creating maildir subfolders so, if
>>> you sync directly make sure that any such program creates them in a way
>>> that they can be read by dovecote.
>>>
>>> If you just a one-off transfer from the remote imap server to the
>>> local imap server it might be easier to just use a mail client to move
>>> the mail manually - and then switch to getmail for new mail.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>