Re: [Dovecot] v1.1 status and benchmarks

[Arkadiusz Miskiewicz]

On Thursday 12 of July 2007, Timo Sirainen wrote:
> v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to
> have a stable v1.1 in a month or two. The rest of the features that
> didn't make it into v1.1 will go to v1.2. I'll write more about this
> when v1.1 alpha is released.
>
> I also did a bit of benchmarking. v1.1's performance improvements are
> looking pretty great, it seems to be twice as fast as v1.0.

Could you somehow test system usage resources, too? That will be probably 
problematic to measure.

For example being twice fast and eating four time more resources isn't a great 
win. That bit me when I wanted to switch from tpop3d to dovecot for pop3 
(already done similar switch for imap). It looks like dovecot does much more 
I/O (even when delivery is used at MTA level so indexes are available) which 
caused huge problems (unsolved unfortunately).
-- 
Arkadiusz MiśkiewiczPLD/Linux Team
arekm / maven.plhttp://ftp.pld-linux.org/

Re: [Dovecot] v1.0.2 release candidate

[Timo Sirainen]

On 12.7.2007, at 9.47, Tan Shao Yi wrote:

Just a quick check, if a round-robin hostname was specified in the  
hosts key/value pair in dovecot-ldap.conf, will dovecot round-robin  
LDAP queries among the IPs?


Dovecot doesn't even try to parse the hosts setting. it just passes  
it to LDAP library.




PGP.sig
Description: This is a digitally signed message part

Re: [Dovecot] v1.1 status and benchmarks

[Timo Sirainen]

On 12.7.2007, at 10.07, Arkadiusz Miskiewicz wrote:


I also did a bit of benchmarking. v1.1's performance improvements are
looking pretty great, it seems to be twice as fast as v1.0.


Could you somehow test system usage resources, too? That will be  
probably

problematic to measure.


It is problematic to measure. Feel free to figure out how to do that. :)

For example being twice fast and eating four time more resources  
isn't a great
win. That bit me when I wanted to switch from tpop3d to dovecot for  
pop3
(already done similar switch for imap). It looks like dovecot does  
much more
I/O (even when delivery is used at MTA level so indexes are  
available) which

caused huge problems (unsolved unfortunately).


Yes, Dovecot's hasn't been a very good POP3 server. With v1.1 there  
are several improvements that should make it a lot better, although  
maybe still not perfect.


Although I'm guessing your "much more I/O" means that Dovecot reads  
the message contents to calculate the messages' correct virtual size,  
while tpop3d violates POP3 spec by returning physical message sizes.  
Also Dovecot 1.0's deliver doesn't help with this, because it doesn't  
write the virtual size to cache file.


PGP.sig
Description: This is a digitally signed message part

Re: [Dovecot] v1.1 status and benchmarks

[Arkadiusz Miskiewicz]

On Thursday 12 of July 2007, Timo Sirainen wrote:

> > For example being twice fast and eating four time more resources
> > isn't a great
> > win. That bit me when I wanted to switch from tpop3d to dovecot for
> > pop3
> > (already done similar switch for imap). It looks like dovecot does
> > much more
> > I/O (even when delivery is used at MTA level so indexes are
> > available) which
> > caused huge problems (unsolved unfortunately).
>
> Yes, Dovecot's hasn't been a very good POP3 server. With v1.1 there
> are several improvements that should make it a lot better, although
> maybe still not perfect.
>
> Although I'm guessing your "much more I/O" means that Dovecot reads
> the message contents to calculate the messages' correct virtual size,
> while tpop3d violates POP3 spec by returning physical message sizes.
> Also Dovecot 1.0's deliver doesn't help with this, because it doesn't
> write the virtual size to cache file.

Is this improved in 1.1 so virtual size is stored there?

-- 
Arkadiusz MiśkiewiczPLD/Linux Team
arekm / maven.plhttp://ftp.pld-linux.org/

Re: [Dovecot] v1.1 status and benchmarks

[Timo Sirainen]

On 12.7.2007, at 10.22, Arkadiusz Miskiewicz wrote:


Although I'm guessing your "much more I/O" means that Dovecot reads
the message contents to calculate the messages' correct virtual size,
while tpop3d violates POP3 spec by returning physical message sizes.
Also Dovecot 1.0's deliver doesn't help with this, because it doesn't
write the virtual size to cache file.


Is this improved in 1.1 so virtual size is stored there?


v1.1 stores the virtual size to the maildir filename (,W=1234) and  
for existing files it adds them to dovecot-uidlist. If only POP3 is  
used, the cache file isn't created at all. If IMAP is used then  
virtual size is stored also to the cache file.




PGP.sig
Description: This is a digitally signed message part

Re: [Dovecot] 1.0.1: corrupt index on fresh mailbox, ideas?

[Chris Laif]

On 7/12/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:

On Wed, 2007-07-11 at 15:18 +0200, Chris Laif wrote:
> On 7/10/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:
> > On Mon, 2007-07-09 at 11:45 -0700, Troy Engel wrote:
> > > dovecot: Jul 09 09:38:54 Error: IMAP(xxx): Maildir
> > > /home/x/xxx/Maildir sync: UIDVALIDITY changed (1183406107 -> 
1183999134)
> >
> > Fixed: http://hg.dovecot.org/dovecot-1.0/rev/90ea01bfaf82
> >
>
> Thanks. I applied this patch to 1.0.1 and after some hours I got:
>
> Error: IMAP(box1909): file maildir-uidlist.c: line 979
> (maildir_uidlist_sync_deinit): assertion failed:
> (ctx->uidlist->uid_validity != 0)

How about this then: http://hg.dovecot.org/dovecot-1.0/rev/b6753fd66298



Ok, thank you for your quick response. Patch applied. Let's wait and see :)

Chris

Re: [Dovecot] v1.1 status and benchmarks

[DINH Viêt Hoà]

On 7/12/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to
have a stable v1.1 in a month or two. The rest of the features that
didn't make it into v1.1 will go to v1.2. I'll write more about this
when v1.1 alpha is released.

I also did a bit of benchmarking. v1.1's performance improvements are
looking pretty great, it seems to be twice as fast as v1.0.

v1.0: Maildir, dovecot-1.0 hg + inotify dotlock wait patch, mmap_disable=yes
v1.1: Maildir, dovecot hg, mmap_disable=no
cydir: Cydir, dovecot hg, mmap_disable=no


is dovecot+cydir as fast as native Cyrus-IMAP ?

--
DINH Viêt Hoà

Re: [Dovecot] v1.1 status and benchmarks

[Arkadiusz Miskiewicz]

On Thursday 12 of July 2007, Timo Sirainen wrote:
> On 12.7.2007, at 10.22, Arkadiusz Miskiewicz wrote:
> >> Although I'm guessing your "much more I/O" means that Dovecot reads
> >> the message contents to calculate the messages' correct virtual size,
> >> while tpop3d violates POP3 spec by returning physical message sizes.
> >> Also Dovecot 1.0's deliver doesn't help with this, because it doesn't
> >> write the virtual size to cache file.
> >
> > Is this improved in 1.1 so virtual size is stored there?
>
> v1.1 stores the virtual size to the maildir filename (,W=1234) and
> for existing files it adds them to dovecot-uidlist. 

Great.

> If only POP3 is 
> used, the cache file isn't created at all. If IMAP is used then
> virtual size is stored also to the cache file.

Hm, http://wiki.dovecot.org/POP3Server doesn't mention anything about cache 
not being created. It even says that dovecot.index.cache  is actually used 
and updated.

Is it used (including updates) when and only when if it's created earlier by 
imap?

-- 
Arkadiusz MiśkiewiczPLD/Linux Team
arekm / maven.plhttp://ftp.pld-linux.org/

Re: [Dovecot] NFS cache flush tester

[Cor Bosman]

> Running rpc.lockd and rpc.statd on FreeBSD 6.2-STABLE #17: Sun Jun 24 
> 22:11:00 EDT 2007
> with a NetApp filer as the server, ran 3 times and compared output (same):
> 

Weird, I have the exact same setup and for me this program hangs, and I have
to kill lockd.

Cor

[Dovecot] Today's stable hg pull destroyed dovecot...

[Ralf Hildebrandt]

I performed a hg pull today for 1.0.1 and after recompilation my log
was flooded with:

