Re: dovecot/config processes open, and consuming all memory
currently the client_limt is at zero, and I believe this is unlimited
service config {
chroot =
client_limit = 0
drop_priv_before_exec = no
executable = config
extra_groups =
group =
idle_kill = 1 mins
privileged_group =
process_limit = 0
process_min_avail = 16
protocol =
service_count = 100
type = config
unix_listener config {
group =
mode = 0600
user =
}
user =
vsz_limit = 2 G
}
On 16/08/2022 18:06, Aki Tuomi wrote:
Can you try increasing client_limit for service config, to maybe, say, 1000?
There should be no reason to have lots of multiple config processes, so it
sounds more like the client limit is being reached.
Re: dovecot/config processes open, and consuming all memory
The only thing I had initially configured was vsz_limit, but as the
number of clients grew, the number of dovecot/config processes grew, and
with that I added idle_kill and service_count to try to minimize the use
of ram memory
In dovecot 2.2.33.2 , another server, has the same amount of accounts (+
or -30 thousand) but there is only one dovecot/config process and every
dovecot does not consume more than 5Gb
On 16/08/2022 06:20, Aki Tuomi wrote:
On 16/08/2022 03:40 EEST Joseph Tam wrote:
I'm having strange behavior in dovecot 2.3.16.
It's opening dozens of dovecot/config process and consuming all server
memory. Normally each process consumes between 700Mb and 1Gb of ram.
Would anyone have an idea about this?
service config {
vsz_limit = 2048M
idle_kill = 60s
service_count = 1024
}
Not sure it's related, but if you have service_count not 0 or 1, there
is a strange interaction
with other limits that could cause processes to hang around. My
description of problem
https://www.mail-archive.com/dovecot%40dovecot.org/msg85850.html
Your situation is slgihtly different (service not imap_login, and
idle_kill timeout should reduce
lingering processes that caused my problem), but try setting
service_limit to either 0 or
1 and see if your problem goes away, or gets worse.
You can also see how many file descriptors are being held by the
config process, and
see the behaviour over time (e.g. monitor /proc/{pid}/fd/*); maybe
that will give you a clue
as to what the config process is doing.
Joseph Tam
The *default* configuration for service config is usually just fine. Is there
some reason you decided to modify it in first place?
Aki
Re: dovecot/config processes open, and consuming all memory
Hello,
I tested the suggestion to decrease the service_count and the accounts
stopped logging in, then I gradually increased it to 500, and now it's
working. But the dovecot/config processes are still being created, there
has been no change for the better.
Now I have an error constantly appearing in the mail.err file
Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error reading
configuration: read(/run/dovecot/config) failed: read(size=8192) failed:
Interrupted system call - Also failed to read config by executing
doveconf: /run/dovecot/config is a UNIX socket (path is from CONFIG_FILE
environment)
Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error reading
configuration: read(/run/dovecot/config) failed: read(size=8192) failed:
Interrupted system call - Also failed to read config by executing
doveconf: /run/dovecot/config is a UNIX socket (path is from CONFIG_FILE
environment)
Aug 15 14:19:34 box6 dovecot: imap(USER_NAME): Error: Error reading
configuration: read(/run/dovecot/config) failed: read(size=8192) failed:
Interrupted system call - Also failed to read config by executing
doveconf: /run/dovecot/config is a UNIX socket (path is from CONFIG_FILE
environment)
On 14/08/2022 22:24, John Stoffel wrote:
"filipe@digirati" == filipe@digirati com br writes:
filipe@digirati> I'm having strange behavior in dovecot 2.3.16.
filipe@digirati> It's opening dozens of dovecot/config process and consuming
all server
filipe@digirati> memory. Normally each process consumes between 700Mb and 1Gb
of ram.
filipe@digirati> Would anyone have an idea about this?
filipe@digirati> service config {
filipe@digirati> vsz_limit = 2048M
filipe@digirati> idle_kill = 60s
filipe@digirati> service_count = 1024
filipe@digirati> }
I wonder why you have the service count so high? I'd drop it down, or
do you really have 1025 connections in 60 seconds?
From the docs:
service_count
Number of client connections to handle until the process kills
itself. 0 means unlimited. 1 means only a single connection is handled
until the process is stopped - this is the most secure choice since
there’s no way for one connection’s state to leak to the next one. For
better performance this can be set higher, but ideally not unlimited
since more complex services can have small memory leaks and/or memory
fragmentation and the process should get restarted eventually. For
example 100..1000 can be good values.
So maybe drop it down to 100 for now and see how that works for you.
filipe@digirati> pstree
filipe@digirati> systemd─┬─ModemManager───2*[{ModemManager}]
filipe@digirati> ├─agetty
filipe@digirati> ├─cron
filipe@digirati> ├─dbus-daemon
filipe@digirati> ├─dovecot─┬─anvil
filipe@digirati> │ ├─6*[auth]
filipe@digirati> │ ├─46*[config]
filipe@digirati> │ ├─1212*[imap]
filipe@digirati> │ ├─155*[imap-login]
filipe@digirati> │ ├─12*[lmtp]
filipe@digirati> │ ├─38*[log]
filipe@digirati> │ ├─10*[managesieve]
filipe@digirati> │ ├─19*[pop3]
filipe@digirati> │ ├─3*[pop3-login]
filipe@digirati> │ └─18*[stats]
filipe@digirati> root 45831 0.0 1.1 774688 752732 ? S 09:31
0:31
filipe@digirati> dovecot/config
filipe@digirati> root 388792 0.0 1.1 775060 753276 ? S 14:00
0:15
filipe@digirati> dovecot/config
filipe@digirati> root 510685 0.0 1.1 775384 753604 ? S 15:06
0:20
filipe@digirati> dovecot/config
filipe@digirati> root 675638 0.0 1.1 775348 753620 ? S 16:56
0:15
filipe@digirati> dovecot/config
filipe@digirati> root 795375 0.0 1.1 775460 753516 ? S 18:03
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 798754 0.2 1.1 775592 753712 ? S 18:05
0:30
filipe@digirati> dovecot/config
filipe@digirati> root 1082696 0.2 1.1 774892 753216 ? S 21:10
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1098433 0.4 1.1 774924 753244 ? S 21:33
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1109255 0.9 1.1 774924 753344 ? S 21:50
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1112976 2.0 1.1 774956 753528 ? S 21:57
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1114137 3.0 1.1 775028 753308 ? S 21:59
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1115382 5.4 1.1 774924 753496 ? S 22:01
0:06
filipe@digirati> dovecot/config
filipe@digirati> root 1883627 0.0 1.1 759120 728832 ? S Aug11
0:07
filipe@digirati> dovecot/config
filipe@digirati> root 1889705 0.0 1.8 1251460 1221872 ? S Aug11
0:11
filipe@digirati> dovecot/config
filipe@digirati> root 1895022 0.0 1.8
dovecot/config processes open, and consuming all memory
I'm having strange behavior in dovecot 2.3.16.
It's opening dozens of dovecot/config process and consuming all server
memory. Normally each process consumes between 700Mb and 1Gb of ram.
Would anyone have an idea about this?
service config {
vsz_limit = 2048M
idle_kill = 60s
service_count = 1024
}
pstree
systemd─┬─ModemManager───2*[{ModemManager}]
├─agetty
├─cron
├─dbus-daemon
├─dovecot─┬─anvil
│ ├─6*[auth]
│ ├─46*[config]
│ ├─1212*[imap]
│ ├─155*[imap-login]
│ ├─12*[lmtp]
│ ├─38*[log]
│ ├─10*[managesieve]
│ ├─19*[pop3]
│ ├─3*[pop3-login]
│ └─18*[stats]
root 45831 0.0 1.1 774688 752732 ? S 09:31 0:31
dovecot/config
root 388792 0.0 1.1 775060 753276 ? S 14:00 0:15
dovecot/config
root 510685 0.0 1.1 775384 753604 ? S 15:06 0:20
dovecot/config
root 675638 0.0 1.1 775348 753620 ? S 16:56 0:15
dovecot/config
root 795375 0.0 1.1 775460 753516 ? S 18:03 0:07
dovecot/config
root 798754 0.2 1.1 775592 753712 ? S 18:05 0:30
dovecot/config
root 1082696 0.2 1.1 774892 753216 ? S 21:10 0:07
dovecot/config
root 1098433 0.4 1.1 774924 753244 ? S 21:33 0:07
dovecot/config
root 1109255 0.9 1.1 774924 753344 ? S 21:50 0:07
dovecot/config
root 1112976 2.0 1.1 774956 753528 ? S 21:57 0:07
dovecot/config
root 1114137 3.0 1.1 775028 753308 ? S 21:59 0:07
dovecot/config
root 1115382 5.4 1.1 774924 753496 ? S 22:01 0:06
dovecot/config
root 1883627 0.0 1.1 759120 728832 ? S Aug11 0:07
dovecot/config
root 1889705 0.0 1.8 1251460 1221872 ? S Aug11 0:11
dovecot/config
root 1895022 0.0 1.8 1253280 1224284 ? S Aug11 0:11
dovecot/config
root 1900690 0.0 1.8 1255684 1227528 ? S Aug11 0:12
dovecot/config
root 1905648 0.0 1.8 1257880 1229912 ? S Aug11 0:12
dovecot/config
root 1910857 0.0 1.8 1259156 1231552 ? S Aug11 0:12
dovecot/config
root 1914332 0.0 1.1 764328 736552 ? S Aug11 0:20
dovecot/config
root 2343896 0.0 1.8 1259472 1231516 ? S Aug11 0:12
dovecot/config
root 2346351 0.0 1.8 1259472 1231836 ? S Aug11 0:13
dovecot/config
root 2348559 0.0 1.1 764704 736440 ? S Aug11 0:14
dovecot/config
root 2445701 0.0 1.1 764276 736540 ? S Aug11 0:19
dovecot/config
root 2572525 0.0 1.1 764640 736880 ? S Aug11 0:18
dovecot/config
root 2734251 0.0 1.1 764776 737696 ? S Aug11 0:08
dovecot/config
root 2740980 0.0 1.1 764768 737244 ? S Aug11 0:17
dovecot/config
root 2899925 0.0 1.1 764624 737760 ? S Aug11 0:43
dovecot/config
root 3517063 0.0 1.1 764984 738004 ? S Aug11 0:09
dovecot/config
root 3541465 0.0 1.1 765224 738756 ? S Aug11 0:07
dovecot/config
root 3545589 0.0 1.1 766452 740408 ? S Aug11 0:06
dovecot/config
root 3549259 0.0 1.1 766796 741048 ? S Aug11 0:07
dovecot/config
root 3553902 0.0 1.1 767812 742284 ? S Aug11 0:07
dovecot/config
root 3558080 0.0 1.1 768440 743524 ? S Aug11 0:08
dovecot/config
root 3562091 0.0 1.1 769224 744424 ? S Aug11 0:07
dovecot/config
root 3568721 0.0 1.1 769388 744888 ? S Aug11 0:07
dovecot/config
root 3573024 0.0 1.1 770048 745904 ? S Aug11 0:08
dovecot/config
root 3578416 0.0 1.1 770836 746736 ? S Aug11 0:06
dovecot/config
root 3581765 0.0 1.1 771948 748492 ? S Aug11 0:06
dovecot/config
root 3585837 0.0 1.1 772828 749860 ? S Aug11 0:07
dovecot/config
root 3590276 0.0 1.1 773560 750520 ? S Aug11 0:07
dovecot/config
root 3594640 0.0 1.1 774612 752552 ? S Aug11 0:08
dovecot/config
root 3597417 0.0 1.1 774968 753076 ? S Aug11 0:35
dovecot/config
root 4116314 0.0 1.9 1280496 1258580 ? S 05:31 0:13
dovecot/config
root 4118115 0.0 1.1 774688 752556 ? S 05:33 0:16
dovecot/config
Re: Error: conn unix:/run/dovecot/stats-writer : Timeout waiting for handshake response
soon after starting dovecot these errors start to appear. I will send the first errors after doing a service dovecot start Jul 15 10:08:16 box5 dovecot: pop3: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: auth: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: lmtp: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response ul 15 10:08:16 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: message repeated 5 times: [ imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response] Jul 15 10:08:16 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: message repeated 4 times: [ imap: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response] Jul 15 10:08:16 box5 dovecot: managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: message repeated 3 times: [ managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response] Jul 15 10:08:16 box5 dovecot: lmtp: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: lmtp: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: lmtp: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: pop3: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: lmtp: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: message repeated 2 times: [ lmtp: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response] Jul 15 10:08:16 box5 dovecot: pop3: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: message repeated 6 times: [ pop3: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response] Jul 15 10:08:16 box5 dovecot: managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake response Jul 15 10:08:16 box5 dovecot: managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=4137823,uid=0): Timeout waiting for handshake respon
Error: conn unix:/run/dovecot/stats-writer : Timeout waiting for handshake response
Hi, I'm using ubuntu 22.04 and installed dovecot 2.3.16. I did some initial testing with 100 email accounts and everything seemed to work perfectly the same as dovecot version 2.3.16 on another server. So I performed the migration of approximately 30 thousand email accounts, but the following error started to appear and I know well what to do: Jul 14 18:55:29 box5 dovecot: pop3: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response Jul 14 18:55:29 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response Jul 14 18:55:29 box5 dovecot: managesieve: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response Jul 14 18:55:29 box5 dovecot: lmtp: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response Jul 14 18:55:29 box5 dovecot: imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response Jul 14 18:55:29 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response Jul 14 18:55:29 box5 dovecot: imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response Jul 14 18:55:29 box5 dovecot: message repeated 3 times: [ imap-login: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response] Jul 14 18:55:29 box5 dovecot: imap: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response Jul 14 18:55:29 box5 dovecot: message repeated 2 times: [ imap: Error: conn unix:/run/dovecot/stats-writer (pid=3733995,uid=0): Timeout waiting for handshake response] Permissions on files 79411 srw--- 1 root root 0 Jul 14 18:55 stats-reader 79412 srw-rw 1 root dovecot 0 Jul 14 18:55 stats-writer Does anyone know anything about this problem that can help me?
email migration of mdbox to sdbox with set index in mail_location
Hello, my name is Filipe I'm migrating an email server to another new server. Accounts have their storage configured as mdbox and their index being saved in another storage device. I want to migrate all messages to the new server with a new storage mode, sdbox. The new server will have storage settings set to sdbox for email accounts: In dovecot's doc it says mdbox mode is the only one that supports index storage on another device. https://doc.dovecot.org/admin_manual/mailbox_formats/dbox/#layout /"Index files can be stored in a different location by using the INDEX parameter in the mail location specification. If the INDEX parameter is specified, it will override the root mail location for index files and the "map index" file (mdbox only). "/ Even with this warning I performed the migration of some accounts as a test. running the commands from server A to server B. "Server A" conf: dovecot version: 2.2.33.2 /mail_location: mdbox:/var/spool/imap/test=x.com:INDEX=/var/lib/imap/user/test=x.com/ "Server B" conf: dovecot version: 2.3.7.2 /mail_location: sdbox:/var/spool/imap/test=x.com:INDEX=/var/lib/imap/user/test=x.com/ command executed on server A to execute message migration: /root@serverA: ~# doveadm sync -u test=x.com ssh root@*serverB* doveadm dsync-server -u test=x.com/ In the end, the message migration was successful and the access to the email account worked normally on server B. The question is whether dovecot has this support to move the index when I use the sdbox? Thank you for your help
Re: [Dovecot] POP3/IMAP newbie question
[EMAIL PROTECTED] wrote: Lars Stavholm wrote: Well, as a matter of being somewhat relaxed about things like this, I would like the users to choose whatever suits them, as opposed to some techie moron (me) making the choice for them. Common sense, right? Actually, from my experience, a user will do whatever the techie tells them, because they don't really know the difference...I've forcibly moved users on my server to IMAP, and they didn't realize until then how much better it was than POP3 Some of my users have (and really want to continue) over 10Gb of email. And that is growing. I do prefer these users on POP3, so they are on their own with all that. Just an example... FiL
Re: [Dovecot] Migration to Dovecot
How much mail do you have to migrate? Do you convert mbox to Maildir? Please, let us know how did it go. Good luck with it!!! FiL Frank Bonnet wrote: Hello all Tomorrow is the day , I'm gonna migrate all our mailboxes and imap folders from our old mailhub to the new one. In the same time I will migrate from UW to Dovecot , I've read all the stuff about it on the Dovecot web site. I have one question , do I have to care about the .imap cache directory created by Dovecot in any way or will it be "all automatic" when starting Dovecot ? Many thanks
Re: [Dovecot] Running a dovecot IMAPS server
Charles Marcus wrote: On 9/21/2007, FiL @ Kpoxa ([EMAIL PROTECTED]) wrote: I know this is totally unrelated to this topic, but... Is there any extension to create and use templates? ? Just 'Save as' > Template... Save as Template just save a message, but it doesn't allow you to use variables, use different templates, based on the action (reply, forward, new) and so on. I don't like " wrote:" in my reply messages and would prefer some custom templates, that would be different for different accounts. Oh... maybe you meant 'custom quote line' instead of 'template'? Quickquote can do this to an extent (not to mention its killer, couldn't-live-without-it feature, 'Quote only selected text')... I want something, that would allow me to do this - 1) different custom quote lines and different rules of using either full quote or just the latest message in the thread, based on the account I'm using (I have 4 accounts configured in TB) 2) I want custom quote line, that would have date and time of the message am replying to. Something like "On %DATE% %SENDER% wrote:" 3) I want cursor positioned AFTER quoted message automatically. Most of the FIDO mailers back in 1990 had this functionality. I've seen some kind of Outlook Express add-on, that had something like that. But there is nothing current and nothing that works with TB. Well, anyway, thank you for trying to help. FiL
Re: [Dovecot] Running a dovecot IMAPS server
Charles Marcus wrote: 1. No proper 'Signature Manager' (yes, I've seen and used the Signature extensions (Signature, Signature Switch, etc), but they still require you to manually create the sigs first. This is a *glaring* lack in my opinion... 2. Monolithic message storage... this is still a biggie to me, but I can live with it... I know this is totally unrelated to this topic, but... Is there any extension to create and use templates? I don't like "name> wrote:" in my reply messages and would prefer some custom templates, that would be different for different accounts. Thanks, FiL
Re: [Dovecot] Running a dovecot IMAPS server
Timothy Murphy wrote: I don't use KMail on my desktop, except as an experiment, but when I do there do not appear to be any problems. My Local folders are kept in directories ~/Mail/Folder1/[cur,new,tmp[/ and are not seen by IMAPS. My IMAPS folders are kept in directories ~/Maildir/.Folder2/[cur,new,tmp]/ and are not seen my kmail. If Local folders are under ~/Mail/ - this is OK. But you were saying your local messages are under ~/Maildir/ - the same as dovecot-accessed. And this is wrong. This might be working fine, but still, this is wrong. FiL
Re: [Dovecot] What is your dovecot setup?
Timothy Murphy wrote:
Surely it would take far less time to give your actual setup
than it would to explain (at length) how easy it is to set it up ...
Here is my server directory setup:
~/Maildir/[cur,new,tmp], ~/Maildir/.Family/[cur,new,tmp], etc.
My dovecot.conf sets
mail_location = maildir:~/Maildir/
My .procmailrc sets
MAILDIR=/var/spool/mail
DEFAULT=$HOME/Maildir/
I cannot see the Family folder from my IMAPS client.
Also it complains of the lack of .INBOX.directory
("Could Not Determine Resource Status").
Now we are talking. Not some useless "give me your setup", but "here
what I have, and I have a problem".
Several questions to follow:
1. Have you tried IMAP (not imaps)? This shouldn't be a problem, but
still worth checking.
2. "I cannot see the Family folder" means you can not see it in the list
of all folders? in the list of subscribed folders? can not access it?
3. How did you CREATE that "Family" folder? manually on the server or
from the IMAP client?
3.1. Can you create a folder from the client?
3.2. If you can create one, can you see it? Can you access it? Can you
put messages into it? All from within IMAP clent.
4. Have you tried another client (you are using kmail, AFAIR), like
Thunderbird? If not, try it.
I might have more questions for you later depending on your answers.
P.S. Forget about procmail for now.
P.P.S. I have very simple config like yours on one of my servers (no
procmail) and IMAPS works fine.
FiL
Re: [Dovecot] Migration woes from tpop mbox to dovecot maildir
Chris Richardson wrote: I was hoping some one might be able to offer me some advice on a little problem I have. I am looking to A. move from mbox to maildir B. looking to move from tpop to dovecot to bring both pop and imap under the same program. anyways the problem I am having is this tpop3d mbox uses MD5 sum of the mailbox headers in hex which is option %m in the uidl section but the problem is when dovecot convert plugin runs and makes in a maildir it fails to find the md5 of this because it is only used for mboxs. if I change this from %m to %Mf it downloads every message on the clients computer which is not desirable. I was thinking only options i have is to allow it to download all them mail and or write a script to convert it to maildir or another pop servers uidl. but i dont know much about how other pop servers generate there headers. so I was hoping maybe some one has done something similar to this or could offer some input. thanks -Chris I have the very same problem. The only difference is that I have already migrated to dovecot and using mbox for both pop3 and imap. Am still looking for the good solution to migrate to Maildir without making my clients re-download all their mail (they won't get dups with imap, but downloading gigabytes of mail isn't good idea either. Timo suggested writing a script that would create dovecot-uidlist files for every mailbox with old-style (%m in your case) UIDs during migration and that makes perfect sense to me. However I'm really bad with programming and cat rely on my own script for such an important task. P.S. not sure how dovecot handles pop3 UID's. In my case I need preserving UIDs in imap-to-imap (mbox-to-Maildir) migration. FiL
Re: [Dovecot] mbox vs maildir
The last time I tried to convert from mbox to maildir, things got pretty botched up, no data loss, but it wasn't pretty. :-) just because you got it wrong doesn't make it's hard. you probably didn't take enough time to get it right. Well, if you know the RIGHT way - just share it with the rest of us. I was asking Timo before and as far as I understood - there is no way of converting mbox to Maildir without losing message UIDs. And given that we already have huge mailboxes, that means that every user, connecting to the server after the conversion will need to redownload all the messages and delete all the messages in the local cache. Just imagine that user with ~5Gb of mail across 5-10 folders connect from home not-so-fast DSL line to check email and has to wait until the client rechecks all the mail No, this is not right. Exactly as Don Russell wrote - "no data loss, but it isn't pretty". And this is the only reason I don't migrate to Maildir. I really want to do it, but this is not something I can do to my users. FiL
Re: [Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
Timo Sirainen wrote: On Fri, 2007-05-25 at 14:36 -0400, FiL wrote: > This is not only about POP3, as far as I can tell. If you > converting mbox to Maildir (dovecot to dovecot) - UIDs change. And > if you have your client set to cache all the messages and you have > over 1Gb in your mail... well, it will be transferring all your > mail again. Deleting the old one (as it is not on the server > anymore) and re-downloading new ones. Right. But it's not as bad as with POP3 where the messages are downloaded as duplicates. It's pretty bad if you trying to check your mail over the slow connection (and some users do that). Also at least 1/3 of my users have 100Mb just in the inbox and much more in other mailboxes. And I know, that server just wouldn't handle the load the first day after migration. > I have all my mbox-es in /raid/mbox/%u I have set convert_mail = > mbox:/raid/mbox/%u:INBOX=/var/mail/%u in the dovecot.conf. But for > some reason the folder with mail doesn't get renamed after > conversion. Is that the way it should be? And the destination isn't /raid/mbox/%u? It should have renamed the %u to %u-converted. The destination is /raid/Maildir/%u/ but the original folder doesn't get renamed. I will play with it a little more and let you know the details. FiL
Re: [Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
Timo Sirainen wrote: On 24.5.2007, at 22.22, Eric and Barbara Sammons wrote: I am running dovecot 0.99. Everything works great; however, now I am looking at several different tools to convert mbox to Maildir. It seems the tools, mb2md.pl, perfect_maildir.pl, and others all do what they claim; however, when the messages are converted and they are stored in Maildir/cur, the email clients download these messages as new. I guess you're talking about POP3. You'd need to be able to preserve the POP3 UIDLs (see http://wiki.dovecot.org/Migration), which would require that you also preserve the IMAP UIDs in the mbox -> Maildir switch. Unfortunately I'm not aware of any scripts that preserves the UIDs, although it wouldn't be difficult to write support for that. This is not only about POP3, as far as I can tell. If you converting mbox to Maildir (dovecot to dovecot) - UIDs change. And if you have your client set to cache all the messages and you have over 1Gb in your mail... well, it will be transferring all your mail again. Deleting the old one (as it is not on the server anymore) and re-downloading new ones. It would be nice to have Convert plugin, that preserves UIDs and UIDVALIDITY values. P.S. A little unrelated question about convert plugin. I have all my mbox-es in /raid/mbox/%u I have set convert_mail = mbox:/raid/mbox/%u:INBOX=/var/mail/%u in the dovecot.conf. But for some reason the folder with mail doesn't get renamed after conversion. Is that the way it should be? Of course, it tries to convert the same boxes next time I log in. FiL
Re: [Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
Timo Sirainen wrote: On 24.5.2007, at 22.22, Eric and Barbara Sammons wrote: I am running dovecot 0.99. Everything works great; however, now I am looking at several different tools to convert mbox to Maildir. It seems the tools, mb2md.pl, perfect_maildir.pl, and others all do what they claim; however, when the messages are converted and they are stored in Maildir/cur, the email clients download these messages as new. I guess you're talking about POP3. You'd need to be able to preserve the POP3 UIDLs (see http://wiki.dovecot.org/Migration), which would require that you also preserve the IMAP UIDs in the mbox -> Maildir switch. Unfortunately I'm not aware of any scripts that preserves the UIDs, although it wouldn't be difficult to write support for that. This is not only about POP3, as far as I can tell. If you converting mbox to Maildir (dovecot to dovecot) - UIDs change. And if you have your client set to cache all the messages and you have over 1Gb in your mail... well, it will be transferring all your mail again. Deleting the old one (as it is not on the server anymore) and re-downloading new ones. It would be nice to have Convert plugin, that preserves UIDs and UIDVALIDITY values. P.S. A little unrelated question about convert plugin. I have all my mbox-es in /raid/mbox/%u I have set convert_mail = mbox:/raid/mbox/%u:INBOX=/var/mail/%u in the dovecot.conf. But for some reason the folder with mail doesn't get renamed after conversion. Is that the way it should be? Of course, it tries to convert the same boxes next time I log in. FiL
