Re: [Dovecot] Maildir from offlineimap, INBOX folder created

2009-07-24 Thread Ng Oon-Ee
On Fri, 2009-07-24 at 01:47 -0400, Timo Sirainen wrote:
 On Jul 24, 2009, at 1:35 AM, Ng Oon-Ee wrote:
 
  On Fri, 2009-07-24 at 01:25 -0400, Timo Sirainen wrote:
  On Jul 24, 2009, at 1:18 AM, Ng Oon-Ee wrote:
 
  Anyway, it all works spiffingly well, except that I can't see my  
  inbox
  at all. What happens is that attempting to subscribe to Inbox will
  create an INBOX folder in the root folder, which is (of course)  
  empty,
  so I see an empty folder.
 
  mail_location: maildir:/home/data/Profiles/OfflineIMAP/ 
  root:LAYOUT=fs
 
  Append :INBOX=/home/data/Profiles/OfflineIMAP/root
 
 
  Hey, thanks, worked perfectly. I just rechecked the wiki, and this is
  not mentioned at all, should it be added? The only part of
  MalboxFormat/Maildir dealing with this, under Directory Structure,  
  only
  mentions that v1.1 supports subfolders with :LAYOUT=fs.
 
 Well, this wasn't really intentional.. LAYOUT=fs hasn't really been  
 used much. I'm beginning to think maybe I should change this to be the  
 default with it too.
 

I guess offlineimap-dovecot (serving IMAP)-mail client IS a bit of a
corner case. Thing is, unless I'm mistaken (which wouldn't surprise me)
the Maildir++ specification doesn't allow/suggest a separate INBOX
folder? In that case, then yes that default would make sense.

Thank you for your time, assistance, and this wonderful piece of
software.



Re: [Dovecot] Maildir from offlineimap, INBOX folder created

2009-07-24 Thread Timo Sirainen

On Jul 24, 2009, at 2:10 AM, Ng Oon-Ee wrote:


Well, this wasn't really intentional.. LAYOUT=fs hasn't really been
used much. I'm beginning to think maybe I should change this to be  
the

default with it too.



I guess offlineimap-dovecot (serving IMAP)-mail client IS a bit of a
corner case. Thing is, unless I'm mistaken (which wouldn't surprise  
me)

the Maildir++ specification doesn't allow/suggest a separate INBOX
folder? In that case, then yes that default would make sense.


You're using fs layout, not Maildir++ layout.


Re: [Dovecot] Maildir from offlineimap, INBOX folder created

2009-07-24 Thread Ng Oon-Ee
On Fri, 2009-07-24 at 02:14 -0400, Timo Sirainen wrote:
 You're using fs layout, not Maildir++ layout.

Well, I'm obviously much less well-informed on these matters, but from
my POV I was using Evolution (probably one of the more popular
maildir-capable GUI app), and this is the maildir format it uses. I
always thought it was simply the base Maildir++ format, but with
subfolders instead of lots of dots.



Re: [Dovecot] Maildir from offlineimap, INBOX folder created

2009-07-24 Thread Timo Sirainen

On Jul 24, 2009, at 2:22 AM, Ng Oon-Ee wrote:


On Fri, 2009-07-24 at 02:14 -0400, Timo Sirainen wrote:

You're using fs layout, not Maildir++ layout.


Well, I'm obviously much less well-informed on these matters, but from
my POV I was using Evolution (probably one of the more popular
maildir-capable GUI app), and this is the maildir format it uses. I
always thought it was simply the base Maildir++ format, but with
subfolders instead of lots of dots.


Nope. Maildir++ is basically the dot-subfoldering and also Maildir++  
quota file. Evolution uses neither.


Re: [Dovecot] Maildir from offlineimap, INBOX folder created

2009-07-24 Thread Ng Oon-Ee
On Fri, 2009-07-24 at 02:28 -0400, Timo Sirainen wrote:
 Nope. Maildir++ is basically the dot-subfoldering and also Maildir++  
 quota file. Evolution uses neither.

Ah, thanks for clearing that up. So this LAYOUT=fs is simply for the
Maildir spec, not Maildir++? Or is it some amalgamation that doesn't
properly fit? In particular, the wikipedia for maildir says that maildir
++ was created to ALLOW subfolders, so i guess maildir didn't in the
first place?



Re: [Dovecot] Maildir from offlineimap, INBOX folder created

2009-07-24 Thread Timo Sirainen

On Jul 24, 2009, at 2:34 AM, Ng Oon-Ee wrote:


On Fri, 2009-07-24 at 02:28 -0400, Timo Sirainen wrote:

Nope. Maildir++ is basically the dot-subfoldering and also Maildir++
quota file. Evolution uses neither.