Jul 12 10:29:21 postamt dovecot: IMAP(kxx4): UID larger than next_uid in file 
/home/k/j/kxx4/Maildir/dovecot-uidlist (6 >= 0)
Jul 12 10:29:21 postamt dovecot: IMAP(rexxxes): UID larger than next_uid in 
file /home/r/e/rexxxes/Maildir/dovecot-uidlist (1 >= 0)
Jul 12 10:29:21 postamt dovecot: IMAP(sxxkim): Maildir /home/s/i/sxxkim/Maildir 
sync: UIDVALIDITY changed (1184228955 -> 3086699759)

and people were reporting "the IMAP server closing and dropping connections".

I then downloaded 1.0.1 from the webpage, rebuilt and the problems
are gone.

Now I'm getting those:
Jul 12 10:33:10 postamt dovecot: IMAP(blxxe): Corrupted index cache file 
/home/b/l/blxxe/Maildir/dovecot.index.cache: indexid changed

Somethin amiss with the index code?

-- 
Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED]
Postfix - Einrichtung, Betrieb und Wartung   Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
Those who would give up essential liberty to purchase a little temporary
safety deserve neither liberty nor safety.-- Benjamin Franklin, 1759

[Dovecot] Patches to log imap bandwidth?

[Jason Fesler]

Anyone patch dovecot to syslog bytes transfered during a session or 
anything of that sort?  I'm trying to track down imap bandwidth spikes, 
and unfortunately the uid (according to ipfw) for the imap port spikes is 0.
(Presumably FreeBSD's ipfw accounting is based on who started the app 
instead of the effective user id?)


--
 Jason Fesler, email/jabber <[EMAIL PROTECTED]> resume: http://jfesler.com
 "Give a man fire, and he'll be warm for a day;
 set a man on fire, and he'll be warm for the rest of his life."

Re: [Dovecot] ssh tunneling and maildir

[Johannes Berg]

On Wed, 2007-07-11 at 08:57 -0700, Joel Becker wrote:

>   Ok.  How do I configure it if I cannot modify /etc?

Ah, good question.

> /usr/sbin/dovecot -c /home/jlbec/.dovecotrc

Sounds good.

> .  I also assume I need -F to
> run it as a foreground process?

No, with --exec-mail imap it automatically runs in the foreground

>   Will I need any auth?  I don't right
> now?

No, with --exec-mail imap it gives you a preauth imap session.

johannes


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

Re: [Dovecot] v1.0.2 release candidate

[Nicolas STRANSKY]

Le 12.07.2007 03:38, Timo Sirainen a écrit :
> http://dovecot.org/tmp/dovecot-1.0.2-rc.tar.gz
> 
> Unless someone finds something broken, I'll release v1.0.2 in a few
> days. The most important changes since v1.0.1:

Hello,

Is there any plan to add rquotad support in v1.0.2 or to release a
changeset that can be applied to v1.0.2 ?
Thanks a lot,

-- 
Nico
Comme toute science, la mathématique ne peut être construite sur la
seule logique.
-+- David Hilbert, Les fondements des mathématiques -+-

Re: [Dovecot] dovecot-dspam plugin & virtual users

[Johannes Berg]

Hi Wicher,

[now I know who it was on jabber. heh]

> I'm trying to use the dovecot-dspam plugin (
> http://johannes.sipsolutions.net/Projects/dovecot-dspam-integration )
> with vpopmail's virtual users.
> All seems well, except for the fact that dspam should be called with
> '--user [EMAIL PROTECTED]' at line 157 here:
> http://johannes.sipsolutions.net/Projects/dovecot-dspam-integration/beta7-code
> 
> For my needs, '[EMAIL PROTECTED]' could be taken as the login
> name I use for logging in to Dovecot. As I'm not a C-programmer by a
> long shot, I was wondering if one of you could help me use the
> bincimap-API to import the login name into a variable so I can use
> that variable to construct a suitable dspam-command. Hope this is
> possible!

Why the bincimap API? The login name from dovecot should already be
available in the USER variable or such.

johannes


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

[Dovecot] Dovecot login failing

[Richard Ellis]

Fedora 7
Dovecot version 1.0.1

Hi All,

I've been using a combination of getmail/Dovecot/Squirrelmail for a while
now and its all been fine. However, last week when trying to demonstrate how
to use Squirrelmail to my wife, her login failed. I then tried mine, which I
had used many times before and it also fails.

Looking in the logs, Dovecot appears to be trying to add a domain name
against the login, instead of just checking that user against the UNIX
logins of my machine. I thought at first this was because when I'm away from
home, I use a no-ip address to access my mailserver, but it also fails when
I'm in the house, or even on the server console.

dovecot: Jul 12 12:04:56 Info: imap-login: Aborted login: user=<
[EMAIL PROTECTED]>, method=PLAIN, rip=:::127.0.0.1, lip=:::
127.0.0.1, secured
dovecot: Jul 12 12:10:00 Info: pop3-login: Login: user=, method=PLAIN,
rip=:::127.0.0.1, lip=:::127.0.0.1, secured

Anybody any idea how to rectify this? I can't see an option in the
/etc/dovecot.conf file to stop it and using auth_default_realm =
doesn't seem to make any difference. If I telnet into dovecot using my local
username and password, it works fine.

Any advice would be most welcome before I break it fiddling.

Thanks

Rik


--
The Truth is out there, does anyone have the URL?

Re: [Dovecot] v1.1 status and benchmarks

[Farkas Levente]

Timo Sirainen wrote:
> v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to
> have a stable v1.1 in a month or two. The rest of the features that
> didn't make it into v1.1 will go to v1.2. I'll write more about this
> when v1.1 alpha is released.
> 
> I also did a bit of benchmarking. v1.1's performance improvements are
> looking pretty great, it seems to be twice as fast as v1.0.
> 
> v1.0: Maildir, dovecot-1.0 hg + inotify dotlock wait patch, mmap_disable=yes
> v1.1: Maildir, dovecot hg, mmap_disable=no
> cydir: Cydir, dovecot hg, mmap_disable=no
> 
> 1 client
> 
> 
> ./imaptest logout=0 seed=1 secs=10 clients=1
>   Logi List Stat Sele Fetc  Fet2 Stor Dele Expu Appe 
>   100%  50%  50% 100% 100%  100%  50% 100% 100% 100% 
>30%  5% 
> v1.0:1 1221 11791 2420  3458  323 1934 2419 2552 
> v1.1:1 2606 25971 5221  7352  688 4181 5221 5489 
> cydir:   1 4495 45341 8960 12786 1216 7224 8959 9434 
> 
> 10 clients
> --
> 
> ./imaptest logout=0 seed=1 secs=10 clients=10
>   Logi List Stat Sele  Fetc  Fet2 Stor  Dele  Expu  Appe 
>   100%  50%  50% 100%  100%  100%  50%  100%  100%  100% 
>   30% 5% 
> v1.0:   10 2058 2102   10  4157  6019 1426  3348  4157  4391 
> v1.1:   10 5029 5072   10 10064 14352 3176  8092 10064 10624 
> cydir:  10 6332 6393   10 12664 17965 3958 10154 12663 13336 

what is cydir? dovecot suppurt cydir format or it's cyrus speed?
if it's dovecot cydir support so fast will the v.x.y be ever so fast? or
it'd be better to use/switch to cydir?
is there any converter script?


-- 
  Levente   "Si vis pacem para bellum!"

Re: [Dovecot] NFS cache flush tester

[Chris Wakelin]

Timo Sirainen wrote:
> http://dovecot.org/tools/nfstest.c
> 
> I wrote a test utility that tests different ways to flush NFS attribute
> cache and data cache. Please test in your NFS setup and show me the
> results, so I can make Dovecot v1.1 works well with NFS.
> 

Results for Solaris 8 talking to a NetApp filer (OS: ONTAP 7.2.2p3)

