Re: [Dovecot] Unable to send email out using Dovecot SASL
[EMAIL PROTECTED] wrote: Hi, I am currently using Dovecot 1.0.rc17 with Postfix 2.3.8 on Ubuntu. So far I'm able to receive my email using dovecot pop3 but I can't send out the email. Anybody managed to get Postfix with Dovecot SASL support so far? What do I missed out? You must configure both of them - for working example see: http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL Uldis
Re: [Dovecot] modules/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set
I have tested this issue on the following versions: * Debian etch: 1.0.rc15 * RedHat AS 5: 1.0.rc15 * Debian sid: 1.0.0 Isn't it considered best practices to not report a bug unless/until you have tested something on the current shipping/stable version (1.0.1), as opposed to an older test version that has known problems? I do believe a *lot* of quota stuff was fixed after rc15... -- Best regards, Charles
[Dovecot] modules/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set
Hi,
I wanted to enable FS quota support in dovecot, and have configured the
following directives:
protocol imap {
mail_plugins = imap_quota
}
plugin {
quota = fs
}
With this additional settings, my normally working dovecot.conf doesn't start
anymore:
Starting mail server:
dovecotEdlopen(/usr/lib/dovecot/modules/imap/lib02_imap_quota_plugin.so)
failed: /usr/lib/dovecot/modules/imap/lib02_imap_quota_plugin.so: undefined
symbol: quota_set
Error: imap dump-capability process returned 89
I have tested this issue on the following versions:
* Debian etch: 1.0.rc15
* RedHat AS 5: 1.0.rc15
* Debian sid: 1.0.0
Thanks for any help in this issue.
Philipp Kolmann
--
If you have problems in Windows: REBOOT
If you have problems in Linux: BE ROOT
Re: [Dovecot] modules/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set
Hi,
Quoting Philipp Kolmann [EMAIL PROTECTED]:
Hi,
I wanted to enable FS quota support in dovecot, and have configured the
following directives:
protocol imap {
mail_plugins = imap_quota
The imap_quota plugin depends on the quota plugin. You should try
mail_plugins = quota imap_quota
Cheers,
Nicolas
[Dovecot] assertion failed invalid password field
I'm getting these in my log: Jul 6 09:52:51 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 09:52:51 postamt dovecot: child 31576 (login) killed with signal 6 Jul 6 10:37:44 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 10:37:44 postamt dovecot: child 25241 (login) killed with signal 6 Jul 6 13:14:51 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 6 13:14:51 postamt dovecot: child 4418 (login) killed with signal 6 and I get those for accounts I deactivated using usermod -L, maybe dovecot should log something like account disabled instead: Jul 6 11:07:01 postamt dovecot: auth(default): shadow(vnedwed,77.128.63.72): invalid password field Jul 6 11:07:06 postamt dovecot: auth(default): shadow(vnedwed,77.128.63.72): invalid password field Jul 6 14:12:40 postamt dovecot: auth(default): shadow(jechafch,141.42.4.251): invalid password field This is dovecot-1.0.1 -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise.
Re: [Dovecot] modules/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set
On Fri, Jul 06, 2007 at 02:58:58PM +0200, Nicolas Boullis wrote:
Hi,
Quoting Philipp Kolmann [EMAIL PROTECTED]:
Hi,
I wanted to enable FS quota support in dovecot, and have configured the
following directives:
protocol imap {
mail_plugins = imap_quota
The imap_quota plugin depends on the quota plugin. You should try
mail_plugins = quota imap_quota
thanks Nicolas, that was the trick.
Philipp
PS: It gives the same error msg with 1.0.1
--
If you have problems in Windows: REBOOT
If you have problems in Linux: BE ROOT
Re: [Dovecot] Unable to send email out using Dovecot SASL
At 1:34 PM +0800 7/6/07, [EMAIL PROTECTED] imposed structure on a stream of electrons, yielding: Hi, I am currently using Dovecot 1.0.rc17 with Postfix 2.3.8 on Ubuntu. Upgrading to the release version of Dovecot would be a good idea. although it is not likely to be related to your trouble. So far I'm able to receive my email using dovecot pop3 but I can't send out the email. Anybody managed to get Postfix with Dovecot SASL support so far? Yes. I use it all the time. What do I missed out? Probably nothing on the Dovecot side. Outbound mail does not involve Dovecot except in providing authentication services for Postfix. You will need to at least share the error message you are getting for anyone to have any clue as to how to help, and probably your master.cf and main.cf files from Postfix as well. This is *probably* better directed at the Postfix community, but there are likely to be people here who can help. -- Bill Cole [EMAIL PROTECTED]
[Dovecot] problem with subscriptions file version 1.0.1
Hello, I am currently working on a patch to add IMAPdir support to dovecot. (For those who do not know, IMAPdir is exactly like Maildir except that instead of having a folder .foo it would just be foo. The advantage is that the file system is slightly easier to search through without the dot in front of the folders.) The first thing I did was get the configuration file working for Maildir. So I know that the problem has nothing to do with the configuration file. Next I looked through the actual source code to find any place where a dot might be added to the beginning of a folder. It transpired that there is a constant, MAILDIR_FS_SEP_S, which is assigned the value .. I deleted all the occurrences of this constant, compiled the source code again, and ran into a rather interesting problem. When I try to create a new folder through Thunderbird on a separate machine, the folder is not visible unless I restart Thunderbird. I checked on the machine acting as a server and the folder is created and the subscriptions file is updated, and the dot at the beginning is indeed absent. So I see no reason why this should not work. If I had deleted some of the constants that ought not have been deleted, the subscriptions file would not be readable at all and I would not be able to see the folder when Thunderbird restarts. If there were some sort of deadlock going on with the subscriptions file, one would think that it would not be caused by deleting the constants. I would have run into the problem before editing any of the source code. I know for fact that the only thing different about my source code and the code available for downloading is the deleted constants. If anyone has any ideas, please let me know. If you need more information, please feel free to prompt me for it because I have no idea what might be useful that I have not already provided. Regards, Elizabeth Bermel
Re: [Dovecot] Upgrade from 1.00 to 1.0.1
On Thursday 05 July 2007 10:49:02 Timo Sirainen wrote: On Thu, 2007-07-05 at 11:34 +0200, Jon Essen-Moller wrote: Hi, I tried uprading and I get less errors but I still get them. Don't you get any error messagess with dovecot-1.0_rc29? What error messages? FWIW, after my upgrade from 1.0.0 - 1.0.1, I started getting similar error messages in my mail.err log but no one is complaining so I figure they are harmless. Jul 5 14:14:08 giganta dovecot: IMAP([EMAIL PROTECTED]): /home/h/Maildir/.Development.HUD/dovecot-uidlist: Broken header (uidvalidity = 0, next_uid=2) Jul 5 14:14:08 giganta dovecot: IMAP([EMAIL PROTECTED]): Maildir /home/h/Maildir/.Development.HUD sync: UIDVALIDITY changed (1168017041 - 1183659248) Jim
Re: [Dovecot] utime : operation not permitted
On Tuesday 03 July 2007 18:47:41 Jim Horner wrote: This should fix it: http://hg.dovecot.org/dovecot-1.0/rev/8f7e3311006f before I try that I found Jul 1 22:13:48 giganta dovecot: IMAP([EMAIL PROTECTED]): utime(/home/rootmail/Maildir/tmp) failed: Operation not permitted I've applied the patch. I will report back. It happens pretty infrequently... so it could be a while. I haven't seen any utime errors in 3 days. Thanks.
Re: [Dovecot] Unable to send email out using Dovecot SASL
I am currently using Dovecot 1.0.rc17 with Postfix 2.3.8 on Ubuntu. When you choose to use software with known bugs and security issues that have already been fixed in later versions, you really should make sure you know exactly what all of those issues are and whether or not they affect you. So far I'm able to receive my email using dovecot pop3 but I can't send out the email. Why not? Error messages and a postconf -n might help here. What do I missed out? Have you read: http://www.postfix.org/SASL_README.html what were the results when you went through the troubleshooting steps? -- Kenny Dail [EMAIL PROTECTED]
Re: [Dovecot] Your IMAP server has closed the connection.
-Original Message- From: [EMAIL PROTECTED] [mailto:dovecot- [EMAIL PROTECTED] On Behalf Of Dehnert James Sr Sent: Friday, July 06, 2007 11:16 AM To: Dovecot Mailing List Subject: [Dovecot] Your IMAP server has closed the connection. I'm getting a large number of ... Your IMAP server has closed the connection. This may occur if you have left the connection idle for too long. errors. These are confusing my clients. Is there a way to set the timeout on the dovecot server to help avoid this? [Bill Milford] I get these too. I am using outlook 2003 in IMAP mode. I have turned on raw logs and I do not see anything happening in the dovecot logs.
