similar to: 0.99.6rc1 released

First let me thank you for my initial newby question about poping from a pop3 server and delivering into my Dovecot maildir folders. Now I'm getting an assertion in imap-bodystructure.c and one of my imap folders is now inaccessable. I think the two are related. Whenever I select the folder from my email client (kmail) I get two log entries in the dovecot log of the format:

Several bugfixes since 0.99.6rc3. Here's again the change summary since 0.99.5: v0.99.6 2003-01-13 Timo Sirainen <tss at iki.fi> + THREAD=REFERENCES extension support. ORDEREDSUBJECT would be easy to add, but I think it's pretty useless. + SORT is much faster now. + mbox: If ~/mail directory isn't found, create it. + Log login usernames * Some coding style changes

Well, "release candidate" wasn't really right name for last two versions. Maybe not for this one either, it has a few changes that could potentially break things badly (new hash table code especially). Anyway, seems to work with me. If I don't see any problems with it for a few days it'll be the final. The really great news is that we support threading. A lot of people have

Ok, I have narrowed my IMP/Dovecot attachment problem down to what I think is a bug in Dovecot. The test that follow are performed on 0.99.11. When you download an attachment in IMP it uses the php function imap_fetchbody() which contacts the IMAP server and retrieves just the mime chunk you are looking for. It does this by first fetching some information about the email, and then grabs the

What I want to do is pop my email off of a Pop3 server and give it to dovecot for imap serving. Does anyone know of a utility that will allow me to do this? I looked at fetchmail but it seems to want to talk to an SMTP server. Thanks, Brad -- Brad Figg - brad at tpi.com 503.601.0235 ext. 105 TriplePoint, Inc. - http://www.tpi.com

http://dovecot.procontrol.fi/test/ I should have released 0.99.10 already I think.. There's just two annoying problems that I think should be fixed first: - PAM: If user gives a wrong password, dovecot-auth process sleeps for two seconds, blocking everyone else who are trying to authenticate at the time. So using PAM isn't very good idea at the moment. - OpenSSL problems. Are they

FYI. Does Dovecot implement BODYSTRUCTURE? An eval copy of Mulberry can be downloaded from <http://www.cyrusoft.com/mulberry/>. ------------ Forwarded Message ------------ Date: Tuesday, February 10, 2004 6:56 PM +0100 From: Lennart Petersson <lennart at informatik.gu.se> To: mulberry-discuss at cyrusoft.com Subject: Dovecot and Mulberry I've recently changed my imap-server

Hi there, Quoting RFC 3501 sec. 7.4.2 ?FETCH Response? (data item BODYSTRUCTURE): ?A body type of type MESSAGE and subtype RFC822 contains, immediately after the basic fields, the envelope structure, body structure, and size in text lines of the encapsulated message.? According the ABNF (RFC 3501 sec. 9) the envelope structure is that of the ENVELOPE FETCH data item, and the

This causes the body structure to be incorrect. The RFC says it's fine o have empty header field values. --- This just adds a failing test, inspired from an e-mail spotted in the wild. Ideas welcome to fix it. src/lib-imap/test-imap-bodystructure.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/lib-imap/test-imap-bodystructure.c

On Sun, Mar 15, 2015 at 5:56 PM, Sonny Rajagopalan <sonny.rajagopalan at gmail.com> wrote: > George, > > I have the detailed log below. (Resending after trimming the email to 40KB.) > > The sequence below just repeats ad-nauseam. Is this a SIP trunk issue? > > Thanks! > I don't see anything obvious. The registration works though, right? You might want to compare

Hello, I have the following issue: When using command? FETCH 2 (BODY.PEEK[HEADER] UID INTERNALDATE FLAGS BODYSTRUCTURE) on 2 different emails, we get 2 different response structure. First response structure contains the BODYSTRUCTURE in a single line, while in the second response, the BODYSTRUCTURE is divided into multiple lines with "{61}" character at the end of each line.

Hi, Sorry, It comes by fetching ENVELOPE, not BODYSTRUCTURE. For example: A01 UID FETCH 24 (ENVELOPE) * 4 FETCH (UID 24 ENVELOPE ("Fri, 08 Dec 2017 09:44:35 +0900" "test2" ((NIL NIL "service" "paypal.com")) (("dev1" NIL "dev1-bounces" "example.com")) ((NIL NIL "service" "paypal.com")) (("user1"

Hi all, at work we use Roundcube acting as a mail client for the Dovecot Imap server. In Roundube the messages are parsed through the Imap BODYSTRUCTURE command If a message contains forwarded messages and attachments and some of the messages contains a quote (") in the subject, then the resulting BODYSTRUCTURE appears to be malformed. --- After some digging through the code of

Hi, I tried to see a mail that have a strange From header in bellow URL: https://www.mailsploit.com/index Then, I got BODYSTRUCTURE response contain next: ((NIL NIL "service" "paypal.com")) Are this problem already founded by anyone? So already fixed? -- TACHIBANA Masashi QUALITIA CO., LTD. mailto:tachibana at qualitia.co.jp

Hi All, I am attempting to setup Asterisk with sipcall.co.uk. They use Intertex kit to provide the SIP service. Unfortunately Asterisk cannot seem to authenticate against Intertex. Having provided SIP debug info the provider has informed me that Asterisk does not appear to support 'qop', 'nc' and 'cnonce' which are used to stop replay attacks. So, does Asterisk support

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Attached is a patch against current CVS that adds support for the GSSAPI SASL mechanism. It was written from scratch, after reading the patch from Colin Walters against a much older version of dovecot. Other then support for the 'GSSAPI' mechanism, it contains the following changes: - - Added 'auth_krb5_keytab' option for

Hello, We upgraded one of our dovecot servers to debian stretch with dovecot 2.2.27 and since then one of our users has been experiencing random IMAP failures. We enabled raw logging at the server side and it shows normal IMAP commands/responses: 1507292522.222427 * 6 FETCH (FLAGS () BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL

Hi, my dovecot installation works since months and clients authenticate using CRAM-MD5. But today I got the first chance to test an client that supports DIGEST-MD5 - and it doesn't work. Because of lack of other supporting clients and servers I'm now at the point I don't know which side is to blame. The error I get after the client answers the servers challenge is "-ERR

Hi, I need to create something like this: <?xml version="1.0" encoding="UTF-8"?> <Container> <id>aQlfVHX+qPM</id> <lifetime>2009-09-19T08:14:55Z</lifetime> </Container> The response should contain the next headers: Content-Type=`application/vnd.3gpp+xml`

Hi! I'm using rc9 and DIGEST-MD5 passwords. Sometimes it works, sometimes it's not... When failed, I get this in the logs: 12:45:11 Info: auth(default): client in: AUTH 1 DIGEST-MD5 \ service=POP3 secured lip=<lip> rip=<rip> resp=<something_long> 12:45:11 Info: auth(default): client out: CONT 1 <something_long> 12:45:11 Info: auth(default): client in: CONT 1