[Dovecot] dovecot creating unknown users
Hi
We recently installed a dovecot postfix roundcube debian
wheezy serverIt is now in production and we are feeling
our way as we progressivelyadd new users to this local
server.
I noticed that dovecot is creating user directory structures
for unknown users withinour domain in /var/vmail, even
though we have setup a static users.conf db file.
I tried omiting the "allow_all_users=yes" parameter but
that doesn't seem to be linked to this issue
Sorry if this has been asked a number of times already
Is there an easy way to search the archives of this
mailinglist ?
Thanks
yann
# 2.2.2 (45399357008a): /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-686-pae i686 Debian 7.0 ext4
auth_debug = yes
auth_mechanisms = plain login
auth_socket_path = /var/run/dovecot/auth-userdb
auth_verbose = yes
disable_plaintext_auth = no
first_valid_gid = 5000
first_valid_uid = 5000
hostname = holimail.holinice.com
last_valid_gid = 5000
last_valid_uid = 5000
listen = *
mail_debug = yes
mail_gid = vmail
mail_location = maildir:/var/vmail/%d/%n/Maildir
mail_privileged_group = mail
mail_uid = vmail
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
namespace inbox {
inbox = yes
location = maildir:/var/vmail/%d/%n/Maildir
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
subscriptions = yes
}
passdb {
args = scheme=CRAM-MD5 /etc/dovecot/users.conf
driver = passwd-file
}
passdb {
driver = pam
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
postmaster_address = azur...@holinice.com
protocols = " imap sieve pop3"
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
}
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
}
service imap-login {
group = dovecot
inet_listener imap {
port = 143
}
inet_listener imaps {
port = 993
ssl = yes
}
}
service imap {
process_limit = 1024
}
service pop3-login {
inet_listener pop3 {
port = 110
}
inet_listener pop3s {
port = 995
ssl = yes
}
}
service pop3 {
process_limit = 1024
}
ssl_cert =
[Dovecot] Transparent IMAP proxy
Hi, I'm considering patching Dovecot to work as a transparent (and virus scanning) IMAP proxy. What is the appropriate feature to extend? (I've considered the following: IMAPC and reverse proxying, with IMAPC looking more promising since it actually parses IMAP communication). Can anyone who is familiar with the IMAPC code recommend what are the most appropriate locations in the code to make the required changes? (I've considered hooking the storage virtual functions and making the settings local rather than global - but would appreciate more specific ideas). Thanks.
Re: [Dovecot] Transparent IMAP proxy
Am 16.06.2013 15:42, schrieb Yonatan Broza: > I'm considering patching Dovecot to work as a transparent (and virus > scanning) IMAP proxy why would someone implement a virus scanner on the IMAP-level? what happens with POP3? this has to be done on SMTP level long before the message is stored and not every time a client is downloading a message signature.asc Description: OpenPGP digital signature
[Dovecot] Still virtio problems
Hello! As posted on May 27th this year, dovecot 2.1.7 does not allow for the mailstore to be located in a virtio partition. I still receive fstat()-errors on the lock files in this combination: May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/.quotausage.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: file dict commit: file_dotlock_open(/var/vmail/mydomain/test/.quotausage) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory Config includes: mmap_disable=yes dotlock_use_excl=no Any ideas? Thanks Erich
Re: [Dovecot] Still virtio problems
Am 16.06.2013 16:21, schrieb Erich N. Pekarek: > As posted on May 27th this year, dovecot 2.1.7 does not allow for the > mailstore to be located in a virtio partition. > I still receive fstat()-errors on the lock files in this combination: > > May 27 12:54:51 host dovecot: imap(test@mydomain): Error: > fstat(/var/vmail/mydomain/test/.quotausage.lock) failed: No such file or > directory > May 27 12:54:51 host dovecot: imap(test@mydomain): Error: file dict commit: > file_dotlock_open(/var/vmail/mydomain/test/.quotausage) failed: No such file > or directory > May 27 12:54:51 host dovecot: imap(test@mydomain): Error: > fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such > file or directory > > Config includes: > mmap_disable=yes > dotlock_use_excl=no dovecot knows nothing about virtio as any other software because it is a layer far below the applications /var/vmail/mydomain/test/.quotausage.lock: No such file or directory does the folder "/var/vmail/mydomain/test" exists and what permissions? what permissions has "/var/vmail/mydomain/"? and what permissions has "/var/vmail/"? signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Transparent IMAP proxy
On 16.6.2013, at 16.42, Yonatan Broza wrote: > I'm considering patching Dovecot to work as a transparent (and virus > scanning) IMAP proxy. > > What is the appropriate feature to extend? (I've considered the following: > IMAPC and reverse proxying, with IMAPC looking more promising since it > actually parses IMAP communication). > > Can anyone who is familiar with the IMAPC code recommend what are the most > appropriate locations in the code to make the required changes? (I've > considered hooking the storage virtual functions and making the settings > local rather than global - but would appreciate more specific ideas). imapc and http://dovecot.org/patches/2.1/mail-filter.tar.gz can do this. But note that the MIME structure or the parts' sizes must not change. Basically you'll have to replace the viruses with empty spaces or something. imapc isn't very efficient though. It translates all IMAP commands to rather simple ones. So for example a SEARCH won't be passed through to the backend server.
Re: [Dovecot] Dovecot 2.2.2: doveadm user doesn't honor -x option
On 6.6.2013, at 21.51, Axel Luttgens wrote: > Hello, > > 1. Considering a user_query similar to this one: > > SELECT ... FROM ... WHERE CASE '%s' WHEN 'lmtp' THEN ... > > and issuing following command: > > doveadm user -x service=lmtp someu...@example.com > > the log shows: > > SELECT ... FROM ... WHERE CASE 'doveadm' WHEN 'lmtp' THEN ... > > and the query of course fails. Fixed: http://hg.dovecot.org/dovecot-2.2/rev/c290383e60da > The same config with Dovecot 2.1.16 yields expected results. v2.1 worked a bit differently by returning only the userdb info and skipping the dovecot.conf settings. Giving -u parameter to doveadm user uses the old way, and the service works also there. > 2. This is more a question. > > Issuing above command first writes this to the log: > > prefetch(someu...@example.com): passdb didn't return userdb entries, > trying the next userdb > > Is there really an attempt to make use of the prefetch database? Yes. > If yes, under which circumstances could it succeed? Never with only a userdb lookup. But it's generic code. I guess the debug log entry could be hidden if it disturbs people too much..
Re: [Dovecot] doveadm index crashes when indexing shared mailboxes
On 10.6.2013, at 14.56, W. de Hoog wrote: > We store our mail archive in a tree of subfolders. I am trying to speed up > text searching on our mail archive but when running "doveadm -D -v index -u > neil shared/Exalon/Aandeelhouders" the following output is produced: .. > doveadm(neil): Panic: file mbox-storage.c: line 711 > (mbox_transaction_unlock): assertion failed: (mbox->box.transaction_count > > 0 || mbox->mbox_lock_type > == F_UNLCK) mbox is a pretty difficult format, and I wouldn't recommend using it for anything else than small simple legacy setups. > # 2.1.7: /etc/dovecot/dovecot.conf If this happens also with v2.2 I could look into it.
Re: [Dovecot] Connection closed by foreign host.
On 13.6.2013, at 9.16, Michael Cramer wrote: > 3 LIST () "" (*) > Connection closed by foreign host. .. > now the full conf > > # 2.2.2 (45399357008a): /etc/dovecot/dovecot.conf Is it fixed with a newer version? I think http://hg.dovecot.org/dovecot-2.2/rev/04ee59c96fc9 fixed it?
Re: [Dovecot] rawlog without setting home in userdb
On 13.6.2013, at 11.03, clau...@bayern-mail.de wrote: > A little extra question: why do you split in and out in rawlog? It was easier to implement :) Although nowadays there's iostream_rawlog that would make it easy to implement a combined log.
Re: [Dovecot] Connection closed by foreign host.
Zitat von Timo Sirainen : On 13.6.2013, at 9.16, Michael Cramer wrote: 3 LIST () "" (*) Connection closed by foreign host. .. now the full conf # 2.2.2 (45399357008a): /etc/dovecot/dovecot.conf Is it fixed with a newer version? I think http://hg.dovecot.org/dovecot-2.2/rev/04ee59c96fc9 fixed it? i tired today the 2.2.2-auto+68 build and it works, thanks
Re: [Dovecot] Transparent IMAP proxy
From: Reindl Harald why would someone implement a virus scanner on the IMAP-level? what happens with POP3? this has to be done on SMTP level long before the message is stored and not every time a client is downloading a message Or, as an alternative, most desktop antivirus tools have a mail-scanning capability. But SMTP is certainly better (though IMO even that is not really needed if you have reasonable antispam filtering and think before opening attachments). Cheers Eugene
Re: [Dovecot] LMTP crash with sdbox and SIS
On 13.6.2013, at 10.34, Bernhard Schmidt wrote: >>> Jun 12 21:46:23 lxmhs69 dovecot: lmtp(20120, >>> ext44...@mstoretest.mail.xxx.de): Panic: file istream.c: line 163 >>> (i_stream_read): assertion failed: (old_size == _stream->pos - >>> _stream->skip) >> >> Can you easily reproduce this? Does it happen with all mails? Only mails >> that contain attachments? Only one specific mail? I couldn't reproduce >> with a couple of tests. > > I can reproduce with mails with a random attachment > 128k. I'm using > smtp-cli to test > > dd if=/dev/random of=random1M bs=1M count=1 > ./smtp-cli-3.2 --server --from --to > --subject Test --attach=random1M Thanks, fixed: http://hg.dovecot.org/dovecot-2.2/rev/9dcbcc0871f0
Re: [Dovecot] MULTIAPPEND + literal8 issue
Fixed: http://hg.dovecot.org/dovecot-2.2/rev/dd04b4ef530d
On 13.6.2013, at 18.22, Michael M Slusarz wrote:
> Background: importing a mbox file containing ~700 messages (20 MB). Our
> program splits MULTIAPPENDS into approx. 5MB chunks. We don't use literal+
> in order to immediately catch errors.
>
> I can reproducibly produce the following error (2.2.2) when doing a
> MULTIAPPEND where every append is using literal8:
>
> [...340 messages appended in 7 previous APPEND commands...]
> C: 10 APPEND Test "16-Dec-2011 17:19:46 -0700" ~{3128}
> [...~30 APPENDed messages...]
> C: "18-Jan-2012 12:38:21 -0700" ~{2893}
> S: + OK
> [...2893 octets of data...]
> C: "18-Jan-2012 22:09:41 -0700" ~{6492}
> S: 10 BAD Error in IMAP command APPEND: Expected '{'
> S: 492} BAD Error in IMAP command : Unknown command.
>
> This error occurs about 340 messages in. If I switch to using regular
> literals, this error does not occur. I can verify that neither the 12:38:21
> message nor the 22:09:41 message alone is broken (I can put just these two in
> a file and import and it is successful).
>
> I can provide the mbox file privately, if needed.
>
> michael
>
Re: [Dovecot] dovecot 2.2 with lucene compile error
On 14.6.2013, at 12.15, Robert Schetterer wrote: > Hi ,i get an compile error > > security -Werror=format-security -MT lucene-wrapper.lo -MD -MP -MF > .deps/lucene-wrapper.Tpo -c lucene-wrapper.cc -fPIC -DPIC -o > .libs/lucene-wrapper.o > lucene-wrapper.cc: In function 'lucene_index* lucene_index_init(const > char*, mailbox_list*, const fts_lucene_settings*)': > lucene-wrapper.cc:128:2: error: 'else' without a previous 'if' > make[5]: *** [lucene-wrapper.lo] Error 1 Fixed: http://hg.dovecot.org/dovecot-2.2/rev/3c9bb07ea92e
Re: [Dovecot] [Dovcot 2.2.2] Q: Prequisits for compiling and plugins
On 14.6.2013, at 10.11, Christoph Hintermüller wrote: > Where can i find the list of prerequisites for compiling dovocot 2.2.2 > form the sources, is there a dedicated link or what terms i should best > use to search the archives of this mailing list, the documentation or > the web? Dovecot doesn't really require anything, but depending on what features you want to use you may need to install some libraries, like openssl. http://wiki2.dovecot.org/CompilingSource has some things if you want to compile from Mercurial. > Where do I find information (links or search terms) whether plugins > available for 1.x 2.1.x series, especially the metadata plugin, are > still needed for 2.2.2 or may even be harmful for 2.2.2 as built in. > Documentation on Dovecot webpage is rather sparse and not really > conclusive concerning metadata plugin within 2.x series. On my Ubuntu > 12.X systems i still find it for 2.1.x but I have difficulties to > understand whether there exist a version for 2.2.X series, if this is > equal to the one for 2.1.X or whether it is not needed any more for > 2.2.X series. Further what libraries would be required. In general: If it compiles, it works. http://hg.dovecot.org/dovecot-metadata-plugin/ has v2.2 compatibility. At some point in v2.2.x development it will probably have native METADATA support.
Re: [Dovecot] Transparent IMAP proxy
On 06/16/2013 01:31 PM, Eugene wrote: Or, as an alternative, most desktop antivirus tools have a mail-scanning capability. But SMTP is certainly better (though IMO even that is not really needed if you have reasonable antispam filtering and think before opening attachments). In my experience, an anti-virus is left with almost nothing to catch if you let spamassassin reject mail above a certain score, and so the AV never gets to see those. However one benefit of delaying AV scanning is that you get later signatures, so you could potentially deal better with 0-hour viruses. But overall AV is just ineffective.
Re: [Dovecot] IMAP MOVE and lazy_expunge_only_last_instance
On 14.6.2013, at 10.12, Pavel Volkovitskiy wrote: > im testing lazy_expunge_only_last_instance here and it seems it works wrong > with IMAP MOVE I suppose you mean with mdbox format? Seems to be annoyingly difficult to fix..
Re: [Dovecot] Multiple user sharing a single mailbox
On 14.6.2013, at 22.31, Jonathon Price wrote: > If having a single seen flag for the mailboxs was preferred, i.e. no > private indexes. Is there a recommended mail store format that would work > best with higher levels of concurrent access? Anything but mbox works fine.
Re: [Dovecot] quota-status not working in distributed environment
On 14.6.2013, at 9.15, Benoit Panizzon wrote: > Is there a way to get quota-status to also use the proxy feature to request > the quota information from the correct machine? Looks like this is a missing feature. I first thought quota-status would go through doveadm protocol, which would make this work via doveadm proxying, but looks like it doesn't. Perhaps it optionally should. > Btw, the quota-status just return DUNNO or 'Quota Full'. Is there a similar > easy way to check the ammount of quota used? I could then update that > information in the database and use it to, for example find abandoned > mailboxes. doveadm quota get command can be used to ask for the user's current quota. You can ask the same via TCP protocol as well: http://wiki2.dovecot.org/Design/DoveadmProtocol
Re: [Dovecot] Transparent IMAP proxy
On 06/16/2013 03:42 PM, Yonatan Broza wrote: > I'm considering patching Dovecot to work as a transparent (and virus > scanning) IMAP proxy. > [...] Have you considered non transparent caching proxy?
[Dovecot] v2.2.3 released
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig
This is a pretty important upgrade for v2.2 users, because of the IMAP
ENVELOPE reply fix.
* LDA/LMTP: If new mail delivery first fails with "temporary
failure", tempfail the whole delivery instead of falling back to
delivering the mail to INBOX. (Requires new Pigeonhole as well.)
* doc/solr-schema.xml was updated to Solr v4.x format. Also the
default analyzers were changed, hopefully for the better. Note that
the schema can't be changed for existing Solr indexes without
rebuilding everything.
* Solr plugin does only soft commits from now on. You'll need a
cronjob to send a hard commit command to it every few minutes.
+ Added %N modifier for variables as %H-like "new hash"
+ sdbox, mdbox: Support POP3 message order field (for migrations)
+ Added mailbox { driver } to specify a different mail storage
format for the mailbox than generally used within the namespace.
+ Added initial lib-sasl library for client side SASL support.
Currently supports only PLAIN, LOGIN and plugins. Used currently
by IMAP and POP3 proxying when authenticating to the remote server.
- IMAP: If subject contained only whitespace, Dovecot returned an
ENVELOPE reply with a huge literal value, effectively causing the
IMAP client to wait for more data forever.
- IMAP: Various URLAUTH fixes.
- imapc: Various bugfixes and improvements
- pop3c: Various fixes to make it work in dsync (without imapc)
- dsync: Fixes to syncing subscriptions. Fixes to syncing mailbox
renames.
[Dovecot] Trash plugin
Hello! This is my first dovecot install, which I put together by mixing
and matching pieces of various online howtos (fortunately, Dovecot doesn't
seem to be overly complex - a big plus). I've got it mostly working, but
the trash plugin doesn't seem to be working right. Below are configs and
some logs.
Any thoughts? Also, any suggestions regarding my configuration? I can
post other items for troubleshooting if they'd be helpful.
-Jason Pfingstmann
Here's my doveconf -n:
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-358.6.2.el6.x86_64 x86_64 CentOS release 6.4 (Final) ext4
auth_anonymous_username = anonymous
auth_cache_negative_ttl = 1 hours
auth_cache_size = 0
auth_cache_ttl = 1 hours
auth_debug = no
auth_debug_passwords = no
auth_default_realm =
auth_failure_delay = 2 secs
auth_first_valid_uid = 500
auth_gssapi_hostname =
auth_krb5_keytab =
auth_last_valid_uid = 0
auth_master_user_separator =
auth_mechanisms = plain login
auth_realms =
auth_socket_path = auth-userdb
auth_ssl_require_client_cert = no
auth_ssl_username_from_cert = no
auth_use_winbind = no
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@
auth_username_format =
auth_username_translation =
auth_verbose = no
auth_verbose_passwords = no
auth_winbind_helper_path = /usr/bin/ntlm_auth
auth_worker_max_count = 30
base_dir = /var/run/dovecot
config_cache_size = 1 M
debug_log_path =
default_client_limit = 1000
default_idle_kill = 60
default_internal_user = dovecot
default_login_user = dovenull
default_process_limit = 100
default_vsz_limit = 256 M
deliver_log_format = msgid=%m: %$
dict {
quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf
}
dict_db_config =
director_doveadm_port = 0
director_mail_servers =
director_servers =
director_user_expire = 15 mins
disable_plaintext_auth = yes
dotlock_use_excl = no
doveadm_socket_path = doveadm-server
doveadm_worker_count = 0
first_valid_gid = 12
first_valid_uid = 101
hostname =
imap_capability =
imap_client_workarounds =
imap_id_log =
imap_id_send =
imap_idle_notify_interval = 2 mins
imap_logout_format = bytes=%i/%o
imap_max_line_length = 64 k
info_log_path =
last_valid_gid = 0
last_valid_uid = 0
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lda_original_recipient_header =
libexec_dir = /usr/libexec/dovecot
listen = *, ::
lmtp_proxy = no
lmtp_save_to_detail_mailbox = yes
lock_method = fcntl
log_path = syslog
log_timestamp = "%b %d %H:%M:%S "
login_access_sockets =
login_greeting = Dovecot ready.
login_log_format = %$: %s
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c
login_trusted_networks =
mail_access_groups =
mail_attachment_dir =
mail_attachment_fs = sis posix
mail_attachment_hash = %{sha1}
mail_attachment_min_size = 128 k
mail_cache_fields = flags
mail_cache_min_mail_count = 0
mail_chroot =
mail_debug = no
mail_fsync = optimized
mail_full_filesystem_access = no
mail_gid =
mail_home =
mail_location = maildir:/home/vmail/%d/%n
mail_log_prefix = "%s(%u): "
mail_max_keyword_length = 50
mail_max_lock_timeout = 0
mail_max_userip_connections = 10
mail_never_cache_fields = imap.envelope
mail_nfs_index = no
mail_nfs_storage = no
mail_plugin_dir = /usr/lib64/dovecot
mail_plugins = trash
mail_privileged_group =
mail_save_crlf = no
mail_temp_dir = /tmp
mail_uid =
mailbox_idle_check_interval = 30 secs
mailbox_list_index_disable = no
maildir_copy_with_hardlinks = yes
maildir_stat_dirs = no
maildir_very_dirty_syncs = no
managesieve_client_workarounds =
managesieve_implementation_string = Dovecot Pigeonhole
managesieve_logout_format = bytes=%i/%o
managesieve_max_compile_errors = 5
managesieve_max_line_length = 65536
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
master_user_separator =
mbox_dirty_syncs = yes
mbox_dotlock_change_timeout = 2 mins
mbox_lazy_writes = yes
mbox_lock_timeout = 5 mins
mbox_min_index_size = 0
mbox_read_locks = fcntl
mbox_very_dirty_syncs = no
mbox_write_locks = dotlock fcntl
mdbox_preallocate_space = no
mdbox_rotate_interval = 0
mdbox_rotate_size = 2 M
mmap_disable = no
passdb {
args = /etc/dovecot/dovecot-mysql.conf
deny = no
driver = sql
master = no
pass = no
}
plugin {
acl = vfile:/etc/dovecot/acls
quota = dict:user::proxy::quotadict
sieve = ~/dovecot.sieve
sieve_dir = ~/sieve
sieve_global_dir = /home/sieve/
sieve_global_path = /home/sieve/globalfilter.sieve
sieve_max_script_size = 1M
trash = /etc/dovecot/trash.conf
}
pop3_client_workarounds =
pop3_enable_last = no
pop3_fast_size_lookups = no
pop3_lock_session = no
pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s
pop3_no_flag_updates = no
pop3_reuse_xuidl = no
pop3_save_uidl = no
pop3_uidl_format = %08Xu%08Xv
postmaster_address =
protocols = imap pop3 lmtp sieve
quota_full_tempfail = no
recipient_delimite
[Dovecot] Trash plugin
Hello all! I tried to post this earlier today, but it's stuck in a moderator queue for being too long, so here's a shorter version (mod, please delete the pending message from me, if you read this). I'm new to dovecot and just finished setting everything up. It's a postfix + dovecot + myql + spamassassin + postgrey virtual mail server. The issue I'm having (1 of 2) is that the Trash plugin isn't working, over-quota mail is being rejected despite a large piece that would bring it under quota with room to spare for the piece being delivered that is in the Trash folder. My configs (postconf -n, doveconf -n, trash.conf): http://pastebin.com/vFJ0rfZ6 It may be unrelated, but it seems postgrey isn't running either, but maybe those are partially tied together? Thanks for all your help! Jason Pfingstmann
Re: [Dovecot] [Dovecot-news] v2.2.3 released
Have just upgraded to 2.2.3 and when it started I got these lines in the log: dovecot[44069]: master: Dovecot v2.2.3 starting up (core dumps disabled) Jun 17 15:48:46 mail dovecot[44072]: config: Error: Module is for different ABI version 2.2.ABIv2(2.2.2) (we have 2.2.ABIv3(2.2.3)): /usr/local/lib/dovecot/settings/libmanagesieve_login_settings.so Jun 17 15:48:46 mail dovecot[44072]: config: Error: Module is for different ABI version 2.2.ABIv2(2.2.2) (we have 2.2.ABIv3(2.2.3)): /usr/local/lib/dovecot/settings/libmanagesieve_settings.so Can someone tell me how to fix this? I'm running on Mac OS X 10.7.5. Many thanks, James.
Re: [Dovecot] [Dovecot-news] v2.2.3 released
James Brown skrev den 2013-06-17 08:02: Jun 17 15:48:46 mail dovecot[44072]: config: Error: Module is for different ABI version 2.2.ABIv2(2.2.2) (we have 2.2.ABIv3(2.2.3)): /usr/local/lib/dovecot/settings/libmanagesieve_settings.so Can someone tell me how to fix this? you wait for pigenhole 2.2.3 try disable this plugin and dovecot 2.2.3 works like a charm sieve managesieve -- senders that put my email into body content will deliver it to my own trashcan, so if you like to get reply, dont do it
Re: [Dovecot] [Dovecot-news] v2.2.3 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benny Pedersen said the following on 17/06/2013 08:09: > James Brown skrev den 2013-06-17 08:02: >> Jun 17 15:48:46 mail dovecot[44072]: config: Error: Module is for >> different ABI version 2.2.ABIv2(2.2.2) (we have 2.2.ABIv3(2.2.3)): >> /usr/local/lib/dovecot/settings/libmanagesieve_settings.so >> >> Can someone tell me how to fix this? > > you wait for pigenhole 2.2.3 I did a make/make install with pigeonhole 0.4.0 and everything works as expected Ciao, luigi - -- / +--[Luigi Rosa]-- \ I got the bill for my surgery. Now I know what those doctors were wearing masks for. --James Boren -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlG+qHwACgkQ3kWu7Tfl6ZR4xwCeKkFH/mOO5DGnj/OMtUl49GqL OLwAn0MS1griwtEKPWygnKfso1LRFgMv =lsi9 -END PGP SIGNATURE-
Re: [Dovecot] IMAP MOVE and lazy_expunge_only_last_instance
On Sun, Jun 16, 2013 at 11:30 PM, Timo Sirainen wrote: > On 14.6.2013, at 10.12, Pavel Volkovitskiy wrote: > > > im testing lazy_expunge_only_last_instance here and it seems it works > wrong > > with IMAP MOVE > > I suppose you mean with mdbox format? Seems to be annoyingly difficult to > fix.. > > yep, mdbox format can i disable imap move support somehow? imap copy and delete will still works fast, thanks to mdbox -- Pavel
Re: [Dovecot] v2.2.3 released
* Timo Sirainen : > http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz > http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig > > This is a pretty important upgrade for v2.2 users, because of the IMAP > ENVELOPE reply fix. Compiled & installed. Seems to work for me :) > * LDA/LMTP: If new mail delivery first fails with "temporary > failure", tempfail the whole delivery instead of falling back to > delivering the mail to INBOX. (Requires new Pigeonhole as well.) That's wonderful! > - IMAP: If subject contained only whitespace, Dovecot returned an > ENVELOPE reply with a huge literal value, effectively causing the > IMAP client to wait for more data forever. I wonder which clients this affected? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
