[Dovecot] Installing Dovecot v2.0.3 from binary files problem
Hi, I've installed dovecot v2.0.13 from binary files.dovecote starts ok,but I get some errors in /var/run/mail.log : dovecot: anvil: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: EOF dovecot: master: Error: service(anvil): command startup failed, throttling dovecot: master: Error: service(config): child 8606 killed with signal 11 (core dumps disabled) dovecot: master: Error: service(config): command startup failed, throttling dovecot: ssl-params: Fatal: Error reading configuration: read(/var/run/dovecot/config) failed: Connection reset by peer And I've just used example configure files of dovecot. Regards, Meisam Navaki. System Programmer, Bayan Co.
Re: [Dovecot] LDAP timeout
Hi, Fallbacking to another LDAP server is done by OpenLDAP internally. So what would be needed is either a) OpenLDAP to itself figure out that queries are running too slowly and see if another server is faster, or b) Dovecot figure that out itself and force OpenLDAP to switch to another server. I don't know if either of them is possible with OpenLDAP API as it is. I doubt it. You can set a timelimit for a search, but I'm not exactly sure what happens when you specified multiple servers. Maybe the query gets restarted on the next server, maybe it fails. Still doing that (with logging) would be better than hanging there for several minutes. If it completely aborts the query, a workaround would be to use more than one ldap passdb with one server each, no? Bernhard
[Dovecot] ldapsearch dump for passwd file: base64 encoded passwords
hi, is there a way, to let Dovecot2 uses the base64 encoded passwords from a ldapsearch output, without decode them first? cu denny signature.asc Description: This is a digitally signed message part
[Dovecot] [Urgent] Email Retrieval from remote servers doesn't use Dovecot
Dovecot Version:
2.0.13
Output of dovecot -n:
# 2.0.13: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.35-28-generic x86_64 Ubuntu 10.10 ext4
mail_location = maildir:/home/%u/Maildir
passdb {
args = %s
driver = pam
}
protocols = imap pop3
ssl = no
userdb {
driver = passwd
}
protocol imap {
imap_client_workarounds = tb-extra-mailbox-sep
}
protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
}
---
Objective:
---
We need to download emails from remote server using Dovecot and
thunderbird. Our objective is to store emails in maildir or mbox format,
and process them as part of our research project.
---
Problem:
---
Dovecot works for localhost, but not for remote servers. How do I know?
Because thunderbird downloads emails in its default location (specified in
settings) and not in maildir or mbox folders. If I send mail to
user@system_name using mail command, dovecot works and thunderbird
shows the email stored in maildir folder. But for email from
id@yahoo.com goes to thunderbird's default folder and are browsed from
there.
---
Relevant Technical Details:
---
ps auxw|grep dovecot\|imap\|pop3
root 1033 0.0 0.0 52796 1916 ?Ss 12:45 0:00
/usr/sbin/dovecot -F -c /etc/dovecot/dovecot.conf
root 1173 0.0 0.0 75096 3284 ?S12:45 0:00 dovecot-auth
root 1214 0.0 0.0 75188 3424 ?S12:45 0:00
dovecot-auth -w
dovecot 8356 0.0 0.0 50528 2692 ?S13:30 0:00 pop3-login
dovecot 8357 0.0 0.0 50528 2692 ?S13:30 0:00 pop3-login
dovecot 8358 0.0 0.0 50528 2688 ?S13:30 0:00 pop3-login
dovecot 8359 0.0 0.0 50528 2688 ?S13:30 0:00 pop3-login
dovecot 8360 0.0 0.0 50528 2688 ?S13:30 0:00 pop3-login
dovecot 8364 0.0 0.0 50540 2688 ?S13:30 0:00 imap-login
dovecot 8375 0.0 0.0 50540 2692 ?S13:30 0:00 imap-login
dovecot 8378 0.0 0.0 50540 2684 ?S13:30 0:00 imap-login
shaz 9048 0.0 0.0 8956 864 pts/0S+ 15:06 0:00 grep
--color=auto dovecot\|imap\|pop3
sudo netstat -lnptu
[sudo] password for shaz:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp0 0 0.0.0.0:110 0.0.0.0:* LISTEN
1033/dovecot
tcp0 0 0.0.0.0:143 0.0.0.0:* LISTEN
1033/dovecot
tcp0 0 0.0.0.0:64277 0.0.0.0:* LISTEN
2068/skype
tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN
1295/cupsd
tcp0 0 0.0.0.0:25 0.0.0.0:* LISTEN
1389/master
tcp0 0 0.0.0.0:993 0.0.0.0:* LISTEN
1033/dovecot
tcp0 0 0.0.0.0:995 0.0.0.0:* LISTEN
1033/dovecot
tcp6 0 0 ::1:631 :::*LISTEN
1295/cupsd
udp0 0 127.0.0.1:45902 0.0.0.0:*
2068/skype
udp0 0 0.0.0.0:33754 0.0.0.0:*
1065/avahi-daemon:
udp0 0 0.0.0.0:53530.0.0.0:*
1065/avahi-daemon:
udp0 0 0.0.0.0:68 0.0.0.0:*
2132/dhclient
udp0 0 0.0.0.0:64277 0.0.0.0:*
2068/skype
udp6 0 0 :::5353 :::*
1065/avahi-daemon:
udp6 0 0 :::50994:::*
1065/avahi-daemon:
sudo lsof -i | grep LISTEN
dovecot 1033root6u IPv4 7578 0t0 TCP *:imap2 (LISTEN)
dovecot 1033root7u IPv4 7579 0t0 TCP *:imaps (LISTEN)
dovecot 1033root9u IPv4 7580 0t0 TCP *:pop3 (LISTEN)
dovecot 1033root 10u IPv4 7581 0t0 TCP *:pop3s (LISTEN)
cupsd 1295root5u IPv6 7932 0t0 TCP Casper:ipp (LISTEN)
cupsd 1295root6u IPv4 7933 0t0 TCP
localhost.localdomain:ipp (LISTEN)
master1389root 12u IPv4 9284 0t0 TCP *:smtp (LISTEN)
skype 2068shaz 67u IPv4 18344 0t0 TCP *:64277 (LISTEN)
pop3-logi 8356 dovecot4u IPv4 7580 0t0 TCP *:pop3 (LISTEN)
pop3-logi 8356 dovecot5u IPv4 7581 0t0 TCP *:pop3s (LISTEN)
pop3-logi 8357 dovecot4u IPv4 7580 0t0 TCP *:pop3 (LISTEN)
pop3-logi 8357 dovecot5u IPv4 7581 0t0 TCP *:pop3s (LISTEN)
pop3-logi 8358 dovecot4u IPv4 7580 0t0 TCP *:pop3 (LISTEN)
pop3-logi 8358 dovecot5u IPv4 7581 0t0 TCP
Re: [Dovecot] Problem accessing Dovecot mailing lists via IMAP
Am Dienstag, den 28.06.2011, 11:54 +0100 schrieb William Blunn: Any ideas? I guess its not working at the moment. CAPABILITY says LOGINDISABLED and AUTH=ANONYMOUS. If the client does not support this auth method, authentication is denied because login is disabled and starttls or ssl to get AUTH PLAIN or AUTH LOGIN is not enabled. Guess configuration does not match the documentation. At least it does not work for me too because my client does not support AUTH ANONYMOUS. Torsten smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] [Urgent] Email Retrieval from remote servers doesn't use Dovecot
Hi,
What makes you think that e-mail retrieval from remote servers should
be over Dovecot?
Is 193.40.5.156 running Dovecot that it should say Dovecot ready. ?
I think what you need fetchmail or getmail. Dovecot is a MTA, not a MRA.
Best,
Kerem
On Wed, Jun 29, 2011 at 3:19 PM, Shazia Javed sha...@ut.ee wrote:
Dovecot Version:
2.0.13
Output of dovecot -n:
# 2.0.13: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.35-28-generic x86_64 Ubuntu 10.10 ext4
mail_location = maildir:/home/%u/Maildir
passdb {
args = %s
driver = pam
}
protocols = imap pop3
ssl = no
userdb {
driver = passwd
}
protocol imap {
imap_client_workarounds = tb-extra-mailbox-sep
}
protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
}
---
Objective:
---
We need to download emails from remote server using Dovecot and
thunderbird. Our objective is to store emails in maildir or mbox format,
and process them as part of our research project.
---
Problem:
---
Dovecot works for localhost, but not for remote servers. How do I know?
Because thunderbird downloads emails in its default location (specified in
settings) and not in maildir or mbox folders. If I send mail to
user@system_name using mail command, dovecot works and thunderbird
shows the email stored in maildir folder. But for email from
id@yahoo.com goes to thunderbird's default folder and are browsed from
there.
---
Relevant Technical Details:
---
ps auxw|grep dovecot\|imap\|pop3
root 1033 0.0 0.0 52796 1916 ? Ss 12:45 0:00
/usr/sbin/dovecot -F -c /etc/dovecot/dovecot.conf
root 1173 0.0 0.0 75096 3284 ? S 12:45 0:00 dovecot-auth
root 1214 0.0 0.0 75188 3424 ? S 12:45 0:00
dovecot-auth -w
dovecot 8356 0.0 0.0 50528 2692 ? S 13:30 0:00 pop3-login
dovecot 8357 0.0 0.0 50528 2692 ? S 13:30 0:00 pop3-login
dovecot 8358 0.0 0.0 50528 2688 ? S 13:30 0:00 pop3-login
dovecot 8359 0.0 0.0 50528 2688 ? S 13:30 0:00 pop3-login
dovecot 8360 0.0 0.0 50528 2688 ? S 13:30 0:00 pop3-login
dovecot 8364 0.0 0.0 50540 2688 ? S 13:30 0:00 imap-login
dovecot 8375 0.0 0.0 50540 2692 ? S 13:30 0:00 imap-login
dovecot 8378 0.0 0.0 50540 2684 ? S 13:30 0:00 imap-login
shaz 9048 0.0 0.0 8956 864 pts/0 S+ 15:06 0:00 grep
--color=auto dovecot\|imap\|pop3
sudo netstat -lnptu
[sudo] password for shaz:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN
1033/dovecot
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN
1033/dovecot
tcp 0 0 0.0.0.0:64277 0.0.0.0:* LISTEN
2068/skype
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
1295/cupsd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN
1389/master
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN
1033/dovecot
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN
1033/dovecot
tcp6 0 0 ::1:631 :::* LISTEN
1295/cupsd
udp 0 0 127.0.0.1:45902 0.0.0.0:*
2068/skype
udp 0 0 0.0.0.0:33754 0.0.0.0:*
1065/avahi-daemon:
udp 0 0 0.0.0.0:5353 0.0.0.0:*
1065/avahi-daemon:
udp 0 0 0.0.0.0:68 0.0.0.0:*
2132/dhclient
udp 0 0 0.0.0.0:64277 0.0.0.0:*
2068/skype
udp6 0 0 :::5353 :::*
1065/avahi-daemon:
udp6 0 0 :::50994 :::*
1065/avahi-daemon:
sudo lsof -i | grep LISTEN
dovecot 1033 root 6u IPv4 7578 0t0 TCP *:imap2 (LISTEN)
dovecot 1033 root 7u IPv4 7579 0t0 TCP *:imaps (LISTEN)
dovecot 1033 root 9u IPv4 7580 0t0 TCP *:pop3 (LISTEN)
dovecot 1033 root 10u IPv4 7581 0t0 TCP *:pop3s (LISTEN)
cupsd 1295 root 5u IPv6 7932 0t0 TCP Casper:ipp (LISTEN)
cupsd 1295 root 6u IPv4 7933 0t0 TCP
localhost.localdomain:ipp (LISTEN)
master 1389 root 12u IPv4 9284 0t0 TCP *:smtp (LISTEN)
skype 2068 shaz 67u IPv4 18344 0t0 TCP *:64277 (LISTEN)
pop3-logi 8356 dovecot 4u IPv4 7580 0t0 TCP *:pop3 (LISTEN)
pop3-logi 8356 dovecot 5u IPv4 7581 0t0 TCP *:pop3s (LISTEN)
pop3-logi 8357 dovecot
Re: [Dovecot] [Urgent] Email Retrieval from remote servers doesn't use Dovecot
On 6/29/2011 7:19 AM, Shazia Javed wrote: As is obvious from the commands and output listed above that dovecot is running, listening on 110 and 143 - but only for localhost. When I try to telnet mail.ut.ee 110/143 I get to see IMAP4/POP3 ready rather than Dovecot ready. It seems obvious that mail.ut.ee/193.40.5.156 do not address the Dovecot host in question, but another host. Otherwise you would see Dovecot ready across the board. Please show: ~$ ifconfig|grep inet -- Stan
Re: [Dovecot] what to expect from changing index location
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/28/2011 07:29 PM, Charles Marcus wrote: On 2011-06-28 12:13 PM, Davide Vaghetti wrote: mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox and I want to switch to mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox:INDEX=/var/indexes/%-1.1u/%u/ But I cannot figure out a pair of things: - - do the switch trigger the rebuilding of the index files? - - can I get rid of all the old index files? I'm by no means an expert, but with that many users I think if you did this in one shot (all indexes being rebuilt simultaneously as users logged in) your system would slow to a crawl... I would first rsync the existing indexes over live, then stop dovecot, do another quick rsync of the indexes, then make the change and restart dovecot... That will minimize the impact (rebuilding of indexes)... Good hint! Thank you. What about the index grow factor? Do some of you folks have any idea about that (no ftp squat)? bye davide - -- Dott. Davide Vaghetti Centro Servizi Informatici Facolta' di Ingegneria Universita' di Pisa PGP: http://keys.keysigning.org:11371/pks/lookup?op=getsearch=0x7A1B3BA18C4E0A4D -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4LSr0ACgkQehs7oYxOCk2iBwCfbcygrvBaO4JJFAtgTb9fXwZg FPMAoI/yZFborIJH+U3gTx28In602H7k =pHbw -END PGP SIGNATURE-
[Dovecot] Dovecot 2.0, mysql and quota
Hello all,
I have some troubles to make the quota_check working with dovecot 2.0.
My config is the following: postfix, dovecot as lda, mysql as virtual
mailuser backend, and postfixadmin for the mailuser administration.
Previously i have a working setup with dovecot 1.x, now with the 2.0
something is wrong about the quota, but i don't know what...
Here is my config:
# 2.0.13: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.37.6-0.5-desktop x86_64 openSUSE 11.4 (x86_64) ext3
auth_mechanisms = plain login
first_valid_gid = 51
first_valid_uid = 51
info_log_path = /var/log/dovecot-inf.log
last_valid_gid = 51
last_valid_uid = 51
log_path = /var/log/dovecot-err.log
mail_home = /var/mail/virtual/%d/%u/
mail_location = maildir:/var/mail/virtual/%d/%u
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date
namespace {
hidden = no
inbox = yes
list = yes
location =
prefix = INBOX.
subscriptions = yes
type = private
}
passdb {
args = /etc/dovecot/dovecot-mysql.conf
driver = sql
}
plugin {
quota = maildir:User quota
quota_warning = storage=80%% /usr/bin/quota_warning.sh 80
quota_warning2 = storage=90%% /usr/bin/quota_warning.sh 90
quota_warning3 = storage=99%% /usr/bin/quota_warning.sh 90
sieve = /var/mail/virtual/%d/%u/.dovecot.sieve
sieve_storage = /var/mail/virtual/%d/%u/sieve
}
protocols = imap pop3 sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
unix_listener auth-master {
mode = 0600
}
unix_listener auth-userdb {
group = nobody
mode = 0660
user = postfix
}
}
service imap-login {
inet_listener imap {
address = 127.0.0.1
port = 143
}
}
service managesieve-login {
executable = /usr/lib/dovecot/managesieve-login
}
service managesieve {
executable = /usr/lib/dovecot/managesieve
}
service quota-warning {
executable = script /usr/bin/quota_warning.sh
user = postfix
}
ssl = no
userdb {
driver = passwd
}
userdb {
args = /etc/dovecot/dovecot-mysql.conf
driver = sql
}
protocol imap {
imap_client_workarounds =
mail_plugins = quota imap_quota
}
protocol sieve {
managesieve_max_line_length = 65536
plugin {
sieve = /var/mail/virtual/%d/%u/.dovecot.sieve
sieve_storage = /var/mail/virtual/%d/%u/sieve
}
}
protocol pop3 {
mail_plugins = quota
pop3_uidl_format = UID%u-%v
}
protocol lda {
auth_socket_path = /var/run/dovecot/auth-master
log_path = /var/log/dovecot-lda.log
mail_debug = yes
mail_plugins = quota sieve
postmaster_address = postmas...@mediaservice.net
}
My user query for mysql is the following:
user_query = SELECT maildir, 51 AS uid, 51 AS gid, CONCAT('*:bytes=',
mailbox.quota ) AS quota_rule FROM mailbox WHERE username = '%u' AND
active = '1'
I have made some test, with a test mailbox, with the quota setted to 1
Mb, in fact the maildirsize file contains:
1024000S
When i write a mail, something strange is happening: with the debug mail
of dovecot active i see this:
Jun 29 17:42:19 lda: Debug: Loading modules from directory:
/usr/lib64/dovecot/modules
Jun 29 17:42:19 lda: Debug: Module loaded:
/usr/lib64/dovecot/modules/lib10_quota_plugin.so
Jun 29 17:42:19 lda: Debug: Module loaded:
/usr/lib64/dovecot/modules/lib90_sieve_plugin.so
Jun 29 17:42:19 auth: Info: mysql(127.0.0.1): Connected to database postfix
Jun 29 17:42:19 lda: Debug: auth input: testqu...@mediaservice.pri
maildir=mediaservice.pri/testquota/ uid=51 gid=51 quota_rule=*:bytes=1024000
Jun 29 17:42:19 lda: Debug: Added userdb setting:
plugin/maildir=mediaservice.pri/testquota/
Jun 29 17:42:19 lda: Debug: Added userdb setting:
plugin/quota_rule=*:bytes=1024000
Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Effective
uid=51, gid=51,
home=/var/mail/virtual/mediaservice.pri/testqu...@mediaservice.pri/
Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota root:
name=User quota backend=maildir args=
Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota rule:
root=User quota mailbox=* bytes=1024000 messages=0
Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota warning:
bytes=819200 (80%) messages=0 reverse=no
command=/usr/bin/quota_warning.sh 80
Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota warning:
bytes=921600 (90%) messages=0 reverse=no
command=/usr/bin/quota_warning.sh 90
Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota warning:
bytes=1013760 (99%) messages=0 reverse=no
command=/usr/bin/quota_warning.sh 90
Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Namespace :
type=private, prefix=INBOX., sep=, inbox=yes, hidden=no, list=yes,
subscriptions=yes
location=maildir:/var/mail/virtual/mediaservice.pri/testqu...@mediaservice.pri
Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: maildir++:
Re: [Dovecot] [Urgent] Email Retrieval from remote servers doesn't use Dovecot
On 29/06/2011 13:19, Shazia Javed wrote: --- Objective: --- We need to download emails from remote server using Dovecot and thunderbird. Dovecot doesn't download e-mail from other servers. Our objective is to store emails in maildir or mbox format, and process them as part of our research project. --- Problem: --- Dovecot works for localhost, but not for remote servers. How do I know? Because thunderbird downloads emails in its default location (specified in settings) and not in maildir or mbox folders. If I send mail to user@system_name using mail command, dovecot works and thunderbird shows the email stored in maildir folder. But for email from id@yahoo.com goes to thunderbird's default folder and are browsed from there. It looks like you want to get e-mail from someone else's mail server and store it in maildir or mbox format on your server. You could do this by pulling the mail from someone else's mailserver using Thunderbird, then using Thunderbird to move it across to an account configured to access your server by IMAP. Alternatively you could do it by retrieving the mail using fetchmail on your server and have it delivered to an address on your server. This would have the benefit of being more reliable and more scriptable. - Commentary: - As is obvious from the commands and output listed above that dovecot is running, listening on 110 and 143 - but only for localhost. When I try to telnet mail.ut.ee 110/143 I get to see IMAP4/POP3 ready rather than Dovecot ready. That is the expected behaviour. You installed Dovecot on your server, ergo it is only on your server. Installing Dovecot on your server doesn't magically install and configure it on other people's servers. - Queries - Shouldn't I get Dovecot ready message for remote servers as well? No; you only installed it on your server. It is an MRA and we shouldn't be required to install it on remote servers, right? If, by MRA, you mean Mail Retrieval Agent, then no, Dovecot is not an MRA. What should I do to make dovecot work for remote servers? Dovecot, in and of itself, won't work for remote servers. You may be able to do what I think you want to do by pulling the mail from the remote server on to your server. You may want to look into fetchmail. Bill
Re: [Dovecot] what to expect from changing index location
On 28/06/2011 17:13, Davide Vaghetti wrote: I have one thousand virtual users with mdbox mailbox format and 10 GByte quota. I have noticed some performance problem related to I/O (the mailbox disk is a 6TB raid1+0 on ISCSI), so I want to put the index files on a different disk. My actual mail_location is: mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox and I want to switch to mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox:INDEX=/var/indexes/%-1.1u/%u/ But I cannot figure out a pair of things: - - do the switch trigger the rebuilding of the index files? ! DANGER, DANGER !! Index files cannot be re-generated under mdbox Go away and read http://wiki2.dovecot.org/MailboxFormat/dbox ... with dbox the Index files actually contain significant data which is held nowhere else. Index files for both *single-dbox* and *multi-dbox* contain message flags and keywords. For *multi-dbox*, the index file also contains the map_uids which link (via the map index) to the actual message data. This data cannot be automatically recreated, so it is important that Index files are treated with the same care as message data files. If you don't already know this, then you probably shouldn't even be using mdbox. - - can I get rid of all the old index files? NO! - - how much the index files (no fts squat) can grow? First solve your understanding problem with mdbox, then worry about details such as this. Bill
Re: [Dovecot] what to expect from changing index location
In fact, under sdbox and mdbox, calling these files index files is misleading because it implies that they can be re-created, leading to situations like this. Such situations could result in catastrophic data loss. Whilst we could say it is user error, users could argue that it is common knowledge that files referred to as index files can be re-created from the data files. In reality, these so-called index files are actually database files containing critical data. They happen to use the same format as Dovecot uses for index files in connection with mbox and maildir, but they contain data which is held nowhere else and cannot be recreated. Perhaps the per-mailbox index files for sdbox and mdbox should be re-named to message metadata databases, and the map index should be renamed to message store database. Specifically we should avoid the word index. By including the word database, we make it clearer that these files contain data. Timo, what do you reckon? Regards, Bill On 29/06/2011 17:36, William Blunn wrote: On 28/06/2011 17:13, Davide Vaghetti wrote: I have one thousand virtual users with mdbox mailbox format and 10 GByte quota. I have noticed some performance problem related to I/O (the mailbox disk is a 6TB raid1+0 on ISCSI), so I want to put the index files on a different disk. My actual mail_location is: mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox and I want to switch to mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox:INDEX=/var/indexes/%-1.1u/%u/ But I cannot figure out a pair of things: - - do the switch trigger the rebuilding of the index files? ! DANGER, DANGER !! Index files cannot be re-generated under mdbox Go away and read http://wiki2.dovecot.org/MailboxFormat/dbox ... with dbox the Index files actually contain significant data which is held nowhere else. Index files for both *single-dbox* and *multi-dbox* contain message flags and keywords. For *multi-dbox*, the index file also contains the map_uids which link (via the map index) to the actual message data. This data cannot be automatically recreated, so it is important that Index files are treated with the same care as message data files. If you don't already know this, then you probably shouldn't even be using mdbox. - - can I get rid of all the old index files? NO! - - how much the index files (no fts squat) can grow? First solve your understanding problem with mdbox, then worry about details such as this. Bill
Re: [Dovecot] what to expect from changing index location
On 29/06/2011 18:00, William Blunn wrote:
Perhaps the per-mailbox index files for sdbox and mdbox should be
re-named to message metadata databases, and the map index should
be renamed to message store database.
Also it might be an idea to change the filenames of the files to avoid
the word index.
Perhaps use something like ddb instead (means Dovecot database).
So,
${location}/mailboxes/INBOX/dbox-Mails/dovecot.index
${location}/mailboxes/INBOX/dbox-Mails/dovecot.index.cache
${location}/mailboxes/INBOX/dbox-Mails/dovecot.index.log
${location}/storage/dovecot.map.index
becomes
${location}/mailboxes/INBOX/dbox-Mails/dovecot.ddb
${location}/mailboxes/INBOX/dbox-Mails/dovecot.ddb.cache
${location}/mailboxes/INBOX/dbox-Mails/dovecot.ddb.log
${location}/storage/dovecot.map.ddb
To allow for migration of existing installations, it might be an idea to
make Dovecot look for both ddb and index when opening, but use ddb
when creating new files.
Regards,
Bill
Re: [Dovecot] Virtual Servers
I think we all know who the troll is here Yup. Me! **.:\:/:. .:\:\:/:/:. :.:\:\:/:/:.: :=.' - - '.=: '=(\ 9 9 /)=' ( (_) ) /`-vvv-'\ / \ / /|,|\ \ /_// /^\ \\_\ WW( ( ) )WW __\,,\ /,,/__ (__Y__)** -- Daniel
[Dovecot] NFS mail storage
The parameters listed for nfs installations (mmap_disable, doctlock_use_excl, mail_nfs_storage, mail_nfs_index) - are they necessary for data integrity, and/or do they compensate for NFS latency and improve performance? My understanding is the indexes are a critical part of a dbox storage, but on the other hand having local indexes is a major performance consideration. Is maildir a better choice under NFS than dbox? -- Daniel
[Dovecot] lda root vs lda postfix
hello folks hello Timo I am facing a new problem I'm using dovecot LDA to deliver the emails now root of the system emails are delivered in the box to the letter of the postfix directory /vap/spool/postfix I do not know what to do to redirect mail from root to root -- http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x092164A7 gpg --keyserver pgp.mit.edu --recv-key 092164A7 pgp77Huc6oBoZ.pgp Description: PGP signature
[Dovecot] Rawlogging uid
Hi, this is my first post to the list after years of passive following
every now and then.
Dovecot: 2.0.13 (3d07ab746a67) prebuilt binaries from xi.rename-it.nl
OS: i686 Debian 6.0 squeeze/sid
I am about to run a setup where users are virtual and their mail is owned by
vmail user. I bumped into minor client issue and needed to enable rawlogging
according to http://wiki2.dovecot.org/Debugging/Rawlog
This is what was printed to log at first try:
Jun 29 21:46:25 (null)Fatal: This process must not be run as root
I changed service postlogin to contain user = vmail and above
error disapperead. I also tried user = dovecot which seem to work
as well.
Is vmail or dovecot user more appropriate for raw logging?
From wiki I got the impression that user must be same as the effective UID
of logged in user, which in my setup is vmail(121).
Also, maybe the (null)Fatal -message could be improved(?).
# dovecot -n
# 2.0.13 (3d07ab746a67): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.26-1-686 i686 Debian squeeze/sid ext3
auth_debug = yes
auth_verbose = yes
debug_log_path = /var/log/dovecot/debug.log
first_valid_gid = 123
first_valid_uid = 121
info_log_path = /var/log/dovecot/info.log
last_valid_gid = 123
last_valid_uid = 121
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lmtp_save_to_detail_mailbox = yes
log_path = /var/log/dovecot/dovecot.log
mail_debug = yes
mail_location = maildir:/home/vmail/%n/Maildir
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables
body enotify environment mailbox date
namespace {
inbox = yes
location =
prefix =
separator = /
type = private
}
passdb {
driver = pam
}
plugin {
sieve = /home/vmail/%n/dovecot.sieve
sieve_dir = /home/vmail/%n/sieve
sieve_extensions = +enotify +subaddress +vacation
}
protocols = imap lmtp sieve
rejection_reason = Your message to %t was rejected: %r
rejection_subject = Mail delivery failed: returning message to sender
service auth {
unix_listener auth-userdb {
group = vmail
mode = 0660
}
}
service imap {
executable = imap postlogin
}
service postlogin {
executable = script-login rawlog
user = vmail
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
args = uid=121 gid=123
driver = passwd
}
userdb {
args = uid=121 gid=123 allow_all_users=yes home=/home/vmail/%n
driver = static
}
protocol lda {
info_log_path = /var/log/dovecot/lda-info.log
log_path = /var/log/dovecot/lda.log
mail_plugins = sieve
}
--
Mikko
Re: [Dovecot] [Urgent] Email Retrieval from remote servers doesn't use Dovecot
Shazia Javed writes: Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. ... telnet mail.ut.ee 143 Trying 193.40.5.156... Connected to mailhost.ut.ee. Escape character is '^]'. * OK IMAP4 ready That is weird. Maybe you got NAT forwarding going on where a firewall or other network appliance (like a load balancer) is translating ip1/143 - ip2/143? Or you're not on the host you think you're on. You can check the dovecot logs to verify that in fact your client is connecting. Joseph Tam jtam.h...@gmail.com
Re: [Dovecot] lda root vs lda postfix
On 6/29/2011 5:01 PM, m...@smtp.fakessh.eu wrote: hello folks hello Timo I am facing a new problem I'm using dovecot LDA to deliver the emails now root of the system emails are delivered in the box to the letter of the postfix directory /vap/spool/postfix I do not know what to do to redirect mail from root to root root should never receive mails directly and should always be aliased to some other address. -- Best regards, Charles
Re: [Dovecot] NFS mail storage
On 6/29/2011 1:10 PM, Daniel L. Miller wrote: The parameters listed for nfs installations (mmap_disable, doctlock_use_excl, mail_nfs_storage, mail_nfs_index) - are they necessary for data integrity, and/or do they compensate for NFS latency and improve performance? My understanding is the indexes are a critical part of a dbox storage, but on the other hand having local indexes is a major performance consideration. Is maildir a better choice under NFS than dbox? Depends a lot on the latency and IOPS performance of the NFS server, the aggregate concurrent IMAP IO load, and also the inbound new mail delivery rate from the upstream MTA. With either mbox or maildir you can put the indexes on fast local disk, SLC SSD being great for this, keeping a lot of random IO off the NFS server. This isn't possible with dbox storage since, as you noted, the index data is integral to the mail files. Corrupted mbox/maildir indexes are easy to fix, simply delete them and they're auto re-created. Since maildir is IOPS heavy and NFS/GFS/OCFS don't seem to like high IOPS workloads that make heavy use of locking, mbox becomes very attractive due to it's very low IOPS demands. If you can live with the folder tree limitations of mbox, along with a higher probably of mailbox file corruption, mbox is likely the best format for NFS/GFS/OCFS. Again, this all depends on the performance of the NFS server. If you have a properly configured NetApp filer you can probably do anything you want without limitation. If your NFS server is a home grown Linux or *BSD box that suffers high latency and/or low IOPS throughput, you're probably a good candidate for mbox and local index files. Test such a configuration with both mbox and maildir using local indexes on fast loca disk or SSD. If you don't run out of IOPS with maildir it's probably preferable to mbox. -- Stan
Re: [Dovecot] NFS mail storage
On Wed, 2011-06-29 at 18:40 -0500, Stan Hoeppner wrote: Since maildir is IOPS heavy and NFS/GFS/OCFS don't seem to like high IOPS workloads that make heavy use of locking, mbox becomes very attractive due to it's very low IOPS demands. If you can live with the folder tree limitations of mbox, along with a higher probably of mailbox file corruption, mbox is likely the best format for NFS/GFS/OCFS. I don't believe I just read that. Timo I will bite my tongue, look at that the sky today is purple signature.asc Description: This is a digitally signed message part
[Dovecot] Migrating shared folders from courier-imap to dovecot
Hi, I'm hoping you'll be able to help. I'm working on a project to migrate our users from a courier-imap (4.3.0) based mail server to a dovecot (2.0.8) mail server. I have got all the users migrated and working. However, I can't see how to migrate the shared folders from courier-imap. I have tried to find extra information all the migration information seems to centre around a user mailbox rather than shared mailboxes. Is it simply a case of setting up the shared folders on dovecot, then copying the messages in, finally running the dovecot migration script across them? Any advice would be greatly appreciated. Thanks, Tom
Re: [Dovecot] NFS mail storage
On Wed, 2011-06-29 at 11:10 -0700, Daniel L. Miller wrote: The parameters listed for nfs installations (mmap_disable, doctlock_use_excl, mail_nfs_storage, mail_nfs_index) - are they necessary for data integrity, and/or do they compensate for NFS latency and improve performance? My understanding is the indexes are a critical part of a dbox storage, but on the other hand having local indexes is a major performance consideration. Is maildir a better choice under NFS than dbox? If you have only a single Dovecot server, you don't really need to worry about anything. If you have more, use Dovecot director (with LMTP) and again you don't have to worry about anything. Any other configuration will have random errors regardless of what settings you use.
Re: [Dovecot] NFS mail storage
On Wed, 2011-06-29 at 18:40 -0500, Stan Hoeppner wrote: Since maildir is IOPS heavy and NFS/GFS/OCFS don't seem to like high IOPS workloads that make heavy use of locking, mbox becomes very attractive due to it's very low IOPS demands. If you can live with the folder tree limitations of mbox, along with a higher probably of mailbox file corruption, mbox is likely the best format for NFS/GFS/OCFS. You shouldn't equate NFS with GFS/OCFS. They have very little in common. The above is more or less true for GFS/OCFS, but definitely not NFS.
Re: [Dovecot] Rawlogging uid
On Thu, 2011-06-30 at 00:31 +0300, Mikko Lehto wrote: I am about to run a setup where users are virtual and their mail is owned by vmail user. I bumped into minor client issue and needed to enable rawlogging according to http://wiki2.dovecot.org/Debugging/Rawlog This is what was printed to log at first try: Jun 29 21:46:25 (null)Fatal: This process must not be run as root I changed service postlogin to contain user = vmail and above error disapperead. I also tried user = dovecot which seem to work as well. Is vmail or dovecot user more appropriate for raw logging? rawlog looks for ~/dovecot.rawlog/ directory and tries to write there. It doesn't really matter what the user is as long as it can write there. I find it a bit weird if dovecot user managed to write there.. You could also have given -d parameter to script-login and it would have figured out the user automatically. Also, maybe the (null)Fatal -message could be improved(?). Yes, fixed: http://hg.dovecot.org/dovecot-2.0/rev/ed0688858e59
Re: [Dovecot] what to expect from changing index location
On Wed, 2011-06-29 at 18:09 +0100, William Blunn wrote:
On 29/06/2011 18:00, William Blunn wrote:
Perhaps the per-mailbox index files for sdbox and mdbox should be
re-named to message metadata databases, and the map index should
be renamed to message store database.
Also it might be an idea to change the filenames of the files to avoid
the word index.
Perhaps use something like ddb instead (means Dovecot database).
Or simply db :)
${location}/mailboxes/INBOX/dbox-Mails/dovecot.ddb
${location}/mailboxes/INBOX/dbox-Mails/dovecot.ddb.cache
${location}/mailboxes/INBOX/dbox-Mails/dovecot.ddb.log
${location}/storage/dovecot.map.ddb
Yes, this would be nice, but..
To allow for migration of existing installations, it might be an idea to
make Dovecot look for both ddb and index when opening, but use ddb
when creating new files.
This makes it annoying. It wastes disk I/O..
BTW. Cyrus also has cyrus.index file, which is the only storage for
message flags. So Dovecot isn't alone with this.
Re: [Dovecot] Problem accessing Dovecot mailing lists via IMAP
On Tue, 2011-06-28 at 11:54 +0100, William Blunn wrote: I recently tried to look at the Dovecot mailing lists through an already-configured IMAP profile, which had worked fine in the past. Yeah, it was broken in two ways. Should be working in a few minutes, hopefully :)
Re: [Dovecot] ldapsearch dump for passwd file: base64 encoded passwords
On Wed, 2011-06-29 at 14:14 +0200, Denny Schierz wrote:
is there a way, to let Dovecot2 uses the base64 encoded passwords from a
ldapsearch output, without decode them first?
Plaintext passwords? Add {plain.base64} prefix to them.
Re: [Dovecot] Dovecot 2.0, mysql and quota
On Wed, 2011-06-29 at 18:02 +0200, Claudio Prono wrote: home=/var/mail/virtual/mediaservice.pri/testqu...@mediaservice.pri/ Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota root: name=User quota backend=maildir args= Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota rule: root=User quota mailbox=* bytes=1024000 messages=0 Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota warning: bytes=819200 (80%) messages=0 reverse=no command=/usr/bin/quota_warning.sh 80 Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota warning: bytes=921600 (90%) messages=0 reverse=no command=/usr/bin/quota_warning.sh 90 Jun 29 17:42:19 lda(testqu...@mediaservice.pri): Debug: Quota warning: bytes=1013760 (99%) messages=0 reverse=no command=/usr/bin/quota_warning.sh 90 Looks ok. First question: why i see two times the quota warning check? The second one is for an internal storage. You can ignore it. Anyway, if the 80% or 90% of the quota is fullfilled, no warning pops out Are you sure you tested it correctly? It is executed only when a mail is delivered across the 79% - 80% quota boundary. I don't see any error in your config.
Re: [Dovecot] Installing Dovecot v2.0.3 from binary files problem
On Wed, 2011-06-29 at 11:19 +0430, Meisam Navaki wrote: dovecot: master: Error: service(config): child 8606 killed with signal 11 (core dumps disabled) config process crashes for some reason. Can you get a gdb backtrace? You should be able to do it simply by: ulimit -c unlimited dovecot gdb /usr/local/libexec/dovecot/config /var/run/dovecot/core (or wherever your config binary is) If the config binary is stripped, this isn't very useful. Then you'd have to build it yourself.
Re: [Dovecot] Exim and Dovecot2 SASL: 435 Unable to authenticate at present
On Tue, 2011-06-28 at 21:38 +0400, Sergey Urushkin wrote: 29279 received: COOKIE cf735efce15b21bbb10568c4a762017c 29279 SMTP 435 Unable to authenticate at present I guess Exim gets confused by the COOKIE that is sent to it. It should just ignore it, but it fails. Since this COOKIE is important for Dovecot itself, this can only be fixed on Exim side.
Re: [Dovecot] mirate to dovecot 2.0.13
On Tue, 2011-06-28 at 19:19 +0200, Giovanni Mancuso wrote: Hi, I have in my system dovecot 1.2.11 and i want migrate to dovecot 2.0.13. I have 2 Frontend that proxy all request to Backend and i want migrate first FE and after the BE. Can i install dovecot 2.0.13 in FE that proxy all request to BE with dovecot 1.2.11? Yes.
Re: [Dovecot] permissions for dbox attachment directory
On Tue, 2011-06-28 at 10:08 -0400, i...@tnde.org wrote: On Sat, 2011-06-25 at 03:58 -0400, i...@tnde.org wrote: I am running dovecot 2.0.13 on CentOS5, set up with only local system users, and single instance store set up in a single directory. e.g. mail_attachment_dir = /var/mail/attachments Currently you can't. I was a bit lazy in implementing this code not to preserve permissions. The idea would be anyway that you could make /var/mail/attachments 02770 and e.g. group=mail. Then set mail_access_groups=mail to Dovecot. Now the code should have created new directories under that with the same permissions and the files as 0660, but looks like it doesn't. The code is in src/lib-fs/fs-posix.c if you want to fix it yourself. You could as a workaround simply change all 0600 - 0660 and 0700 - 0770 and I guess it would work. Ok, if I understand you correctly, I would need to chmod to 660/770, but it would only work on existing folders, and every new item will be created as 600/700? Yes, that's why I suggested modifying the source code so new items would be created with correct mode too. I guess the best way is setting up virtual users, presumably these work under a single system account? (for the time being this is running on a test server, using the simplest setup with system users) Yeah, that's the easiest solution.
Re: [Dovecot] Question about Storage keeps breaking in logs
On Tue, 2011-06-28 at 11:01 +, Maria Arrea wrote: Any other idea about this? Maybe this problem is load-related? All I can really say is that: This just shouldn't be happening, ever. If there's a way to reproduce it I would be interested in knowing how. I know there are other mdbox users who haven't had any corruption trouble for a long time..
Re: [Dovecot] Denying user won't work as expected
On Tue, 2011-06-28 at 10:49 +0200, Frank Bonnet wrote: If I do that the denying does not work , I'we written my login in /usr/local/etc/dovecot/deny-users and I am still able to log in ( after restarting dovecot of course ) see attached the dovecot -n output There is no deny passdb in your dovecot -n output.
Re: [Dovecot] lda root vs lda postfix
On Wed, 29 Jun 2011 19:23:45 -0400, Charles Marcus wrote: On 6/29/2011 5:01 PM, m...@smtp.fakessh.eu wrote: hello folks hello Timo I am facing a new problem I'm using dovecot LDA to deliver the emails now root of the system emails are delivered in the box to the letter of the postfix directory /vap/spool/postfix I do not know what to do to redirect mail from root to root root should never receive mails directly and should always be aliased to some other address. I solved my problem with a new entry in the file virtual of postfix it 's right -- http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x092164A7 gpg --keyserver pgp.mit.edu --recv-key 092164A7
Re: [Dovecot] Dovecot 2.0.13 problem with LMTP
Try to apply these patches to both proxy and backend and see what it logs then? http://hg.dovecot.org/dovecot-2.0/raw-rev/1b1fc681a277 http://hg.dovecot.org/dovecot-2.0/raw-rev/36e7ded2ef0b http://hg.dovecot.org/dovecot-2.0/raw-rev/537d4b6d9a7a On Tue, 2011-06-28 at 08:38 +, Innocenzi, Cinzia wrote: Hello Timo, so far I've seen this happening when proxying a mail for one recipient; I've never seen this happening for multiple recipients. The other thing I've noticed is that if I reload dovecot, the mail usually gets delivered. Once, it remained stuck in the queue, but after a few hours, when I checked postfix's queue again, it got delivered. Let me know if you need further information. Regards, CINZIA INNOCENZI Technical Consulting HP Enterprise Services Telephone +39 06.6542.5758 Email cinzia.innoce...@hp.com Via Achille Campanile, 85 / Rome, Italy 00143 -Original Message- From: Timo Sirainen [mailto:t...@iki.fi] Sent: martedì 28 giugno 2011 2.04 To: Innocenzi, Cinzia Cc: dovecot@dovecot.org; Del Coiro, Maria Giacinta Subject: Re: [Dovecot] Dovecot 2.0.13 problem with LMTP On Wed, 2011-06-22 at 10:31 +, Innocenzi, Cinzia wrote: Hello, we have dovecot 2.0.13 installed in our RHEL5 servers. We use dovecot as a lmtp proxy on the front end mail relays and dovecot for back end lmtp/pop/imap. All our servers have RHEL5.6 64-bit and dovecot 2.0.13 installed, and the back end has also an ext3 mbox file-system mounted. Sometimes we have mails that get stuck on our postfix queue with the following error: Remote server not answering (timeout in DATA input) (in reply to end of DATA command) .. It doesn't happen for every single mail, it's random. My guess is there's a bug somewhere in the LMTP proxy code. It's a bit annoyingly complex code.. Do you see this happening when proxying only a single mail (one RCPT TO per DATA, not multiple)? And I would guess that when attempting to deliver the same mail again it works fine (at least in a few tries)?
Re: [Dovecot] LMTP returncode 450?
On Tue, 2011-06-28 at 10:23 +0200, Peter Mogensen wrote: I can see that a lookup in the userdb is done, but now matter what I return (1/111) from my checkpassword script I just get: Set lmtp_proxy=yes and have passdb lookup return proxy=y and host=1.2.3.4. But how does the LMTP proxy deal with temporary errors? It has no queue like the SMTP-server ? The temporary error is proxied all the way back to the sending SMTP server, which puts it back to its queue.
Re: [Dovecot] Dovecot communication with sasl in dovecot source code
On Tue, 2011-06-28 at 12:07 +0430, Meisam Navaki wrote: Hi all, I'm reading dovecot source codes(2.0.13),and I need to know how dovecot communicate with sasl? For what purpose? Dovecot's login process communicates with auth process via http://wiki2.dovecot.org/Design/AuthProtocol I traced the source code from cmd_login function,and found out something about sasl_callback. but i never found where this function called and also I couldn't understand how sasl inform the dovecot from authentication result. I'll be thankful if someone could help me out. The code is a bit tricky jumping all around.. I can help more if you tell me what it is that you actually want to do.
Re: [Dovecot] Migrating shared folders from courier-imap to dovecot
On Wed, 2011-06-29 at 11:45 +0100, Tom Clark wrote: Hi, I'm hoping you'll be able to help. I'm working on a project to migrate our users from a courier-imap (4.3.0) based mail server to a dovecot (2.0.8) mail server. I have got all the users migrated and working. However, I can't see how to migrate the shared folders from courier-imap. I have tried to find extra information all the migration information seems to centre around a user mailbox rather than shared mailboxes. Is it simply a case of setting up the shared folders on dovecot, then copying the messages in, finally running the dovecot migration script across them? Did you want per-user flags with shared folders? IIRC Courier used some weird symlink directory for that, which won't work with Dovecot. http://wiki2.dovecot.org/SharedMailboxes lists all the ways you can currently do shared folders with Dovecot.