Info: Connected: client
Info: O_EXCL works
Info: Testing attribute cache..
Info: Attr cache flush fchown(-1, -1): OK
Info: Attr cache flush fchown(uid, -1): OK
Info: Attr cache flush fchmod(mode): OK
Info: Attr cache flush chown(-1, -1): OK
Info: Attr cache flush chown(uid, -1): OK
Info: Attr cache flush chmod(mode): OK
Info: Testing write flushing..
Info: Write flush no caching: failed
Info: Write flush fcntl(shared): OK
Info: Write flush fcntl(exclusive): OK
Info: Write flush flock(shared): failed
Info: Write flush flock(exclusive): failed
Info: Write flush reopen: OK
Info: Testing data cache..
Info: data cache: Reading EOF requires attribute cache flush
Info: Data cache flush no caching: failed
Info: Data cache flush attr cache: OK
Info: Data cache flush fcntl(shared): OK
Info: Data cache flush fcntl(exclusive): OK
Info: Data cache flush flock(shared): failed
Info: Data cache flush flock(exclusive): failed
Info: Data cache flush dotlock: failed
Info: Data cache flush O_DIRECT: failed


-- 
--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-
Christopher Wakelin,   [EMAIL PROTECTED]
IT Services Centre, The University of Reading,  Tel: +44 (0)118 378 8439
Whiteknights, Reading, RG6 2AF, UK  Fax: +44 (0)118 975 3094

Re: [Dovecot] Problem with Dovecot SASL in Postfix

[Charles Marcus]

On 7/11/2007, Chris McMacken ([EMAIL PROTECTED]) wrote:
Here the auth section of my dovecot conf. 


Please always only provide dovecot -n output - it eliminates confusion 
and mistakes (maybe you are editing a config file that dovecot is not 
using?)...


--

Best regards,

Charles

Re: [Dovecot] Dovecot login failing

[albinootje]

Richard Ellis wrote:

[getmail/dovecot/squirrelmail login failure]
> Looking in the logs, Dovecot appears to be trying to add a domain name
> against the login, instead of just checking that user against the UNIX
> logins of my machine.

can you provide "dovecot -n" output ?
and did something change ? did you installed extra squirrelmail-plugins ?
did you test it also with an email-client like mozilla thunderbird ?

Re: [Dovecot] Dovecot login failing

[Richard Ellis]

[EMAIL PROTECTED] ~]# dovecot -n
# 1.0.1: /etc/dovecot.conf
log_path: /var/log/dovecot
info_log_path: /var/log/dovecot
protocols: imap pop3 imaps pop3s
ssl_listen: [::]
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
mail_executable(default): /usr/libexec/dovecot/imap
mail_executable(imap): /usr/libexec/dovecot/imap
mail_executable(pop3): /usr/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/lib/dovecot/imap
mail_plugin_dir(imap): /usr/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/pop3
auth default:
 passdb:
   driver: pam
 userdb:
   driver: passwd

No new Squirrelmail plugins installed recently, but I did enable some of the
default ones and add some a while ago. Mail works fine with Thunderbird on
my local network. Yum patched dovecot from 1.0 to 1.0.1 but I don't know if
that caused the problem.

Squirrelmail plugins are:
abook_take   fortune admin_add
index.php
sent_subfolders
info spam_buttons administratorlistcommands
spamcop
bug_report   mail_fetch   squirrelspell
calendar message_details  translate
delete_move_next newmail  vlogin filters
pupdate

SquirrelMail Configuration : Read: config.php (1.4.0)
-
Plugins
 Installed Plugins
   1. delete_move_next
   2. squirrelspell
   3. newmail
   4. spam_buttons
   5. spamcop
   6. administrator
   7. filters
   8. message_details
   9. pupdate
   10. vlogin
   11. admin_add

 Available Plugins:
   12. fortune
   13. abook_take
   14. info
   15. sent_subfolders
   16. translate
   17. mail_fetch
   18. bug_report
   19. calendar
   20. listcommands

Don't see what suddenly changed to make it start appending a domain name

Thanks

Rik



On 7/12/07, albinootje <[EMAIL PROTECTED]> wrote:


Richard Ellis wrote:

[getmail/dovecot/squirrelmail login failure]
> Looking in the logs, Dovecot appears to be trying to add a domain name
> against the login, instead of just checking that user against the UNIX
> logins of my machine.

can you provide "dovecot -n" output ?
and did something change ? did you installed extra squirrelmail-plugins ?
did you test it also with an email-client like mozilla thunderbird ?






--
The Truth is out there, does anyone have the URL?

Re: [Dovecot] NFS cache flush tester

[Andrew Ziem]

Timo Sirainen wrote:

On Wed, 2007-07-11 at 22:12 -0600, Andrew Ziem wrote:
  

Info: Data cache flush O_DIRECT: OK



I suppose this means that your kernel was compiled with
CONFIG_NFS_DIRECTIO=y? 
  

Yes, apparently so.  I think this is the correct file:

http://cvs.fedora.redhat.com/viewcvs/devel/kernel/configs/config-generic?root=core&rev=1.308&view=auto


Interesting that it is enabled by default in
Fedora and Debian. The kernel itself recommends not to use it by
default: "This kernel build option defaults OFF to avoid exposing system
administrators unwittingly to a potentially hazardous feature."




Andrew

Re: [Dovecot] v1.1 status and benchmarks

[Eric Rostetter]

Quoting Timo Sirainen <[EMAIL PROTECTED]>:


Yes, Dovecot's hasn't been a very good POP3 server. With v1.1 there
are several improvements that should make it a lot better, although
maybe still not perfect.


It may not be as "good" compared to some (like tpop3d) but it certainly
rocks compared to wu-imapd's pop3.  Your milage may vary, and be related
to what you are used to using.

--
Eric Rostetter
The Department of Physics
The University of Texas at Austin

Go Longhorns!

[Dovecot] Problem with Dovecot SASL in Postfix

[Chris McMacken]

Ok lets try this again...

I'm trying to configure my postfix server to use Dovecot as an SASL
server and running into some problems. My server supports a couple of
domain, I have multiple user/password files for multiple domains to
make the files a little easier to manage. Not sure if this question
should belong in the dovecot mailing list or the postfix one, but here
goes anyway. I have everything configured to use CRAM-MD5
authentication, including my mail client.

Here is the Dovecot -n output:

mail# dovecot -n
# /usr/local/etc/dovecot.conf
log_path: /var/log/dovecot
info_log_path: /var/log/dovecot.info
protocols: imap pop3
ssl_disable: yes
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
verbose_proctitle: yes
first_valid_gid: 0
mail_extra_groups: mail
mail_location: maildir:/home/vmail/%d/%n
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
imap_client_workarounds(default): delay-newmail outlook-idle
netscape-eoh tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(pop3): outlook-idle
pop3_uidl_format(default):
pop3_uidl_format(imap):
pop3_uidl_format(pop3): %08Xu%08Xv
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
auth default:
 mechanisms: plain cram-md5
 passdb:
   driver: passwd-file
   args: /usr/local/etc/dovecot/%d/passwd
 userdb:
   driver: passwd-file
   args: /usr/local/etc/dovecot/%d/passwd
 socket:
   type: listen
   client:
 path: /var/spool/postfix/private/auth
 mode: 432
 user: postfix
 group: postfix
   master:


heres a sample line from one of the passwd files:

chrism:{CRAM-MD5}a67a65704086a046b3f875d1eaac8cb5c6fd13406507fead30d9bcb1bf82b:1003:1003::/home/vmail/example.com

and to login through SASL I am trying to use the username
[EMAIL PROTECTED] when I use the full email address like this to
login like this I get this output into my postfix log:

Jul 10 18:46:59 mail postfix/smtpd[57343]: connect from unknown[12.244.148.123]
Jul 10 18:46:59 mail postfix/smtpd[57343]: NOQUEUE: reject: RCPT from
unknown[12.244.148.123]: 554 5.7.1 <[EMAIL PROTECTED]>: Relay access
denied; from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP
helo=<[192.168.1.14]>
Jul 10 18:47:00 mail postfix/smtpd[57343]: disconnect from
unknown[12.244.148.123]

(not actually using example.com but I changed it here)
heres my smtpd_recipient_restricitons from postconf

smtpd_recipient_restrictions = permit_mynetworks,
reject_unauth_destination, permit_sasl_authenticated

so when I use the full user name ([EMAIL PROTECTED]) it doesn't
appear to even attempt logging into the sasl server. If I change it to
simply chrism, heres the output:

Jul 10 18:50:36 mail postfix/smtpd[57356]: connect from unknown[12.244.148.123]
Jul 10 18:50:38 mail postfix/smtpd[57356]: warning:
unknown[12.244.148.123]: SASL CRAM-MD5 authentication failed:
PDI3NjU4MTE4NDExMTQzN0BtYWlsPg==
Jul 10 18:50:39 mail postfix/smtpd[57356]: lost connection after AUTH
from unknown[12.244.148.123]
Jul 10 18:50:39 mail postfix/smtpd[57356]: disconnect from
unknown[12.244.148.123]

