similar to: Running dovecot master processes across multiple IPs

I realize these are older versions, but I'd like to know specifically whether dovecot 1.1.6 and dovecot 1.1.8 are compatible index-wise. In particular, if we downgraded from 1.1.8 to 1.1.6 would there be any issues with doing so? I realize there are later versions, but we've tested both of the above extensively, but recently loaded up a server with 1.1.8 and found that the 'imap'

We are running into a situation where Dovecot master is simply trying to do too much. It some situations, we are finding that there are times in which it cannot service requests. Restarting Dovecot seems to help in these situations, possibly due to the fact that it no longer has to manage its THOUSANDS of file descriptors for pipes to the many imap/proxy processes that it uses for logging. Is

We are running Dovecot 1.0-rc27 and have run across what seems to be a fatal error (SIGSEGV) in the past few days (4 times total in past 6 days). It appears to have been 5 separate users, 5 separate remote IP addresses. Two of these have this format: Mar 26 15:13:10 myhostname dovecot: imap-login: Authenticate PLAIN failed: Don't send unrequested data: user=<rmtuser>, method=PLAIN,

http://bugzilla.netfilter.org/show_bug.cgi?id=727 Summary: Open your firewall by a simple typo Product: iptables Version: unspecified Platform: All OS/Version: All Status: NEW Severity: major Priority: P2 Component: iptables AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy:

We are having problems with the latest Dovecot 1.0 (RC15) regarding file descriptors > 255 being handed off to fdopen() via crypt() via PAM(?). This is a problem on Solaris 10 due to the fact that the stdio library does not support file descriptors > 255 (in order to remain binary-compatibile with older binaries). Here are the messages we run into if we get too many (~250?) concurrent

Hi all, My NT environment cannot recognize my SAMBA servers(Bad IP address when ping from MS DOS prompt) and after I restarted the nmbd daemon it can see my SAMBA servers. Does anyone know why this happens? Is it there is a change in the WINS server's database? Please advise. thanks & regards, Bridget

Hi, I'm trying a VPN via ssh between Linux (Suse 10.3, 5.0) and OpenBSD (4.2, 4.7). But it doesn't work... On Linux: sudo ssh -v -f -w 0:1 $OPENBSD true sudo /sbin/ifconfig tun0 10.1.1.1 10.1.1.2 sudo /sbin/route add -net 192.168.17.0 netmask 255.255.255.0 dev tun0 On OBSD: sudo ifconfig tun1 10.1.1.2 10.1.1.1 netmask 255.255.255.0 sudo /sbin/route add 10.0.3.0/24 10.1.1.1 And add a

On Wed, Jun 5, 2024, at 17:58, Rowland Penny via samba wrote: >> > /etc/resolv.conf >> domain mydomain.work >> search mydomain.work > > 'domain, and 'search' in resolv.conf were mutually exclusive and the > last one wins, but in the last resolv.conf code, 'domain' has been > removed. Thank you. This is how it looks now. nameserver 10.1.1.1

I hate to be a pest, but are there any revelations on file descriptor "overusage" by dovecot-auth? ----- Forwarded message from Steven F Siirila <sfs at tc.umn.edu> ----- Date: Sat, 20 Jan 2007 12:42:50 -0600 From: Steven F Siirila <sfs at tc.umn.edu> To: Dovecot Mailing List <dovecot at dovecot.org> User-Agent: Mutt/1.4.2.1i Subject: Re: [Dovecot] dovecot-auth file

I'm working from modified 5.0p1 codebase. What I'm looking for is a mechanism to limit the number of simultaneous connections on a per-user/IP basis. That is, disallow multiple simultaneous logins/authentication of the same user from different IP addresses. e.g.: fred from 10.1.1.1 - accept fred from 10.1.1.2 -- reject while fred is still connected from 10.1.1.1 fred from 10.1.1.1 - OK

I am re-posting this message from last Friday, as I have seen no replies. It is critical that we address this problem, since until then we cannot put more than a few hundred users on our server. If Dovecot-auth TRULY needs to keep open a file descriptor for every single login session, we will have to start looking at alternatives. In short: Help! ----- Forwarded message from Steven F Siirila

I've run into a problem with Gluster stability with the RDMA transport. Below is a description of the environment, a simple script that can replicate the problem, and log files from my test system. I can work around the problem by using the TCP transport over IPoIB but would like some input onto what may be making the RDMA transport fail in this case. ===== Symptoms ===== - Error from test

On Sun, Oct 08, 2006 at 10:25:53PM +0300, Timo Sirainen wrote: > On Fri, 2006-10-06 at 21:00 -0500, Steven F Siirila wrote: > > I am running Dovecot 1.0-rc6 along with dovecot-sieve from 2006-10-05 CVS. > > I am calling dovecot deliver from Postfix (main.cf): > > > > mailbox_command = /opt/dovecot/libexec/dovecot/deliver > > > > Upon switching to dovecot

Hi, I'm setting up the directors for proxying pop3/imap/lmtp/sieve. pop3/imap/lmtp proxying work fine, but sieve not working. The error messages in maillog look not using proxying but local passdb. Error message: Apr 03 12:09:25 managesieve-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=10.1.1.4, lip=10.1.1.201, session=<+SIcx4wvRQAKAQEE> sql in

I am having difficulting getting to www.dovecot.org and wiki.dovecot.org. My browser tells me it can't find them. Anyone know what's up? -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs at umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

On Wed, 05 Jun 2024 17:25:52 +0200 calm.job89448 at fastmail.com wrote: > Hi Rowland, > > thanks again. > > On Wed, Jun 5, 2024, at 17:10, Rowland Penny via samba wrote: > > >> I tried both. First sudo, as I setup everything with sudo and out > >> of curiosity with root. No luck. > >> Was it wrong to setup as user with sudo privileges? > >

Anyone running Dovecot on Solaris, requiring only SSL connections, and servicing thousands of simultaneous users? Our past attempts to do so have failed due to dovecot-auth using up all 256 of its file descriptors. I say 256 since we are limited to that by the 32-bit libraries. We are looking at either compiling Dovecot in 64-bit and letting dovecot-auth file descriptors accumulate (not ideal),

A few RC releases ago we had a problem where a user's restored home directory contained a .imap folder either from a previous RC release or perhaps it was a different server. In any event, restoration of the user caused problems since Dovecot choked on the restored .imap index files. Removing those index files cleared the problem. I'm wondering if this is still an issue, and therefore

Okay, to convince myself that quota handling was working okay with Dovecot 1.0-rc27 on Solaris 10, I tested sending a message to an account that was purposely over-quota. The account in question had a vacation message set up. For the first test, there was no $HOME/.imap directory at all. I received the vacation message, but the message which was supposed to be delivered locally queued in Postfix

Under Dovecot 1.0-rc27 on Solaris 10 we noticed this error today affecting one of our users repeatedly: Mar 28 14:02:01 myhost dovecot: IMAP(myuser): file mbox-sync-rewrite.c: line 423 (mbox_sync_read_and_move): assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 28 14:02:01 myhost dovecot: IMAP(myuser): Raw backtrace: 0x7ac54 -> 0x42cd4 -> 0x3e968 -> 0x3f54c -> 0x3f980