Re: [Dovecot] Login into other user's account // master user for non-master users // chroot to users.user
On 2013-10-18 4:31 AM, Steffen Kaiser skdove...@smail.inf.fh-brs.de wrote: Now, I came into thinking that it would be good in such case, if userB could authentificate as, say sales*userB - much like a master user - and ends in sales's home, but with access permissions of userB, well, like a chroot. Would it be an interesting feature to add to Dovecot's core? I would actually find that very useful. We have similar role based email accounts, and currently we have the same problem - no way to tell which of the users in question did what... -- Best regards, */Charles/*
Re: [Dovecot] Login into other user's account // master user for non-master users // chroot to users.user
Am 20.10.2013 15:25, schrieb Charles Marcus: On 2013-10-18 4:31 AM, Steffen Kaiser skdove...@smail.inf.fh-brs.de wrote: Now, I came into thinking that it would be good in such case, if userB could authentificate as, say sales*userB - much like a master user - and ends in sales's home, but with access permissions of userB, well, like a chroot. Would it be an interesting feature to add to Dovecot's core? I would actually find that very useful. We have similar role based email accounts, and currently we have the same problem - no way to tell which of the users in question did what... and how does the different username change anything? the inbox is still shared you see a differnt username for login but you still do not se *what* he did and if you would have *that* in the logs username + ip-address makes the match signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Question to sieve symlink
Andreas Meyer anme...@anup.de wrote:
A Server running openSUSE 12.3 and dovecot version 2.1.13.
In the log I find
Oct 19 00:23:23 managesieve(anme...@anup.de): Warning: sieve-storage: Active
sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is
broken: invalid/unknown path to storage (points to
/var/spool/vhosts/anup.de/anmeyer/.sieve/managesieve.sieve).
But the link is ok and when I login to roundcube I can manage the filters.
What's the problem?
I found the corresponding part in sieve-storage-script.c
/* Check whether the path is any good */
if ( strcmp(scriptpath, storage-link_path) != 0
strcmp(scriptpath, storage-dir) != 0 ) {
i_warning
(sieve-storage: Active sieve script symlink %s is
broken:
invalid/unknown path to storage (points to
%s).,
storage-active_path, link);
return NULL;
}
but I am not a programmer to say what's wrong there.
Andreas
Re: [Dovecot] Question to sieve symlink
On 10/19/2013 1:55 AM, Andreas Meyer wrote: Hello! A Server running openSUSE 12.3 and dovecot version 2.1.13. In the log I find Oct 19 00:23:23 managesieve(anme...@anup.de): Warning: sieve-storage: Active sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown path to storage (points to /var/spool/vhosts/anup.de/anmeyer/.sieve/managesieve.sieve). But the link is ok and when I login to roundcube I can manage the filters. What's the problem? What is your configuration (output from dovecot -n) ? Regards, Stephan
[Dovecot] Upgrade from 2.1 to 2.2 on Debian
Hello, I am currently running Dovecot 2.1 on current Debian and need to upgrade to 2.2 to use the replication features. I understand that I therefore need to compile Dovecot myself. I am using a MySQL database for users authentication, therefore I need to compile Dovecot with mysql support: *./configure --with-mysql* Unfortunately this terminates with: *configure: error: Can't build with MySQL support: libmysqlclient not found* I installed libmysqlclient from debian repos, but it does not help. Also, how do I then connect the newly installed dovecot to my existing /etc/init.d/dovecot script? Thank you. Lucas -- Lucas Rothamel Eye Catching Webdesign i...@eye-catching-webdesign.de - www.eye-catching-webdesign.de You know, we go to the gym to keep the body fit. Similarly the mind needs some rest. The mind is bombarded with so many impressions. Our mind has been bombarded by impressions the whole time. It needs a different kind of rest other than sleep. And meditation is such a rest. It calms the mind. energizes the spirit and makes the body more strong and vibrant. improves the immune system. The immune cells, the T-cell count go higher through Sudarshan Kriya and meditation. And you feel so nice inside. - Sri Sri Ravi Shankar I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams smime.p7s Description: S/MIME Cryptographic Signature
Re: [Dovecot] Question to sieve symlink
Hello! Stephan Bosch step...@rename-it.nl wrote: On 10/19/2013 1:55 AM, Andreas Meyer wrote: Hello! A Server running openSUSE 12.3 and dovecot version 2.1.13. In the log I find Oct 19 00:23:23 managesieve(anme...@anup.de): Warning: sieve-storage: Active sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown path to storage (points to /var/spool/vhosts/anup.de/anmeyer/.sieve/managesieve.sieve). But the link is ok and when I login to roundcube I can manage the filters. What's the problem? What is your configuration (output from dovecot -n) ? I will not send this sensitive output to a public mailinglist. Do you need a special part of the output? Andreas
Re: [Dovecot] Question to sieve symlink
On 2013-10-20 11:39 AM, Andreas Meyer anme...@anup.de wrote: Stephan Bosch step...@rename-it.nl wrote: What is your configuration (output from dovecot -n) ? I will not send this sensitive output to a public mailinglist. Do you need a special part of the output? Don't be stupid. There is little to nothing in that output that would put your system at risk - and if there was, a few seconds to obfuscate it is all it would take. Otherwise, there is nothing anyone here can dot to help you. -- Best regards, */Charles/*
Re: [Dovecot] Question to sieve symlink
Charles Marcus cmar...@media-brokers.com wrote:
On 2013-10-20 11:39 AM, Andreas Meyer anme...@anup.de wrote:
Stephan Bosch step...@rename-it.nl wrote:
What is your configuration (output from dovecot -n) ?
I will not send this sensitive output to a public mailinglist.
Do you need a special part of the output?
Don't be stupid. There is little to nothing in that output that would
put your system at risk - and if there was, a few seconds to obfuscate
it is all it would take.
Otherwise, there is nothing anyone here can dot to help you.
ok, here it is:
# 2.1.17: /etc/dovecot/dovecot.conf
# OS: Linux 3.7.10-1.16-pae i686 openSUSE 12.3 (i586)
auth_mechanisms = plain cram-md5
auth_verbose = yes
debug_log_path = /var/log/dovecot-debug.log
disable_plaintext_auth = no
hostname = delta.bitcorner.eu
log_path = /var/log/dovecot1
login_log_format_elements = user=%u method=%m rip=%r lip=%l mpid=%e %c %k
mail_home = /var/spool/vhosts/%d/%n
mail_location = maildir:~/
mail_plugins = quota
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 vacation-seconds
namespace inbox {
inbox = yes
location =
prefix =
}
passdb {
args = /etc/dovecot/passwd
driver = passwd-file
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
autocreate = Trash
autocreate2 = Drafts
autocreate3 = Sent
autosubscribe = Trash
autosubscribe2 = Drafts
autosubscribe3 = Sent
quota = maildir:User quota
quota_grace = 10%%
quota_rule = *:storage=500MB
quota_rule2 = Trash:storage=+10%%
quota_status_nouser = DUNNO
quota_status_overquota = 552 5.2.2 Mailbox is full / Mailbox ist voll
quota_status_success = DUNNO
sieve = ~/.dovecot.sieve
sieve_dir = ~/.sieve
sieve_extensions = +vacation-seconds
sieve_vacation_default_period = 10d
sieve_vacation_max_period = 30d
sieve_vacation_min_period = 1h
}
postmaster_address = postmas...@bitcorner.de
protocols = imap pop3 lmtp sieve
quota_full_tempfail = yes
service auth {
unix_listener auth-userdb {
group = vmail
mode = 0666
user = vmail
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
}
service quota-warning {
executable = script /usr/local/bin/quota-warning.sh
unix_listener quota-warning {
mode = 0666
user = vmail
}
user = vmail
}
ssl_cert = /etc/dovecot/ssl/startsslkeys/bitcorner/server.pem
ssl_cipher_list =
DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ALL:!LOW:!SSLv2:!EXP:!aNULL
ssl_key = /etc/dovecot/ssl/startsslkeys/bitcorner/key.pem
userdb {
args = /etc/dovecot/passwd
driver = passwd-file
}
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lda {
info_log_path = /var/log/dovecot-lda.log
log_path = /var/log/dovecot-lda-errors.log
mail_plugins = quota sieve
}
protocol imap {
imap_idle_notify_interval = 29 mins
mail_max_userip_connections = 20
mail_plugins = quota quota imap_quota autocreate
}
protocol lmtp {
mail_plugins = quota sieve
}
protocol sieve {
mail_max_userip_connections = 10
managesieve_implementation_string = Dovecot Pigeonhole
managesieve_logout_format = bytes=%i/%o
managesieve_max_compile_errors = 5
managesieve_max_line_length = 65536
}
protocol pop3 {
mail_max_userip_connections = 10
pop3_uidl_format = %08Xu%08Xv
}
local 78.47.3.18 {
protocol imap {
ssl_cert = /etc/dovecot/ssl/anup/server.pem
ssl_key = /etc/dovecot/ssl/anup/mail-anup-de-key.pem
}
}
local 78.47.3.18 {
protocol pop3 {
ssl_cert = /etc/dovecot/ssl/anup/server.pem
ssl_key = /etc/dovecot/ssl/anup/mail-anup-de-key.pem
}
}
local 78.47.3.19 {
protocol imap {
ssl_cert = /etc/dovecot/ssl/startsslkeys/bitcorner/server.pem
ssl_key = /etc/dovecot/ssl/startsslkeys/bitcorner/key.pem
}
}
local 78.47.3.19 {
protocol pop3 {
ssl_cert = /etc/dovecot/ssl/startsslkeys/bitcorner/server.pem
ssl_key = /etc/dovecot/ssl/startsslkeys/bitcorner/key.pem
}
}
local 78.47.3.21 {
protocol imap {
ssl_cert = /etc/dovecot/ssl/startsslkeys/foxmailer/server.pem
ssl_key = /etc/dovecot/ssl/startsslkeys/foxmailer/key.pem
}
}
local 78.47.3.21 {
protocol pop3 {
ssl_cert = /etc/dovecot/ssl/startsslkeys/foxmailer/server.pem
ssl_key = /etc/dovecot/ssl/startsslkeys/foxmailer/key.pem
}
}
local 78.47.3.22 {
protocol imap {
ssl_cert = /etc/dovecot/ssl/baubetreuung/bau.pem
ssl_key = /etc/dovecot/ssl/baubetreuung/mail-baubetreuung-de-key.pem
}
}
local 78.47.3.22 {
protocol pop3 {
ssl_cert = /etc/dovecot/ssl/baubetreuung/bau.pem
ssl_key = /etc/dovecot/ssl/baubetreuung/mail-baubetreuung-de-key.pem
}
}
I did not have this problem with the symlink before with a selfcompiled
dovecot version 2.1.17 and a selfcompiled version of
dovecot-2.1-pigeonhole-0.3.1
Now, I used the rpm-packages of the
Re: [Dovecot] Upgrade from 2.1 to 2.2 on Debian
You need the libmysqlclient-dev package if you want to compile something with mysql. Did you install it? On 10/20/2013 11:27 AM, Lucas Rothamel - Eye Catching Webdesign wrote: Hello, I am currently running Dovecot 2.1 on current Debian and need to upgrade to 2.2 to use the replication features. I understand that I therefore need to compile Dovecot myself. I am using a MySQL database for users authentication, therefore I need to compile Dovecot with mysql support: *./configure --with-mysql* Unfortunately this terminates with: *configure: error: Can't build with MySQL support: libmysqlclient not found* I installed libmysqlclient from debian repos, but it does not help. Also, how do I then connect the newly installed dovecot to my existing /etc/init.d/dovecot script? Thank you. Lucas
[Dovecot] backup maildir mailbox bugs
Hi, Using dovecot v2.2.5.5, I get the following: $ doveadm -v backup -R -u u...@example.com maildir:/home/rsync/ example.com/user/Maildir/ [...] dsync(u...@example.com): Panic: file dsync-mailbox-export.c: line 228 (export_save_change_get): assertion failed: (change-type == DSYNC_MAIL_CHANGE_TYPE_FLAG_CHANGE) dsync(u...@example.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x59e6a) [0x7f91ad185e6a] - /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f91ad185f2a] - /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f91ad144b89] - doveadm [u...@example.com Printing Quotes send:mailbox recv:mailbox](dsync_mailbox_export_init+0x8b8) [0x434028] - doveadm [ u...@example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_sync_mailbox_open+0x233) [0x42ba83] - doveadm [ u...@example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_slave_recv_mailbox+0x125) [0x42c615] - doveadm [ u...@example.com Printing Quotes send:mailbox recv:mailbox](dsync_brain_run+0x369) [0x42a929] - doveadm [user@example.comPrinting Quotes send:mailbox recv:mailbox]() [0x42881b] - doveadm [ u...@example.com Printing Quotes send:mailbox recv:mailbox]() [0x411ad7] - doveadm [u...@example.com Printing Quotes send:mailbox recv:mailbox](doveadm_mail_try_run+0x260) [0x4127a0] - doveadm [ u...@example.com Printing Quotes send:mailbox recv:mailbox](main+0x3f0) [0x4116c0] - /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f91acd8e76d] - doveadm [u...@example.com Printing Quotes send:mailbox recv:mailbox]() [0x4118bd] Other lines emitted were Info lines indicating what message was being processed. Unfortunately this appears to stop the backup dead in it's tracks. Suggestions on how to proceed? I was (originally) doing this as an IMAP to IMAP copy, and when that failed I managed to get the raw Maildir. Now I appear stuck with that too. Regards, Anand -- “Don’t be sad because it’s over. Smile because it happened.” – Dr. Seuss
Re: [Dovecot] unusual dsync lines
Hi, $ doveadm sync -1 -r raw.log -R 'doveadm -o imapc_user=foo -o imapc_password=bar -o mail=imapc: dsync-server' I couldn't get that line to work, I get errors like: doveadm(root): Fatal: Error reading configuration: Invalid -o parameter imapc:: Missing '=' dsync-local(root): Error: read(remote) failed: EOF (version not received) dsync-local(root): Panic: file iostream.c: line 37 (io_stream_unref): assertion failed: (stream-refcount 0) *** glibc detected *** doveadm: corrupted double-linked list: 0x02312620 *** I have ended up doing: $ doveadm -v -o imapc_user=u...@example.com -o imapc_password=password -o imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no sync -1 -r raw2.log -R -u u...@example.com imapc: I'll let you know if it finishes. Thanks, Anand On 22 September 2013 01:03, Timo Sirainen t...@iki.fi wrote: On 17.9.2013, at 6.25, Anand Kumria wildf...@progsoc.org wrote: Another day, another dysnc attempt. Using Dovecot v2.2.5.4; I see: Is it still duplicating mails? So if you first delete everything from destination directory, then run doveadm sync -1 twice it duplicates the mails? Or just gives them new UIDs without duplicating anything? I can't reproduce either with the latest hg version at least. There were a few fixes since v2.2.5, but I'm not sure if they were related to this. # doveadm -v -o imapc_user=u...@example.com -o imapc_password=password -o imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no sync -1 -R -u u...@example.com imapc: dsync(u...@example.com): Info: copy from Drafts: box=Drafts, uid=8343, msgid=4f387a25.5010...@example.com, size=2954969 dsync(u...@example.com): Info: copy from Drafts: box=Drafts, uid=8344, msgid=5237b0bf.7030...@example.com, size=3371710 dsync(u...@example.com): Info: copy from Drafts: box=Drafts, uid=8345, msgid=5237b588.6040...@example.com, size=3266 dsync(u...@example.com): Info: copy from Drafts: box=Drafts, uid=8346, msgid=5237b6b4.2030...@example.com, size=4201 dsync(u...@example.com): Info: copy from Drafts: box=Drafts, uid=8347, msgid=5237b888.7030...@example.com, size=3371445 dsync(u...@example.com): Info: copy from Drafts: box=Drafts, uid=8348, msgid=5237c224.9010...@example.com, size=3371745 dsync(u...@example.com): Info: copy from Drafts: box=Drafts, uid=8349, msgid=5237c350.5080...@example.com, size=3371700 dsync(u...@example.com): Info: copy from Drafts: box=Drafts, uid=8350, msgid=5237c5ee.5030...@example.com, size=3371619 dsync(u...@example.com): Info: expunge: box=Drafts, uid=8209, msgid= 4f387a25.5010...@example.com, size=2954969 The interesting lines being uid=8209 and uid=8343; why would dsync both copy and then expunge the same message from the same mailbox? I think move gets logged as copy+expunge. It probably just wanted to give a new UID to the message. Why it wanted to do that, I'm not sure .. One way to debug this would be to get rawlogs of the traffic between the two dsync brains, by running something like: doveadm sync -1 -r raw.log -R 'doveadm -o imapc_user=foo -o imapc_password=bar -o mail=imapc: dsync-server' The rawlog would then show why dsync does what it does. Also latest hg has some additional debug logging (doveadm -D), but it's still not in all the places so it might not be enough.
Re: [Dovecot] Question to sieve symlink
On 10/20/2013 6:05 PM, Andreas Meyer wrote: I did not have this problem with the symlink before with a selfcompiled dovecot version 2.1.17 and a selfcompiled version of dovecot-2.1-pigeonhole-0.3.1 Now, I used the rpm-packages of the distribution (version 2.1.13), upgraded yesterday with rpm's to version 2.1.17 but the problem persists. Could you enable mail_debug and show us what the logs say? Regards, Stephan
Re: [Dovecot] Question to sieve symlink
Stephan Bosch step...@rename-it.nl wrote: On 10/20/2013 6:05 PM, Andreas Meyer wrote: I did not have this problem with the symlink before with a selfcompiled dovecot version 2.1.17 and a selfcompiled version of dovecot-2.1-pigeonhole-0.3.1 Now, I used the rpm-packages of the distribution (version 2.1.13), upgraded yesterday with rpm's to version 2.1.17 but the problem persists. Could you enable mail_debug and show us what the logs say? I specified mail_debug = yes debug_log_path = /var/log/dovecot-debug.log in dovecot.conf and restarted dovecot, but nothing is written to the log. # doveadm log find Debug: /var/log/dovecot-debug.log Info: /var/log/dovecot1 Warning: /var/log/dovecot1 Error: /var/log/dovecot1 Fatal: /var/log/dovecot1 Regards, Stephan Andreas
Re: [Dovecot] Question to sieve symlink
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 20.10.2013 20:01, schrieb Andreas Meyer: Stephan Bosch step...@rename-it.nl wrote: On 10/20/2013 6:05 PM, Andreas Meyer wrote: I did not have this problem with the symlink before with a selfcompiled dovecot version 2.1.17 and a selfcompiled version of dovecot-2.1-pigeonhole-0.3.1 Now, I used the rpm-packages of the distribution (version 2.1.13), upgraded yesterday with rpm's to version 2.1.17 but the problem persists. Could you enable mail_debug and show us what the logs say? I specified mail_debug = yes debug_log_path = /var/log/dovecot-debug.log in dovecot.conf and restarted dovecot, but nothing is written to the log. # doveadm log find Debug: /var/log/dovecot-debug.log Info: /var/log/dovecot1 Warning: /var/log/dovecot1 Error: /var/log/dovecot1 Fatal: /var/log/dovecot1 Regards, Stephan Andreas does it exist ,is it writable ? Best Regards MfG Robert Schetterer - -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSZBtOAAoJEP8jBObu0LlEhDkH/2OnCkfIKQWlun97jeJk6ujR BefuHWVr4AKyoLlCbhy5iZ4rLMIMtWGrqTMHqI6hgieAwmVrv2k7VOhziiBU25q5 c5M1ymR3tnYUIG6D4ublGLbOyPh4F063ZdVbOgb9tVjI8Kd7JMU434liBzIMmdrF CixXQU1YiCuCz+tSjXOYIOjlcEarh0OGSFUBq1luUYL2b0NivcMQE0xAHX7jQP09 OyXpVdDvG7dfInn3o6/4GOE+1Ar8l239RW67STrAM8mOJ47bzxIBBn7YmSIbwE6Z Sv1JqzwhrFElPqgJMcDI9j5aAPdxREaNEv0JV/F7DX54lT10u5Dc7s6NhXrigg8= =RXO3 -END PGP SIGNATURE-
Re: [Dovecot] Question to sieve symlink
Stephan Bosch step...@rename-it.nl wrote: On 10/20/2013 6:05 PM, Andreas Meyer wrote: I did not have this problem with the symlink before with a selfcompiled dovecot version 2.1.17 and a selfcompiled version of dovecot-2.1-pigeonhole-0.3.1 Now, I used the rpm-packages of the distribution (version 2.1.13), upgraded yesterday with rpm's to version 2.1.17 but the problem persists. Could you enable mail_debug and show us what the logs say? In the debug.log I have this Oct 20 20:10:39 managesieve: Debug: Loading modules from directory: /usr/lib/dovecot/modules Oct 20 20:10:39 managesieve: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Oct 20 20:10:39 managesieve: Debug: Added userdb setting: mail=maildir:~/ Oct 20 20:10:39 managesieve: Debug: Added userdb setting: plugin/quota_rule=*:bytes=1G Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: Effective uid=5000, gid=5000, home=/var/spool/vhosts/anup.de/anmeyer Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: Quota root: name=User quota backend=maildir args= Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=0 Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: Quota rule: root=User quota mailbox=Trash bytes=+107374182 (10%) messages=0 Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/ Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: maildir++: root=/var/spool/vhosts/anup.de/anmeyer, index=, control=, inbox=/var/spool/vhosts/anup.de/anmeyer, alt= Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: sieve-storage: using active sieve script path: /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: sieve-storage: using sieve script storage directory: /var/spool/vhosts/anup.de/anmeyer/.sieve Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: sieve-storage: using permissions from /var/spool/vhosts/anup.de/anmeyer/.sieve: mode=0700 gid=-1 Oct 20 20:10:39 managesieve(anme...@anup.de): Debug: sieve-storage: relative path to sieve storage in active link: .sieve/ Oct 20 20:10:51 managesieve: Debug: Loading modules from directory: /usr/lib/dovecot/modules Oct 20 20:10:51 managesieve: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Oct 20 20:10:51 managesieve: Debug: Added userdb setting: mail=maildir:~/ Oct 20 20:10:51 managesieve: Debug: Added userdb setting: plugin/quota_rule=*:bytes=1G Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: Effective uid=5000, gid=5000, home=/var/spool/vhosts/anup.de/anmeyer Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: Quota root: name=User quota backend=maildir args= Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: Quota rule: root=User quota mailbox=* bytes=1073741824 messages=0 Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: Quota rule: root=User quota mailbox=Trash bytes=+107374182 (10%) messages=0 Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/ Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: maildir++: root=/var/spool/vhosts/anup.de/anmeyer, index=, control=, inbox=/var/spool/vhosts/anup.de/anmeyer, alt= Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve-storage: using active sieve script path: /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve-storage: using sieve script storage directory: /var/spool/vhosts/anup.de/anmeyer/.sieve Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve-storage: using permissions from /var/spool/vhosts/anup.de/anmeyer/.sieve: mode=0700 gid=-1 Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve-storage: relative path to sieve storage in active link: .sieve/ Oct 20 20:10:51 imap: Debug: Loading modules from directory: /usr/lib/dovecot/modules Oct 20 20:10:51 imap: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Oct 20 20:10:51 imap: Debug: Module loaded: /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so Oct 20 20:10:51 imap: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_autocreate_plugin.so Oct 20 20:10:51 imap: Debug: Added userdb setting: mail=maildir:~/ Oct 20 20:10:51 imap: Debug: Added userdb setting: plugin/quota_rule=*:bytes=1G Oct 20 20:10:51 imap(anme...@anup.de): Debug: Effective uid=5000, gid=5000, home=/var/spool/vhosts/anup.de/anmeyer Oct 20 20:10:51 imap(anme...@anup.de): Debug: Quota root:
Re: [Dovecot] Question to sieve symlink
Robert Schetterer r...@sys4.de wrote: Am 20.10.2013 20:01, schrieb Andreas Meyer: Stephan Bosch step...@rename-it.nl wrote: Now, I used the rpm-packages of the distribution (version 2.1.13), upgraded yesterday with rpm's to version 2.1.17 but the problem persists. Could you enable mail_debug and show us what the logs say? I specified mail_debug = yes debug_log_path = /var/log/dovecot-debug.log in dovecot.conf and restarted dovecot, but nothing is written to the log. # doveadm log find Debug: /var/log/dovecot-debug.log Info: /var/log/dovecot1 Warning: /var/log/dovecot1 Error: /var/log/dovecot1 Fatal: /var/log/dovecot1 does it exist ,is it writable ? I set mail_debug = yes debug_log_path = /var/log/dovecot-debug.log in the dovecot.conf but in the 10-logging.conf there was mail_debug = no set. I thought the dovecot.conf would overtop the 10-logging.conf Best Regards MfG Robert Schetterer Andreas
Re: [Dovecot] Question to sieve symlink
On 10/20/2013 8:15 PM, Andreas Meyer wrote: Stephan Bosch step...@rename-it.nl wrote: Could you enable mail_debug and show us what the logs say? In the debug.log I have this Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve-storage: using active sieve script path: /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve-storage: using sieve script storage directory: /var/spool/vhosts/anup.de/anmeyer/.sieve Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve-storage: using permissions from /var/spool/vhosts/anup.de/anmeyer/.sieve: mode=0700 gid=-1 Oct 20 20:10:51 managesieve(anme...@anup.de): Debug: sieve-storage: relative path to sieve storage in active link: .sieve/ In the regular log this: Oct 20 20:10:39 managesieve-login: Info: Login: user=anme...@anup.de, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, mpid=1898, secured Oct 20 20:10:39 managesieve(anme...@anup.de): Warning: sieve-storage: Active sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown path to storage (points to /var/spool/vhosts/anup.de/anmeyer/.sieve/banane.sieve). Oct 20 20:10:39 managesieve(anme...@anup.de): Warning: sieve-storage: Active sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown path to storage (points to /var/spool/vhosts/anup.de/anmeyer/.sieve/banane.sieve). Oct 20 20:10:39 managesieve(anme...@anup.de): Info: Disconnected: Logged out bytes=52/1565 This looks like a bug to me. Could you try to set: sieve_dir = ~/.sieve/ (notice the slash at the end) Does it stop complaining now? Regards, Stephan.
Re: [Dovecot] Question to sieve symlink
Stephan Bosch step...@rename-it.nl wrote: Oct 20 20:10:39 managesieve-login: Info: Login: user=anme...@anup.de, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, mpid=1898, secured Oct 20 20:10:39 managesieve(anme...@anup.de): Warning: sieve-storage: Active sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown path to storage (points to /var/spool/vhosts/anup.de/anmeyer/.sieve/banane.sieve). Oct 20 20:10:39 managesieve(anme...@anup.de): Warning: sieve-storage: Active sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is broken: invalid/unknown path to storage (points to /var/spool/vhosts/anup.de/anmeyer/.sieve/banane.sieve). Oct 20 20:10:39 managesieve(anme...@anup.de): Info: Disconnected: Logged out bytes=52/1565 This looks like a bug to me. Could you try to set: sieve_dir = ~/.sieve/ (notice the slash at the end) Does it stop complaining now? well allright, that seems to solve the problem. No complains anymore so far about the broken symlink. Regards, Stephan. Thank you so much! Andreas
Re: [Dovecot] Upgrade from 2.1 to 2.2 on Debian
Lucas Rothamel - Eye Catching Webdesign i...@eye-catching-webdesign.de wrote: I am currently running Dovecot 2.1 on current Debian and need to upgrade to 2.2 to use the replication features. I understand that I therefore need to compile Dovecot myself. No. Just use the excellent packages from http://xi.rename-it.nl/debian/ See http://wiki2.dovecot.org/PrebuiltBinaries for more information. It says Don't use them in production on the label of the repository, but if you set the installed packages on hold via dpkg/apt-get so you don't get suprised by sudden updates, this repository is safe to use. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: [Dovecot] Upgrade from 2.1 to 2.2 on Debian
On 10/20/2013 05:39 PM, Sven Hartge wrote: Lucas Rothamel - Eye Catching Webdesign i...@eye-catching-webdesign.de wrote: I am currently running Dovecot 2.1 on current Debian and need to upgrade to 2.2 to use the replication features. I understand that I therefore need to compile Dovecot myself. No. Just use the excellent packages from http://xi.rename-it.nl/debian/ See http://wiki2.dovecot.org/PrebuiltBinaries for more information. It says Don't use them in production on the label of the repository, but if you set the installed packages on hold via dpkg/apt-get so you don't get suprised by sudden updates, this repository is safe to use. Grüße, Sven. I agree in principle, specifically if you just look at the last commits at http://hg.dovecot.org/dovecot-2.2/ so you know what your latest binaries contain, and it seems to make sense, then you can put the packages on hold, and test them given your particular configuration and demands. if it works, then .. it works. If you want the proper debian way, just take the 2.2 package from debian's experiemental suite , refresh it to 2.2.6 and compile it. It's not all that hard to do.
Re: [Dovecot] Upgrade from 2.1 to 2.2 on Debian
Gedalya geda...@gedalya.net wrote: On 10/20/2013 05:39 PM, Sven Hartge wrote: Lucas Rothamel - Eye Catching Webdesign i...@eye-catching-webdesign.de wrote: I am currently running Dovecot 2.1 on current Debian and need to upgrade to 2.2 to use the replication features. I understand that I therefore need to compile Dovecot myself. No. Just use the excellent packages from http://xi.rename-it.nl/debian/ See http://wiki2.dovecot.org/PrebuiltBinaries for more information. It says Don't use them in production on the label of the repository, but if you set the installed packages on hold via dpkg/apt-get so you don't get suprised by sudden updates, this repository is safe to use. I agree in principle, specifically if you just look at the last commits at http://hg.dovecot.org/dovecot-2.2/ so you know what your latest binaries contain, and it seems to make sense, then you can put the packages on hold, and test them given your particular configuration and demands. if it works, then .. it works. If you want the proper debian way, just take the 2.2 package from debian's experiemental suite , refresh it to 2.2.6 and compile it. It's not all that hard to do. The moment the included pigeonhole patch does no longer apply cleanly, simply respinning the package becomes a tad more difficult. If you know your way around the Debian packaging tools, this is of course no big problem. All others might be better of with the packages from rename-it.nl, as those are based on the latest packages from Debian with all the matching patches applied. Grüße, Sven. -- Sigmentation fault. Core dumped.