Ah, thanks for clearing that up. So this LAYOUT=fs is simply for the
Maildir spec, not Maildir++? Or is it some amalgamation that doesn't
properly fit? In particular, the wikipedia for maildir says that  
maildir

++ was created to ALLOW subfolders, so i guess maildir didn't in the
first place?


You seem to be a bit too much obsessed over Maildir++ :) Maildir++ is  
just Courier IMAP's way of storing Maildir folders, which was adopted  
by a few other programs. Other programs use more human-understandable  
way (LAYOUT=fs). Nothing would prevent creating yet another different  
way of storing them. In all cases once the Maildir directory is found,  
the Maildir handling works exactly the same.




Re: [Dovecot] Maildir from offlineimap, INBOX folder created

2009-07-24 Thread Ng Oon-Ee
On Fri, 2009-07-24 at 02:45 -0400, Timo Sirainen wrote:
 
 You seem to be a bit too much obsessed over Maildir++ :) Maildir++ is  
 just Courier IMAP's way of storing Maildir folders, which was adopted  
 by a few other programs. Other programs use more human-understandable  
 way (LAYOUT=fs). Nothing would prevent creating yet another different  
 way of storing them. In all cases once the Maildir directory is found,  
 the Maildir handling works exactly the same.
 

Okay, thanks for clearing that up =). I was just interested because
maildir is such a 'new' thing to me compared with the mboxes of this
world, and its made my life much easier since I started using it
(especially the rsync backups). I think this thread is pretty much done,
and your explanations could prove useful for the archives.



[Dovecot] High Availability strategies

2009-07-24 Thread Joseba Torre
Hi,

we have a medium setup (8000 pop and imap users using almost every 
available client, 800GB of stored mails using maildir on a Celerra NFS 
server, with index files on local disks, and procmail for local 
delivery), being served by a Dell PowerEdge 2850 (2GB RAM and dual P4 
Xeon 3,2GHz).

Our current not-so-high availability setup is based on a similar 
server with the same setup and a easy but manual process to switch 
from one server to another.

We are thinking about  setting up some kind of serious high 
availability, but for every strategy we think about some problems 
appear, and I'd like to hear your opinions about them:

- The recommended setup, with each user being sent always to the same 
server, is not possible because our load balancers (Cisco Catalyst 
6000) can't do that.

- We could put both servers behind the load balancer, and keep local 
index files on each server. Usually the same ip we'll be redirected to 
the same server, so few problems will arise. When a user is sent to a 
new server, index will be rebuilt so performance will be bad but we 
should not expect other problems, right?

- We could also put the index files on a nfs share. No problems, but 
pretty bad performance.

- We could also get more ram for the servers and keep indices in 
memory.

How can we compare these solutions? Apart from performance, are other 
problems expected? Using deliver instead of procmail could improve 
performance?

- We've also thought about some more or less weird setups, like 
setting up a GFS filesystem for the index files, or setting up a proxy 
on every server which redirect users to their fixed server, but they 
seem too complex for few advantages.

Any recommendations? How are you doing this? 
-- 
Joseba Torre. Vicegerencia de TICs, área de Explotación


[Dovecot] fts_squat + virtual = crash

2009-07-24 Thread intrigeri
Hi,

dovecot's imap process segfaults when I search a virtual mailbox using
the fts_squat plugin. Is this supposed to work, or a known bug?
I've seen some changes commited to fts_solr a couple of months ago
that where supposed to fix search issues on virtual mailboxes, maybe
fts_squat needs to be fixed to?

log
===

rawlog
--

3551 SELECT INBOX.virtual.unseen
3552 UID SEARCH TEXT catalyst

syslog
--

11:34 kernel: [78583.208983] imap[29376]: segfault at 0 ip 0 sp 7fff9b3e1698 
error 14 in imap[40+f4000]
11:34 dovecot: dovecot: child 29376 (imap) killed with signal 11 (core dumps 
disabled)

backtrace
=

As I'm using Debian's 1.2.1 package, the debugging symbols
are stripped. Tell me if a backtrace with debugging symbols enabled
would help debugging this problem.

Here's the backtrace anyway:

(gdb) bt full
#0  0x in ?? ()
No symbol table info available.
#1  0x7ff134163fbc in ?? () from 
/usr/lib/dovecot/modules/imap/lib20_fts_plugin.so
No symbol table info available.
#2  0x7ff1341647a5 in ?? () from 
/usr/lib/dovecot/modules/imap/lib20_fts_plugin.so
No symbol table info available.
#3  0x00429546 in imap_search_start ()
No symbol table info available.
#4  0x004207e8 in cmd_search ()
No symbol table info available.
#5  0x0042347c in ?? ()
No symbol table info available.
#6  0x0042352d in ?? ()
No symbol table info available.
#7  0x004236a5 in client_handle_input ()
No symbol table info available.
#8  0x0042403f in client_input ()
No symbol table info available.
#9  0x004ad67b in io_loop_handler_run ()
No symbol table info available.
#10 0x004acaf8 in io_loop_run ()
No symbol table info available.
#11 0x0042c04b in main ()

