Re: [Dovecot] High CPU utilization on Solaris 10

2007-08-17 Thread Tan Shao Yi


On Thu, 16 Aug 2007, Jon Alessandrello wrote:


It is putting me in an infinite loop:



truss -p 548

pollsys(0xFFBFF5B8, 5, 0xFFBFF548, 0x)  = 0
pollsys(0xFFBFF5B8, 5, 0xFFBFF548, 0x)  = 0


Hi Jon,

I'm on Solaris 10 SPARC (11/06) too but I don't seem to experiencing this. 
Did you compile yours using gcc?


Cheers.




[Dovecot] Recover mailboxes

2007-08-17 Thread Jordi Espasa Clofent

HI all,

Some time ago I've [EMAIL PROTECTED] in maildir mailbox with their own 
mails, their folders, subfolders, indexes files.. etc


My server was missconfigured and I've rebuilded all SMTP; I've recreated 
all the mailboxes with same names that before. Of course, the problem is 
the content of these mailboxes it's not the same. So, the idea is:


add all the contento from [EMAIL PROTECTED] (old) mailbox to 
[EMAIL PROTECTED] (new) mailbox.


because I have got a complete copy of (old) mailboxes and their content.

¿How can I do it?


Re: [Dovecot] MANAGESIEVE patch v6 for dovecot 1.0.3

2007-08-17 Thread Robin Breathe
Stephan Bosch wrote:
> I have updated the MANAGESIEVE patch to (hopefully) fix the compilation
> issues reported by Robin Breathe. This is a patch against the latest
> stable release 1.0.3. It currently won't compile with 1.1 due to
> significant changes in the master code.  

I can confirm that it's now compiling fairly cleanly with Sun CC under
Solaris 10 again, thanks.

> Change Log V6
> -
> 
> - Corked the client output stream while producing the capability greeting and 
> on
>   other some other occasions as well. Some naive client implementations 
> expect to
>   receive this as a single tcp frame and it is a good practice to do so 
> anyway.
>   Using this change the Thunderbird sieve extension (v0.1.1) seemed to work. 
> However,
>   scripts larger than a tcp frame still caused failures. All these issues are 
> fixed
>   in the latest version of the sieve add-on (currently v0.1.4).

Should the current incarnation of the patch support TLS, or is there
anything I need to do to enable TLS for managesieve; the Thunderbird
Sieve extension hangs when "Use TLS" option is selected. Configuration
below:

# ./dovecot -n
# 1.0.3: /app/dovecot/1.0.3-managesieve/etc/dovecot.conf
base_dir: /dovecot/run-managesieve/
protocols: managesieve
listen: imap.brookes.ac.uk:12000
ssl_cert_file: /app/openssl/certs/public/dovecot.pem
disable_plaintext_auth: no
login_dir: /dovecot/run-managesieve/login
login_executable:
/app/dovecot/1.0.3-managesieve/libexec/dovecot/managesieve-login
login_processes_count: 16
login_max_processes_count: 512
max_mail_processes: 8192
verbose_proctitle: yes
first_valid_uid: 900
first_valid_gid: 10
mail_location:
maildir:%h/Maildir:INDEX=/dovecot/index/%u:CONTROL=/dovecot/control/%u
mail_debug: yes
mail_executable: /app/dovecot/1.0.3-managesieve/libexec/dovecot/managesieve
mail_plugin_dir: /app/dovecot/1.0.3-managesieve/lib/dovecot/managesieve
namespace:
  type: private
  inbox: yes
auth default:
  cache_size: 8192
  verbose: yes
  debug: yes
  passdb:
driver: pam
args: cache_key=%u%r%l%s dovecot
  userdb:
driver: passwd
plugin:
  quota: fs

Regards,
Robin


Re: [Dovecot] Sieve Vacation cause deliver to die

2007-08-17 Thread Steffen Kaiser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 17 Aug 2007, M1 wrote:


# Sieve Filter
# 由 Ingo (http://www.horde.org/ingo/) 產生 (August 15, 2007, 10:49 am)

