Displaying 20 results from an estimated 60 matches similar to: "sig11 in 1.1rc5 fts"
2008 May 06
1
A previously unreported lsub/list discrepancy in 1.1rc5 and earlier
Not sure about 1.0, I don't run it anymore :) But a few users discovered
for a small issue that only affects a very small portion of my userbase
where instructional correction will suffice. I guess I am reporting it
in the interest of getting it out there, and I can live with it if not
fixed but it might be an issue for some people. I'm running through my
list of issues. Basically,
2008 May 25
2
1.1rc5 Panic: mailbox-tree.c: line 171 (mailbox_tree_iterate_set_next_node)
Hi,
I do hope this hasn't been covered. I googled and looked in the
archives but didn't see anything related, so hopefully I am not covering
old ground.
I recently upgraded from 1.0.10 to 1.1rc5.
I am seeing this error from clients:
May 25 11:01:54 finity dovecot: Panic: IMAP(xxx at here.org): file
mailbox-tree.c: line 171 (mailbox_tree_iterate_set_next_node): assertion
failed:
2008 May 07
1
Bug [1.1rc5]: Crash during "CPU architecture changed" index upgrade
Hello List,
We just migrated from a PPC Xserve to an Intel Xserve.
I used "rsync" to bring everyone's home directories over, and in the
back of my mind wondered about how it would handle the binary index
files... only one way to find out! :)
Once I tried to login to IMAP, I got the following results:
May 6 19:46:48 posh dovecot[1169]: IMAP(cabel): Rebuilding index
file
2004 Aug 30
3
sig11 with test36/37 on some emails
Sometimes I'll get an email from a luser which will cause the POP3 daemon to
sig11. The email "appears" to be legal. The sig11s only happen on specific
emails, and once I remove the emails from the server, the rest can be
downloaded. I gzipped the email, and its at
http://theapt.org/bogusemail.gz. While this example is international spam,
the sig11s happen with real emails too.
2004 Dec 10
1
Lots of SIG11 with test57
Hi,
Here is the backtrace.
--
Nico
Que de tout inconnu le sage se m?fie.
-+- Jean de La Fontaine (1621-1695),
Le Renard, le Loup et le Cheval (Fables XII.17) -+-
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Dovecot-1.0-test57-backtrace
URL:
2005 Aug 29
2
Sig11 and some corrupted indexes after 1.0-stable -> 1.0.alpha1
I just upgraded my production box from 1.0-stable to 1.0.alpha1. I've
noted some new errors in my dovecot logs:
Aug 28 23:23:56 cliff dovecot: IMAP(rsferra): Corrupted index cache
file /mail/mcad.edu/rsferra/Maildir/.Sent Items/dovecot.index.cache:
indexid changed
Aug 28 23:33:57 cliff dovecot: IMAP(acarr): Corrupted transaction log
file /mail/mcad.edu/acarr/Maildir/.Deleted
2017 Jun 05
0
SIG11/Auth/FreeBSD
On Mon, Jun 05, 2017 at 10:18:13AM +0300, Aki Tuomi wrote:
>
>
> On 04.06.2017 22:35, Larry Rosenman wrote:
> > On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote:
> >> I'm seeing lots of:
> > [snipped]
> >> Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM
1998 Dec 07
0
SIG11 at runtime
Hello.
My smbd dies with SIG11. This occurs in 1.9.18p10 as well in 2.0.0beta2.
I've read the Samba archive and found the article "Re: 1.9.17p4 - SIGNAL
11 error ??" from Luke and recompiled it with "-g -g". Here the results:
After a "smbclient -L localhost" or any other tries to connect to the
server the server dies an
--- output of "gdb smbd core"
2005 Apr 18
0
3.0.14a: sig11/panic on redhat6x
Linux Red Hat 6.x:
egcs-1.1.2-24
glibc-2.1.3-22
binutils-2.9.1.0.23-6
kernel-2.2.22-6.2.3
libiconv-1.9.1-1
libiconv-devel-1.9.1-1
Last working is 3.0.10, never tried 3.0.11 3.0.12.
3.0.13 and 3.0.14a will crash at first smbd usage.
Notes:
- To make it compile I performed the following adaptations
perl -pi -e 's|-Wl,-Bsymbolic -Wl,--allow-shlib-undefined||' Makefile
- No
2006 Mar 30
0
sig11 with 1.0.beta3 on openbsd-i386
i recently helped a friend of mine migrate from imap-uw using mboxes to
dovecot on top of Maildirs and came up against two issues. this is
quite embarrassing as ive been claiming dovecot is Solid As A Rock(tm)
and hasn't ever given me any issues.
1. if dovecot runs out of file descriptors it will loop forever trying
to open new logging pipes. the code in question is at line 624 of
2017 Jun 05
2
SIG11/Auth/FreeBSD
On 04.06.2017 22:35, Larry Rosenman wrote:
> On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote:
>> I'm seeing lots of:
> [snipped]
>> Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM
>> IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data
2008 Mar 09
2
1.1r1: auth-worker(default): BUG: PASSV had missing parameters, sig11
I don't know how this happened. I'm not sure if there is a coredump
somewhere because
I don't know what user, and I have nothing for 'root' or 'dovecot'. Any
advice, or should
I make all my coredumps go to a central writable directory so I have
better chance of
catching it if it happens again? Is it maybe from someone connecting to
postfix and causing
a SMTP-AUTH
2004 Nov 29
4
1.0-test53, sig11 when sorting by thread
Hello.
When trying to sort a folder by thread (with pine4.61), I get a sig11.
The mailstore is Maildir, indexes stored in /var/indexes/%u.
The syslog on the server shows this:
Nov 29 11:37:55 olan dovecot: IMAP(kowalski): Corrupted index cache file /var/indexes/kowalski/.INBOX/dovecot.index.cache: record points outside file
Nov 29 11:37:56 olan dovecot: child 14344 (imap) killed with signal 11
2017 Jun 04
0
SIG11/Auth/FreeBSD
On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote:
> I'm seeing lots of:
[snipped]
> Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM
> IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web)
> Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login
2003 Jul 23
3
cvs pserver sig11 on 4.8-R
Hi all,
We recently moved our CVS repository from a 4.6-STABLE machine to a brand
new 4.8 install, on another identical machine. The server runs cvs in
'pserver' mode, for remote access by various Windows/Solaris/Linux/FreeBSD
clients.
We pretty soon noticed that the cvs server process was occasionally crashing
on sig11 (ie. a segfault). The only evidence for this was in the message
2008 May 07
2
How do I increase the fd limit on OS X?
Hi All,
I just upgraded to the new 1.1rc5 from 1.0 that I had been using and it
advised me to increase the file descriptor limit. I'm not sure how to
do this. There is a command built into tcsh that allows me to do this
called limit, but sudo limit 4224 doesn't work, and usually dovecot is
started from the rc.local file if I recall right, and I'm not sure how
to set this up from
2017 Jun 02
2
SIG11/Auth/FreeBSD
I'm seeing lots of:
Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM
IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web)
Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM
IN)
2008 May 09
1
ipv6 woes
I'm trying to bring up dovecot on a dual stack machine. I tried search for
the answers; the answers I found and tried failed :-(.
If I try this:
protocol imap {
listen = 216.218.228.114:143, [2001:470:1:18::114]:143
ssl_listen = 216.218.228.114:993, [2001:470:1:18::114]:993
}
(and similiar for pop3)
I get:
Fatal: listen: Can't resolve address 216.218.228.114:143,
2008 May 27
2
Error when using include directive in Sieve
Hi
I have two sieve scripts:
# cat /var/vmail/sieve/global
require ["include"];
include :global "spam";
include :personal "sieve";
# cat /var/vmail/sieve/spam
require "fileinto";
if exists "X-Spam-Flag" {
fileinto "Junk";
}
# ls -l /var/vmail/sieve/
total 16
-rw-r--r-- 1 mailuser mailgroup 68 2008-05-28 00:40 global
-rw------- 1
2008 May 17
2
expire plugin - setgid failed
Hello all,
I'm trying to get the expire plugin working, but still having issues
even with 1.1RC5.
If I run the expire tool I get the following error:
server:~# dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool
Fatal: setgid(100) failed with euid=2005, gid=0, egid=0: Operation not
permitted
Same thing with --test:
server:~# dovecot --exec-mail ext