if I put my user name in as chrism and don't add the @example.com it
tried to login but it can't login.

anyone have any ideas?

Re: [Dovecot] NFS cache flush tester

[Doug Council]

On Thu, 12 Jul 2007, Timo Sirainen wrote:

On Wed, 2007-07-11 at 15:43 -0700, Doug Council wrote:

Here are the results for FreeBSD 6.2-RELEASE-p5 and a NetApp NFS server.
FYI, the fcntl errors also appeared on the server instance.

..

Error: fcntl(setlk, read) failed: Operation not supported
Info: Data cache flush fcntl(shared): failed
Error: fcntl(setlk, write) failed: Operation not supported
Info: Data cache flush fcntl(exclusive): failed


Would you be able to enable lockd and see what these show then?


The NetApp filer is in production, so I am not able to.

But, Adam has posted his results using rpc.lockd/statd on FreeBSD 6.2 with 
a NetApp filer in 
http://www.dovecot.org/list/dovecot/2007-July/024070.html.


-Doug

Re: [Dovecot] NFS cache flush tester

[Timo Sirainen]

On Thu, 2007-07-12 at 12:45 +0100, Chris Wakelin wrote:
> Results for Solaris 8 talking to a NetApp filer (OS: ONTAP 7.2.2p3)

Thanks, could you try once more with an updated nfstest.c version? I
added "dup+close" which works for data and write cache flushing with
Linux. I really hope it works with Solaris+FreeBSD too.



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

Re: [Dovecot] NFS cache flush tester

[Chris Wakelin]

Timo Sirainen wrote:
> On Thu, 2007-07-12 at 12:45 +0100, Chris Wakelin wrote:
>> Results for Solaris 8 talking to a NetApp filer (OS: ONTAP 7.2.2p3)
> 
> Thanks, could you try once more with an updated nfstest.c version? I
> added "dup+close" which works for data and write cache flushing with
> Linux. I really hope it works with Solaris+FreeBSD too.
> 

OK, here it is!

Info: Connected: client
Info: O_EXCL works
Info: Testing attribute cache..
Info: Attr cache flush fchown(-1, -1): OK
Info: Attr cache flush fchown(uid, -1): OK
Info: Attr cache flush fchmod(mode): OK
Info: Attr cache flush chown(-1, -1): OK
Info: Attr cache flush chown(uid, -1): OK
Info: Attr cache flush chmod(mode): OK
Info: Attr cache flush dup+close: failed
Info: Testing write flushing..
Info: Write flush no caching: failed
Info: Write flush fcntl(shared): OK
Info: Write flush fcntl(exclusive): OK
Info: Write flush flock(shared): failed
Info: Write flush flock(exclusive): failed
Info: Write flush reopen: OK
Info: Write flush dup+close: failed
Info: Write flush attr cache: OK
Info: Testing data cache..
Info: data cache: Reading EOF requires attribute cache flush
Info: Data cache flush no caching: failed
Info: Data cache flush attr cache: OK
Info: Data cache flush fcntl(shared): OK
Info: Data cache flush fcntl(exclusive): OK
Info: Data cache flush flock(shared): failed
Info: Data cache flush flock(exclusive): failed
Info: Data cache flush dotlock: failed
Info: Data cache flush O_DIRECT: failed
Info: Data cache flush dup+close: OK

Best Wishes,
Chris

-- 
--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-
Christopher Wakelin,   [EMAIL PROTECTED]
IT Services Centre, The University of Reading,  Tel: +44 (0)118 378 8439
Whiteknights, Reading, RG6 2AF, UK  Fax: +44 (0)118 975 3094

Re: [Dovecot] NFS cache flush tester

[Timo Sirainen]

On Thu, 2007-07-12 at 18:35 +0100, Chris Wakelin wrote:
> > Thanks, could you try once more with an updated nfstest.c version? I
> > added "dup+close" which works for data and write cache flushing with
> > Linux. I really hope it works with Solaris+FreeBSD too.
> > 
> 
> Info: Write flush dup+close: failed
> Info: Write flush attr cache: OK

I didn't expect fchown() to flush write cache, but since dup+close
didn't work this is just as good.

> Info: Data cache flush dup+close: OK

Great. Now how about FreeBSD once more? :)



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

Re: [Dovecot] NFS cache flush tester

[Doug Council]

On Thu, 12 Jul 2007, Timo Sirainen wrote:

Thanks, could you try once more with an updated nfstest.c version? I
added "dup+close" which works for data and write cache flushing with
Linux. I really hope it works with Solaris+FreeBSD too.


I didn't expect fchown() to flush write cache, but since dup+close
didn't work this is just as good.


Info: Data cache flush dup+close: OK


Great. Now how about FreeBSD once more? :)


FreeBSD 6.2-RELEASE-p5 and a NetApp NFS server:

Info: Connected: client
Info: O_EXCL works
Info: Testing attribute cache..
Info: Attr cache flush fchown(-1, -1): OK
Info: Attr cache flush fchown(uid, -1): OK
Info: Attr cache flush fchmod(mode): OK
Info: Attr cache flush chown(-1, -1): OK
Info: Attr cache flush chown(uid, -1): OK
Info: Attr cache flush chmod(mode): OK
Info: Attr cache flush dup+close: failed
Info: Testing write flushing..
Info: Write flush no caching: failed
Info: Write flush fcntl(shared): failed
Info: Write flush fcntl(exclusive): failed
Info: Write flush flock(shared): failed
Info: Write flush flock(exclusive): failed
Info: Write flush reopen: OK
Info: Write flush dup+close: failed
Info: Write flush attr cache: failed
Info: Testing data cache..
Info: data cache: Reading EOF requires attribute cache flush
Info: Data cache flush no caching: failed
Info: Data cache flush attr cache: OK
Error: fcntl(setlk, read) failed: Operation not supported
Info: Data cache flush fcntl(shared): failed
Error: fcntl(setlk, write) failed: Operation not supported
Info: Data cache flush fcntl(exclusive): failed
Info: Data cache flush flock(shared): failed
Info: Data cache flush flock(exclusive): failed
Info: Data cache flush dotlock: failed
Info: Data cache flush O_DIRECT: failed
Info: Data cache flush dup+close: failed

-Doug

Re: [Dovecot] NFS cache flush tester

[Troy Engel]

Timo Sirainen wrote:

http://dovecot.org/tools/nfstest.c


Latest version used (2007-07-12 ~11am PST) for tests.


Machine 1: CentOS 4 (RHEL 4 clone)
Linux 2.6.9-42.0.8.ELsmp #1 SMP Tue Jan 30 12:33:47 EST 2007 i686 i686 
i386 GNU/Linux


Machine 2: CentOS 4 (RHEL 4 clone)
Linux 2.6.9-42.0.10.ELsmp #1 SMP Tue Feb 27 10:11:19 EST 2007 i686 i686 
i386 GNU/Linux


NFS Server: SnapServer 4500 (linux software RAID based appliance)
Linux 2.4.19-gos-up #1 Wed Jul 12 23:00:50 PDT 2006 i686 i686 i386 GNU/Linux


machine 1: server
machine 2: client
=
Info: Connected: client
Info: O_EXCL works
Info: Testing attribute cache..
Info: Attr cache flush fchown(-1, -1): failed
Info: Attr cache flush fchown(uid, -1): OK
Info: Attr cache flush fchmod(mode): OK
Info: Attr cache flush chown(-1, -1): failed
Info: Attr cache flush chown(uid, -1): OK
Info: Attr cache flush chmod(mode): OK
Info: Attr cache flush dup+close: OK
Info: Testing write flushing..
Info: Write flush no caching: failed
Info: Write flush fcntl(shared): OK
Info: Write flush fcntl(exclusive): OK
Info: Write flush flock(shared): failed
Info: Write flush flock(exclusive): failed
Info: Write flush reopen: OK
Info: Write flush dup+close: OK
Info: Write flush attr cache: failed
Info: Testing data cache..
Info: data cache: Reading EOF requires attribute cache flush
Info: Data cache flush no caching: failed
Info: Data cache flush attr cache: failed
Info: Data cache flush fcntl(shared): OK
Info: Data cache flush fcntl(exclusive): OK
Info: Data cache flush flock(shared): failed
Info: Data cache flush flock(exclusive): failed
Info: Data cache flush dotlock: failed
Info: Data cache flush O_DIRECT: OK
Info: Data cache flush dup+close: OK


