Re: mailfront imapfront-auth with dovecot 1.2.16 : SUCCESS

Giam Teck Choon <[email protected]> Thu, 11 Nov 2010 07:04:08 +0800
Newsgroups gmane.comp.sysutils.bgware
Organization CHOON.NET
Message-ID <[email protected]>

On 11/11/2010 06:21 AM, Bruce Guenter wrote:
> On Thu, Nov 11, 2010 at 05:38:43AM +0800, Giam Teck Choon wrote:
>>> Please try the appended patch.  Simply set SETUP_DOVECOT=1 (or =
>>> anything) before running imapfront-auth, and it should set $MAIL to an
>>> appropriate string.
>>
>> Yes, the patch works!
>
> Excellent.  Is the choice of $SETUP_DOVECOT a reasonable name, or should
> I use something else (like $DOVECOT_MAIL etc)?

If you ask me about appropriate name, I think $DOVECOT_MAIL_LOCATION or 
$DOVECOT_MAILLOCATION since we are passing the MailLocation to dovecot 
imap directly.  Anyway, whatever name you like doesn't matter as long as 
it works :)

I think if your imapfront-auth can handle dovecot different 
mail_location format would be great.  Yes, read your comment about 
adding stat to handle both cases.... ... :)  So how you stat the two 
format?  Just curious.  By using the $SETUP_DOVECOT variable?  Like 
SETUP_DOVECOT=mbox|maildir?  Or simply stat the $MAIL to see it is a 
directory or a file to differential maildir or mbox respectively before 
modifying $MAIL to maildir or mbox etc. to dovecot imap?

http://wiki.dovecot.org/MailLocation

mbox and maildir are well know standards I guess but dovecot has their 
own called dbox (http://wiki.dovecot.org/MailboxFormat/dbox).  Do you 
plan to support such?  Not a requirement since making mailfront + cvm 
natively support dovecot is primary goal without excessive 
hacking/patching will benefit other users :)


>
> I see by the wiki that this works for version 2 as well, and also
> supports mbox files.  I will add a stat to the imapfront-auth code to
> handle both cases.
>

That is my next task to test for version 2 actually :p

If their version 2 are using $MAIL for mail_location (same as their 
version 1 which I guess should be) and with double colons "::" escape 
feature in their version 2 as well, I don't see why won't work :p

If you are interested, I can report back my progress about the test for 
their version 2?

Many thanks for your prompt response!

Kindest regards,
Giam Teck Choon