dovecot -n output
=

# 1.2.1: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.26-2-vserver-amd64 x86_64 Debian 5.0.1 
log_timestamp: %Y-%m-%d %H:%M:%S 
protocols: imap
listen: 127.0.0.1
ssl: no
login_dir: /var/run/dovecot/login
login_executable: /usr/lib/dovecot/imap-login
valid_chroot_dirs: /var/mail
first_valid_uid: 1222
last_valid_uid: 1222
first_valid_gid: 1222
last_valid_gid: 1222
mail_privileged_group: mail
mail_location: maildir:~/Maildir
maildir_very_dirty_syncs: yes
mail_drop_priv_before_exec: yes
mail_plugins: fts fts_squat virtual
namespace:
  type: private
  separator: .
  prefix: INBOX.
  inbox: yes
  list: yes
  subscriptions: yes
namespace:
  type: private
  separator: .
  prefix: INBOX.virtual.
  location: 
virtual:~/Maildir/virtual:LAYOUT=maildir++:INDEX=~/Maildir/virtual/indices
  list: yes
  subscriptions: yes
auth default:
  passdb:
driver: pam
  passdb:
driver: passwd-file
args: /etc/dovecot/userdb
  userdb:
driver: passwd
  userdb:
driver: passwd-file
args: /etc/dovecot/userdb
  socket:
type: listen
master:
  path: /var/run/dovecot/auth-master
  mode: 432
  user: root
  group: mailgroup
plugin:
  sieve: ~/.dovecot.sieve
  sieve_dir: ~/sieve
  fts: squat
  fts_squat: partial=4 full=10

Bye,
-- 
  intrigeri intrig...@boum.org
  | gnupg key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | Do not be trapped by the need to achieve anything.
  | This way, you achieve everything.


Re: [Dovecot] Maildir from offlineimap, INBOX folder created

2009-07-24 Thread Charles Marcus
On 7/24/2009 1:47 AM, Timo Sirainen wrote:
 mail_location: maildir:/home/data/Profiles/OfflineIMAP/root:LAYOUT=fs

 Append :INBOX=/home/data/Profiles/OfflineIMAP/root

 Hey, thanks, worked perfectly. I just rechecked the wiki, and this is
 not mentioned at all, should it be added? The only part of
 MalboxFormat/Maildir dealing with this, under Directory Structure, only
 mentions that v1.1 supports subfolders with :LAYOUT=fs.

 Well, this wasn't really intentional.. LAYOUT=fs hasn't really been used
 much. I'm beginning to think maybe I should change this to be the
 default with it too.

I agree... maybe 2.0 would be a good time to do this since it would
affect existing installations...

-- 

Best regards,

Charles


Re: [Dovecot] High Availability strategies

2009-07-24 Thread Robert Schetterer
Joseba Torre schrieb:
 Hi,
 
 we have a medium setup (8000 pop and imap users using almost every 
 available client, 800GB of stored mails using maildir on a Celerra NFS 
 server, with index files on local disks, and procmail for local 
 delivery), being served by a Dell PowerEdge 2850 (2GB RAM and dual P4 
 Xeon 3,2GHz).
 
 Our current not-so-high availability setup is based on a similar 
 server with the same setup and a easy but manual process to switch 
 from one server to another.
 
 We are thinking about  setting up some kind of serious high 
 availability, but for every strategy we think about some problems 
 appear, and I'd like to hear your opinions about them:
 
 - The recommended setup, with each user being sent always to the same 
 server, is not possible because our load balancers (Cisco Catalyst 
 6000) can't do that.
 
 - We could put both servers behind the load balancer, and keep local 
 index files on each server. Usually the same ip we'll be redirected to 
 the same server, so few problems will arise. When a user is sent to a 
 new server, index will be rebuilt so performance will be bad but we 
 should not expect other problems, right?
 
 - We could also put the index files on a nfs share. No problems, but 
 pretty bad performance.
 
 - We could also get more ram for the servers and keep indices in 
 memory.
 
 How can we compare these solutions? Apart from performance, are other 
 problems expected? Using deliver instead of procmail could improve 
 performance?
 
 - We've also thought about some more or less weird setups, like 
 setting up a GFS filesystem for the index files, or setting up a proxy 
 on every server which redirect users to their fixed server, but they 
 seem too complex for few advantages.
 
 Any recommendations? How are you doing this? 

