On Sat, 2007-05-05 at 14:48 +0100, Adrian Barker wrote:
> That's right: we cannot change the way that we deliver email, at least
> in the short to medium term, so need to maintain compatibility with the
> UW IMAP server. If we do decide to write a plugin that copies new email
> from the mail spool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 8 May 2007, Chris Wakelin wrote:
Another thought occurred to me. It needn't be a plugin as such, as it
just needs to run before the imap process proper - see
Three reasons why this is not enough:
1) Long-time IMAP connections,
2) New mail
Adrian Barker wrote:
>
> That's right: we cannot change the way that we deliver email, at least
> in the short to medium term, so need to maintain compatibility with the
> UW IMAP server. If we do decide to write a plugin that copies new email
> from the mail spool to the IMAP inbox, is there any
Jonathan wrote:
> Kenny Dail wrote:
>
>>> Adrian Barker wrote:
>>> Thanks for replying. We cannot easily change the way we deliver email,
>>> as we have over 30,000 users, who use a mixture of imap, pop and Unix
>>> email clients, so we have to continue to deliver email to a central mail
>>> spool
Kenny Dail wrote:
Adrian Barker wrote:
Thanks for replying. We cannot easily change the way we deliver email,
as we have over 30,000 users, who use a mixture of imap, pop and Unix
email clients, so we have to continue to deliver email to a central mail
spool. The MTA that we run is Exim, which h
Quoting Chris Wakelin <[EMAIL PROTECTED]>:
I guess you're delivering mail to /var/mail/username, and UW-IMAP
"snarfs" (to use the UW term :)) the messages to ~/mbox (if it exists)
whenever the user opens INBOX in IMAP.
Yes, we used to do this also, but we stopped when we went to dovecot.
Sin
I guess you're delivering mail to /var/mail/username, and UW-IMAP
"snarfs" (to use the UW term :)) the messages to ~/mbox (if it exists)
whenever the user opens INBOX in IMAP.
If so, I guess the problem is the Unix file-system clients which expect
to see mail in /var/mail/username? Dovecot can do
> > Adrian Barker wrote:
> >> We are considering switching from the Washington UW IMAP server to
> >> Dovecot for performance reasons, but we make use of the feature in the
> >> UW server that automatically moves new email from the mail spool to the
> >> IMAP INBOX. Has anyone implemented this in D
Adrian Barker wrote:
Thanks for replying. We cannot easily change the way we deliver email,
as we have over 30,000 users, who use a mixture of imap, pop and Unix
email clients, so we have to continue to deliver email to a central mail
spool. The MTA that we run is Exim, which has the flexibility
Thanks for replying. We cannot easily change the way we deliver email,
as we have over 30,000 users, who use a mixture of imap, pop and Unix
email clients, so we have to continue to deliver email to a central mail
spool. The MTA that we run is Exim, which has the flexibility to deliver
into the '
Hi Adrian,
I'm thinking this is more of an issue with your MTA, as usually that's
responsible for delivering into the mailbox's Inbox.
You might want to look at Dovecot's LDA, "deliver"
(http://wiki.dovecot.org/LDA).
Deliver takes an e-mail piped from your MTA, with appropriate options on
th
We are considering switching from the Washington UW IMAP server to
Dovecot for performance reasons, but we make use of the feature in the
UW server that automatically moves new email from the mail spool to the
IMAP INBOX. Has anyone implemented this in Dovecot, or considered
implementing it ? We
12 matches
Mail list logo
