Hello
I've upgraded from 1.2.11 to 2.0.6 and now to 2.0.7 and since
upgrade I don't get the bounced mails to postmastar or mail-daemon (
the mails with errors )
this is from my logs
Sep 5 22:06:19 debian dbmail/smtp[732]: GetConfigValue(): NULL item
value in item-list
Sep
This looks like a level 3 or 4 trace. Could you please provide a level 5
trace?
Did you do as suggested: run dbmail-utils -ay?
Leonel Nunez wrote:
>
>
> Hello
> I've upgraded from 1.2.11 to 2.0.6 and now to 2.0.7 and since
> upgrade I don't get the bounced mails to postmastar or mail-da
Paul J Stevens wrote:
This looks like a level 3 or 4 trace. Could you please provide a level 5
trace?
Did you do as suggested: run dbmail-utils -ay?
yes I did
here is the level 5 for the smtp I'm using PostgreSQL 8.0.3
Sep 6 06:18:36 debian dbmail/smtp[1886]: dbpgsql.c,db_query
Leonel Nunez wrote:
> Sep 6 06:18:36 debian dbmail/smtp[1886]: dbpgsql.c,db_query: executing
> query [INSERT INTO dbmail_messageblks (is_header, messageblk, blocksize,
> physmessage_id) VALUES ('1','Received: from CHANGED (debian [127.0.0.1])
> ^Iby CHANGED (Postfix) with ESMTP id 7A966601FD;
Paul J Stevens wrote:
Leonel Nunez wrote:
Sep 6 06:18:36 debian dbmail/smtp[1886]: dbpgsql.c,db_query: executing
query [INSERT INTO dbmail_messageblks (is_header, messageblk, blocksize,
physmessage_id) VALUES ('1','Received: from CHANGED (debian [127.0.0.1])
^Iby CHANGED (Postfix) with E
Hello,
I did a brief overview of 1.2.x dbmail pop3 code once looking for that
sort of thing; I'm not a C expert, but from what I saw I don't think
there was a problem. Iirc, dbmail actually caught and handled the extra
length fine, it just chose to drop the pop3 connection on that invalid
input
> So yes! All you 1.2 users (you too, Jesse) better start thinking about
> upgrading.
Yeah, we're thinking about it. Hopefully we'll be able to go right to
2.2.x, by the time we actually get around to it. :)
--
Jesse Norell - [EMAIL PROTECTED]
Kentec Communications, Inc.