machine 1: client
machine 2: server
=
Info: Connected: client
Info: O_EXCL works
Info: Testing attribute cache..
Info: Attr cache flush fchown(-1, -1): failed
Info: Attr cache flush fchown(uid, -1): OK
Info: Attr cache flush fchmod(mode): OK
Info: Attr cache flush chown(-1, -1): failed
Info: Attr cache flush chown(uid, -1): OK
Info: Attr cache flush chmod(mode): OK
Info: Attr cache flush dup+close: OK
Info: Testing write flushing..
Info: Write flush no caching: failed
Info: Write flush fcntl(shared): OK
Info: Write flush fcntl(exclusive): OK
Info: Write flush flock(shared): failed
Info: Write flush flock(exclusive): failed
Info: Write flush reopen: OK
Info: Write flush dup+close: OK
Info: Write flush attr cache: failed
Info: Testing data cache..
Info: data cache: Reading EOF requires attribute cache flush
Info: Data cache flush no caching: failed
Info: Data cache flush attr cache: failed
Info: Data cache flush fcntl(shared): OK
Info: Data cache flush fcntl(exclusive): OK
Info: Data cache flush flock(shared): failed
Info: Data cache flush flock(exclusive): failed
Info: Data cache flush dotlock: failed
Info: Data cache flush O_DIRECT: OK
Info: Data cache flush dup+close: OK


--
Troy Engel | Systems Engineer
Fluid, Inc | http://www.fluid.com

Re: [Dovecot] NFS cache flush tester

[Timo Sirainen]

On Thu, 2007-07-12 at 10:51 -0700, Doug Council wrote:
> > Great. Now how about FreeBSD once more? :)
> 
> FreeBSD 6.2-RELEASE-p5 and a NetApp NFS server:

Thanks.

> Info: Testing write flushing..
> Info: Write flush no caching: failed
> Info: Write flush fcntl(shared): failed
> Info: Write flush fcntl(exclusive): failed
> Info: Write flush flock(shared): failed
> Info: Write flush flock(exclusive): failed
> Info: Write flush reopen: OK
> Info: Write flush dup+close: failed
> Info: Write flush attr cache: failed

So still nothing usable. Updated nfstest.c once again to include
fdatasync() test. It has to work.



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

Re: [Dovecot] NFS cache flush tester

[Timo Sirainen]

On Thu, 2007-07-12 at 21:26 +0300, Timo Sirainen wrote:
> On Thu, 2007-07-12 at 10:51 -0700, Doug Council wrote:
> > > Great. Now how about FreeBSD once more? :)
> > 
> > FreeBSD 6.2-RELEASE-p5 and a NetApp NFS server:
> 
> Thanks.
> 
> > Info: Testing write flushing..
> > Info: Write flush no caching: failed
> > Info: Write flush fcntl(shared): failed
> > Info: Write flush fcntl(exclusive): failed
> > Info: Write flush flock(shared): failed
> > Info: Write flush flock(exclusive): failed
> > Info: Write flush reopen: OK
> > Info: Write flush dup+close: failed
> > Info: Write flush attr cache: failed
> 
> So still nothing usable. Updated nfstest.c once again to include
> fdatasync() test. It has to work.

Oh, looks like it works also for data flushing with Linux. How about
Solaris? :)



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

Re: [Dovecot] NFS cache flush tester

[Chris Wakelin]

Timo Sirainen wrote:
> On Thu, 2007-07-12 at 21:26 +0300, Timo Sirainen wrote:
>> On Thu, 2007-07-12 at 10:51 -0700, Doug Council wrote:
 Great. Now how about FreeBSD once more? :)
>>> FreeBSD 6.2-RELEASE-p5 and a NetApp NFS server:
>> Thanks.
>>
>>> Info: Testing write flushing..
>>> Info: Write flush no caching: failed
>>> Info: Write flush fcntl(shared): failed
>>> Info: Write flush fcntl(exclusive): failed
>>> Info: Write flush flock(shared): failed
>>> Info: Write flush flock(exclusive): failed
>>> Info: Write flush reopen: OK
>>> Info: Write flush dup+close: failed
>>> Info: Write flush attr cache: failed
>> So still nothing usable. Updated nfstest.c once again to include
>> fdatasync() test. It has to work.
> 
> Oh, looks like it works also for data flushing with Linux. How about
> Solaris? :)
> 

Solaris 8 diff (compilation needed -lrt as well as the usual -lnsl and
-lsocket):

Info: Write flush fdatasync: OK
Info: Data cache flush fdatasync: failed

Solaris 10 was the same as Solaris 8 for the previous nfstest.c. I'll
let you know if it differs for fdatasync (seems unlikely).

Best Wishes,
Chris

-- 
--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-
Christopher Wakelin,   [EMAIL PROTECTED]
IT Services Centre, The University of Reading,  Tel: +44 (0)118 378 8439
Whiteknights, Reading, RG6 2AF, UK  Fax: +44 (0)118 975 3094

Re: [Dovecot] NFS cache flush tester

[Doug Council]

On Thu, 12 Jul 2007, Timo Sirainen wrote:

So still nothing usable. Updated nfstest.c once again to include
fdatasync() test. It has to work.


fdatasync() isn't implemented in FreeBSD (see 
http://www.freebsd.org/cgi/query-pr.cgi?pr=64875).  It defaults to 
mapping fdatasync() to fsync().


Results for FreeBSD 6.2-RELEASE-p5 and NetApp NFS server:

Info: Connected: client
Info: O_EXCL works
Info: Testing attribute cache..
Info: Attr cache flush fchown(-1, -1): OK
Info: Attr cache flush fchown(uid, -1): OK
Info: Attr cache flush fchmod(mode): OK
Info: Attr cache flush chown(-1, -1): OK
Info: Attr cache flush chown(uid, -1): OK
Info: Attr cache flush chmod(mode): OK
Info: Attr cache flush dup+close: failed
Info: Testing write flushing..
Info: Write flush no caching: failed
Info: Write flush fcntl(shared): failed
Info: Write flush fcntl(exclusive): failed
Info: Write flush flock(shared): failed
Info: Write flush flock(exclusive): failed
Info: Write flush reopen: OK
Info: Write flush dup+close: failed
Info: Write flush attr cache: failed
Info: Write flush fdatasync: OK
Info: Testing data cache..
Info: data cache: Reading EOF requires attribute cache flush
Info: Data cache flush no caching: failed
Info: Data cache flush attr cache: OK
Error: fcntl(setlk, read) failed: Operation not supported
Info: Data cache flush fcntl(shared): failed
Error: fcntl(setlk, write) failed: Operation not supported
Info: Data cache flush fcntl(exclusive): failed
Info: Data cache flush flock(shared): failed
Info: Data cache flush flock(exclusive): failed
Info: Data cache flush dotlock: failed
Info: Data cache flush dup+close: failed
Info: Data cache flush fdatasync: failed

And with O_DIRECT enabled via vfs.nfs.nfs_directio_enable:

Info: Connected: client
Info: O_EXCL works
Info: Testing attribute cache..
Info: Attr cache flush fchown(-1, -1): OK
Info: Attr cache flush fchown(uid, -1): OK
Info: Attr cache flush fchmod(mode): OK
Info: Attr cache flush chown(-1, -1): OK
Info: Attr cache flush chown(uid, -1): OK
Info: Attr cache flush chmod(mode): OK
Info: Attr cache flush dup+close: failed
Info: Testing write flushing..
Info: Write flush no caching: failed
Info: Write flush fcntl(shared): failed
Info: Write flush fcntl(exclusive): failed
Info: Write flush flock(shared): failed
Info: Write flush flock(exclusive): failed
Info: Write flush reopen: OK
Info: Write flush dup+close: failed
Info: Write flush attr cache: failed
Info: Write flush fdatasync: OK
Info: Testing data cache..
Info: data cache: Reading EOF requires attribute cache flush
Info: Data cache flush no caching: failed
Info: Data cache flush attr cache: OK
Error: fcntl(setlk, read) failed: Operation not supported
Info: Data cache flush fcntl(shared): failed
Error: fcntl(setlk, write) failed: Operation not supported
Info: Data cache flush fcntl(exclusive): failed
Info: Data cache flush flock(shared): failed
Info: Data cache flush flock(exclusive): failed
Info: Data cache flush dotlock: failed
Info: Data cache flush dup+close: failed
Info: Data cache flush fdatasync: failed
Info: Data cache flush O_DIRECT: OK