require "vacation";

# 假期通知
if allof ( not exists ["list-help", "list-unsubscribe", "list-subscribe",
"list-owner", "list-post", "list-archive", "list-id"], not header
:comparator "i;ascii-casemap" :is "Precedence" "list,bulk" ) {
  vacation :days 7 :addresses "[EMAIL PROTECTED]" :subject "test" "test
vacation";
}


This script works on Dovecot v1.0.3 on Linux.

Did you forced a re-compile of the script already?

Bye,

- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBRsWBCy9SORjhbDpvAQKcegf/f6om8HcDzxrqogOduZ0uhf2M311mTqND
PLotOFDFHimERRoAVdf1wMMAvlWfyO/x8ocnhlwb3eR5HLQbvpBp3uftru5Ie8cz
N4jYhFDoEtKXbYd7R23krC7GzcqZbkGyYNrWgeUbaSxrgrkgthamGUhtA6nKoQKN
/c787cQrFtHzmirE6SZSDSylhBzvJ0eezXUPOF9rePAlrvzwVx1ixMt3KP7dreBT
ag2IwnY+3cnquO+DX5ZvOQWJ0TUTx8XYoJsbhTAKXN5heyC7WEKmw+9WIvQLNgqh
hEoSlw+9hwtKm/GxhnXB1F9Zg+h31EAS+/9FQxWUR9mevzL/mr0Xuw==
=Py/G
-END PGP SIGNATURE-

[Dovecot] dovecot notifying a database about total number of messages.

2007-08-17 Thread Erland Nylend
Hello,

in addition to our mail system, we have some other systems which
needs to know how many messages, and how many unread messages, a
user has in his/her inbox (maildir).

Currently, we have a mod_perl script which takes a mail address as
input, and then traverses the maildir, and outputs the number of
unread messages.

Our challenge is that the maildirs are located on a SAN, and
traversing a maildir is slow. We currently have more than 100
requests pr. second, which we handle with caching, and spreading the
load across different servers.

I'm looking into the possibility of either using dovecots index
files, or having dovecot update a database with total number of
messages/number of unread messages.

Question: 

1) if I'm using perl, is there any way I can read in the information
in the index files? Is the data formatted in some standarized way,
so that I can parse it, or use a module which read in the data?

(if I can read the indexes in wrapper scripts to imap/pop/deliver,
then I could probably update a database with the information)

2) how would you proceed, if the aim is to end up with dovecot
notifying a database regarding the number of messages, and unread
messages?


-- 
Erland Nylend



Re: [Dovecot] dovecot notifying a database about total number of messages.

2007-08-17 Thread Timo Sirainen
On Fri, 2007-08-17 at 13:33 +0200, Erland Nylend wrote:
> 1) if I'm using perl, is there any way I can read in the information
> in the index files? Is the data formatted in some standarized way,
> so that I can parse it, or use a module which read in the data?

With v1.0 it would be pretty easy, but v1.1 makes this more difficult
because it doesn't keep dovecot.index up-to-date all the time. Instead
you'd have to read dovecot.index and apply new changes from
dovecot.index.log.

> 2) how would you proceed, if the aim is to end up with dovecot
> notifying a database regarding the number of messages, and unread
> messages?

Create a plugin which overrides mail_storage.sync_deinit(). Quota plugin
could be used as an example:

static int quota_mailbox_sync_deinit(struct mailbox_sync_context *ctx,
 enum mailbox_status_items status_items,
 struct mailbox_status *status_r)
{
struct quota_mailbox *qbox = QUOTA_CONTEXT(ctx->box);

/* just in case sync_notify() wasn't called with uid=0 */
quota_mailbox_sync_finish(qbox);

return qbox->module_ctx.super.sync_deinit(ctx, status_items, status_r);
}

Call super.sync_deinit() with status_items having STATUS_UNREAD.
status_r->unseen then contains the unseen counter.

If you want to avoid useless database updates, you could call
mailbox_get_status() in sync_init() and save the unseen count there, and
then compare in sync_deinit() if it got changed.


signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] imap killed with signal 6 (including backtrace)

2007-08-17 Thread Ralf Hildebrandt
* Ralf Hildebrandt <[EMAIL PROTECTED]>:

> > http://hg.dovecot.org/dovecot-1.0/rev/33690bb286af probably fixes it
> 
> Nope, I did a hg pull yesterday and restarted dovecot.

Maybe it worked, since I see that particular User NOT getting the
errors anymore.


Re: [Dovecot] mail_location ?

2007-08-17 Thread Yu Chen

Yu Chen spake the following on 8/16/2007 10:41 AM:

Hi, my mail server is running fine. But not sure if I am doing right
with "mail_location" in dovecot.conf

I am using dovecot-1.0.0-8_56 on RHEL AS 4 Update 5.
Our users have a "mail" directory under their home directory(~/mail). I
thought the "mail_location" line should be:

mail_location =
mbox:%h/mail:INBOX=/var/mail/%u:INDEX=/var/mail_indexes/%d/%n

but if I do this, all the mailboxes in the "mail" directory won't show,
and a new "mail" folder will be created under "~/mail/", so it is
"~/mail/mail" now.

if I change it to this:

mail_location = mbox:%h:INBOX=/var/mail/%u:INDEX=/var/mail_indexes/%d/%n

Everything is fine, is this the supposed behavior?


Do your clients have a mail directory configured in them like ~/mail? It was a
common practice on older systems using other imap servers.



Yes, that is it. Thanks.

CY







===
Yu Chen
Howard Hughes Medical Institute
Chemistry Building, Rm 182
University of Maryland at Baltimore County
1000 Hilltop Circle
Baltimore, MD 21250

phone:  (410)455-6347 (primary)
(410)455-2718 (secondary)
fax:(410)455-1174
email:  [EMAIL PROTECTED]
===


Re: [Dovecot] MANAGESIEVE patch v6 for dovecot 1.0.3

2007-08-17 Thread Stephan Bosch
On Fri, 2007-08-17 at 11:56 +0100, Robin Breathe wrote:
> Stephan Bosch wrote:
> > I have updated the MANAGESIEVE patch to (hopefully) fix the compilation
> > issues reported by Robin Breathe. This is a patch against the latest
> > stable release 1.0.3. It currently won't compile with 1.1 due to
> > significant changes in the master code.  
> 
> I can confirm that it's now compiling fairly cleanly with Sun CC under
> Solaris 10 again, thanks.
Nice.

