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.
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] 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] 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] dovecot sieve notify mailto
Timo Sirainen wrote:
> On Tue, 2007-07-03 at 21:13 +0300, Uldis Pakuls wrote:
>
>>> http://article.gmane.org/gmane.mail.imap.dovecot/20813/match
>>>
>>> Thanks,
>>>
>> I wrote this patch about 6 moth ago. As far, as I tested it, it works as
>> expected. Other users reports only success with this path too.
>> Timo: My be it's good idea to include this patch in CVS version? Anyway
>> original code only reports "generic error" as "notify" method is
>> unimplemented, and produces bounce messages.
>>
>
> Yes .. Although I have another version by Petr Smotek <[EMAIL PROTECTED]> as
> well. I haven't looked closely either of your patches, so want to tell
> me which one would be better? :) Attached the other one.
>
>
I have "looked closely" at both and here is result - new patch:)
1. Peter removed sieve action report from notify message... this my be
confusing as actions are not only "keep".
notify my be sent for forward, reject etc. actions, so I left this list
at end of message as is.
2. Peter's patch tries to mark sent messages with duplicate_mark() but
never used any check...
Actually I dot see any reason for such marking, as notify message are
not stored anywhere in mail storage - it is sent directly to external
"sendmail_bin" and discarded from memory.
new things added:
1. headers "Auto-Submitted: Precedence:" for better handing by
auto-responders.
2. check for 8bit characters in message.
and most important things:
1. notify now always reports SIEVE_OK as notify failure is not delivery
failure. all notify failures are reported in log. Also "SIEVE_ERROR"
aborts script execution, but there is no reason to abort on notify error.
2. sieve plugin returns "-1" if script failed load or on any error. i
think it is wrong; if no scripts are executed or it is aborted for some
reason - it is not fatal delivery error; this just means "nothing is
done" by script. so i changed plugin always return "0" on errors.
but one problem still remains... if script is executed and mail is
delivered to mailbox, but next action failed (e.g. notify, vocation,
etc.) deliver incorrectly sends bounce messages while mail is
successfully delivered.
sample script:
{
keep;
notify :method...[...]; <- failed action
}
result is:
1. message is delivered
2. bounce message sent...
to fix this I wrote small patch for deliver too... my be you find this
"useful"...:)
Uldis
--- /dovecot-org/src/deliver/deliver.c 2007-05-15 20:27:28.0 +0300
+++ /dovecot-new/src/deliver/deliver.c 2007-07-06 19:13:50.0 +0300
@@ -50,6 +50,7 @@
/* FIXME: these two should be in some context struct instead of as globals.. */
static const char *default_mailbox_name = NULL;
static bool tried_default_save = FALSE;
+static bool default_save_ok = FALSE;
static bool no_mailbox_autocreate = FALSE;
static struct module *modules;
@@ -139,11 +140,17 @@
ret = mailbox_transaction_commit(&t, 0);
msgid = mail_get_first_header(mail, "Message-ID");
- i_info(ret < 0 ? "msgid=%s: save failed to %s" :
- "msgid=%s: saved mail to %s",
+ if (ret < 0) {
+ i_info("msgid=%s: save failed to %s",
msgid == NULL ? "" : str_sanitize(msgid, 80),
str_sanitize(mailbox_get_name(box), 80));
-
+ default_save_ok = TRUE;
+ }else{
+ i_info("msgid=%s: saved mail to %s",
+ msgid == NULL ? "" : str_sanitize(msgid, 80),
+ str_sanitize(mailbox_get_name(box), 80));
+ default_save_ok = FALSE;
+ }
mailbox_close(&box);
return ret;
}
@@ -687,9 +694,13 @@
deliver_mail(storage, mail, destination, mailbox);
if (ret == 0 || (ret < 0 && !tried_default_save)) {
- /* plugins didn't handle this. save into the default mailbox. */
- i_stream_seek(input, 0);
- ret = deliver_save(storage, mailbox, mail, 0, NULL);
+ if (!default_save_ok){
+ /* plugins didn't handle this. save into the default mailbox. */
+ i_stream_seek(input, 0);
+ ret = deliver_save(storage, mailbox, mail, 0, NULL);
+ }else{
+ ret = 0;
+ }
}
if (ret < 0 && strcasecmp(mailbox, "INBOX") != 0) {
/* still didn't work. try once more to save it
--- dovecot-sieve-1.0.1-org/src/sieve-cmu.c 2006-10-10 22:44:54.0 +0300
+++ dovecot-sieve-1.0.1-new/src/sieve-cmu.c 2007-07-06 19:05:29.0 +0300
@@ -18,9 +18,12 @@
#include
#include
+#include
#include
#include
+static int contains_8bit(const char *msg);
+
/* data per script */
typedef struct script_data {
const char *username;
@@ -252,30 +255,84 @@
return SIEVE_OK;
}
-static int sieve_notify(void *ac __attr_unused__,
- void *interp_context __attr_unused__,
- void *script_context __attr_unused__,
- void *mc __attr_unused__,
- const char **errmsg __attr_unused__)
-{
-#if 0
-const char *notifier = config_getstring(IMAPOPT_SIEVENOTIFIER);
-
-if (notifier) {
- sieve_notify_context_t *nc = (sieve_notify_context_t *) ac;
- script_data_t *sd = (script_data_t *) script_context;
- int nopt = 0;
-
- /*
Re: [Dovecot] Debian packages for Dovecot 1.0.1xx (sarge)
On Fri, Jun 15, 2007 at 06:05:59PM +0200, Moritz Mertinkat may have written: > Hi there, > > i'm looking for Debian sarge dovecot packages (yes, still running sarge). > Anyone here that has a backported package? I will likely be building one soon. It will be in the same location as I put in the mailing list previously. I will let the list know when I finish it. -- http://www.delink.net/ If you want a language that doesn't believe in type checking at all, except when it does, try Python. Don't just toss it casually aside for the bizarre indentation-based syntax when there's so much else broken about it. - Peter Corlett in the monastery
[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?
[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] 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
[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] 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]
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
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] 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] bug: no initgroup() after login (was Re: Dovecot shared mailbox folder problem)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 6 Jul 2007, Steffen Kaiser wrote: dvtest3. Maybe the problem is that in create_mail_process() when doing: /* setup environment - set the most important environment first (paranoia about filling up environment without noticing) */ restrict_access_set_env(system_user, uid, gid, chroot_dir, set->first_valid_gid, set->last_valid_gid, set->mail_extra_groups); system_user is not set. I default system_user to user, it seems to work. See attached patch. dovecot: Jul 06 11:59:15 Info: IMAP(dvtest3) [23684]: Effective groups: primary=30006 secondary=8,30004,30006 Hoewever, is it correct? Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRo4TLC9SORjhbDpvAQLw7Qf+I7s2zj5lfDb2A0i5VLUPTZQDgv7huHzX 7Lq+8F/nP4PdEaeBWv6v5GDBzrVOLjMuHB4RrUt7wdlSXtLcFnqoMlqLJHsf+wN9 uBFoDjP7gZT5D5Xve/KAZzDuOl+G/Twc2W5DnMVxvRC2udXN3DJY90EV6852Qubw P1lzGN2ymb9wkvMNCbzmJqYc1llsc+Ohbj5/cBCrV2o9FYEOpqFB5J1QbgbeFltK fuuR3gruVpAGM5kiV6MGP/zqJJGrDcuUIeAL50qstkk/saE7YHyB3xV3Falyp+eI MFPLnEhfhzKX0kbgzyJVwZeYRvMW49QO5kca05OJib4mWwKN2Z4Pcw== =Lxy6 -END PGP SIGNATURE- setSystem_user.diff.gz Description: Binary data
Re: [Dovecot] UW-IMAP style mbox snarfing from /var/mail/ to ~/mbox
Timo Sirainen wrote: http://dovecot.org/patches/mbox-snarf-plugin.c Hi, small update from an end-user of this plugin: generally it works like expected, but some problems I mentioned are not solved yet. Here are my main config settings: mail_location = mbox:~/.imap_mail:INBOX=/var/mail/%u:INDEX=/var/mail/indexes/%u mbox_snarf = ~/.imap_mail/inbox - The index for $HOME/.imap_mail/inbox is created in $HOME/.imap_mail/.imap/inbox/, while the indexes for other mbox files are created in /var/mail/indexes/%u, like its supposed to be. How to disable creating index files in $HOME altogether without using links? - if /var/mail/$user does not exist, syslog is cluttered with these messages for each POP3/IMAP login: Jun 10 22:33:33 server dovecot: IMAP(someuser): stat() failed with mbox file /var/mail/someuser: No such file or directory - the biggest problem is the following scenario: - /var/mail/$user does not exist - Exim can not deliver a mail to $HOME/.imap_mail/ so a second router comes into action and delivers the mail to /var/mail/$user - /var/mail/$user now only contains the mail, without the IMAP headers Dovecot normally writes to a mbox file - the user logs into the account and Dovecot tries to snarf the mail - if snarfing is sucessful Dovecot must delete the mail from /var/mail/$user, but this fails due to the missing IMAP headers - when the user logs into the account the next time the mail is snarfed again, this can be repeated endlessly - the only situation where the snarf plugin works like expected is when /var/mail/$user contains the IMAP headers To circumvent this problem I created a cronjob running once per minute which creates /var/mail/$user for $HOME/* with this content: From MAILER_DAEMON Sat Apr 21 19:48:15 2007 Date: Sat, 21 Apr 2007 19:48:15 +0200 From: Mail System Internal Data <[EMAIL PROTECTED]> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <[EMAIL PROTECTED]> X-IMAP: 1177169799 003411 NonJunk Junk $Forwarded Status: RO This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. This solution is annoying because it does not really fix the problem. Can you help me with this problem? I am using Dovecot 1.0.0, might updating to 1.0.1 help fixing some of the problems mentioned above? Greetings, Bernd
[Dovecot] bug: no initgroup() after login (was Re: Dovecot shared mailbox folder problem)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 4 Jul 2007, Steffen Kaiser wrote: Hello, after adding plenty of i_info()'s into: ./src/lib/restrict-access.c ./src/imap/main.c ./src/master/mail-process.c I found out what the basic problem is, although not why the access to Maildir was successful - it should have been denied, too. OK, attached there are these files: - - logging_only.log, a logfile with added logging only. - - setRESTRICT_USERfromUSER.log: a logfile, where in src/imap/main.c the missing env var RESTRICT_USER is set from the env var USER. - - the patch I used to do the logging and the change. - - the dovecot -n output. The problem is that there is _no_ single call to restrict_access_set_env() with the user argument set, hence, the env var RESTRICT_USER is never set, but the only call to initgroups() in ./src/lib/restrict-access.c is invoked only, if RESTRICT_USER is present. Effectly: No secondary groups of the user are added to the process never. In my situation: # id dvtest3 uid=30004(dvtest3) gid=30006(dvtest3) groups=30006(dvtest3),30004(spamd) # ls -aln ~dvtest3/Maildir/ drwxrwx--- 6 31045 30004 4096 2007-07-06 08:34 ./ drwxrwx--- 2 31045 30004 4096 2007-07-06 08:28 cur/ The access to Maildir/cur fails, because the secondary group 30004 is never added to the process. Surprisingly stat(Maildir) succeeds. I experimented with "drop_priv_before_exec" and "add_extra_groups" settings, if they make any difference, but found none. Maybe the problem is the 1st call to restrict_access_set_env(): dovecot: Jul 06 10:48:00 Info: ska: restrict_access_set_env(): user = The user parameter is empty, but not NULL. I added some more logging, the uid/gid is 30004/30006 - that data of dvtest3. Maybe the problem is that in create_mail_process() when doing: /* setup environment - set the most important environment first (paranoia about filling up environment without noticing) */ restrict_access_set_env(system_user, uid, gid, chroot_dir, set->first_valid_gid, set->last_valid_gid, set->mail_extra_groups); system_user is not set. This is true for both local and LDAP users. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRo4LbC9SORjhbDpvAQL/6wf+KFu4a8f1j9GhLC/aaS+rn0f+/D2kYX5g npq/VPv7mt3Y4+s8xbAf3d3xl/TsH1wgZYx/g7uVpBae54vStcpOPum/yTCasohd 8B+1qJqYDztckpjTKTIfcIZvZWP7vcqALVdmPFcAgWx/wkWiSTKGpYW4JnhloFE8 6q2pEcvnj1k+TpHCxTm22c8w1MMUXKaeiLttxWZcg/VlZdShR+MWpArKgSqwXDlc 8XA05tzAO9xDDl+02zx0ysnp41n/i3n82bGWJFaNtpzurgf82ytVTI5WznrJwVSs +xzrOLmw2C8PJSB8Ur0Lg1HHSu+QuOn4+OcU4Rz8jc6jVeG5SfJJEg== =xbQF -END PGP SIGNATURE- noInitgroup.tgz Description: GNU Unix tar archive