-Doug

Re: [Dovecot] NFS cache flush tester

[Timo Sirainen]

On Wed, 2007-07-11 at 22:21 +0300, Timo Sirainen wrote:
> http://dovecot.org/tools/nfstest.c

v1.1 code does now NFS cache flushing with mail_nfs_storage=yes and
mail_nfs_index=yes. I haven't tried yet how well it works, but at least
it finally should work without disabling attribute caches or anything.

For read caching I ended up using:

#ifdef __linux__
 - fcntl() lock + unlock
#else
 - fchown(uid, -1)

Would have been nice to avoid the fcntl lock, but I couldn't find any
other way (I even checked Linux sources). It also means that either you
must use lockd with Linux or you must mount the filesystem with nolock
option.



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

[Dovecot] Integrating dovecot 1.01 into CentOS-3.8 systemw with chroot passwd dirs?

[Gary Goldberg]

Hello. I'm administrating a CentOS 3.8 linux system (RHEL3) and I just replaced
the imap-2002d-12 package that came with the system, with a dovecot 1.01
package I obtained through the dovecot home page. The problem I have, is that
many of my POP3 users have jailed user accounts set up through wu-ftpd, where
the dir field is of the form /home/group/./pop/user, and wu-ftpd chroots them
from /home/group but then places them into their home directories, in this case
/home/group/pop/user. dovecot can't seem to locate their mail directory.

Can anyone offer any advice on this situation?

Please respond to my email address  if you could.

---

Here are some relevant stats:

example user: lda01
home directory (in /etc/passwd: /home/lda/./pop/lda01
mail folder directory: /home/lda/pop/lda01/mail
INBOX: /home/mail/lda01   (/var/mail, /var/spool/mail symlinked to /home/mail.)

dovecot 1.01

output of dovecot -n:

#1.0.1: /etc/dovecot.conf
base_dir: /var/run/dovecot
log_path: /var/log/dovecot.log
protocols: imap imaps pop3 pop3s
ssl_disable: yes
ssl_cert_file: /usr/share/ssl/certs/dovecot.pem
ssl_key_file: /usr/share/ssl/certs/dovecot.pem
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_greeting: mail.digimark.net ready.
valid_chroot_dirs: /var/mail:/var/spool/mail:/home/mail:/home
mail_extra_groups: mail
mail_location: mbox:~/mail:INBOX=/home/mail/%u
mail_debug: yes
mail_full_filesystem_access: yes
mail_executable(default): /usr/libexec/dovecot/imap
mail_executable(imap): /usr/libexec/dovecot/imap
mail_executable(pop3): /usr/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/lib/dovecot/imap
mail_plugin_dir(imap): /usr/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/pop3
pop3_uidl_format(default): 
pop3_uidl_format(imap): 
pop3_uidl_format(pop3): %08Xv%08Xu

auth default:
  passdb:
driver: pam
args: blocking=yes dovecot
  userdb:
driver: passwd



attempt to login using a Squirrelmail (webmail) client gave these entries in 
the dovecot.log
error log:

dovecot: Jul 12 16:22:50 Info: imap-login: Login: user=, method=PLAIN, 
rip=127.0.0.1, lip=127.0.0.1, secured
dovecot: Jul 12 16:22:50 Info: IMAP(lda01): Effective uid=10572, gid=510, 
home=/pop/lda01
dovecot: Jul 12 16:22:50 Info: IMAP(lda01): mbox: 
data=/pop/lda01/mail:INBOX=/home/mail/lda01
dovecot: Jul 12 16:22:50 Info: IMAP(lda01): mbox: root=/pop/lda01/mail, 
index=/pop/lda01/mail, inbox=/home/mail/lda01
dovecot: Jul 12 16:23:04 Error: IMAP(lda01): open(/home/mail/lda01, O_CREAT) 
failed: No such file or directory
dovecot: Jul 12 16:23:04 Error: IMAP(lda01): access() failed with mbox file 
/home/mail/lda01: No such file or directory
dovecot: Jul 12 16:23:04 Error: IMAP(lda01): stat() failed with mbox file 
/home/mail/lda01: No such file or directory
dovecot: Jul 12 16:23:58 Info: IMAP(lda01): Disconnected: Logged out



--
-- "Outside of a dog, a book is a man's best friend.
-- Inside of a dog, it is too dark to read." -- Groucho Marx.
Gary Goldberg KA3ZYW <[EMAIL PROTECTED]> V:301/249-6501 F:301/390-1955 
AIM:OgGreeb
Digital Marketing/Bowie MD/Systems & Networks Consult 

Re: [Dovecot] Problem with Dovecot SASL in Postfix

[Timo Sirainen]

On Thu, 2007-07-12 at 10:52 -0500, Chris McMacken wrote:
> and to login through SASL I am trying to use the username
> [EMAIL PROTECTED] when I use the full email address like this to
> login like this I get this output into my postfix log:

Postfix's logs aren't very useful. Set auth_debug_passwords=yes in
dovecot.conf and look at Dovecot's logs.

> Jul 10 18:46:59 mail postfix/smtpd[57343]: connect from 
> unknown[12.244.148.123]
> Jul 10 18:46:59 mail postfix/smtpd[57343]: NOQUEUE: reject: RCPT from
> unknown[12.244.148.123]: 554 5.7.1 <[EMAIL PROTECTED]>: Relay access
> denied; from=<[EMAIL PROTECTED]> to=<[EMAIL PROTECTED]> proto=ESMTP
> helo=<[192.168.1.14]>
> Jul 10 18:47:00 mail postfix/smtpd[57343]: disconnect from
> unknown[12.244.148.123]
..
> Jul 10 18:50:36 mail postfix/smtpd[57356]: connect from 
> unknown[12.244.148.123]
> Jul 10 18:50:38 mail postfix/smtpd[57356]: warning:
> unknown[12.244.148.123]: SASL CRAM-MD5 authentication failed:
> PDI3NjU4MTE4NDExMTQzN0BtYWlsPg==

If the first session really got authenticated successfully (auth_debug
shows that too), then it's a Postfix configuration problem.



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

Re: [Dovecot] v1.1 status and benchmarks

[Timo Sirainen]

On Thu, 2007-07-12 at 13:39 +0200, Farkas Levente wrote:
> what is cydir? dovecot suppurt cydir format or it's cyrus speed?
> if it's dovecot cydir support so fast will the v.x.y be ever so fast? or
> it'd be better to use/switch to cydir?

It's a simple mailbox format that is somewhat similar to Cyrus mailbox
format. It completely relies on having all the mailbox metadata in
Dovecot's index files, and currently it can't even rebuild the indexes
if they get lost/corrupted.

I was planning on keeping it mostly for testing/benchmarking purposes.
I'm hoping that the upcoming dbox rewrite will have at least as good
performance as Cydir.


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

Re: [Dovecot] v1.1 status and benchmarks

[Timo Sirainen]

On Thu, 2007-07-12 at 09:37 +0200, DINH Viêt Hoà wrote:
> On 7/12/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:
> > v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to
> > have a stable v1.1 in a month or two. The rest of the features that
> > didn't make it into v1.1 will go to v1.2. I'll write more about this
> > when v1.1 alpha is released.
> >
> > I also did a bit of benchmarking. v1.1's performance improvements are
> > looking pretty great, it seems to be twice as fast as v1.0.
> >
> > v1.0: Maildir, dovecot-1.0 hg + inotify dotlock wait patch, mmap_disable=yes
> > v1.1: Maildir, dovecot hg, mmap_disable=no
> > cydir: Cydir, dovecot hg, mmap_disable=no
> 
> is dovecot+cydir as fast as native Cyrus-IMAP ?

It depends on what you benchmark, but I think it's faster in pretty much
all of them. I did some Cyrus vs Cydir benchmarking a month or two ago,
see mailing list archives.



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

Re: [Dovecot] v1.1 status and benchmarks

[Timo Sirainen]

On Thu, 2007-07-12 at 09:44 +0200, Arkadiusz Miskiewicz wrote:
> > If only POP3 is 
> > used, the cache file isn't created at all. If IMAP is used then
> > virtual size is stored also to the cache file.
> 
> Hm, http://wiki.dovecot.org/POP3Server doesn't mention anything about cache 
> not being created. It even says that dovecot.index.cache  is actually used 
> and updated.

I meant with v1.1 it's not being created/updated anymore with pop3-only
users, because it would just waste disk I/O. But if the cache file
already exists, it's used if needed.



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

Re: [Dovecot] v1.0.2 release candidate

[Timo Sirainen]

On Thu, 2007-07-12 at 12:24 +0200, Nicolas STRANSKY wrote:
> Is there any plan to add rquotad support in v1.0.2 

No. v1.0.x won't have any new features (well, except I made it
upwards-compatible with v1.1 generated files).