search the list archive, this  was disscussed before
a ha balance setup with gfs like filesystem is possible and
working, sorry about cisco i only did small tests
plain ha linux setups with a layout of 4 servers
2 ha loadbalancers and 2 postfix/dovecot servers
on ubuntu with one cluster ip, but posibilities
are serveral ways to goal what you need, so fitting to local network
layouts is always needed as well as hard testing before production stage

is always needed
-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria


[Dovecot] Handling of file maildirsize

2009-07-24 Thread Frank Elsner

Hello,

My exim is doing the deliveries, dovecot handles POP/IMAP.

Exim Log shows:

2009-07-24 14:03:40 1MUJUy-0001Jr-B0 == u...@domain.tu-berlin.de R=maildir_user 
T=maildir_delivery defer (2): No such file or directory: while opening or 
reading /var/Mail/Boxes/u/user/maildirsize

2009-07-24 14:20:32 1MUJUy-0001Jr-B0 = user u...@domain.tu-berlin.de 
F=u...@domain.tu-berlin.de R=maildir_user T=maildir_delivery S=2061 QT=16m52s 
DT=0s


The user was active using IMAP at 14:03:4*. 

Therefor there must be a short period of time where no maildirsize exists.

Can this really happen? If yes, could this behaviour be changed?


Kind regards,
Frank Elsner


Re: [Dovecot] Are host names a secret?

2009-07-24 Thread Steffen Kaiser

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, 16 Jul 2009, Timo Sirainen wrote:


when they get moved to a different servers, etc.. But is this a real
issue? Maybe not.


I agree to that it is no issue.

Maybe, deliver should get a new option, e.g.:

- -X fake_hostname

Bye.

- -- 
Steffen Kaiser

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

iQEVAwUBSmmvjnWSIuGy1ktrAQLZnQf/Y+UacsKVhJmucrR01Ob63xfdqhPwflOe
TVlO4BwP6Qq/d1G/CWLV7b/52gHtc/V1wejw+PA7qMgaCFDAro02ssgAzx42rMNI
XO2v3GKDl+VpUirYuhy1ATA2pOOs4jXi3pC2RdN4CCISvq6fVtiKAjuWTLnKmtSY
Oo63Ps2W/7uAmFUfK58Uy5YucHSRKfULY1kIpGJdmmhv+Va3Gp3gzhWFmhIK9tBB
zYrkuj1NraBSOELdAFnVoXlyc2XpMtU61pW6XZ9UnVPZaW3d3060mBw2xv30dATa
s26rOrnTOaM2aMZ6xxvpQRYHBQMhJM69fPQWsBwve9qyWC9uNg36TA==
=a8zV
-END PGP SIGNATURE-


Re: [Dovecot] High Availability strategies

2009-07-24 Thread Seth Mattinen
Joseba Torre wrote:
 Hi,
 
 we have a medium setup (8000 pop and imap users using almost every 
 available client, 800GB of stored mails using maildir on a Celerra NFS 
 server, with index files on local disks, and procmail for local 
 delivery), being served by a Dell PowerEdge 2850 (2GB RAM and dual P4 
 Xeon 3,2GHz).
 
 Our current not-so-high availability setup is based on a similar 
 server with the same setup and a easy but manual process to switch 
 from one server to another.

If you don't care about keeping an active/standby setup and you're happy
with what you've currently got going on, you can easily automate the
process with heartbeat.

~Seth


Re: [Dovecot] E-Mail Encryption

2009-07-24 Thread Frank Leonhardt
On 19/07/2009 16:03, Tapani Tarvainen wrote:
 On Sun, Jul 19, 2009 at 03:48:25PM +0100, Frank Leonhardt
(t200...@fjl.co.uk) wrote:
 
 Encrypting the whole disk is good if the server gets pinched. My servers
are
 behind several layers of hi-tech locks with permanent security guards on
the
 door. I'm not too worried about them.
 
 How much good do your locks do when police comes and wants to
 confiscate your servers because they suspect one of your users
 has done something criminal? Do you trust they take as good care
 of the machines as you do?

How do you know I'm *not* the Police?

We're in very interesting territory here, and it's going to depend on your
local laws. In England the police are pretty okay about things, and are glad
to have you extract the data yourself. If they really want to do it
themselves it's easy enough to give them half a mirror.

 I'm not in favour of whole disk encryption for data recovery and forensic
 reasons.
 
 Some people favour it for the very same reasons...

