Hello Amon,
Amon Ott, 02.05.2007 (d.m.y):
> All our systems run ntpd, but they might be offline for a while before
> they get contact to a time server, e.g. because of DSL problems.
Define one of your "internal" systems as "master time server" that
connects to other NTP servers outside your ne
Ooooh !
Thanks, I have 250 users reading and sending emails on this server
Sophie
Charles Marcus a écrit :
Anyway, a better idea is upgrading to 1.0; dovecot 0.99 is really
old and
no longer supported.
:-\ I use the version including in my SL 4.4 distribution
I hope there's some RPM somewh
On Friday 04 May 2007 10:07, Christian Schmidt wrote:
> Hello Amon,
>
> Amon Ott, 02.05.2007 (d.m.y):
> > All our systems run ntpd, but they might be offline for a while
> > before they get contact to a time server, e.g. because of DSL
> > problems.
>
> Define one of your "internal" systems as "mas
Anyway, a better idea is upgrading to 1.0; dovecot 0.99 is really
old and no longer supported.
:-\ I use the version including in my SL 4.4 distribution
I hope there's some RPM somewhere for the 1.0
WARNING!
Be sure to read the update notes - the config file format has
changed between 0
Alexander Hoogerhuis wrote:
I am doing all of this on Gentoo, so I decided to just redo the ebuild
so that I got the dovecot 1.0.0 ebuild, but with the sieve plugin
1.0.1. Aparently I get the same error and now am at a loss here. Any
pointers?
Well immediate idea would be to work out exactly wh
James Turnbull wrote:
Alexander Hoogerhuis wrote:
I am doing all of this on Gentoo, so I decided to just redo the ebuild
so that I got the dovecot 1.0.0 ebuild, but with the sieve plugin
1.0.1. Aparently I get the same error and now am at a loss here. Any
pointers?
Well immediate idea would be
Hello Folks,
I've my dovecot working well and authenticating in my ldap servers.
But I'd like configure my users to authenticate in two ways. One is just
submitting the username and the other one is providing [EMAIL PROTECTED] .
I'm moving from a cyrus-imap solution to dovecot and I've
Friday 04 of May 2007 15:34:51 Venilton Junior napisał(a):
> Hello Folks,
>
>
>
> I've my dovecot working well and authenticating in my ldap servers.
>
>
>
> But I'd like configure my users to authenticate in two ways. One is just
> submitting the username and the other one is providing [EMAIL PROT
Tnx, it's working fine! :)
This option in my dovecot.conf worked for me!!
Regards,
Venilton C. Junior
HP Certified Professional
Sercompe Computadores Ltda.
Office: +55 47 3431-9700
Fax: +55 47 3431-9747
Mobile: +55 47 9653-5872
www.sercompe.com.br
-Original Message-
From: [EMAI
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
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
Hello,
How can I configure dovecot in order to allow subfolders on IMAP
directories ?
I dont find in the dovecot.conf file
Thanks
Sophie
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 '
After experiencing these symptoms through many of the release
candidates, we've been at v1.0.0 now for a few weeks, and they're still
there. Perhaps a config issue with my setup (mbox locks?). It's really
too disrupting to continue using this way. I've included symptoms,
client info, mta inf
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
> > 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
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
Hello All,
I have been still struggling with the read only maildir and
I think I found something:
dovecot wants to rename a file but
I/it have/has no rights to do that:
dovecot: 2007-05-04 21:30:14 Error: IMAP(bela):
rename(/home/store/oldmails/.personal/cur/1154939281.5.pc1.S=1879:2,S,
/
I think the main question is, why do you have/want a read-only maildir?
By definition a maildir is constantly changing. In your case, dovecot
was trying to class a new e-mail as "read", hence the move from "new" to
"cur." Other ways in which a maildir changes, is the changing of the
message
Hi,
I have around 100 mailboxes (maildirs) to convert from Courier IMAP
(4.1.3) to Dovecot.
(From a recent backup) I've tested a few mailboxes on Dovecot 1.0.0, and
while the client doesn't notice any difference (at least in Thunderbird)
I'm hoping to get rid of the old Courier folders and c
Hello,
Thanks for your reply.
I have some read only maildirs outside my home.
Actually those files and directories does not belong to
me, I am only a member of the group which can read those
files and change to those directories.
This is a bit overworried security:
not to loose any data by accid
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
On Fri, 04 May 2007 09:23:02 -0700
Danno Coppock <[EMAIL PROTECTED]> wrote:
> After experiencing these symptoms through many of the release
> candidates, we've been at v1.0.0 now for a few weeks, and they're
> still there. Perhaps a config issue with my setup (mbox locks?).
> It's really too dis
I believe that there is one more patch required for a successful build
on Tru64:
# diff ./src/lib/mountpoint.c.orig ./src/lib/mountpoint.c
60a61,63
> #ifdef __osf__
> point_r->type = p_strdup(pool, getvfsbynumber(buf.f_type));
> #else
62c65,66
< point_r->block_size = buf.f_bsize;
---
On 5/4/07, Andy Shellam <[EMAIL PROTECTED]> wrote:
If I can't salvage anything useful, is there any adverse effects to me
deleting all the "courier*" files/folders from each mailbox and
subfolders so when the client connects back when Dovecot's running, it
creates it's own UIDs and keywords etc
25 matches
Mail list logo
