[Dovecot] Command output: Failed to write to log file
Hi dovecot -n at end of message. Jul 13 09:41:56 findb postfix/smtpd[15996]: connect from unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/smtpd[15996]: 3B7EF56ABA: client=unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/cleanup[15999]: 3B7EF56ABA: message-id=26cdbd30f4fe1d4fb6fb5f6d16bca93e0e5b777...@rveb1srvmsgccr1.c ymru.nhs.uk Jul 13 09:41:56 findb postfix/qmgr[15667]: 3B7EF56ABA: from=, size=1711, nrcpt=1 (queue active) Jul 13 09:41:56 findb postfix/smtpd[15996]: disconnect from unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/local[16000]: 3B7EF56ABA: to=endu...@thishost.com, relay=local, delay=0.05, delays=0.03/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to write to log file) Our postfix server started logging the above messages so I was thinking I had a postfix issue, but it turned out that recreating the dovecot.log file fixed the issue. Does the /var/log/dovecot.log file require special permissions or can it only grow to a certain size ? [/var/log]# dovecot -n # 1.2.10: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 x86_64 Red Hat Enterprise Linux Server release 5.2 (Tikanga) log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_access_groups: mail mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: postmaster_address: r...@localhost mail_plugins: sieve auth default: debug: yes passdb: driver: pam userdb: driver: passwd plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/ log_path: /var/log/dovecot.log Many thanks Nick . __ Information from ESET NOD32 Antivirus, version of virus signature database 5273 (20100712) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
Re: [Dovecot] v2.0.rc2 released
Le 07/12/2010 02:18 PM, Timo Sirainen a écrit : I think you can do make pkgsysconfdir=/etc/opt/dovecot-rc It doesn't work properly for the «install» Makefile target: libdovecot is built to look for the config file in /etc/opt/dovecot-rc, so that's good. But it seems in two places, it's not used on install. In doc/example-config/Makefile.in: install-data-local: $(mkdir_p) $(DESTDIR)/$(sysconfdir)/dovecot And another one is using a dovecotconfdir instead of pkgsysconfdir: doc/example-config/Makefile.in: dovecotconfdir = $(sysconfdir)/dovecot I guess you mean that it stops at doc/man/? That was a bug and has been fixed. Alright, so it was a bug :-) Thanks for fixing it. Laurent
[Dovecot] sieve make test fails
I am trying out the sieve plugin (commit 843ba8e66e1b) and dovecot-2.0.rc2. Given $ ./configure --with-dovecot=../dovecot-2.0.rc2/ --with-managesieve make test fails with: testu...@linode /tmp/dovecot-2-0-pigeonhole-843ba8e66e1b $ make test testsuite(testuser): Error: user testuser: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/testuser testsuite(testuser): Fatal: Invalid user settings. Refer to server log for more information. make: *** [tests/testsuite.svtest] Error 89 /home/testuser and /home/testuser/sieve exists. What am I missing? -- Eray
Re: [Dovecot] Command output: Failed to write to log file
On 13.7.2010, at 9.53, Nick Lunt wrote: Jul 13 09:41:56 findb postfix/local[16000]: 3B7EF56ABA: to=endu...@thishost.com, relay=local, delay=0.05, delays=0.03/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to write to log file) Our postfix server started logging the above messages so I was thinking I had a postfix issue, but it turned out that recreating the dovecot.log file fixed the issue. Does the /var/log/dovecot.log file require special permissions or can it only grow to a certain size ? See http://wiki.dovecot.org/LDA#logging, especially the part about Postfix's mailbox_size_limit.
Re: [Dovecot] Director proxy timeout
On 12.7.2010, at 22.13, Brad Davidson wrote: It does look like all of the Maximum execution time of 120 seconds exceeded errors logged by Apache are within Roundcube's GetCapability readLine loop. There have been problems in the past with Roundcube's IMAP code going off the deep end if it loses its IMAP connection. I'll see if I can't do something about that, but it would also be nice if I could figure out why I'm getting disconnected between LOGIN and CAPABILITY in the first place. Hmm. Between? Is it doing CAPABILITY before or after login or both? That anyway sounds different from the idle timeout problem..
Re: [Dovecot] v2.0.rc2 released
On 13.7.2010, at 10.15, Laurent Blume wrote: Le 07/12/2010 02:18 PM, Timo Sirainen a écrit : I think you can do make pkgsysconfdir=/etc/opt/dovecot-rc It doesn't work properly for the «install» Makefile target: libdovecot is built to look for the config file in /etc/opt/dovecot-rc, so that's good. But it seems in two places, it's not used on install. Yes, I noticed those too and fixed them yesterday.
Re: [Dovecot] Command output: Failed to write to log file
-Original Message- From: Timo Sirainen [mailto:t...@iki.fi] Sent: 13 July 2010 12:45 To: Nick Lunt Cc: dovecot@dovecot.org Subject: Re: [Dovecot] Command output: Failed to write to log file On 13.7.2010, at 9.53, Nick Lunt wrote: Jul 13 09:41:56 findb postfix/local[16000]: 3B7EF56ABA: to=endu...@thishost.com, relay=local, delay=0.05, delays=0.03/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to write to log file) Our postfix server started logging the above messages so I was thinking I had a postfix issue, but it turned out that recreating the dovecot.log file fixed the issue. Does the /var/log/dovecot.log file require special permissions or can it only grow to a certain size ? See http://wiki.dovecot.org/LDA#logging, especially the part about Postfix's mailbox_size_limit. Aha that must be it, thanks for the pointer, much appreciated. Nick. __ Information from ESET NOD32 Antivirus, version of virus signature database 5273 (20100712) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
[Dovecot] Master Users
Greetings, My company is currently using dovecot with ldap, I am in the process of migrating this over to Exchange. However, to make the process a lot smoother I need to make use of the master user function of dovecot to enable access to other users mailboxes without needing their password. I've gone through the documentation but it looks like this might not be possible with an ldap backend. The wiki isnt exactly crystal clear on where the master user config needs to go. I've generated a passdb file with an admin user and password. Any information that would go to help would be very welcome. Cheers --
[Dovecot] pigeonhole, regex, UTF-8
Hello, I am just learning about pigeonhole and thinking of using it. I see that regex doesn't supportf UTF-8. Any particular reason for this? If it is a library problem is the library, have you looked at tre? I am using it in a project (I am using it in wchar_t mode because elsewhere all date is converted to wchar_t). It does work with UTF-8. Thanks, Trever
Re: [Dovecot] Master Users
I have an ldap configuration but i have done the same as you.
In dovecot.conf:
auth_master_user_separator=*
passdb passwd-file {
args = /usr/local/etc/passwd.masterusers
master= yes
}
I have used this to generate passwd.masterusers file:
htpasswd -b -c -s /usr/local/etc/passwd.masterusers user password
The passwd.masterusers :
admin:{SHA}gfdokoir9ewerre
Then i authenticate using:
user*admin
password of the administration.
Greetings,
Andrés Fernando Yacopino
Infraestructura - Dpto Sistemas
AcaSalud
Cooperativa de Prestaciones Médico Asistenciales Limitada
Tel: 0341-4208755
ayacop...@acasalud.com.ar
El 13/07/10 09:48, Ben Watts escribió:
Greetings,
My company is currently using dovecot with ldap, I am in the process of
migrating this over to Exchange. However, to make the process a lot
smoother I need to make use of the master user function of dovecot to
enable access to other users mailboxes without needing their password.
I've gone through the documentation but it looks like this might not be
possible with an ldap backend.
The wiki isnt exactly crystal clear on where the master user config
needs to go. I've generated a passdb file with an admin user and password.
Any information that would go to help would be very welcome.
Cheers
Re: [Dovecot] sieve make test fails
Eray Aslan wrote: I am trying out the sieve plugin (commit 843ba8e66e1b) and dovecot-2.0.rc2. Given $ ./configure --with-dovecot=../dovecot-2.0.rc2/ --with-managesieve make test fails with: testu...@linode /tmp/dovecot-2-0-pigeonhole-843ba8e66e1b $ make test testsuite(testuser): Error: user testuser: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/testuser testsuite(testuser): Fatal: Invalid user settings. Refer to server log for more information. make: *** [tests/testsuite.svtest] Error 89 /home/testuser and /home/testuser/sieve exists. What am I missing My bad. Fixed: http://hg.rename-it.nl/dovecot-2.0-pigeonhole/rev/1809aab8dfa2 Regards, Stephan.
Re: [Dovecot] pigeonhole, regex, UTF-8
Trever L. Adams wrote: Hello, I am just learning about pigeonhole and thinking of using it. I see that regex doesn't supportf UTF-8. Any particular reason for this? The standard regexp library does not support unicode and I was not planning to write my own regexp compiler any time soon. If it is a library problem is the library, have you looked at tre? I am using it in a project (I am using it in wchar_t mode because elsewhere all date is converted to wchar_t). It does work with UTF-8. As a matter of fact, I haven't looked at TRE before. I'm quite interested though, since it is backwards compatible with POSIX and seems to be available in most systems. I'll give it a closer look, also in terms of compatibility with the latest draft of the Sieve regex extension specification. Regards, Stephan.
Re: [Dovecot] pigeonhole, regex, UTF-8
On 07/13/2010 10:16 AM, Stephan Bosch wrote: The standard regexp library does not support unicode and I was not planning to write my own regexp compiler any time soon. I wouldn't want to write one as well. As a matter of fact, I haven't looked at TRE before. I'm quite interested though, since it is backwards compatible with POSIX and seems to be available in most systems. I'll give it a closer look, also in terms of compatibility with the latest draft of the Sieve regex extension specification. Regards, Stephan. There are a few odd things about the wide character support in TRE. Either you need to convert each message to wchar_t and make sure you set the system encoding to wchar_t, or you need to set the system encoding for each message, which may or may not mess up your UTF-8 regex. My project is an Internet Classifier (used with things like Squid proxy to make a filter). I convert everything to wchar_t (using iconv with info gathered from headers) and use the wide character versions of the functions. That way I know everything is just fine. I then have the program set the system encoding (at least the environment variable for the given session) to UTF-8 before I do any of the regex compiling. Everything works wonderfully and quite quickly. I am not sure TRE is available on all systems where dovecot is designed to be compiled. I know it is for most, if not all, Unix-like systems. I use it in Fedora. Anyway, thank you your work on pigeonhole. Trever
Re: [Dovecot] dovecot-antispam for dovecot 2.0?
To be honest, I don't really have a whole lot of time for this project any more, I'd be happy if somebody wanted to adopt it more fully. johannes I may not be the best person for this as I do not have a way of hosting the git tree and I am not super familiar with dovecot's internals, but I think I can help out a bit. Trever
[Dovecot] list=children versus alpine
Hi, when I add a collection in Alpine, Apline verifies the existence of the added folder/namespace, like for instance adding 'common.': 0a LIST common. 0b LIST common Common is a shared folder. Some folder are available under that namespace. With list=yes Alpine can add the collection, with list=children it's not possible. Alpine thinks that the folder doesn't exist and it tries to create it. This results in a Namespace already exists. error. 'LIST common' seems to return different results. I expected that list=children and list=all behave identical as long as there are folders in that namespace. Regards, Matthias
[Dovecot] mailbox_storage_vfuncs: mailbox_open - ? in 2.0
Hello,
I am working on fixing dovecot-antispam to work with dovecot 2.0. I am
down to three errors/warnigns that concern me.
The one I need help from those more familiar with dovecot internals is
in the subject. What happened to mailbox_open? Did it disappear? Did it
get renamed?
It appears that I am needing to override some methods:
if (need_folder_hook) {
/* override save_init to override want_mail, we need that */
box-v.save_begin = antispam_save_begin;
box-v.save_finish = antispam_save_finish;
box-v.transaction_begin =
antispam_mailbox_transaction_begin;
box-v.transaction_commit =
antispam_mailbox_transaction_commit;
box-v.transaction_rollback =
antispam_mailbox_transaction_rollback;
box-v.copy = antispam_copy;
}
if (need_keyword_hook)
box-v.mail_alloc = antispam_mailbox_mail_alloc;
Thank you for any help.
Trever
--
A traveler on the information superhighway who often stops and looks
around...
Re: [Dovecot] mailbox_storage_vfuncs: mailbox_open - ? in 2.0
On Tue, 2010-07-13 at 13:41 -0600, Trever L. Adams wrote: I am working on fixing dovecot-antispam to work with dovecot 2.0. You're actually a bit late :) Eugene Paskevich eug...@raptor.kiev.ua has been working on it for a while now and apparently it's nearly done. We were just about to put the repo to hg.dovecot.org. I am down to three errors/warnigns that concern me. The one I need help from those more familiar with dovecot internals is in the subject. What happened to mailbox_open? Did it disappear? Did it get renamed? With v1.x you could only open+close a mailbox. Now you can alloc, open/close multiple times, free.
Re: [Dovecot] list=children versus alpine
On Tue, 2010-07-13 at 21:32 +0200, Matthias Rieber wrote: 0a LIST common. 0b LIST common Common is a shared folder. Some folder are available under that namespace. With list=yes Alpine can add the collection, with list=children it's not possible. Alpine thinks that the folder doesn't exist and it tries to create it. This results in a Namespace already exists. error. Bug. Fixed: http://hg.dovecot.org/dovecot-2.0/rev/3972e896865d
Re: [Dovecot] mailbox_storage_vfuncs: mailbox_open - ? in 2.0
On 07/13/2010 01:47 PM, Timo Sirainen wrote: You're actually a bit late :) Eugene Paskevich eug...@raptor.kiev.ua has been working on it for a while now and apparently it's nearly done. We were just about to put the repo to hg.dovecot.org. Well, that will save me from having to find a way to host a git tree. Thank you for letting me know. The last few hours have been fun and I have learned a little about dovecot's internals. Thank you Eugene. Will this become an included plugin in the dovecot distribution? Eugene, would you be interested in some comments on fixing the build system so that it can be packaged in RPM easily (all plugin versions compiled)? Right now, I do the trick through RPM, but I think they can all be moved into the Makefile without too much trouble. Thank you Eugene and Timo. Trever
Re: [Dovecot] mailbox_storage_vfuncs: mailbox_open - ? in 2.0
On Tue, 2010-07-13 at 14:05 -0600, Trever L. Adams wrote: Will this become an included plugin in the dovecot distribution? Problem 1) It's currently GPL so it would need a license change to LGPLv2. Problem 2) I don't want to add support for n different antispam software inside Dovecot. I'd rather prefer the code to just be a generic execute this program and then have those different external programs/scripts for different antispams. And if 2) is done, it would be even nicer if the whole plugin could be a more generic execute program x when event y happens type of plugin that didn't really even have anything to do with spam..
[Dovecot] Migrating to dovecot configuration questions
I am currently running a mail server on an earlier version of Red Hat Advanced Server, sendmail and UW IMAP (imap-2007e). I am considering changing to Dovecot for IMAP but have a few configuration questions in regards to a hashed directory setup. Right now the mail spool for everyone's mailbox is located in /var/mail/first letter of email address/second letter of email address, for example ajaym would be found in /var/mail/a/j ,email address john would be in /var/mail/j/o and so on. Most users using IMAP have a home directory where they can store their personal folders, trash, sent items, etc.. in /home/username. I am looking for some configuration information on making a smooth transition from UW IMAP to Dovecot and keeping the existing directory structure. Any info or suggestions?? Thanks Adam -
Re: [Dovecot] Migrating to dovecot configuration questions
On 14.7.2010, at 0.50, Adam wrote: Right now the mail spool for everyone's mailbox is located in /var/mail/first letter of email address/second letter of email address, for example ajaym would be found in /var/mail/a/j ,email address john would be in /var/mail/j/o and so on. So that would be the INBOX. Most users using IMAP have a home directory where they can store their personal folders, trash, sent items, etc.. in /home/username. This would be the mail root directory. Probably you can use the home directory that's in passwd. I am looking for some configuration information on making a smooth transition from UW IMAP to Dovecot and keeping the existing directory structure. mail_location = mbox:~/:INBOX=/var/mail/%1n/%1.1n/%n Although you should consider moving the mails from home directory to e.g. ~/mail/ directory. Would help to avoid trouble in future.