Again, it depends on the jurisdiction. In England, if you can't decrypt the
data it can be a bit awkward (RIPA) - unless it's clearly NOT your data in
the first place (i.e. a message body).

 Protection against a rogue admin by encryption is a red herring. Such a
 person would simply not enable the encryption in the first place.
 
 Here I beg to differ. You are right in the simple situation where
 there's just one admin who's a crook to begin with, but often enough
 there're several and only one (or few) unreliable ones among them,
 and even if they're all good they can be forced by their bosses
 or blackmailers or even untrustworthy authorities.
 This is not purely theoretical, I can assure you.

Yes, but the rogue administrator ought to be able to circumvent encryption
anyway - if it's whole disk it's effectively not encrypted. It'd rely on a
policy of someone else periodically checking the files to see if they were
still encrypted - don't see that happening somehow! And even then, an
administrator could easily tee the data off before its stored.

The main reason I'd be in favour of application-based file encryption is to
get around the fact that whole-disk encryption is meaningless as protection
from the operator - if the operator is dodgy (or someone's bypassed
security) then they can read the mail files just as easily as everything
else. If the files themselves are encrypted then access to the running
system won't reveal their contents (although it would help).




Re: [Dovecot] lock files causing time outs with Thunderbird

2009-07-24 Thread Timo Sirainen
On Fri, 2009-07-24 at 15:55 -0600, CJ Keist wrote:
 I have dovecot 1.1.16 running on Solaris 10.  We are seeing problem with 
 lock files taking forever to be removed after opening a email folder 
 like Trash with several thousand messages in them.  We use mbox format. 

You mean dotlock files (e.g. Trash.lock)? Does Dovecot log anything?

 Is there something I can do in the config file to speed things up?

Are you using Dovecot deliver? If not, mbox_very_dirty_syncs=yes should
speed things up with large mboxes.



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


[Dovecot] Several errors

2009-07-24 Thread FraNL
Hi,

Running OS: CentOS 5.3 (2.6.18-128.2.1.el5)

1.
My Linux distribution comes with Dovecot 1.0.7. After trying to make it
running, I encoutnered many problems. So I decided to upgrade to 1.2.1.
When running dovecot -r from CLI, it returns with version 1.2.1.
But at the top of the log file it says: Info: Dovecot v1.0.7 starting up

So I am not sure which version I am running.

That's the first problem.

The other two problems I am having were also actual before updating to 1.2.1:

2.  Every minute, the following lines (except for the timestamps, which
are different, ofcourse) are being added to my log file:
dovecot: Jul 24 23:54:24 Error: imap-login: USER environment missing
dovecot: Jul 24 23:54:24 Error: imap-login: USER environment missing
dovecot: Jul 24 23:54:24 Error: child 3712 (login) returned error 89
dovecot: Jul 24 23:54:24 Error: child 3713 (login) returned error 89
dovecot: Jul 24 23:54:24 Error: imap-login: USER environment missing
dovecot: Jul 24 23:54:24 Error: child 3714 (login) returned error 89

3.  As soon as a user tries to log on via POP3 (telnet localhost pop3),
the user is kicked out.
The log file says (username and domain name are fake):
dovecot: Jul 25 00:01:02 Info: pop3-login: Login:
user=u...@mydomain.tld, method=PLAIN, rip=:::127.0.0.1,
lip=:::127.0.0.1, secured
dovecot: Jul 25 00:01:02 Error: POP3(u...@mydomain.tld):
file_dotlock_open() failed with file
/var/mail/vhosts/mydomain.tld/user/dovecot.index.log: Permission denied
dovecot: Jul 25 00:01:02 Error: POP3(u...@mydomain.tld):
file_dotlock_open(/var/mail/vhosts/mydomain.tld/user/dovecot-uidlist)
failed: Permission denied
dovecot: Jul 25 00:01:02 Error: POP3(u...@mydomain.tld): Couldn't init
INBOX: Can't sync mailbox: Messages keep getting expunged
dovecot: Jul 25 00:01:02 Info: POP3(u...@mydomain.tld): Mailbox init
failed top=0/0, retr=0/0, del=0/0, size=0

And the user gets:

[r...@nestorix ~]# telnet localhost pop3
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
+OK Dovecot ready.
user u...@mydomain.tld
+OK
pass mypwd
+OK Logged in.
-ERR Internal error occurred. Refer to server log for more information.
[2009-07-25 00:01:02]
-ERR [IN-USE] Couldn't sync mailbox.
Connection closed by foreign host.

This is my dovecot.conf

base_dir = /var/run/dovecot/
protocols = pop3 pop3s imap imaps
log_path = /var/log/dovecot
info_log_path = /var/log/dovecot
login_dir = /var/run/dovecot/login
login_chroot = yes
valid_chroot_dirs = /var/mail/vhosts
#login = imap
login_user = dovecot
login_process_size = 64
login_processes_count = 3
login_max_processes_count = 128
login_max_connections = 256
login_greeting = Havecom Mailserver ready.