> Should the current incarnation of the patch support TLS, or is there
> anything I need to do to enable TLS for managesieve; the Thunderbird
> Sieve extension hangs when "Use TLS" option is selected. 
Yes, it should. I'll have a look at the sieve extension's TLS support
this evening (i didn't know it supported TLS already). I re-tested the
TLS support of the managesieve patch v6 at my end and it still works. 

You could test it yourself using the method I described earlier:

http://dovecot.org/list/dovecot/2007-August/024470.html

Last time I forgot to mention that the second parameter to the
authenticate "plain" should be a bese64-encoded version of a string
"\0username\0password" (http://www.ietf.org/rfc/rfc4616.txt). The
following script should for example do the trick if your username would
be breathe with password hutsefluts:

#!/usr/bin/perl
use MIME::Base64 ();
print MIME::Base64::encode("\0breathe\0hutsefluts");

This produces 'AGJyZWF0aGUAaHV0c2VmbHV0cw==' and thus you would send the
following command after TLS negotiation:

AUTHENTICATE "PLAIN" "AGJyZWF0aGUAaHV0c2VmbHV0cw=="

Please let me know when problems occur. Include any log lines that might
be of interest. 

Regards,

Stephan. 




Re: [Dovecot] imap memory footprint rather large

2007-08-17 Thread Leroy van Logchem



I found the file to be ever growing, so when it had grown back to
160Mb in a single day, I decided to employ cron on the mail server:

  11 4 * * * find $HOME/.maildir -type f -name dovecot.index.cache -exec rm {} 
\;

Since my mail is fetched in the background anyway, I am happy to
take the performance hit first thing in the morning.
  


I'm wondering, can this be done safely with connected users?

--
Leroy






Re: [Dovecot] Dovecot IMAP/POP3 Proxy with LDAP

2007-08-17 Thread Raphael Bittencourt S. Costa
I made some progress, but it still don't connect to the server. See
below:

Aug 17 09:22:29 bastion01 dovecot: auth(default): client in: AUTH  1
PLAIN   service=POP3lip=10.0.2.1rip=10.0.1.1
resp=AHJhcGhhZWwuY29zdGFAYmlnaG9zdxsdC5jb20uYnIAMTIzcXdl

Aug 17 09:22:29 bastion01 dovecot: auth(default):
ldap([EMAIL PROTECTED],10.0.1.1): bind search:
base=ou=.com.br,ou=accounts,o=comMail
filter=(&(objectClass=qmailUser)([EMAIL PROTECTED])(accountStatus=active))

Aug 17 09:22:29 bastion01 dovecot: auth(default):
ldap([EMAIL PROTECTED],10.0.1.1): result: qmailUID(proxy)=1033
mailHost(host)=mailserver-01..com.br
uid(user)[EMAIL PROTECTED]

Aug 17 09:22:29 bastion01 dovecot: auth(default):
ldap([EMAIL PROTECTED],10.0.1.1): bind:
dn=cn=raphael.costa,ou=.com.br,ou=accounts,o=comMail

Aug 17 09:22:29 bastion01 dovecot: auth(default): client out: OK
1   [EMAIL PROTECTED]   proxy
host=mailserver-01..com.br  pass=

Aug 17 09:22:29 bastion01 dovecot: auth(default): master in: REQUEST
1   18709   1

Aug 17 09:22:29 bastion01 dovecot: auth(default): Master request 18709.1
not found

Aug 17 09:22:29 bastion01 dovecot: auth(default): master out: NOTFOUND
1

Aug 17 09:22:29 bastion01 dovecot: pop3-login: Internal login failure:
user=<[EMAIL PROTECTED]>, method=PLAIN, rip=10.0.1.1,
lip=10.0.2.1


any idea?



On Thu, 2007-08-16 at 18:58 -0300, Raphael Bittencourt S. Costa wrote:
> Hello all,
> 
> I'm having problems to make Dovecot proxy work, I configured it
> following dovecot's site. See my test below:
> 
> It accepts login and password and then closes the connection.
> 
> bastion01:~/build# telnet localhost 110
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> +OK Dovecot ready.
> user [EMAIL PROTECTED]
> +OK
> pass xx
> +OK Logged in.
> Connection closed by foreign host.
> 
> 
> See that it get the host information but still try to access the mbox
> locally.
> 
> Aug 16 16:22:36 bastion01 dovecot: auth(default):
> ldap([EMAIL PROTECTED],127.0.0.1): bind:
> dn=cn=raphael.costa,ou=.com.br,ou=accounts,o=comMail
> Aug 16 16:22:36 bastion01 dovecot: auth(default): client out: OK
> 2   [EMAIL PROTECTED]
> host=mailserver-01..com.br
> Aug 16 16:22:36 bastion01 dovecot: auth(default): master in: REQUEST
> 1   38942
> 
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> maildir: access(/dev/null/Maildir, rwx): failed: Not a directory
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> maildir: couldn't find root dir
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> mbox: root: access(/dev/null/mail, rwx) failed: Not a directory
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> mbox: root: access(/dev/null/Mail, rwx) failed: Not a directory
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> mbox: checking if we are chrooted:
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> mbox autodetect: data=
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> mbox autodetect: has .imap/: stat(/.imap) failed: No such file or
> directory
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> mbox autodetect: has inbox: stat(/inbox) failed: No such file or
> directory
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> mbox autodetect: has mbox: stat(/mbox) failed: No such file or
> directory
> Aug 16 16:22:36 bastion01 dovecot: POP3([EMAIL PROTECTED]):
> mbox: root mail directory not found
> 
> 
> 
> My dovecot-ldap.conf:
> pass_attrs =
> uid=user,userPassword=password,mailMessageStore=userdb_home,qmailUID=userdb_uid,qmailGID=userdb_gid,proxy,mailHost=host
> 
> 
> What am I doing wrong?
> 
> 
> Raphael Costa



[Dovecot] High CPU utilization on Solaris 10

2007-08-17 Thread instigatetrouble
Yes, I compiled with gcc (GCC) 3.4.6 from sunfreeware.

-Jon



Re: [Dovecot] MANAGESIEVE patch v6 for dovecot 1.0.3

2007-08-17 Thread Steffen Kaiser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, 16 Aug 2007, Stephan Bosch wrote:


I have updated the MANAGESIEVE patch to (hopefully) fix the compilation
issues reported by Robin Breathe. This is a patch against the latest
stable release 1.0.3. It currently won't compile with 1.1 due to


I have the problem that, if I do not explicitly set

login_dir = /var/run/dovecot/login

Managesieve-login dies with:
dovecot: Aug 17 16:01:18 Error: managesieve-login: chroot(login) failed: 
No such file or directory
dovecot: Aug 17 16:01:18 Error: managesieve-login: chroot(login) failed: 
No such file or directory
dovecot: Aug 17 16:01:18 Error: managesieve-login: chroot(login) failed: 
No such file or directory

dovecot: Aug 17 16:01:18 Error: child 11480 (login) returned error 89
dovecot: Aug 17 16:01:18 Error: child 11481 (login) returned error 89
dovecot: Aug 17 16:01:18 Error: child 11482 (login) returned error 89

There is the default run-directory missing, I guess. If I start the 
command from command line, it uses 
/usr/local/dovecot-1.0.3/var/run/dovecot/login - however the base 
directory does not exists.


I did not explicitly assigned login_dir in the .conf:

Some settings of dovecot -n

# 1.0.3: /usr/local/dovecot-1.0.3/etc/dovecot.conf
base_dir: /var/run/dovecot/
log_path: /var/log/dovecot/dovecot.log
protocols: imap imaps pop3 pop3s managesieve
login_dir(default): /var/run/dovecot//login
login_dir(imap): /var/run/dovecot//login
login_dir(pop3): /var/run/dovecot//login
login_dir(managesieve): /var/run/dovecot/login
Note the difference of the last two lines (double slash)!

Secondly, I suggest to add to the README.managesieve, that the server is 
using the CONTROL= directory to store the sieve scripts and that you can 
set mail_location= to change that, e.g.:


protocol managesieve {
# Without the login_dir managesieve-login fails to start up
login_dir = /var/run/dovecot/login
listen = *:2000
# Otherwise the Sieve scripts would be placed into the CONTROL= dir
mail_location = maildir:%h/Maildir
}

Bye.

- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBRsWs1C9SORjhbDpvAQKAagf/YQta9xt1iEdzZDL+eUjEsVWX6uWwjFkC
Ge8AH85u4AOghBS8GrsVGPTyAGJP7T+wtwLjiPZI+/PVkWnQkVNYcOfMAmQRzcWl
vHhWhWgMKCHpZGsRrnmK+IzjK9IYSqQ9ApR5V7YXDHWfag6dhmvUjL4sD287o9EJ
Ssl/KkpZ1c3HPFp4GCxepxtoQXoTu9dl+wfUytYleKnh3kBN1zRy0nhxYzEsVkUO
B2aJzk0BoAy3DS5E2H3+clB1d013TzbjFotibmIs8kVzSsfkTkqlDPTxodjTUg2c
heV8S1ZQFq2+S50uvbCH7Lh4uaAEnr/9UKylqiOEtp1pcS9vMJUIXg==
=rgxC
-END PGP SIGNATURE-


Re: [Dovecot] MANAGESIEVE patch v6 for dovecot 1.0.3

2007-08-17 Thread Robin Breathe
Stephan Bosch wrote:
> On Fri, 2007-08-17 at 11:56 +0100, Robin Breathe wrote:
>> Should the current incarnation of the patch support TLS, or is there
>> anything I need to do to enable TLS for managesieve; the Thunderbird
>> Sieve extension hangs when "Use TLS" option is selected. 
> Yes, it should. I'll have a look at the sieve extension's TLS support
> this evening (i didn't know it supported TLS already). I re-tested the
> TLS support of the managesieve patch v6 at my end and it still works. 

I can confirm that TLS is working via gnutls-cli, so I guess the problem
must lie with the Sieve extension. Of note, we're using a non-standard
port (12000) and a chained, wildcard GlobalSign certificate.

Regards,
Robin


[Dovecot] Dovecot 1.0.3: LDA + quota plugin

2007-08-17 Thread Przemek Grądzki
I have problem with quota limit settings for "deliver" - global plugin
settings overrides userdb quota setting !!!
imap and pop3 works fine.
Quota limit for user is set to "quota=maildir:ignore=Kosz:storage=512".
And "maildirsize" file in user's mail_location contains "524288S" line -
good.
But when I set:

plugin {
  quota = maildir:ignore=Kosz:storage=102400
}

in "/etc/dovecot.conf",  quota limit is set to "104857600S" in "maildirsize"
file - BAD.

Local delivery is configured as in http://wiki.dovecot.org/LDA, quota plugin
is set in /etc/dovecot.conf:

protocol lda {
  ..
  mail_plugins = cmusieve quota
  #mail_plugin_dir = /usr/lib/dovecot/lda
  .
}

Per-user quota is configured like this (from LDAP):

user_attrs =
homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuotaSize=quota=maildir:ignore=Kosz:storage
pass_attrs =
uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid,mailQuotaSize
=userdb_quota=maildir:ignore=Kosz:storage

"mailQuotaSize" attribute contains quota limit in kilobytes.

/etc/dovecot.conf:

# 1.0.3: /etc/dovecot.conf
log_path: /dev/stderr
protocols: imap imaps pop3s managesieve
login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap-login
login_executable(imap): /usr/libexec/dovecot/imap-login
login_executable(pop3): /usr/libexec/dovecot/pop3-login
login_executable(managesieve): /usr/libexec/dovecot/managesieve-login
first_valid_uid: 8
first_valid_gid: 12
mail_location: maildir:%h/Maildir
mail_executable(default): /usr/libexec/dovecot/imap
mail_executable(imap): /usr/libexec/dovecot/imap
mail_executable(pop3): /usr/libexec/dovecot/pop3
mail_executable(managesieve): /usr/libexec/dovecot/managesieve
mail_plugins(default): quota imap_quota
mail_plugins(imap): quota imap_quota
mail_plugins(pop3): quota
mail_plugins(managesieve):
mail_plugin_dir(default): /usr/lib/dovecot/imap
mail_plugin_dir(imap): /usr/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/pop3
mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
pop3_client_workarounds(managesieve):
auth default:
  mechanisms: plain login gssapi
  passdb:
driver: ldap
args: /etc/dovecot-ldap.conf
  userdb:
driver: prefetch
  userdb:
driver: ldap
args: /etc/dovecot-ldap.conf
  socket:
type: listen
master:
  path: /var/run/dovecot/auth-master
  mode: 438
plugin:
  quota: maildir:ignore=Kosz:storage=102400
-

PS. Sorry for my english.


[Dovecot] Migrating from imapd to dovecot - how to keep user's Mail folders

2007-08-17 Thread Patrick - South Valley Internet

Hi all,

We're migrating off our current mail server with runs postfix and imapd 
on an AIX machine to Postfix and Dovecot running linux.  Our customers 
have a lot of IMAP folders with folders they configured, which are 
currently located in their /home directory on the current mail server.  
The new mail server will have them at the same location.


How do I configure Dovecot so that when a customer connects via IMAP 
using their favorite e-mail client, that the folders will be there?


Thanks in advance.

Patrick


Re: [Dovecot] MANAGESIEVE patch v6 for dovecot 1.0.3

2007-08-17 Thread Stephan Bosch

Hi,

Robin Breathe schreef:

 Stephan Bosch wrote:



> On Fri, 2007-08-17 at 11:56 +0100, Robin Breathe wrote:



>> Should the current incarnation of the patch support TLS,or is
>> there anything I need to do to enable TLS for managesieve;the
>> Thunderbird Sieve extension hangs when "Use TLS" option is
>> selected.
> Yes, it should. I'll have a look at the sieve extension's TLS
> support this evening (i didn't know it supported TLS already). I
> re-tested the TLS support of the managesieve patch v6 at my end and
> it still works
 I can confirm that TLS is working via gnutls-cli, so I guess the
 problem must lie with the Sieve extension. Of note, we're using a
 non-standard port (12000) and a chained, wildcard GlobalSign
 certificate.
Ok, I have the same problem here and as for KMail I decided to dive into 
the sourcecode of Thunderbird's Sieve extension.  The offending source 
code is the following 
(extensions/[EMAIL PROTECTED]/chrome/chromeFiles/content/editor/SieveFilterExplorer.js):


onStartTLSResponse : function(response)
{
   // activate TLS
  sieve.startTLS();

   // we should call now Capabilities ...
   // .. they can change with enabled TLS

   var request = new SieveCapabilitiesRequest();
   request.addCapabilitiesListener(event);
   request.addErrorListener(event);

   sieve.addRequest(request);
},

This method is called after the server gives an Ok response to the 
STARTTLS command. It starts the TLS negotiation and afterwards it sends 
a capability command. So, it seems like managesieve client implementors 
have a hard time reading the specification which clearly gives the 
following example (KMail had this problem as well):


C: StartTls
S: oK

S: "IMPLEMENTATION" "Example1 ManageSieved v001"
S: "SASL" "PLAIN DIGEST-MD5 GSSAPI"
S: "SIEVE" "FILEINTO VACATION"
S: ok

As you can see, the server is supposed to send the CAPABILITY reponse 
implicitly, just like when the client first connects. The Sieve 
extension for Thunderbird does not expect this implicit reponse and 
sends a CAPABILITY command to get the new capabilities. The unexpected  
data  causes the  sieve extension's connection attempt to freeze. The 
following log shows the sequence of commands:


Aug 18 00:14:29 xi dovecot: managesieve-login: managesieve: C: STARTTLS
Aug 18 00:14:31 xi dovecot: managesieve-login: managesieve: C: CAPABILITY
Aug 18 00:14:31 xi dovecot: managesieve-login: managesieve: C: AUTHENTICATE

I'll give it a try to fix it, but my Xul/JavaScript is a bit rusty. I'll 
pop the author an e-mail in either case.


Regards,

Stephan.















[Dovecot] MANAGESIEVE patch v7 for dovecot 1.0.3

2007-08-17 Thread Stephan Bosch

Hello dovecot users,

I have updated the MANAGESIEVE patch to fix a recently reported problem. 
This is a patch against the latest stable release 1.0.3. It currently 
won't compile with 1.1 due to significant changes in the master code.


Change Log V7
-

- Robin Breathe indicated that the regex capability was missing in the
  server's SIEVE listing. It turns out I forgot to make arrangements for
  setting ENABLE_REGEX in the cmu libsieve sources, so the regex
  extension was not compiled in. I copied the configure.in section
  regarding ENABLE_REGEX from dovecot-sieve-1.0.2 and that fixed the
  problem.

This patch still includes (yet another) instance of the CMU Sieve
source, as explained in one of my previous e-mails
(http://dovecot.org/list/dovecot/2006-July/015016.html).

The patch can be downloaded at:

http://sinas.rename-it.nl/~sirius/dovecot-1.0.3-MANAGESIEVE-v7.diff.gz

The README.managesieve is located in the root of the dovecot source tree
after applying the patch.

Have fun testing the patch. Don't hesitate to notify me when there are 
problems.


Regards,

--
Stephan Bosch
[EMAIL PROTECTED]
IRC: Freenode, #dovecot, S[r]us