Re: [Dovecot] Dovecot LDA + Fedora destribution = no go?
Jakob Hirsch jh at plonk.de Sat Mar 25 04:40:29 EET 2006 Quoting Charlie Davis:
Anyone know of a way to get the LDA to work on the fedora distribution available on yum? I'm a big fan of the whole yum-auto-updating thing but if this isn't possible, I'll go tarball.
To use the LDA, AFAIK you'll have to go CVS.
Going CVS, can we build and install dovecot-lda and keep the dovecot executable the way it is? Or do we have to rebuild the dovecot executable from the CVS tree too?
Thank you.
Marilyn Davis
Quoting Marilyn Davis:
if this isn't possible, I'll go tarball. To use the LDA, AFAIK you'll have to go CVS. Going CVS, can we build and install dovecot-lda and keep the dovecot executable the way it is? Or do we have to rebuild the dovecot executable from the CVS tree too?
I don't really know about the current status of LDA, but as it uses parts of lda you should at least compile with current CVS' dovecot, but perhaps you don't have to use it.
I'm under the impression that the lda is currently basically a proof-of-concept implementation, I wouldn't use it on a production server (and the current CVS does not even compile here).
On Sun, 26 Mar 2006, Jakob Hirsch wrote:
Quoting Marilyn Davis:
if this isn't possible, I'll go tarball. To use the LDA, AFAIK you'll have to go CVS. Going CVS, can we build and install dovecot-lda and keep the dovecot executable the way it is? Or do we have to rebuild the dovecot executable from the CVS tree too?
I don't really know about the current status of LDA, but as it uses parts of lda you should at least compile with current CVS' dovecot, but perhaps you don't have to use it.
I'm under the impression that the lda is currently basically a proof-of-concept implementation, I wouldn't use it on a production server (and the current CVS does not even compile here).
Oh. That's interesting. OK. I'll back up. I have my own edges to bleed on.
Exim allows a conversation to a socket from the configuration file, so it would be even better to talk directly to a socket into dovecot for delivering, rather than via a shell. Then I could talk to dovecot via my python code too.
But cool. We'll wait and continue to dance around the imap server.
Thank you for the scoop.
Marilyn
Quoting Marilyn Davis:
Exim allows a conversation to a socket from the configuration file, so it would be even better to talk directly to a socket into dovecot for delivering, rather than via a shell. Then I could talk to dovecot via
Exim doesn't start a shell (unless explicitly specified) when using the pipe transport, but there's always a fork&exec, of course, but the impact is little on modern systems. There was a little talk a while ago that it would be very cool to have a LMTP server inside dovecot (just like Cyrus), but I think it'll take a while until Timo will have time for such things. I thought about doing it myself, when time permits, as plugin, if this is possible.
On Sun, 26 Mar 2006, Jakob Hirsch wrote:
Quoting Marilyn Davis:
Exim allows a conversation to a socket from the configuration file, so it would be even better to talk directly to a socket into dovecot for delivering, rather than via a shell. Then I could talk to dovecot via
Exim doesn't start a shell (unless explicitly specified) when using the pipe transport, but there's always a fork&exec, of course, but the impact is little on modern systems.
Oh. I see. Good.
There was a little talk a while ago that it would be very cool to have a LMTP server inside dovecot (just like Cyrus), but I think it'll take a while until Timo will have time for such things. I thought about doing it myself, when time permits, as plugin, if this is possible.
Thank you for the help and info.
Marilyn
--
On Sun, 2006-03-26 at 03:37, Jakob Hirsch wrote:
There was a little talk a while ago that it would be very cool to have a LMTP server inside dovecot (just like Cyrus), but I think it'll take a while until Timo will have time for such things. I thought about doing it myself, when time permits, as plugin, if this is possible.
As an alternative to an LDA, would it be possible to let deliveries go to /var/spool/mail in mbox format, then have dovcot (in imap mode only) transparently move them to maildir with appropriate indexing? I'd prefer to have mbox format for users that use pop to download everything but have maildir folders for imap users who keep things on the server.
-- Les Mikesell lesmikesell@gmail.com
On 2006-03-26 12:04:46 -0600, Les Mikesell wrote:
As an alternative to an LDA, would it be possible to let deliveries go to /var/spool/mail in mbox format, then have dovcot (in imap mode only) transparently move them to maildir with appropriate indexing? I'd prefer to have mbox format for users that use pop to download everything but have maildir folders for imap users who keep things on the server.
what about pop users who keep the mail on the server? than you have the same as an imap user.
darix
-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
On Sun, 2006-03-26 at 12:36, Marcus Rueckert wrote:
As an alternative to an LDA, would it be possible to let deliveries go to /var/spool/mail in mbox format, then have dovcot (in imap mode only) transparently move them to maildir with appropriate indexing? I'd prefer to have mbox format for users that use pop to download everything but have maildir folders for imap users who keep things on the server.
what about pop users who keep the mail on the server? than you have the same as an imap user.
No, the inefficient operations on mbox files are where you move things into other folders or delete some messages from the middle. Pop users don't do those things on the server. Besides, I think the only reason anyone ever sets their pop client to leave messages on my server is that they check mail from more than one location, but their 'main' computer will delete when it downloads.
-- Les Mikesell lesmikesell@gmail.com
participants (4)
-
Jakob Hirsch
-
Les Mikesell
-
Marcus Rueckert
-
Marilyn Davis