> or to release a changeset that can be applied to v1.0.2 ?

No.



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

Re: [Dovecot] Today's stable hg pull destroyed dovecot...

[Timo Sirainen]

On Thu, 2007-07-12 at 10:34 +0200, Ralf Hildebrandt wrote:
> I performed a hg pull today for 1.0.1 and after recompilation my log
> was flooded with:
> 
> Jul 12 10:29:21 postamt dovecot: IMAP(kxx4): UID larger than next_uid in file 
> /home/k/j/kxx4/Maildir/dovecot-uidlist (6 >= 0)
> Jul 12 10:29:21 postamt dovecot: IMAP(rexxxes): UID larger than next_uid in 
> file /home/r/e/rexxxes/Maildir/dovecot-uidlist (1 >= 0)
> Jul 12 10:29:21 postamt dovecot: IMAP(sxxkim): Maildir 
> /home/s/i/sxxkim/Maildir sync: UIDVALIDITY changed (1184228955 -> 3086699759)

Oh, looks like I forgot to push fix for this to hg.dovecot.org. It's
there now.



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

Re: [Dovecot] Dovecot login failing

[Timo Sirainen]

On Thu, 2007-07-12 at 15:12 +0100, Richard Ellis wrote:
> auth default:
>   passdb:
> driver: pam
>   userdb:
> driver: passwd

You have no auth settings that change the username, so it must be
Squirrelmail that adds it.



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

Re: [Dovecot] Patches to log imap bandwidth?

[Timo Sirainen]

On Thu, 2007-07-12 at 02:01 -0700, Jason Fesler wrote:
> Anyone patch dovecot to syslog bytes transfered during a session or 
> anything of that sort?

http://dovecot.org/patches/imap-bytes.diff



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

Re: [Dovecot] Patches to log imap bandwidth?

[Jason Fesler]

Anyone patch dovecot to syslog bytes transfered during a session or
anything of that sort?


http://dovecot.org/patches/imap-bytes.diff


Thank you Sir.

Re: [Dovecot] Quota exceeded messages

[Timo Sirainen]

On Tue, 2007-07-10 at 12:14 +0100, Frank Church wrote:

> Another thing to note is that the quota snippet in the SQL requires a
> cast and should be
> concat('dirsize:storage=', cast(quota as char)) AS
>  userdb_quota

Are you sure you want to use dirsize and hot maildir quota? dirsize is
horribly slow with maildir. Do you still see this kind of a dirsize
example mentioned somewhere in the Wiki?



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

Re: [Dovecot] Quota Messages

[Timo Sirainen]

On Tue, 2007-07-10 at 09:41 +0200, Hermann wacker wrote:
> The question is: Is there a way where Dovecot (or Postfix) inform the
> user that his quota is reaching its limit? Or maybe the postmaster,
> thats not important. The important thing is a way where my mailsystem
> tells somebody that quotas are reaching their limits.

From Dovecot's side you can currently do this only with a patch:
http://dovecot.org/patches/quota-warning.patch



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

Re: [Dovecot] dovecot sieve notify mailto

[Timo Sirainen]

On Fri, 2007-07-06 at 20:25 +0300, Uldis Pakuls wrote:
> and most important things:
> 1. notify now always reports SIEVE_OK as notify failure is not delivery
> failure. all notify failures are reported in log. Also "SIEVE_ERROR"
> aborts script execution, but there is no reason to abort on notify error.

These should maybe be changed elsewhere too..

> 2. sieve plugin returns "-1" if script failed load or on any error. i
> think it is wrong; if no scripts are executed or it is aborted for some
> reason - it is not fatal delivery error;  this just means "nothing is
> done" by script. so i changed plugin always return "0" on errors.

How about: http://hg.dovecot.org/dovecot-1.0/rev/87d0ae7fbe12

I committed the notify patch too with small changes.



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

Re: [Dovecot] v1.0.2 release candidate

[Timo Sirainen]

On Fri, 2007-07-13 at 00:35 +0200, Bernhard Schmidt wrote:
> Timo Sirainen <[EMAIL PROTECTED]> wrote:
> 
> > Unless someone finds something broken, I'll release v1.0.2 in a few
> > days. The most important changes since v1.0.1:
> 
> I'm getting a _large_ number of UIDVALIDITY changes logging messages,
> even when I have completely removed all old index files

rc2 should have fixed these. Did you get -rc.tar.gz or -rc2.tar.gz?



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

Re: [Dovecot] v1.0.2 release candidate

[Timo Sirainen]

On Fri, 2007-07-13 at 01:02 +0200, Bernhard Schmidt wrote:
> Jul 13 01:01:55 vs02 dovecot: IMAP(berni): Maildir 
> /var/mail/vmail/b/berni/.sysprak sync: UIDVALIDITY changed (7052738 -> 
> 1177317433)
> Jul 13 01:01:55 vs02 dovecot: IMAP(berni): Disconnected: Internal error 
> occurred. Refer to server log for more information. [2007-07-13 01:01:54]
> 
> Would that be an expected message after upgrading to the fixed version?

Yes, that's expected. It should happen only once for each mailbox. With
Dovecot v1.1 it handles this even more nicely without giving internal
errors.



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

Re: [Dovecot] v1.0.2 release candidate

[Bernhard Schmidt]

Timo Sirainen <[EMAIL PROTECTED]> wrote:

> Unless someone finds something broken, I'll release v1.0.2 in a few
> days. The most important changes since v1.0.1:

I'm getting a _large_ number of UIDVALIDITY changes logging messages,
even when I have completely removed all old index files

Jul 13 00:30:18 vs02 dovecot: IMAP(bernilrz): Corrupted transaction log
file /var/indexes/b/bernilrz/.hostmaster/dovecot.index.log.2: invalid
indexid (1184278797 != 1184279418)
Jul 13 00:30:18 vs02 dovecot: IMAP(berni): UID larger than next_uid in
file /var/mail/vmail/b/berni/.unsorted/dovecot-uidlist (7105250 >=
6978786)
Jul 13 00:30:18 vs02 dovecot: IMAP(berni): Maildir
/var/mail/vmail/b/berni/.unsorted sync: UIDVALIDITY changed (7105250 ->
6978786)
Jul 13 00:30:18 vs02 dovecot: IMAP(bernilrz): Corrupted index cache file
/var/indexes/b/bernilrz/.hostmaster/dovecot.index.cache: indexid changed
Jul 13 00:32:19 vs02 dovecot: IMAP(bernilrz): Maildir
/var/mail/vmail/b/bernilrz/.hostmaster sync: UIDVALIDITY changed
(7136882 -> 7053650)
Jul 13 00:32:19 vs02 dovecot: IMAP(bernilrz): Disconnected: Internal
error occurred. Refer to server log for more information. [2007-07-13
00:32:19]

x86_64 Ubuntu Feisty (Linux 2.6) in a Xen-domain

Bernhard

Re: [Dovecot] v1.0.2 release candidate

[Bernhard Schmidt]

Timo Sirainen wrote:

Hi Timo,


Unless someone finds something broken, I'll release v1.0.2 in a few
days. The most important changes since v1.0.1:

I'm getting a _large_ number of UIDVALIDITY changes logging messages,
even when I have completely removed all old index files

rc2 should have fixed these. Did you get -rc.tar.gz or -rc2.tar.gz?


Sorry I forgot to send that detail, I was using the dovecot-1.0 
hg-repository. I just pulled again with your last fix and it looks 
slightly better so far.