mail_location = maildir:/var/mail/vhosts/%d/%n/

protocol imap {
 login_executable = /usr/libexec/dovecot/imap
 imap_max_line_length = 65536
 mail_plugin_dir = /usr/lib/dovecot/imap
 imap_client_workarounds = delay-newmail outlook-idle netscape-eoh
}

protocol pop3 {
 login_executable = /usr/libexec/dovecot/pop3-login
 mail_executable = /usr/libexec/dovecot/pop3
 pop3_no_flag_updates = no
 pop3_enable_last = no
 pop3_reuse_xuidl = no
 pop3_lock_session = no
 pop3_uidl_format = %08Xu%08Xv
 pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s
 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
}

auth_executable = /usr/libexec/dovecot/dovecot-auth
auth_process_size = 256
auth_cache_size = 0
auth_cache_ttl = 3600
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@
auth_username_translation = /$
auth_verbose = yes
auth default {
 socket listen {
  client {
   path = /var/spool/postfix/private/auth
   mode = 0660
   user = postfix
   group = postfix
  }
 }
 mechanisms = plain
 passdb passwd-file {
  args = /etc/dovecot/passwd
  }

 userdb passwd-file {
 args = /etc/dovecot/userdb
 }
 user = root
}



dovecot -n returns in:

[r...@nestorix etc]# dovecot -n
# 1.2.1: /usr/local/etc/dovecot.conf
Warning: There is no way to login to this server:
disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms.
Warning: There is no way to login to this server:
disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms.
# OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3
base_dir: /var/run/dovecot/
log_path: /var/log/dovecot
info_log_path: /var/log/dovecot
protocols: pop3 pop3s imap imaps
ssl: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap
login_executable(imap): /usr/libexec/dovecot/imap
login_executable(pop3): /usr/libexec/dovecot/pop3-login
login_greeting: Havecom Mailserver ready.
valid_chroot_dirs: /var/mail/vhosts
mail_location: maildir:/var/mail/vhosts/%d/%n/
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/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): 

Re: [Dovecot] lock files causing time outs with Thunderbird

2009-07-24 Thread CJ Keist


Yes, I'm talking about Trash.lock files, not seeing any errors in the 
log files related with lock files.


Yes, I am using dovecot deliver.  So does that mean I should not set 
mbox_very_dirty_syncs to yes?



Timo Sirainen wrote:

On Fri, 2009-07-24 at 15:55 -0600, CJ Keist wrote:
I have dovecot 1.1.16 running on Solaris 10.  We are seeing problem with 
lock files taking forever to be removed after opening a email folder 
like Trash with several thousand messages in them.  We use mbox format. 


You mean dotlock files (e.g. Trash.lock)? Does Dovecot log anything?


Is there something I can do in the config file to speed things up?


Are you using Dovecot deliver? If not, mbox_very_dirty_syncs=yes should
speed things up with large mboxes.



--
C. J. Keist Email: cj.ke...@colostate.edu
UNIX/Network ManagerPhone: 970-491-0630
Engineering Network ServicesFax:   970-491-5569
College of Engineering, CSU
Ft. Collins, CO 80523-1301

All I want is a chance to prove 'Money can't buy happiness'


Re: [Dovecot] lock files causing time outs with Thunderbird

2009-07-24 Thread Timo Sirainen
On Fri, 2009-07-24 at 16:25 -0600, CJ Keist wrote:
 Yes, I'm talking about Trash.lock files, not seeing any errors in the 
 log files related with lock files.

Can you look at what Dovecot is doing while those .lock files exist? You
can get the process pid from the .lock file and then do:

truss -d -p pid

And what process is it that's keeping those .lock files long? The same
imap process that's trying to open the mailbox?

 Yes, I am using dovecot deliver.  So does that mean I should not set 
 mbox_very_dirty_syncs to yes?

It means it shouldn't make a difference if it's set or not. But I guess
you could try if enabling it happens to help for some reason..



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


Re: [Dovecot] Several errors

2009-07-24 Thread Timo Sirainen
On Sat, 2009-07-25 at 00:07 +0200, FraNL wrote:
 Running OS: CentOS 5.3 (2.6.18-128.2.1.el5)
 
 1.
 My Linux distribution comes with Dovecot 1.0.7. After trying to make it
 running, I encoutnered many problems. So I decided to upgrade to 1.2.1.
 When running dovecot -r from CLI, it returns with version 1.2.1.
 But at the top of the log file it says: Info: Dovecot v1.0.7 starting up
 
 So I am not sure which version I am running.

It means you're using some weird mix of both. Get rid of all of Dovecot
v1.0 binaries (rpm -e dovecot or something) and your problems should go
away.



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


Re: [Dovecot] Several errors

