similar to: message-decoder bug for attachments with charset=binary attribute in content-type?

Hi, My second case of this assert, gdb analysis of the core dump attached. My setup: Solaris 9, dovecot built with gcc 4.0.2, mbox format, imap usage only. INBOX is NFS mounted from another Solaris 9 system, index files are local. Syslog complaint is: imap(user): file message-body-search.c: line 414 (message_body_search_ctx): assertion failed: (input->v_offset == part->physical_pos +

Hi. I'm seeing some issues where Entourage clients can see new mail, download it (or partially), but won't display the mail in the mailbox list. Mail shows up as having arrived, but never displays. These clients have worked in the past with versions of 0.99, but not in 1.0-test-56. I have dumped the connection traffic and it looks like Entourage aborts the IMAP session before it

Hi, This is an "important fixes only" release in case you don't want to upgrade to v2.3.15. There is no matching Pigeonhole release - use the same v2.3.14 instead. https://dovecot.org/releases/2.3/dovecot-2.3.14.1.tar.gz <https://dovecot.org/releases/2.3/dovecot-2.3.14.1.tar.gz> https://dovecot.org/releases/2.3/dovecot-2.3.14.1.tar.gz.sig

Hi, This is an "important fixes only" release in case you don't want to upgrade to v2.3.15. There is no matching Pigeonhole release - use the same v2.3.14 instead. https://dovecot.org/releases/2.3/dovecot-2.3.14.1.tar.gz <https://dovecot.org/releases/2.3/dovecot-2.3.14.1.tar.gz> https://dovecot.org/releases/2.3/dovecot-2.3.14.1.tar.gz.sig

My setup: Solaris 9, dovecot built with gcc 4.0.2. Mailboxes on remote NFS file mount from another S9 box (mbox format), index files local disk. IMAP usage only. Dovecot build like so: VERSION=1.0.alpha5 CC=gcc CFLAGS="-g -O" CPPFLAGS=-I/opt/openssl/include \ LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot.$VERSION --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl

A problem here getting winbind traffic to be encrypted using Kerberos. I have set up a test environment with a pair of servers (actually lxc containers): - samba server (ubuntu 16.04, stock samba 4.3.11) - client machine (ubuntu 16.04) joined with "net ads join" and winbind The client machine has the following in /etc/samba/smb.conf: ------- [global] #netbios name = client-ad

I am now testing XEN live migration on two physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). Host A also acts as a NFS server, and Host B acts as a NFS client. When I migrate a guest domain from B to A. The ssh connection experiences a downtime of about 1 minute (the terminal does not react to the keyboard input till about 1 minute later). However, the "sudo xm console" does

On Tue, 22 Nov 2016 15:19:34 +0000 Brian Candler via samba <samba at lists.samba.org> wrote: > On 21/11/2016 17:21, Brian Candler wrote: > > I'd quite like to be able to fetch a ticket using the keytab > > I found a solution to that part by using a different form of > principal name with "hostname$" > > root at client-ad:~# kinit -k -t

I have setup dovecot to allow users to login using their email address or uid and have found a strange behaviour when the user logs in using the email address for a "username". I am using OpenLDAP for a backend data store with a rather customized schema. This behaviour occurs for both POP3 and IMAP logins. For some users it works as expected, but for others the pass_attrs->user

Hi, I'm unable to get past the subject error trying to setup dovecot 2.1.10 on FreeBSD 6.4: right after login the server closes the connection (testing with telnet) I've tried manualy chown()ing auth-master to 666, so permission issues should be ruled out. I'm attaching logs, config and excerpt of ktrace -id. I've built a version with debug symbols, but I don't seem to hit a

On 21/11/2016 17:21, Brian Candler wrote: > I'd quite like to be able to fetch a ticket using the keytab I found a solution to that part by using a different form of principal name with "hostname$" root at client-ad:~# kinit -k -t /etc/krb5.keytab 'CLIENT-AD$@AD.EXAMPLE.NET' root at client-ad:~# klist Ticket cache: FILE:/tmp/krb5cc_0 Default principal:

Hello everyone, recently I've found something I consider a bug. Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A. Imagine my surprise when I saw that all messages that are being output on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are terminated with 0x0D, 0x0A. Maybe that's standard behaviour of all stderr messages in all Linux

(Drats! Jitterbug is playing tricks with the PR# again. Attempting to refile so that we can kill PR#10509) Peter Dalgaard wrote: > Kurt.Hornik at wu-wien.ac.at wrote: > =20 >> ------- Start of forwarded message ------- >> Date: Tue, 13 Nov 2007 21:44:57 +0100 >> To: Steve Mongin <sjm at ccbr.umn.edu> >> Cc: cran at r-project.org >> Subject: Re: range(

Kirtland Air Force Base has denied approval for the use of R on its Windows network. Some of their objections seem a bit strange, but some appear to be legitimate. In particular, they have detected registry "vulnerabilities" which are detailed in the attachment. I know nothing about Windows registry vulnerabilities. If any of these issues are legitimate concerns,

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next