I still see messages about invalid indexid / indexid changed, even one 
disconnect with internal server error, but that might be because the 
indices were messed with by the broken version.


Jul 13 01:01:55 vs02 dovecot: IMAP(berni): Maildir 
/var/mail/vmail/b/berni/.sysprak sync: UIDVALIDITY changed (7052738 -> 
1177317433)
Jul 13 01:01:55 vs02 dovecot: IMAP(berni): Disconnected: Internal error 
occurred. Refer to server log for more information. [2007-07-13 01:01:54]


Would that be an expected message after upgrading to the fixed version?

Since that box is only a private mailserver and doesn't get many mails 
(especially during the night) I can't tell whether the problem is fixed 
now for sure.


Regards,
Bernhard

Re: [Dovecot] Dovecot login failing

[John Robinson]

On 12/07/2007 23:19, Timo Sirainen wrote:

On Thu, 2007-07-12 at 15:12 +0100, Richard Ellis wrote:

auth default:
  passdb:
driver: pam
  userdb:
driver: passwd


You have no auth settings that change the username, so it must be
Squirrelmail that adds it.


I suspect the vlogin plugin. Quoting 
http://www.squirrelmail.org/plugin_view.php?id=47 :


Some of Vlogin's helpful features include:

* make sure all usernames given on login page do not have any 
domain portion in them
* make sure all usernames given on login page have the SquirrelMail 
default domain appended to them
* make sure all usernames given on login page have the domain that 
corresponds to the domain in the URL of the login page appended to them
* allow users to log in with just a "user" when in fact their IMAP 
login might be something like "[EMAIL PROTECTED]"


Cheers,

John.

Re: [Dovecot] Monitoring Recomendations

[Timo Sirainen]

On Fri, 2007-06-29 at 10:45 -0700, Dehnert James Sr wrote:
> I believe that Dovecot is running just fine, but I need some metrics  
> to prove that to the users.

You could for example patch rawlog to log timestamps before each
input/output packet so you can see how long it takes for Dovecot to
reply to commands. If most of the time is spent waiting for incoming
commands then the problem isn't with Dovecot.

Attached a patch (untested though), and
http://dovecot.org/bugreport.html#sniffing explains how to enable
rawlog.

If the problem isn't with Dovecot, maybe your users have some software
firewall on the way that slows everything down.

diff -r 87d0ae7fbe12 src/util/rawlog.c
--- a/src/util/rawlog.c	Fri Jul 13 01:46:26 2007 +0300
+++ b/src/util/rawlog.c	Fri Jul 13 02:10:31 2007 +0300
@@ -40,6 +40,7 @@ struct rawlog_proxy {
 	enum rawlog_flags flags;
 
 	time_t last_write;
+	unsigned int last_in_lf:1;
 	unsigned int last_out_lf:1;
 };
 
@@ -76,8 +77,21 @@ static void proxy_write_in(struct rawlog
 static void proxy_write_in(struct rawlog_proxy *proxy,
 			   const void *data, size_t size)
 {
+	struct tm *tm;
+	char buf[256];
+
 	if (proxy->fd_in == -1 || size == 0)
 		return;
+
+	if (proxy->last_in_lf &&
+	(proxy->flags & RAWLOG_FLAG_LOG_TIMESTAMPS) != 0) {
+		tm = localtime(&ioloop_time);
+
+		if (strftime(buf, sizeof(buf), TIMESTAMP_FORMAT, tm) <= 0)
+			i_fatal("strftime() failed");
+		if (write_full(proxy->fd_out, buf, strlen(buf)) < 0)
+			i_fatal("Can't write to log file: %m");
+	}
 
 	if (write_full(proxy->fd_in, data, size) < 0) {
 		/* failed, disable logging */
@@ -85,6 +99,7 @@ static void proxy_write_in(struct rawlog
 		(void)close(proxy->fd_in);
 		proxy->fd_in = -1;
 	}
+	proxy->last_in_lf = ((const unsigned char *)buf)[size-1] == '\n';
 }
 
 static void proxy_write_out(struct rawlog_proxy *proxy,
@@ -97,8 +112,7 @@ static void proxy_write_out(struct rawlo
 		return;
 
 	if (proxy->last_out_lf &&
-	(proxy->flags & RAWLOG_FLAG_LOG_TIMESTAMPS) != 0 &&
-	ioloop_time - proxy->last_write >= TIMESTAMP_WAIT_TIME) {
+	(proxy->flags & RAWLOG_FLAG_LOG_TIMESTAMPS) != 0) {
 		tm = localtime(&ioloop_time);
 
 		if (strftime(buf, sizeof(buf), TIMESTAMP_FORMAT, tm) <= 0)


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

Re: [Dovecot] Integrating dovecot 1.01 into CentOS-3.8 systemw with chroot passwd dirs?

[Timo Sirainen]

On Thu, 2007-07-12 at 17:33 -0400, Gary Goldberg wrote:
> Hello. I'm administrating a CentOS 3.8 linux system (RHEL3) and I just 
> replaced
> the imap-2002d-12 package that came with the system, with a dovecot 1.01
> package I obtained through the dovecot home page. The problem I have, is that
> many of my POP3 users have jailed user accounts set up through wu-ftpd, where
> the dir field is of the form /home/group/./pop/user, and wu-ftpd chroots them
> from /home/group but then places them into their home directories, in this 
> case
> /home/group/pop/user. dovecot can't seem to locate their mail directory.

Dovecot chroots the users as well then.

> mail_location: mbox:~/mail:INBOX=/home/mail/%u

Change this to:

mail_location: mbox:~/mail:INBOX=~/%u

Does it work then?


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

Re: [Dovecot] Integrating dovecot 1.01 into CentOS-3.8 systemw with chroot passwd dirs?

[Gary Goldberg]

On Fri, 13 Jul 2007, Timo Sirainen wrote:


Dovecot chroots the users as well then.


Thanks for the reply; That's good news.


mail_location: mbox:~/mail:INBOX=/home/mail/%u


Change this to:
mail_location: mbox:~/mail:INBOX=~/%u
Does it work then?


Wouldn't that parse to $HOME/$USER for each inbox? Currently sendmail/procmail
delivers mail to /var/mail, which is symlinked to /home/mail in my system.

--
-- "Outside of a dog, a book is a man's best friend.
-- Inside of a dog, it is too dark to read." -- Groucho Marx.
Gary Goldberg KA3ZYW <[EMAIL PROTECTED]> V:301/249-6501 F:301/390-1955 
AIM:OgGreeb
Digital Marketing/Bowie MD/Systems & Networks Consult 

Re: [Dovecot] Integrating dovecot 1.01 into CentOS-3.8 systemw with chroot passwd dirs?

[Timo Sirainen]

On 13.7.2007, at 3.57, Gary Goldberg wrote:


mail_location: mbox:~/mail:INBOX=/home/mail/%u


Change this to:
mail_location: mbox:~/mail:INBOX=~/%u
Does it work then?


Wouldn't that parse to $HOME/$USER for each inbox? Currently  
sendmail/procmail
delivers mail to /var/mail, which is symlinked to /home/mail in my  
system.


Yes, but $HOME expands to / since you have the chroot.



PGP.sig
Description: This is a digitally signed message part

Re: [Dovecot] Dovecot login failing

[Rik Ellis]

Hi John,

You are correct. Something has changed in default behaviors between a 
previous version I had installed and the latest one. I have disabled it 
while I work out what. Means some of my friends can't get to their mail 
remotely at the moment, but at least mine works now :)


Rik

John Robinson wrote:

On 12/07/2007 23:19, Timo Sirainen wrote:

On Thu, 2007-07-12 at 15:12 +0100, Richard Ellis wrote:

auth default:
  passdb:
driver: pam
  userdb:
driver: passwd


You have no auth settings that change the username, so it must be
Squirrelmail that adds it.


I suspect the vlogin plugin. Quoting 
http://www.squirrelmail.org/plugin_view.php?id=47 :


Some of Vlogin's helpful features include:

* make sure all usernames given on login page do not have any 
domain portion in them
* make sure all usernames given on login page have the 
SquirrelMail default domain appended to them
* make sure all usernames given on login page have the domain that 
corresponds to the domain in the URL of the login page appended to them
* allow users to log in with just a "user" when in fact their IMAP 
login might be something like "[EMAIL PROTECTED]"


Cheers,

John.