similar to: proxy_maybe regex

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

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

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 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 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 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

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, 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

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

Just wanted to mentioned that those of you who were having issues with unread messages in Thunderbird should see your problem fixed with TB 3.0.2 that was released today. http://www.rumblingedge.com/2010/02/25/thunderbird-3-0-2-released/ If you previously turned off CONDSTORE support, don't forget to enable it. -- ================================ David Halik System Administrator OIT-CSS

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

When using proxy_maybe CRAM-MD5 authentication fails when the connection is proxied. Is this expected behavior? Is proxy_maybe too simplified for this case? We're using SQL so I could rewrite the query with IFs to fake proxy_maybe and return the password as NULL and nologin as Y, but if it works that way couldn't it work with proxy_maybe? This works: password_query = \ SELECT NULL AS

Hi Folks, I spent quite some time yesterday understanding how proxy works along with the director. I came to the conclusion that proxy_maybe and director cannot be used together, but this isn?t a true incompatibility so much as caused by the way things are handled and the order they are processed in. The way proxy_maybe works is that it is processed by the auth provider once it gets the

Hello. 1. I have two identically hosts 2. I have set up replication between two hosts 3. I have 'Y' AS proxy_maybe in password_query. 4. password_query returns one of this one hosts 5. I set this parameters in dovecot config: disable_plaintext_auth = yes ssl = yes auth_mechanisms = plain login for enforce use encrypted connections by client programs.

Before I spend some time experimenting with what might be impossible, maybe someone can just tell me (either "how" or that it's impossible). I'd like to get perdition out of my environment (mainly to have one less moving part in my architecture). I'm looking at dovecot's built-in proxying. In my setup, I don't have dedicated front-end machines. A user can connect

Hello, I'm using proxy_maybe and auth_default_realm. It seems that when a user logs in without the domain name, relying on auth_default_realm, and the "host" field points to the local server, I get the Proxying loops to itself error. It does work as expected - log on to the local server without proxying, if the user does include the domain name in the login. (IP's and

Hi all, I have some IMAP servers fronted with separate perdition processes, and it would be ideal if I could collapse this down to having dovecot do both the IMAP proxying and the IMAP serving at the same time on the same IP addresses. One of the fields in my LDAP entries contains the canonical name of the server that hosts their mailbox, and if I follow the manual at