similar to: Thunderbird 3.0.2 released (CONDSTORE fixed)

Hello all, Following the Dovecot wiki and migration help, we recently migrated our core IMAP systems from Courier to Dovecot on Solaris. So far it's been working great, but I have one issue that I'm curious about. Just as the docs mention, we also use "syslog_facility = mail" for logging. Unlike in the past, failed PAM auth attempts are now getting logged as mail.error: Nov

While using 1.1.13 and squat with local pine imap on Solaris 9 I had a random core dump today. I was doing a search in a maildir folder with about 2000 emails. Unfortunately, I haven't been able to reproduce it yet, but I wanted to send along the info anyways. Environment: # uname -a SunOS 5.9 Generic_122300-39 sun4u sparc SUNW,Sun-Blade-100 Backtrace: http://pastebin.com/f7aa8bb5 ~#

Hi all, I was just wondering when this update will trickle down into the Centos repo: http://rhn.redhat.com/errata/RHBA-2008-0611.html Obviously, it just came out yesterday, so I'm not expecting it to suddenly appear. ;) Just curious what the turn around time usually is for RHEL bug fixes that get released and when we should expect it. As a side note, does anyone know if there is a way

Hello all, I recently started seeing these messages on the consoles of three production Centos 5.2 servers. They have been occurring nonstop for the past few days and show up routinely every five minutes. INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast:

Hi, I was just looking for some advice on avoiding getting DoS'd from brute force log in attempts. We came in this morning to find that one of our Solaris 9 dovecot severs had wedged overnight due to a brute force connection attempt to pop3 from Brasil. In the span of about 15 seconds we received 342 connection auth attempts from the same IP: Sep 3 00:10:51 xxxxx dovecot: [ID 583609

Quick question. How important are these? Are the errors recoverable and not a big deal, or are they actually a problem? I see a few of these randomly over the course of the day. Jan 15 10:04:04 gehenna13.rutgers.edu dovecot: IMAP(user): unlink(/rci/nqu/rci/u8/user/dovecot/.such and such maildir/.nfs00000000001e951000002b8d) failed: Device or resource busy Jan 15 10:04:04 gehenna13.rutgers.edu

Hi all, I just upgraded a couple of Fedora 9 workstations to try out 1.1.1 over NFS'd homedir's and I'm having trouble running dovecot in the same configuration we were with 1.0.14. It's fairly simple, we use pine/alpine and set a couple of variables to fork rimapd directly: * smtp-server=host (for the main mail machine) * user-domain=host (same) * set the

Hi all, I recently upgraded from courier to dovecot 1.1.12 on a Solaris 9 system with about 100 users. We have been testing dovecot for sometime in a mixed Linux/Solaris environment and are aware of the index endianess issue with multiple archs. To solve this, we run with INDEX=MEMORY (as seen in the docs) so that only Linux clients have anything to do with the indexes. We generally have

Hi, I was looking through the archives and wiki for something related to this, but all I keep coming up with are options for the prompt timeout and user input. Is there a way to change the default timeout for tftp in pxelinux? The be more specific, we use IP in HEX to network boot and it takes a very long time for pxelinux to timeout on GUID and MAC, before finally getting to HEX and

Does anyone know if dovecot support regex lookups for proxy/proxy_maybe, rather than mysql/ldap etc? I've been comparing it with perdition to see which one might be better for us to do layer7 username switching. Perdition supports the ability to not have any auth/db looks, but rather just a regex file that parses the usernames as they come in and forwards to the particular machine on the

Hi all, I crawled through the archives for a bit but didn't see anything helpful, so I apologize if this has already been addressed. We've been dying to move from Courier to Dovecot across our whole infrastructure for quite some time, but until recently our setup wasn't possible until this happened: "Dovecot allows mailboxes and their indexes to be modified by multiple

Hi, I just had a couple of questions about nfsnobody. We run a very large NFS infrastructure based off of a NetApp, and we're been discussing whether or not it is necessary to have 64 bit nfsnobody as 4294967294. I understand the reasoning behind this (2^32 - 2 gives you a max UID), but we're having issues since we run multiple architectures. The UID doesn't play nice across

I'm not sure how useful this is with optimization turned back on, but here it is anyway. This was just a one off that happened last night: Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): fscking index file /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot.index Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): Panic: file mail-transaction-log-view.c: line 108

Timo (and anyone else who feels like chiming in), I was just wondering if you'd be able to tell me if the amount of corruption I see on a daily basis is what you consider "average" for our current setup and traffic. Now that we are no longer experiencing any core dumps with the latest patches since our migration from courier two months ago, I'd like to know what is expected

Something I noticed on a 2.1.7 director test cluster (two directors, three backends): 'doveadm proxy kick user' will kick all connections for that user on that director only. Any additional connections on other directors will remain active unless the command is run on all directors. Are the proxy and director sub-commands intended to be separate and distinct in their operation? If so,

Hi all, I've run into an issue we have with dovecot versions 2.0.12 through 2.0.14 on latest CentOS 6.2 when dealing with Maildirs located on NFS partitions. Although I saw Mr. Egbert's thread, his resolution does not work on our end. When dealing with users with over 500 messages in any of their Maildir folders, they occasionally receive an error from the server: Internal error

Just wanted to share the bad news: https://bugzilla.mozilla.org/show_bug.cgi?id=541337 It seems that Dovecot is really showing the Mozilla Thunderbird team how to read and use an RFC ;-) -- Christian Rohmann Content Delivery Server u. Dienste Network Engineering & Design NETCOLOGNE Gesellschaft f?r Telekommunikation mbH Am Coloneum 9 | 50829 K?ln Tel: 0221 2222-5751 | Fax: 0221

Hi all, I use a local dovecot server which is synchronized with my two imap accounts using OfflineIMAP. This works very nice and is highly usable. But one thing I'd like to improve is the slow IMAP search. When I search for a string in the subjects of all messages in a mailbox using some mail client, dovecot seems to grep all the messages in there. Is there a way to let dovecot index more

System: Linux 2.6.25.6-55.fc9.x86_64 #1 SMP Tue Jun 10 16:05:21 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux Dovecot: dovecot-1.0.14-8.fc9.x86_64 We have used Dovecot for several years. The error message below appears in the system log quite frequently. I have run a test which shows that this message is due to 2 or more users accessing the same mail (i.e connecting using the same userid). This

In both 1.2.6 and 1.2.7 (probably also before that, but dont have logs) im seeing quite a few of these: Nov 17 12:45:12 userimap10.xs4all.nl dovecot: IMAP(xxxxxxx): /var/spool/mail/dovecot-control/c/c0/xxxxxxx/INBOX/.INBOX/dovecot-uidlist: Duplicate file entry at line 2650: 1257768394._smtp.mxdrop238.41874,S=17304:2,Sad (uid 34270 -> 37166) I never really looked at it because it doesnt seem