Re: [Dovecot] ntlm_auth in Dovecot
On Fri, 2012-06-08 at 16:53 +0200, Leonardo wrote: Hi, I'm trying getting NTLM auth working against AD in my Dovecot 2.0.15. I'm getting the following error: Jun 08 14:18:11 auth: Info: winbind(?,10.44.3.151): user not authenticated: NT_STATUS_UNSUCCESSFUL BTW I forgot to say that I've already disjoined and rejoined the server to the domain. I saw someone suggested that on the list (I wasn't subscribe until now). -- leonardo
Re: [Dovecot] [ Re: best practises for mail systems]
On 9.6.2012, at 4.55, Matthias-Christian Ott wrote: Yes, there is. You have to replicate the entire state of the IMAP session (protocol states, buffers, TLS state etc.) and the TCP state of the connection. The state of the IMAP session is (in theory) easily replicable (although you probably have to rely on internals of the TLS implementation; OpenSSL can serialise TLS sessions from/into ASN.1 via i2d_SSL_SESSION, though this is meant to resume session via TLS) Interesting! I thought OpenSSL didn't have a way to [de]serialize the session state. The first time I wanted to do that was 13 years ago. I see there are some google hits for i2d_SSL_SESSION, but do you already know a good web page / example code I could look at? and for TCP there is RTCP [1]. RTCP intercepts the TCP session is able to recover the TCP state. It works without any modification of the operating system (at the moment limited to Linux). Thanks for this too. If this would be implemented in Dovecot it would really set it apart from other IMAP servers and software that I've seen so far. Being able to transparently handle failover of a TCP connection is unique. Yes.
Re: [Dovecot] [ Re: best practises for mail systems]
On 2012-06-09 16:11, Timo Sirainen wrote: On 9.6.2012, at 4.55, Matthias-Christian Ott wrote: Yes, there is. You have to replicate the entire state of the IMAP session (protocol states, buffers, TLS state etc.) and the TCP state of the connection. The state of the IMAP session is (in theory) easily replicable (although you probably have to rely on internals of the TLS implementation; OpenSSL can serialise TLS sessions from/into ASN.1 via i2d_SSL_SESSION, though this is meant to resume session via TLS) Interesting! I thought OpenSSL didn't have a way to [de]serialize the session state. The first time I wanted to do that was 13 years ago. I see there are some google hits for i2d_SSL_SESSION, but do you already know a good web page / example code I could look at? The Apache httpd module mod_ssl uses it. GnuTLS has similar functions with gnutls_db_*, although it's also only intended to be used to resume a session. Have look at the Apache httpd module mod_gnutls. Regards, Matthias-Christian
Re: [Dovecot] ntlm_auth in Dovecot
On Fri, 2012-06-08 at 16:53 +0200, Leonardo wrote: Hi, I'm trying getting NTLM auth working against AD in my Dovecot 2.0.15. I'm getting the following error: Jun 08 14:18:11 auth: Info: winbind(?,10.44.3.151): user not authenticated: NT_STATUS_UNSUCCESSFUL wbinfo -u reports all the users of the domain and ntlm_auth --username=%name% --domain=%domain% gets authenticated successfully. Debugging winbind I can see the following error: [2012/06/08 14:18:11.129611, 10] winbindd/winbindd.c:651(process_request) process_request: unknown request fn number 14 [2012/06/08 14:18:11.129671, 10] winbindd/winbindd.c:738(winbind_client_response_written) winbind_client_response_written[2822:unknown request]: delivered response to client Upgrading to Dovecot 2.1.5 did not help. -- leo
Re: [Dovecot] Corrupted mdbox on LMTP director delivery while user [solved] is logged in via IMAP
Daniel Parthey wrote:
we get errors about corrupted indexes and we are losing flags with mdbox on
NFSv4:
Error: Recent flags state corrupted for mailbox
Error: Corrupted dbox file
Error: Corrupted transaction log file
It looks like a LMTP director problem. The user has IMAP IDLE connections
open and lmtp delivers to another host. This leads to nfs corruption problems.
Jun 8 03:36:03 10.129.3.200 dovecot: mailbox: mail:
imap(someu...@example.de): Error: Corrupted transaction log file
/mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-
Mails/dovecot.index.log seq 82: Invalid transaction log size (32856 vs
32824):
/mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index.log
(sync_offset=32856)
Jun 8 03:36:03 10.129.3.200 dovecot: mailbox: mail:
imap(someu...@example.de): Error: Index
/mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index:
Lost log for seq=82
offset=32856
Jun 8 03:36:03 10.129.3.200 dovecot: mailbox: mail:
imap(someu...@example.de): Warning: fscking index file
/mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index
Jun 8 03:36:03 10.129.3.200 dovecot: mailbox: mail:
imap(someu...@example.de): Error: Fixed index file
/mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index:
log_file_seq 82
- 83
Jun 8 03:36:38 10.129.3.200 dovecot: mailbox: mail:
imap(someu...@example.de): Error: Transaction log file
/mail/dovecot/example.de/someuser/mail/mailboxes/INBOX/dbox-Mails/dovecot.index.log.2:
marked corrupted
How to enable the LMTP director to deliver to the correct mailbox host?
The reason were different usernames for different protocols (lmtp and imap)
of the same user, which resulted in different target hosts in the director:
LMTP director was using usern...@example.org - Host mail01
IMAP director was using usern...@dovecotmail.example.org - Host mail04
# 2.0.20: /etc/dovecot-director/dovecot-director.conf
passdb {
args = proxy=y nopassword=y user=%n@dovecotmail.%d
driver = static
}
Removing the user mapping in the static imap passdb solved the problem:
passdb {
args = proxy=y nopassword=y
driver = static
}
Now the user is directed to the same host for all protocols again.
Regards,
Daniel
Re: [Dovecot] per user quota
Hello Andreas,
Andreas Meyer wrote:
I activated quota
plugin {
quota = maildir:User quota
quota_rule = *:storage=1GB
# 10% of 1GB = 100MB
quota_rule2 = Trash:storage=+10%%
}
But when I want to do per user quota in the passwd-file
...vhosts/anup.de/anmeyer::userdb_mail=maildir:~/userdb_quota_rule=*:bytes=10G
It looks like you are at least missing a space between userdb_mail=maildir:~/
and userdb_quota_rule.
I get this in the logfile and can't login:
Jun 08 22:25:52 imap(anme...@anup.de): Error: user anme...@anup.de:
Initialization failed: Initializing mail storage from mail_location setting
failed: Unknown setting: bytes
Jun 08 22:25:52 imap(anme...@anup.de): Error: Invalid user settings. Refer to
server log for more information.
Same with 'storage' in the passwd-file. What's wrong?
You forgot to attach your doveconf -n output.
Regards,
Daniel
Re: [Dovecot] director and IPs shown at the backends
Angel L. Mateo wrote: El 07/06/12 14:12, Urban Loesch escribió: # Space separated list of trusted network ranges. Connections from these # IPs are allowed to override their IP addresses and ports (for logging and # for authentication checks). disable_plaintext_auth is also ignored for # these networks. Typically you'd specify your IMAP proxy servers here. login_trusted_networks = I didn't find that option in any example config file, but it's working. Maybe it must be documented in somewhere. This command lists all available options of your release: doveconf Regards Daniel
Re: [Dovecot] Dovecot over NFS
James Devine wrote: I'm playing with running dovecot over NFS and I am running into some issues. I have followed the guide at http://wiki2.dovecot.org/NFS and my setup includes 1 nfs server and 1 client running postfix/dovecot. In testing I am running postal via the command: postal -t 10 -c 10 localhost users399 The test file has a list of 399 users to deliver to. I've provided a sample of the errors I'm receiving and my configuration below, I am running dovecot 2.0.19. Any idea what I might be doing wrong and what I might do to resolve it? My ultimate goal is to setup multiple clients with director so each user is still handled on a single machine, however with a single machine I still seem to be having issues. Have a look at http://wiki2.dovecot.org/Director Here is a sample of some of the errors I'm seeing: Jun 6 15:55:12 test-gluster-client1 dovecot: lmtp(12072, testuser130): Error: mdbox /mnt/testuser130/mdbox/mailboxes/INBOX/dbox-Mails: Invalid dbox header size: 0 Jun 6 15:55:12 test-gluster-client1 dovecot: lmtp(11999, testuser99): Error: Log synchronization error at seq=2,offset=556 for /mnt/testuser99/mdbox/storage/dovecot.map.index: Append with UID 2, but next_uid = 3 mdbox format requires a correct index and you will lose flags, if you lose the index file. The index will be automatically tried to restore from mails in the storage. You should avoid accessing the same user directory from different NFS clients, since this often leads to corruptions or invalid files. You need a director which ensures that one directory is only accessed from one host at the same time. This applies to IMAP, POP3, LMTP etc, which are all writing to the mailbox. Then you should access all mailboxes only via the director listener ports. My dovecot config is: You posted only the configuration of your mailbox instance and might have a look your director configuration too: doveconf -c /etc/dovecot-director/dovecot-director.conf -n (or wherever your director configuration is located) Regards Daniel
Re: [Dovecot] Dovecot 1.x on AIX - Dovecot 2.x on Ubuntu
r...@yuma.acns.colostate.edu wrote: We are working on migrating Dovecot 1.2.17 running on AIX 5.3 (believe it or not!) to Dovecot 2.0.13 running on Ubuntu. We have hundreds of users mboxes we will be migrating. My question is regarding the index files. Should we remove those after the migration, but before we open it up to users so Dovecot can create new ones? I did a test migration of a single user, and Dovecot detects the architecture change and put out some panic errors, corrupt files and backtrace messages in syslog on Ubuntu. The messages are shown below. If every user is going to generate these types of errors, I'm thinking maybe it makes sense to remove all the .imap directories and let Dovecot create new clean ones. I realize that may slow things down for awhile while Dovecot is rebuilding new files. Which mail storage format (mbox,maildir,sdbox,mdbox) are you using and is it stored on NFS? Would you provide your doveconf -n output for dovecot 2.0.13, please? You might also have a look at imapsync[1] for clean mass migration from one architecture to another. Regards Daniel [1] http://imapsync.lamiral.info/
[Dovecot] Deliver quota-warning via director
Hi there, I'm using NFS with Dovecot 2.0.20 and would like to deliver a quota warning to the user using the LMTP director. I have configured quota warnings according to http://wiki2.dovecot.org/Quota/Configuration But it seems that lda delivers the mail directly to the local filesystem and is not using our lmtp director, which prevents NFS mailboxes from getting corrupted. Is there a way to tell lda to use LMTP or the director and ignore the quota while delivering the notification? Regards Daniel
Re: [Dovecot] Authentication issue
Hi Emiliano, Emiliano Rago wrote: I need to set up a weird dovecot configuration: 1) outside a ssl tunnel I'd like to authenticate only with cram-md5 scheme 2) inside a ssl tunnel I'd like to authenticate only with plain auth You might try to set up two instances of dovecot, one for plain, one for ssl: http://wiki2.dovecot.org/RunningDovecot#Running_Multiple_Invocations_of_Dovecot Regards Daniel
Re: [Dovecot] director and doveadm server
Hello Angel,
Angel L. Mateo wrote:
I've been reading doc at http://wiki2.dovecot.org/Director to
configure my servers. My question is regarding configuration of
doveadm server.
I have configured both, director and backend servers, as described
in that doc, but I don't know how to run doveadm commands in
director servers.
doveadm is working, because I can run commands, but they are
executed in local (director) server.
See
http://wiki2.dovecot.org/Tools/Doveadm/Mailbox
doveadm help
doveadm help who
A few doveadm commands allow the -S socket_path argument
where socket_path can be a hostname:port combination of
your director doveadm service:
altmove [-u user|-A] [-S socket_path] [-r] search query
expunge [-u user|-A] [-S socket_path] search query
fetch[-u user|-A] [-S socket_path] fields search query
force-resync [-u user|-A] [-S socket_path] mailbox
import [-u user|-A] [-S socket_path] source mail location dest
parent mailbox search query
index[-u user|-A] [-S socket_path] mailbox mask
move [-u user|-A] [-S socket_path] destination search query
purge[-u user|-A] [-S socket_path]
search [-u user|-A] [-S socket_path] search query
The http://wiki2.dovecot.org/Director article explains
how to set up a Doveadm server on a specific port.
After you have set up your doveadm server correctly,
an example command might look like this:
doveadm search -A -S director:24245 mailbox * all
but doveadm who seems to be executed just in local:
For doveadm who however, you need a local anvil socket,
which provides the necessary information:
doveadm who -a /var/run/dovecot/anvil
Remember there is also the proxy list command,
since the director is just a proxy with a hash table
which always proxies the same username to the same backend:
doveadm proxy list
And another question about this... what is the local config option?
I haven't found it documented anywhere.
I assume the local { } section is to restrict the inside
options to client IPs located in a specific subnet.
Regards
Daniel
Re: [Dovecot] per user quota
Daniel Parthey daniel.part...@informatik.tu-chemnitz.de wrote:
Hello Andreas,
Andreas Meyer wrote:
I activated quota
plugin {
quota = maildir:User quota
quota_rule = *:storage=1GB
# 10% of 1GB = 100MB
quota_rule2 = Trash:storage=+10%%
}
But when I want to do per user quota in the passwd-file
...vhosts/anup.de/anmeyer::userdb_mail=maildir:~/userdb_quota_rule=*:bytes=10G
It looks like you are at least missing a space between userdb_mail=maildir:~/
and userdb_quota_rule.
Wow, great! The space was missing and now it works.
You forgot to attach your doveconf -n output.
ok, next time.
Regards,
Daniel
Andreas
Re: [Dovecot] Dovecot 1.x on AIX - Dovecot 2.x on Ubuntu
On 6.6.2012, at 23.27, r...@yuma.acns.colostate.edu wrote: We are working on migrating Dovecot 1.2.17 running on AIX 5.3 (believe it or not!) to Dovecot 2.0.13 running on Ubuntu. We have hundreds of users mboxes we will be migrating. My question is regarding the index files. Should we remove those after the migration, but before we open it up to users so Dovecot can create new ones? I did a test migration of a single user, and Dovecot detects the architecture change and put out some panic errors, corrupt files and Yeah, there's still some problem with properly handling index file recreation when CPU architecture (endianess) change is detected. Better just delete your index files, since they have to be regenerated anyway.
Re: [Dovecot] Deliver quota-warning via director
On 9.6.2012, at 22.11, Daniel Parthey wrote: But it seems that lda delivers the mail directly to the local filesystem and is not using our lmtp director, which prevents NFS mailboxes from getting corrupted. Is there a way to tell lda to use LMTP or the director and ignore the quota while delivering the notification? That's a bit tricky problem. Even if LDA used LMTP, it couldn't ignore quota since LMTP server is the one enforcing it. Perhaps you need to create two LMTP ports, one with a quota ignored configuration. Then you need to somehow get the mail delivered there (maybe send it to your MTA and route it from there). Or write a script that sends the mail directly to the LMTP port on director.
Re: [Dovecot] Upgrading 1.2.17 - 2.1.x
On 9.6.2012, at 0.53, Adam G Tilghman wrote: We're planning to upgrade our site from 1.2.17 to 2.1.x within the next few months, but we must ensure our ability to revert to 1.2.17 if problems arise. I don't expect our maildir storage would present a problem, but am less certain about 2.1.x index/control files remaining readable under 1.2.17. Should I have any reason to worry? 1.2.17 can read v2.0 indexes without problems (it has some forwards compatibility code). I don't think I added any incompatible changes to v2.1 either, at least nothing major..
Re: [Dovecot] Director problems
On 6.6.2012, at 16.01, Joseba Torre wrote: I've just setup a testing enviroment for director, and it's not working as expected. I have just 1 director (called director) and 2 dovecot servers (dovecot1 and dovecot2); these are exact copies. First problem: when both dovecot servers are up, every imap connection is redirected to the same server as you can see here: $ sudo doveadm director map user mail server ip expire time unknown 158.227.4.186 2012-06-06 13:34:12 unknown 158.227.4.186 2012-06-06 13:34:27 unknown 158.227.4.186 2012-06-06 13:34:34 (I don't know if that unknown is good or not) I've tried with 3 different users and ips to no change, users are always directed to the same host. Perhaps you just managed to use such usernames that map to the same director.. You can try with doveadm director status user to see where they should go. Second problem: if I try to add/remove/modify one of the dovecot servers, the output of doveadm director map/status seems to be ok, but any new user connection fails with this log: Jun 6 14:51:59 director dovecot: director: Warning: Delaying new user requests until ring is synced Looks like there's a bug when only one director is used. I'll try and fix it later..
Re: [Dovecot] director: backend health monitoring
On 8.6.2012, at 4.25, Костырев Александр Алексеевич wrote: I am wonder if there are plans to include backend health monitoring feature to Dovecot Director ? Yes, but it's not a very high priority right now.
[Dovecot] Dovecot antispam plugin bug: got an empty message
It is few months ago I requested help with combination dovecot - dovecot-
antispam plugin and dspam.
Now I got into troubles with a lot of spam delivering to users inbox. Problem
described bellow is now better hidden but stil remains:
When moving a message from INBOX to Junk, dspam got an empty message.
I made a wrapper about dspamc and there is no input on stdio. The dspam was
not trained (got an empty message).
Looking to source code of dspam and antispam plugin I suspect the dovecot not
to sending any content to plugin when moving from inbox to junk.
Petr Bravenec
Dne Wednesday 25 of January 2012 17:19:18 Tom Hendrikx napsal(a):
On 25-01-12 08:05, Petr Bravenec wrote:
Few weeks ago I upgraded dovecot from 1.2 to 2.0.16 and antispam plugin
to 2.0_pre20101222. Since the upgrade I'm not able to move messages to
my Junk folder. In the maillog I have found this message:
dspam[25060]: empty message (no data received)
Gentoo has included the antispam plugin from Johannes historically, but
added the fork by Eugene to support upgrades to dovecot 2.0. It is not
really made clear by the gentoo ebuild is that the forked plugin needs a
slightly different config.
I use the config below with dovecot 2.0.17 and a git checkout for
dovecot-antispam:
===8
plugin {
antispam_signature = X-DSPAM-Signature
antispam_signature_missing = move
antispam_spam_pattern_ignorecase = Junk;Junk.*
antispam_trash_pattern_ignorecase = Trash;Deleted Items;Deleted
Messages
# Backend specific
antispam_backend = dspam
antispam_dspam_binary = /usr/bin/dspamc
antispam_dspam_args =
--user;%u;--deliver=;--source=error;--signature=%%s
antispam_dspam_spam = --class=spam
antispam_dspam_notspam = --class=innocent
#antispam_dspam_result_header = X-DSPAM-Result
}
--
Regards,
Tom
[Dovecot] Dovecot setup fails w. multiple mail locations (gnus/dovecot/offlineimap)
Hi,
I am trying to setup a Gnus - Dovecot - Offlineimap - Webmail (Gmail /
Fastmail) chain and cannot configure the correct behaviour.
Any advice to get this working properly would be very appreciated!
I have set up Offlineimap to synchronise two mail accounts into separate
folders under ~/Maildir. After running Offlineimap, the folders look as
below.
Maildir/
|-- Gmail
| |-- cur
| |-- dovecot.index.log
| |-- dovecot-uidlist
| |-- dovecot-uidvalidity
| |-- dovecot-uidvalidity.4fd3b80e
| |-- [Gmail].All\ Mail
| |-- [Gmail].Drafts
| |-- [Gmail].Important
| |-- [Gmail].Sent\ Mail
| |-- [Gmail].Spam
| |-- [Gmail].Starred
| |-- [Gmail].Trash
| |-- INBOX
| |-- new
| |-- Personal
| |-- Receipts
| |-- tmp
| |-- Travel
| `-- Work
`-- Fastmail
|-- cur
|-- dovecot.index.log
|-- dovecot.mailbox.log
|-- dovecot-uidlist
|-- dovecot-uidvalidity
|-- dovecot-uidvalidity.4fd3b75e
|-- INBOX
|-- INBOX.Drafts
|-- INBOX.Sent\ Items
`-- INBOX.Trash
The Dovecot config is below. (I have set up a blank MailTest directory
as inbox, believing that this may preserve the two imap directories
better for offlineimap synching (not sure if this is correct)).
,
| mail_location = maildir:~/Maildir:LAYOUT=fs
|
| namespace inbox {
| location = maildir:~/MailTest
| inbox = yes
| }
|
| namespace mygmail {
| type = private
| separator = .
| prefix = mygmail.
| location = maildir:%h/Maildir/Gmail/:LAYOUT=fs
| inbox = no
| hidden = no
| list = yes
| subscriptions = yes
| }
|
| namespace myfastmail {
| type = private
| separator = .
| prefix = myfastmail.
| location = maildir:%h/Maildir/FASTMAIL/:LAYOUT=fs
| inbox = no
| hidden = no
| list = yes
| subscriptions = yes
| }
`
Accessing dovecot through gnus with this setup only sees the files in
the directories that are not prefixed (e.g. under Fastmail, INBOX is the only
seen folder, all INBOX.subfolder are not there). Removing the prefix
manually they can be seen again however (e.g. INBOX.subfolder -
subfolder). If I remove LAYOUT=fs in the dovecot config, nothing is
seen at all, although the directories look like proper Maildirs!
A second issue is that running Offlineimap a second time seems to work
ok for gmail, but Fastmail complains that cannot create directory
'.'?
Thanks!
--
Johnny
Dovecot 2.1.6
Offlineimap 6.5.2.1
Ma Gnus v0.6
[Dovecot] Error: doveadm client attempted non-PLAIN authentication
Hi
doveadm search -u u...@example.org -S localhost:19000 all
produces the following error in the logs:
dovecot: doveadm: Error: doveadm client attempted non-PLAIN authentication
What am I missing?
* tcpdump of tcp communication on port 19000 is attached
* dovecot.conf is attached
Regards
Daniel
dump
Description: tcpdump.dat
# 2.0.20: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-40-server x86_64 Ubuntu 10.04.4 LTS
auth_cache_negative_ttl = 0
auth_cache_size = 10 M
auth_cache_ttl = 1 mins
auth_verbose = yes
auth_verbose_passwords = sha1
deliver_log_format = mailbox: deliver: msgid=%m from=%f: %$
dict {
quota = mysql:/etc/dovecot/conf.d/dovecot-dict-sql.conf.ext
}
disable_plaintext_auth = no
doveadm_password = bf79a088601795554d6d428ece2ea92a1c91ae11
instance_name = dovecot-mailbox
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
login_greeting = Mailbox
login_log_format = mailbox: login: %$: %s
login_trusted_networks = 10.129.3.0/24
mail_debug = yes
mail_fsync = always
mail_gid = vmail
mail_home = /mail/dovecot/%d/%n
mail_location = mdbox:~/mail
mail_log_prefix = mailbox: mail: %s(%u):
mail_plugins = quota
mail_privileged_group = vmail
mail_uid = vmail
managesieve_implementation_string = Sieve
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 ihave
mdbox_rotate_interval = 1 weeks
mdbox_rotate_size = 50 M
mmap_disable = yes
passdb {
args = /etc/dovecot/conf.d/dovecot-sql.conf.ext
driver = sql
}
plugin {
quota = dict:User quota::proxy::quota
quota_rule = *:storage=10G
quota_rule2 = Trash:storage=+100M
quota_warning = storage=95%% quota-warning 95 %u
quota_warning2 = storage=80%% quota-warning 80 %u
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap pop3 lmtp sieve
service auth {
unix_listener auth-userdb {
group = dovecot
mode = 0660
user = dovecot
}
}
service dict {
unix_listener dict {
group = vmail
mode = 0660
}
}
service doveadm {
inet_listener doveadm-server {
port = 19000
}
}
service imap-login {
inet_listener imap {
port = 19143
}
}
service imap-postlogin {
executable = script-login /usr/local/bin/dovecot-postlogin
user = $default_internal_user
}
service imap {
executable = imap imap-postlogin
}
service lmtp {
inet_listener lmtp {
address = *
port = 19024
}
}
service managesieve-login {
inet_listener sieve {
port = 19200
}
}
service pop3-login {
inet_listener pop3 {
port = 19110
}
}
service pop3-postlogin {
executable = script-login /usr/local/bin/dovecot-postlogin
user = $default_internal_user
}
service pop3 {
executable = pop3 pop3-postlogin
}
service quota-warning {
executable = script /usr/local/bin/quota-warning
extra_groups = dovecot
unix_listener quota-warning {
user = vmail
}
user = vmail
}
ssl = no
userdb {
driver = prefetch
}
userdb {
args = /etc/dovecot/conf.d/dovecot-sql.conf.ext
driver = sql
}
verbose_proctitle = yes
protocol imap {
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep
mail_plugins = quota imap_quota
}
protocol lmtp {
mail_plugins = quota sieve
}
Re: [Dovecot] Restoring older messages to new server?
Reindl imapsync is your friend Thanks for suggestion. After a few false starts, with impasync saying source server dropped connection, it seemed to have worked. But, now, my K9 email client seems to download entire inbox... rather than last 25 messages... Also, in Squirrel, recent messages before sync seems preceded by old messages, then, messages since sync... any tips on this..? Voytek -- Sent from my Moom with K-9 Mail. Please excuse my brevity.
