-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm happy to announce the availability of dbmail-2.2.8-rc1.
This is a bugfix-only release that addresses a couple of problems that
have come up since 2.2.7. No new features were added.
changes since 2.2.7:
- - avoid gmime mbox parser to
Got it.
It was the From_ line at the beginning that kicked in the gmime mbox scanner.
Attached patch fixes this.
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm happy to announce the availability of dbmail-2.2.8-rc1.
This is a bugfix-only release that addresses a couple of problems that
have come up since 2.2.7. No new features were added.
changes since 2.2.7:
- - avoid gmime mbox parser to
I have a feeling that this is a squirrelmail problem, but maybe somebody here
has a solution.
for messages that have no body but they do have an attachment I get the error:
Body retrieval error. The reason for this is most probably that the message is
malformed.Command:FETCH 1761137
What about RFC 3501 4.5 ?
Date: Wed, 5 Dec 2007 20:54:14 +0100
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Dbmail] squirrelmail issues
Eric Hiller writes:
It looks like the problem lies in that
* 148 FETCH (UID 1761137 BODY[1] NIL)
Line. Is it proper for an
Any message that has nothing for a body, but has attachments, I was talking
with a squirrelmail dev and he said that it looks like they were not quite
compliant with the rfc for this and has already implemented a bugfix. I really
did not know where the problem lie, with squirrelmail or dbmail
can you show me such a message?
Eric Hiller wrote:
I have a feeling that this is a squirrelmail problem, but maybe somebody
here has a solution.
for messages that have no body but they do have an attachment I get the
error:
Body retrieval error. The reason for this is most probably that
I have a spam filter that works pretty good, only problem is most users are too
lazy to click purge and actually clean out their 'Trash' folder and then they
call and complain that their quote is exceeded. So I put together this little
query below to solve that problem, it will delete the
It looks like the problem lies in that
* 148 FETCH (UID 1761137 BODY[1] NIL)
Line. Is it proper for an IMAP server to return NIL there?
We are trying to figure that out now in squirrelmail.
From: [EMAIL PROTECTED]
To: dbmail@dbmail.org
Date: Wed, 5 Dec 2007
I remember putting something like that together. It's in the contrib
directory of the trunk. But I'll attach a copy here.
Don't filter on the datefield table. It represents the Date: header of a
message, not the received date. The physmessage.internal_date represents
the received date. Which is
Date: Wed, 5 Dec 2007 20:54:14 +0100
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Dbmail] squirrelmail issues
Eric Hiller writes:
It looks like the problem lies in that
* 148 FETCH (UID 1761137 BODY[1] NIL)
Line. Is it proper for an IMAP server to return NIL there?
Would this work? I am trying to get it down to a single statement.
UPDATE dbmail_messages SET status=2 WHERE physmessage_id NOT IN (SELECT id FROM
dbmail_physmessage WHERE current_timestamp at time zone 'GMT' - '1
day'::interval = internal_date) AND mailbox_idnr IN (SELECT mailbox_idnr FROM
That sounds like it might be alot of overhead, because then it is actually
getting all the data, i dont need that.
Did you think my standalone query would work Aaron?
Subject: RE: [Dbmail] automatic purgeing of trash folder
From: [EMAIL PROTECTED]
To: dbmail@dbmail.org
Date: Wed, 5 Dec
dbmail-export already does all of this, albeit with the overhead of
dumping the messages (to /dev/null, if you'd like).
Aaron
On Wed, 2007-12-05 at 17:22 -0600, Eric Hiller wrote:
Would this work? I am trying to get it down to a single statement.
UPDATE dbmail_messages SET status=2 WHERE
14 matches
Mail list logo