2009-07-24 Thread A. van Harten
Tried that, same result.

dovecot: Jul 25 00:55:41 Info: Dovecot v1.0.7 starting up
dovecot: Jul 25 00:55:42 Error: Temporary failure in creating login
processes, slowing down for now
dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing
dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing
dovecot: Jul 25 00:55:42 Info: Created login processes successfully,
unstalling
dovecot: Jul 25 00:55:42 Error: child 3850 (login) returned error 89
dovecot: Jul 25 00:55:42 Error: child 3851 (login) returned error 89
dovecot: Jul 25 00:55:42 Error: Temporary failure in creating login
processes, slowing down for now
dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing
dovecot: Jul 25 00:55:42 Error: child 3852 (login) returned error 89
dovecot: Jul 25 00:55:42 Info: Created login processes successfully,
unstalling

[r...@nestorix etc]# dovecot -n
# 1.2.1: /usr/local/etc/dovecot.conf
Warning: There is no way to login to this server:
disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms.
Warning: There is no way to login to this server:
disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. #
OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3
base_dir: /var/run/dovecot/
log_path: /var/log/dovecot
info_log_path: /var/log/dovecot
protocols: pop3 pop3s imap imaps
ssl: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap
login_executable(imap): /usr/libexec/dovecot/imap
login_executable(pop3): /usr/libexec/dovecot/pop3-login
login_greeting: Havecom Mailserver ready.
valid_chroot_dirs: /var/mail/vhosts
mail_location: maildir:/var/mail/vhosts/%d/%n/
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/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/local/lib/dovecot/pop3
imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
imap_client_workarounds(pop3):
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
auth default:
  executable: /usr/libexec/dovecot/dovecot-auth
  username_translation: /$
  verbose: yes
  passdb:
driver: passwd-file
args: /etc/dovecot/passwd
  userdb:
driver: passwd-file
args: /etc/dovecot/userdb
  socket:
type: listen
client:
  path: /var/spool/postfix/private/auth
  mode: 432
  user: postfix
  group: postfix
[r...@nestorix etc]# service dovecot stop
Stopping Dovecot Imap: [  OK  ]
[r...@nestorix etc]# gedit /var/log/dovecot
[r...@nestorix etc]# service dovecot start
Starting Dovecot Imap: [  OK  ]
[r...@nestorix etc]# gedit /var/log/dovecot
^C

[r...@nestorix etc]# dovecot -n
# 1.2.1: /usr/local/etc/dovecot.conf
Warning: There is no way to login to this server:
disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms.
Warning: There is no way to login to this server:
disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. #
OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3
base_dir: /var/run/dovecot/
log_path: /var/log/dovecot
info_log_path: /var/log/dovecot
protocols: pop3 pop3s imap imaps
ssl: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap
login_executable(imap): /usr/libexec/dovecot/imap
login_executable(pop3): /usr/libexec/dovecot/pop3-login
login_greeting: Havecom Mailserver ready.
valid_chroot_dirs: /var/mail/vhosts
mail_location: maildir:/var/mail/vhosts/%d/%n/
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/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/local/lib/dovecot/pop3
imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
imap_client_workarounds(pop3):
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
auth default:
  executable: /usr/libexec/dovecot/dovecot-auth
  username_translation: /$
  verbose: yes
  passdb:
driver: passwd-file
args: /etc/dovecot/passwd
  userdb:
driver: passwd-file
args: /etc/dovecot/userdb
  socket:
type: listen
client:
  path: /var/spool/postfix/private/auth
  mode: 432
  user: postfix
  group: postfix
[r...@nestorix etc]#

Albert


[QUOTE] Timo Sirainen[/QUOTE]
 On Sat, 2009-07-25 at 00:07 +0200, FraNL wrote:
 Running OS: CentOS 5.3 (2.6.18-128.2.1.el5)

 1.
 My Linux distribution comes with Dovecot 1.0.7. After trying to 

Re: [Dovecot] Several errors

2009-07-24 Thread Timo Sirainen

On Jul 24, 2009, at 6:58 PM, A. van Harten wrote:


Tried that, same result.

dovecot: Jul 25 00:55:41 Info: Dovecot v1.0.7 starting up


If it's logging this, it means you have v1.0 binaries around. If rpm - 
e dovecot didn't remove it, something else will. I can't really help  
you there.


Anyway most likely the problem is that you have Dovecot v1.0 installed  
to /usr prefix (e.g. you have /usr/sbin/dovecot and /usr/lib/dovecot/)  
but v1.2 was installed to /usr/local prefix (e.g. /usr/local/sbin/ 
dovecot). And I guess you're starting Dovecot with /etc/init.d/ 
dovecot, which uses the /usr/sbin/dovecot instead of /usr/local/sbin/ 
dovecot..


