similar to: 1.07 to 1.0.13 mail_extra_groups

Displaying 20 results from an estimated 2000 matches similar to: "1.07 to 1.0.13 mail_extra_groups"

2008 Apr 12
2
Mailbox locking issue?
Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.
2008 May 07
2
Clarification wanted on mail_access_groups vs. mail_privileged_group
I have just upgraded to dovecot 1.0.13. All the documentation I can find in the example .conf file and the NEWS and ChangeLog files seems to say that the mail_privileged_group = mail setting is all I should need to make dovecot use group mail to create dotlock files. My understanding from what I read is that mail_privileged_group is used to set the group used while creating dotlock files in (in
2009 Jan 08
2
Panic in v1.1.8
I just tried installing dovecot 1.1.8 as an upgrade to 1.1.7 and encountered Panics like the following with pop3 accesses Jan 8 10:55:31 sbh16 dovecot: Killed with signal 15 Jan 8 10:55:49 sbh16 dovecot: Dovecot v1.1.8 starting up Jan 8 10:57:01 sbh16 dovecot: pop3-login: Login: user=<user2>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Jan 8 10:57:01 sbh16 dovecot: Panic:
2010 May 12
2
auth: Error: PLAIN(user): Request 27511.1 timeouted after 150 secs, state=3
Since upgrading from Dovecot 2.0.beta4 + patches http://hg.dovecot.org/dovecot-2.0/rev/96496e1d3d12 and http://hg.dovecot.org/dovecot-2.0/rev/aefa279e2c70 to Dovecot 2.0.beta 5, I have started to see the subject error from Dovecot for SASL authentications. It doesn't happen every time, but it happens more often than not. It doesn't seem to affect Postfix's acceptance of the message.
2010 Jun 17
3
Problem configuring rawlog with 2.0beta6
The initial problem I was seeing after upgrade from 2.0beta5 to 2.0beta6 was error messages from my Android phone K9 client that dovecot was reporting -1 messages in various mailboxes. These mailboxes do have the special "Mail System Internal Data" message in them. In trying to get more information for debugging, I tried toenable rawlog using the same configuration I used successfully
2014 Nov 28
2
Dovecot 2.2.15, Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed:
The log messages are attached. The core dump is at <https://www.dropbox.com/s/9i80ms7xkyxoqj7/core.26450?dl=0> The server is $ uname -a Linux sbh16.songbird.com 2.6.18-8.1.14.el5 #1 SMP Thu Sep 27 18:58:54 EDT 2007 i686 i686 i386 GNU/Linux -- Mark Sapiro <mark at msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
2009 Mar 15
2
fstat(mboxname.lock) failed: Bad file descriptor
I have just upgraded from 1.2.beta1 to 1.2.beta2. My configuration is: [root at sbh16 ~]# dovecot -n # 1.2.beta2: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/postfix/sbh16-cert.pem ssl_key_file: /etc/postfix/sbh16-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default):
2013 Nov 02
1
Assertion error in Dovecot 2.2.6
Background. A while back I upgraded my phone to one currently using Android 4.1.2 and K9 mail 4.409. This phone/MUA combination seems at times to go crazy making IMAP connections. At first, I had mail_max_userip_connections = 30 (my largest imap account has 19 folders). The issue I had at that time was multiple errors like Oct 14 17:45:16 sbh16 dovecot: imap-login: Maximum number of connections
2010 Mar 07
1
Question about SASL auth
I have recently upgraded from Dovecot 1.2.10 to 2.0.beta3. I have Postfix 2.3.3 and use Dovecot to provide SASL auth for Postfix. # dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail
2010 Feb 21
1
Dovecot 2.0.beta3 Configuration issue (I think)
I have been running dovecot 1.2.10 without problems. I am trying to install 2.0.beta3. I have I think translated all my configuration customizations correctly, but I have problems. I can start dovecot, but I can't login, at least not with SSL. Here's my dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms
2014 Oct 10
0
Error with dovecot 2.2.14rc1
I don't know if this is significant or not, but it is at least unusual here. First we see this: > Oct 9 10:10:03 sbh16 dovecot: imap(mark): Error: Sync failed for mbox file /var/spool/mail/mark: seq=393 uid=201517 uid_broken=0 originally needed 0 bytes, now needs 66 bytes which has apparently added 66 bytes to UID 201517 Then, later we see: > Oct 9 11:26:19 sbh16 dovecot:
2010 Feb 23
2
panic in istream-raw-mbox.c - 2.0.beta3+
Saw the following in the log after shutting down my client. Feb 22 20:44:47 sbh16 dovecot: imap(mark): Disconnected: Logged out bytes=1755/9765 Feb 22 20:44:47 sbh16 dovecot: imap(mark): Panic: file istream-raw-mbox.c: line503 (istream_raw_mbox_get_start_offset): assertion failed: (rstream->seeked) Feb 22 20:44:47 sbh16 dovecot: imap(mark): Raw backtrace:
2009 Sep 23
9
pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:
2008 Mar 10
2
1.0.13: mail_extra_groups alternative syntax?
"Warning: mail_extra_groups setting was often used insecurely so it is now deprecated, use mail_access_groups or mail_privileged_group instead" I use the following: mail_extra_groups = mail nogroup Because I have the real and virtual accounts. What's the correct way to replace the above line? It seems that mail_privileged_group only accepts one group, but I need two. Any
2009 Feb 11
2
Panic in dovecot 1.2.beta1
I tried Dovecot 1.2.beta1 yesterday. I had been using 1.1.11. I started getting "Panic: POP3(xxx): Trying to allocate 0 bytes" There are two kinds of pop3 users. In the attached log.txt file, user u1 is using a pop3 MUA. For users u2, u3, u4 and u5 fetchmail is coming through an ssh tunnel and retrieving their mail. u1 is able to interact normally with dovecot, but the fetchmail users
2012 Jan 10
2
Clients show .subscriptions folder
Since upgrading from dovecot-2.1.rc1 to dovecot-2.1.rc3, some clients are showing a .subscriptions file in the user's mbox path as a folder. Some clients such as T'bird on Mac OS X create this file listing subscribed mbox files. Other clients such as T'bird on Windows XP show this file as a folder in the folder list even though it cannot be accessed as a folder (dovecot returns CANNOT
2010 Dec 22
1
Some Dovecot LDA version sends MDN rather than DSN for overquota.
It appears that there is some version of the Dovecot LDA that is sending an RFC 3798 MDN rather than an RFC 3464 DSN to report non-delivery to a user who is over quota. See <https://bugs.launchpad.net/mailman/+bug/693134> for a discussion of this and <https://bugs.launchpad.net/mailman/+bug/693134/+attachment/1773018/+files/Automatically%20rejected%20mail.msg> for the actual MDN
2013 Feb 22
0
Dovecot list archives not updating
The February archive indexes of this list haven't been updating since Feb 8. The text file at <http://dovecot.org/pipermail/dovecot/2013-February.txt> appears to be up to date with all posts, but the index pages at <http://dovecot.org/pipermail/dovecot/2013-February/thread.html>, <http://dovecot.org/pipermail/dovecot/2013-February/subject.html>,
2013 Feb 07
2
Dovecot 2.2.beta1
Just an FYI, I have been running 2.2.beta1 for a few days now with no problems, but I'm not using any of the new features ;) -- Mark Sapiro <mark at msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
2008 Mar 04
4
Security issue #5: mail_extra_groups setting is often used insecurely
mail_extra_groups=mail setting is often used insecurely to give Dovecot access to create dotlocks to /var/mail directory. If you don't use mboxes in /var/mail, make sure this setting is cleared. If you do use /var/mail mboxes and Dovecot gives permission errors without it, do one of the following (in the preferred order): a) Upgrade to v1.0.11 and use the new mail_privileged_group setting