Robert Tomanek wrote:
Hello Peter,
Thursday, January 10, 2008, 8:17:15 PM, you wrote:
All the suggested ones have just one big FAT problem - they are all
written in that security bug ridden language that the hackers just love
to exploit - PHP. Running a web application available to the whole
Charles Marcus wrote:
On 1/10/2008, Timo Sirainen ([EMAIL PROTECTED]) wrote:
No-one mentioned WebAlpine yet, which also uses persistent
connections. I haven't tried it myself though.
I though this is what imapproxy did for webmail? We only have one or two
people who actually use ours (Squirre
Mike Brudenell wrote:
Whatever you do, DON'T move to Maildir if you are using the Prayer
webmail software!
We have used Prayer here for many years with the UW IMAP server backend
and first Berkeley, then later MBX, format mail folders.
When we migrated new users to Dovecoe with Maildir fol
Charles Marcus wrote:
On 1/10/2008, Robert Tomanek ([EMAIL PROTECTED]) wrote:
I can confirm RoundCube ( http://www.roundcube.net/ ) is a good
recommendation.
Can you confirm that it uses persistent IMAP connections? I can't tell
from the website or searching the mail archives or forum...
I've tried compiling 1.1.rc9 on everything to hand and I get various
compilation warnings (but the compilation finishes). I don't know
whether any of them are worth tracking down?
I'm guessing most of the differences depend on the default gcc options
and a couple of them are probably specific
Erinn Looney-Triggs wrote:
I am getting this failure when trying to compile dovecot on Sparc Solaris 8:
make[4]: Entering directory
`/home/systems/looneytr/dovecot-1.1.rc12/src/lib'
source='str-find.c' object='str-find.o' libtool=no \
DEPDIR=.deps depmode=gcc /bin/bash ../../depcomp \
Erinn Looney-Triggs wrote:
Chris Wakelin wrote:
What version of gcc? What configure options? I had no problems with gcc
3.3.2 (well, a still a few compiler warnings; see
http://www.dovecot.org/list/dovecot/2008-June/031350.html)
Chris
Hello,
gcc --version 2.95.3
Had to set LDFLAGS and
Timo Sirainen wrote:
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz.sig
There's always time for one more release candidate. :) I was planning on
releasing v1.1.0 a couple of minutes before summer solstice (23:59 UTC
according
Timo Sirainen wrote:
I've finally read and answered most of the mails on this list. If you
haven't received an answer to your question, resend it. There are a
couple of tricky mbox issues left, but I'm not sure if I can do anything
about them unless someone can show me how to reproduce the probl
Timo Sirainen wrote:
On Mon, 2008-07-21 at 10:14 +0100, Chris Wakelin wrote:
+ zlib plugin supports now bzip2 also.
This breaks for me on Solaris 8 and gcc 3.3.2
In file included from istream-bzlib.c:8:
/usr/include/bzlib.h:170: error: parse error before "FILE"
/usr/inclu
Timo Sirainen wrote:
On Wed, 2008-07-23 at 15:58 +0100, Chris Wakelin wrote:
I've tried this on both Solaris 8 and SuSE Enterprise 9 (64-bit).
I get a assert-crash when using a gzipped mbox folder
..
istream-raw-mbox.c: line 363 (i_stream_create_raw_mbox): assertion
failed: (
Timo Sirainen wrote:
On Thu, 2008-07-24 at 00:34 +0100, Chris Wakelin wrote:
Well, now it doesn't assert crash, but (on the Solaris 8 machine):
dovecot: Jul 24 00:22:22 Error: IMAP 13458 xxx.xxx.xxx.xxx : Cached
message offset 75979 is invalid for mbox file (read-only mbox s
Timo Sirainen wrote:
make clean shouldn't ever be necessary, since automake does dependency
tracking..
I thought so too, but it was fine on SuSE when I did a "make clean".
Anyway, it didn't make any difference on Solaris 8 :(
I can try this in Solaris 10, but I don't really see why the
OS
Chris Wakelin wrote:
I can try this in Solaris 10, but I don't really see why the
OS/architecture should matter.
Oh, unless there are some bugs in your zlib version, such as related to
seeking..
Could be, I imagine it's as prehistoric as the bzlib :)
Right, I've tried dove
Arkadiusz Miskiewicz wrote:
On Saturday 26 July 2008, Timo Sirainen wrote:
On Jul 26, 2008, at 5:31 PM, Kai Schaetzl wrote:
I have imap-login processes staying arround and occupying port
Ah, well, that's a different question! Stopping dovecot won't kill the
processes with actual logins. -> kil
Arkadiusz Miskiewicz wrote:
What do you have for the "shutdown_clients" option?
shutdown_clients: no
I think the imap-login processes will hang around if there are SSL or
proxy connections through them (but perhaps they shouldn't be
"listen"-ing for new connections?).
It would be good if
Chris Wakelin wrote:
Oh, unless there are some bugs in your zlib version, such as related to
seeking..
Could be, I imagine it's as prehistoric as the bzlib :)
Right, I've tried dovecot-1.1.2 using my own zlib-1.2.3 (and
bzlib-1.0.5) build on Solaris 8:
ldd lib20_zlib_plugi
Brian Hayden wrote:
Have you investigated Prayer? That's what we use, in a modded version,
because it maintains persistent IMAP connections (among other reasons).
You could think of it as an IMAP client that happens to be using a web
browser to draw back to your screen, as if it were X Windows.
Timo Sirainen wrote:
Yea, ...
I've been meaning to tell you that should be "Yeah" for an informal
version of "Yes", otherwise it's a very archaic form of "Yes" or
"Indeed" as in "Yea, though I walk in the valley of the shadow of death"!
I think that's also true of American/Aussie etc. as
Chris Wakelin wrote:
> I've been testing zlib again in Dovecot 1.1.1 (plus assert-crash fix)
> and 1.1.2 and I'm beginning to think it may be some sort of race
> condition (the Solaris 8 box is significantly slower than the SuSE one!).
>
> If I leave a few seconds pause
Andrey Panin wrote:
> On 349, 12 14, 2008 at 08:03:25AM +0200, Timo Sirainen wrote:
>> On Fri, 2008-11-21 at 15:30 +0300, Andrey Panin wrote:
>>> Hello all,
>>>
>>> this patch allows master process to drop more root priveleges under
>>> Solaris. My limited testing shows that code works, but I'm not
Andrey Panin wrote:
>> I've applied the patch to Dovecot 1.1.7 (with minor change to
>> configure.in) on Solaris 10 sparc 64-bit but Dovecot fails on startup
>>
>> dovecot: Dec 18 12:45:47 Info: Dovecot v1.1.7 starting up
>> dovecot: Dec 18 12:45:47 Fatal: auth(default): initgroups(root, 0)
>> fail
Chris Wakelin wrote:
> Andrey Panin wrote:
>>> I've applied the patch to Dovecot 1.1.7 (with minor change to
>>> configure.in) on Solaris 10 sparc 64-bit but Dovecot fails on startup
>>>
>>> dovecot: Dec 18 12:45:47 Info: Dovecot v1.1.7 starting up
>
I've been seeing lots of index cache file errors (using mbox on Solaris
8 sparc 64-bit, but with 32-bit Dovecot) since I switched my account to
Dovecot 1.2.0 (we're still on 1.0.15 mostly, but I'm hoping to upgrade
to 1.1.17+ this summer, or 1.2.x if it's stable enough).
e.g.
Error: Corrupted ind
Timo Sirainen wrote:
> On Tue, 2009-07-14 at 11:08 +0100, Chris Wakelin wrote:
>> Error: Corrupted index cache file
>> /.imap/INBOX/dovecot.index.cache: field index too large (47 >= 25)
>
> Wonder if http://hg.dovecot.org/dovecot-1.2/rev/ae3e0ff64c94 fixes it?
I've n
Chris Wakelin wrote:
> I'm still getting errors like
>
> Aug 04 18:01:22 IMAP 23842 127.0.0.1 : Error: Corrupted index
> cache file /.imap/INBOX/dovecot.index.cache: used_file_size too large
> Aug 04 18:01:22 IMAP 23842 127.0.0.1 : Error:
> fcntl(write-lock) locking f
We upgraded from Dovecot 1.0.15 to 1.2.5 last night, on Solaris 10 using
mboxes, mostly without issues.
However I had to trash the index/cache files (too many folders were
showing corruption issues which is especially bad for Prayer Webmail
".prayer" folders that store preferences; Prayer sees a d
Timo Sirainen wrote:
> On Wed, 2009-09-30 at 11:06 +0100, Chris Wakelin wrote:
>>> Sep 30 09:57:11 IMAP 25384 134.225.xx.xx : Panic: file
>>> mail-index-sync-update.c: line 933 (mail_index_sync_map): assertion failed:
>>> (map->hdr.indexid == index-
Timo Sirainen wrote:
> On Wed, 2009-09-30 at 11:48 -0400, Timo Sirainen wrote:
>> So it basically just issues NOOP commands and does no disk I/O (opens no
>> index files or anything). Looks like each imap process uses about 420 kB
>> of memory (420 MB total according to "free" before/after). That's
Timo Sirainen wrote:
> On Wed, 2009-09-30 at 14:54 +0100, Chris Wakelin wrote:
>>>>> Sep 30 09:57:11 IMAP 25384 134.225.xx.xx : Panic: file
>>>>> mail-index-sync-update.c: line 933 (mail_index_sync_map): assertion
>>>>> failed: (map-&g
Timo Sirainen wrote:
> On Wed, 2009-09-30 at 17:21 +0100, Chris Wakelin wrote:
>> I've put in the patched imap-login and turned on per-process setid core
>> dumps with "coreadm -e proc-setid" (I don't think we need the global
>> setid ones). We had a
Timo Sirainen wrote:
> On Sep 30, 2009, at 6:10 PM, Chris Wakelin wrote:
>
>>> #0 client_get_extra_disconnect_reason (client=0x635b8) at
>>> client-common.c:206
>>> 206 if (ssl_require_client_cert)
>>> (gdb) bt
>>> #0 cli
We've had another random imap process crash. This is with the original
1.2.5 imap (I haven't applied the patch for two processes creating an
index simultaneously):
> Oct 03 13:24:56 imap-login: Info: Login: user=, method=PLAIN,
> rip=134.225.1.46, lip=134.225.16.6
> Oct 03 13:25:59 IMAP 6067
Chris Wakelin wrote:
> We've had another random imap process crash. This is with the original
> 1.2.5 imap (I haven't applied the patch for two processes creating an
> index simultaneously):
>
> Backtrace:
Sorry, wrong binary again (it *was* rather late at night!). He
Timo Sirainen wrote:
> On Oct 6, 2009, at 9:00 AM, Bruce Bodger wrote:
>
>>
>> On Oct 6, 2009, at 3:55 AM, Jernej Porenta wrote:
>>
>>> I am expiriencing compiling issues on Solaris 8 and Solaris 10 boxes
>>> with dovecot 1.2.6. On Solaris 8 the compiler is gcc 64bit 3.2.2, on
>>> Solaris 10 gcc 3
Christian Schmidt wrote:
> Hello Timo,
>
> Timo Sirainen, 06.10.2009 (d.m.y):
>
>> What OpenSSL version do you have? I thought those compression functions
>> were new enough that everyone would have them by now..
>
> I'm experiencing the same problem when buidling dovecot on Solaris 10
> (SPARC
1.46 : Panic: file
> istream-raw-mbox.c: line 578 (istream_raw_mbox_get_body_size): assertion
> failed: (rstream->body_offset != (uoff_t)-1)
Best Wishes,
Chris
Chris Wakelin wrote:
>
> Chris Wakelin wrote:
>> We've had another random imap process crash. This is with the o
Timo Sirainen wrote:
>> The panic was
>>> Oct 03 13:34:20 IMAP 6067 134.225.1.46 : Panic: file
>>> istream-raw-mbox.c: line 578 (istream_raw_mbox_get_body_size): assertion
>>> failed: (rstream->body_offset != (uoff_t)-1)
>
> So it has only happened twice now in total? I've seen this bef
Timo Sirainen wrote:
> Can someone find an OS where the attached program doesn't work? It
> should print "success". So far tested for success: Linux 2.6, Solaris
> 10, FreeBSD 7.2, OpenBSD 4.2.
>
>
Fine in Solaris 2.8 (32-bit and 64-bit binaries, Sparc).
Chris
--
--+---+---+---+---+---+---+
Hi all,
We moved our Dovecot installation first of all to have all folders and
inboxes on NetApps via NFS (with indexes local) then from a physical
Solaris 8 4-way UltraSparc server running Dovecot 1.2.5 (32-bit) to a
virtualised Ubuntu 8.04 64-bit server with a single virtual processor
(in VMWare
On 18/12/2009 01:01, Chris Wakelin wrote:
>
> Up until this afternoon we had "login_process_per_connection = yes", and
> login_max_connections at the default (256).
I meant, of course, "login_process_per_connection = no" ...
>
> This evening I tried with
On 18/12/2009 01:11, Timo Sirainen wrote:
> On Dec 17, 2009, at 8:01 PM, Chris Wakelin wrote:
>
>>> Dec 18 00:27:58 imap-login: Info: Disconnected: Connection queue full (auth
>>> failed, 1 attempts): user=, method=PLAIN, rip=,
>>> lip=134.225.32.156, TLS
>
On 18/12/2009 15:08, Timo Sirainen wrote:
>> We have something in the
>> region of 1000 concurrent connections and login_max_processes_count *
>> login_max_connections = 128 * 256 should be enough for 32000+ of them!
>>
>> Would it be better to have login_max_connections = 1024 (or even higher)?
>
Jay Chandler wrote:
> Timo Sirainen wrote:
>> What does "lockd" mean there? It's waiting for a lock? What does tracing
>> the process say it's doing?
>> http://wiki.dovecot.org/Debugging/ProcessTracing
>>
>>
> Apparently the process is hung-- I can't even kill -9 it. The trace
> returns empty
Timo Sirainen wrote:
> On Thu, 2007-03-15 at 14:45 -0400, Stewart Dean wrote:
>> It never hurts to ask..
>> I am bringing up DC on my production mailserver (which runs UWIMAP for
>> production IMAP service) to learn and test it, much as I did when I
>> introduced SSL protected IMAP, using a
Randall Svancara wrote:
> In the server logs, when I attempt to connect to port 993 using imap
> over SSL, i receive the following error:
>
> dovecot: Mar 21 15:34:25 Info: imap-login: Login: user=,
> method=PLAIN, rip=134.121.92.228, lip=134.121.5.141, TLS
> dovecot: Mar 21 15:34:25 Error: IMAP
Eric Rostetter wrote:
>> b) Odd-even numbering: 1.1.x (unstable) -> 1.2.0 (stable)
>
> I don't like this, as the average new user has no idea that the odds
> are unstable, and runs them, then gets flamed for it, etc. No matter
> how well you document it on the web/wiki, people are going to mis
Well, it builds OK for me on Solaris 8 32-bit SPARC with OpenLDAP 2.3,
with less complaints from gcc (3.3.2), just:-
mail-index.c: In function `mail_index_parse_extensions':
mail-index.c:343: warning: comparison between signed and unsigned
mail-index.c: In function `mail_index_map_clone':
mail-ind
I guess you're delivering mail to /var/mail/username, and UW-IMAP
"snarfs" (to use the UW term :)) the messages to ~/mbox (if it exists)
whenever the user opens INBOX in IMAP.
If so, I guess the problem is the Unix file-system clients which expect
to see mail in /var/mail/username? Dovecot can do
Adrian Barker wrote:
>
> That's right: we cannot change the way that we deliver email, at least
> in the short to medium term, so need to maintain compatibility with the
> UW IMAP server. If we do decide to write a plugin that copies new email
> from the mail spool to the IMAP inbox, is there any
David Lee wrote:
> We have for many years been a UW-IMAP site, with users having their own
> traditional, private, mbox-format INBOX and folders: almost (but not
> quite) no complications of shared or simultaneous access. We have just
> completed a transparent transition to dovecot (official 1.0.0
Timo Sirainen wrote:
> http://dovecot.org/tools/nfstest.c
>
> I wrote a test utility that tests different ways to flush NFS attribute
> cache and data cache. Please test in your NFS setup and show me the
> results, so I can make Dovecot v1.1 works well with NFS.
>
Results for Solaris 8 talking
Timo Sirainen wrote:
> On Thu, 2007-07-12 at 12:45 +0100, Chris Wakelin wrote:
>> Results for Solaris 8 talking to a NetApp filer (OS: ONTAP 7.2.2p3)
>
> Thanks, could you try once more with an updated nfstest.c version? I
> added "dup+close" which works for data a
Timo Sirainen wrote:
> On Thu, 2007-07-12 at 21:26 +0300, Timo Sirainen wrote:
>> On Thu, 2007-07-12 at 10:51 -0700, Doug Council wrote:
Great. Now how about FreeBSD once more? :)
>>> FreeBSD 6.2-RELEASE-p5 and a NetApp NFS server:
>> Thanks.
>>
>>> Info: Testing write flushing..
>>> Info: W
Mike Brudenell wrote:
> Greetings -
>
> A lot of reading and testing has led me part-way to an answer. If
> anyone can help me get all the way there I'll be really grateful: I only
> have 48 hours now before the system has to go live!
>
> The problem...
>
> We are using "userdb passwd" to get
Doug Council wrote:
> I have been getting these assertion failures every couple days, killing
> the IMAP process. After it happens, I can login immediately and
> everything is fine until it happens again. Here is the log entry:
>
> Sep 10 10:03:41 mailbox-4 dovecot: nh: IMAP(username): file
>
Mike Brudenell wrote:
> Yes... However the dovecot.conf configuration file includes a comment
> which says this:
>
> # Should all IMAP and POP3 processes be killed when Dovecot master process
> # shuts down. Setting this to "no" means that Dovecot can be upgraded
> without
> # forcing existing c
Mike Brudenell wrote:
> Greetings -
>
> Now that users are beginning to pile up more on our new Dovecot-based
> IMAP service I'm seeing a small number of entries like this in the
> logfiles:
>
> Corrupted index cache file
> /mailstore/index/o/ozw100/.INBOX/dovecot.index.cache
> : invalid record
58 matches
Mail list logo