Maybe it's easiest if you just do make uninstall in v1.2 source dir,  
and then install v1.2.1 rpm from http://atrpms.net/dist/el5/dovecot/




Re: [Dovecot] High Availability strategies

2009-07-24 Thread Timo Sirainen

On Jul 24, 2009, at 5:00 AM, Joseba Torre wrote:


we have a medium setup (8000 pop and imap users using almost every
available client, 800GB of stored mails using maildir on a Celerra NFS
server, with index files on local disks, and procmail for local
delivery), being served by a Dell PowerEdge 2850 (2GB RAM and dual P4
Xeon 3,2GHz).

Our current not-so-high availability setup is based on a similar
server with the same setup and a easy but manual process to switch
from one server to another.


So you currenly have a single server serving all imap/pop3 users?


- The recommended setup, with each user being sent always to the same
server, is not possible because our load balancers (Cisco Catalyst
6000) can't do that.

- We could put both servers behind the load balancer, and keep local
index files on each server. Usually the same ip we'll be redirected to
the same server, so few problems will arise. When a user is sent to a
new server, index will be rebuilt so performance will be bad but we
should not expect other problems, right?


If a single server can handle all users fine, I wouldn't try anything  
special here. Just have them work as a master/slave and install some  
kind of a heartbeat to switch between them.



- We could also put the index files on a nfs share. No problems, but
pretty bad performance.


If there's only a single server accessing the mails, you can use  
mail_nfs_*=no and the performance shouldn't be that bad.



- We could also get more ram for the servers and keep indices in
memory.


I'd say local disk is much better.


Using deliver instead of procmail could improve performance?


http://wiki.dovecot.org/LDA/Indexing


- We've also thought about some more or less weird setups, like
setting up a GFS filesystem for the index files, or setting up a proxy
on every server which redirect users to their fixed server, but they
seem too complex for few advantages.


Assuming still a master/slave setup, you could use DRBD to replicate  
indexes between local disks.


Re: [Dovecot] Several errors

2009-07-24 Thread Timo Sirainen

On Jul 24, 2009, at 8:19 PM, FraNL wrote:

If this message again appear as new message - my apologies, but then  
a bit

more info on how to reply on the mailing list would be appreciated.

The problem with the version number is solved.


Not really..


Solution:
1. # rpm -e dovecot
2. Remove manually all files and directories called dovecot or  
something

with dovecot in the name
3. Download http://www.dovecot.org/releases/1.2/dovecot-1.0.7.tar.gz
4. # tar -zxvf dovecot-1.0.7.tar.gz


Why did you now install 1.0.7, and from sources even? My suggestion:

rpm -e dovecot
find /usr -name 'dovecot*' | xargs rm -rf

Download v1.2.1 RPM from http://atrpms.net/dist/el5/dovecot/

Install it.


dovecot: Jul 25 01:59:55 Info: Dovecot v1.0.7 starting up
dovecot: Jul 25 01:59:56 Error: Temporary failure in creating login
processes, slowing down for now
dovecot: Jul 25 01:59:56 Error: imap-login: USER environment missing


The only reason why this error would happen is if you have mixed  
versions of Dovecot installed.


Re: [Dovecot] Several errors

2009-07-24 Thread Timo Sirainen

On Jul 24, 2009, at 8:40 PM, Timo Sirainen wrote:


dovecot: Jul 25 01:59:55 Info: Dovecot v1.0.7 starting up
dovecot: Jul 25 01:59:56 Error: Temporary failure in creating login
processes, slowing down for now
dovecot: Jul 25 01:59:56 Error: imap-login: USER environment missing


The only reason why this error would happen is if you have mixed  
versions of Dovecot installed.


Actually I was wrong here. The problem is this:


login_executable(imap): /usr/libexec/dovecot/imap


It needs to be imap-login, not imap.

In any case, I'd suggest using 1.2 and not 1.0.



Re: [Dovecot] Several errors

2009-07-24 Thread Timo Sirainen

On Jul 24, 2009, at 8:19 PM, FraNL wrote:


dovecot: Jul 25 02:00:26 Error: POP3(u...@mydomain.tld):
file_dotlock_open() failed with file
/var/mail/vhosts/mydomain.tld/user/dovecot.index.log: Permission  
denied

dovecot: Jul 25 02:00:26 Error: POP3(u...@mydomain.tld):
file_dotlock_open(/var/mail/vhosts/mydomain.tld/user/dovecot-uidlist)
failed: Permission denied


The directory/files are owned by wrong user, or you have set wrong  
user to userdb. v1.2 gives better error messages here.

http://wiki.dovecot.org/UserIds