[Dbmail-dev] [DBMail 0000548]: WISH: Better parsing 8bit header characters
A NOTE has been added to this issue. == http://www.dbmail.org/mantis/view.php?id=548 == Reported By:idk Assigned To: == Project:DBMail Issue ID: 548 Category: IMAP daemon Reproducibility:N/A Severity: feature Priority: normal Status: new target: == Date Submitted: 22-Mar-07 11:23 CET Last Modified: 23-Mar-07 08:16 CET == Summary:WISH: Better parsing 8bit header characters Description: In mail header values there are valid only 7bit characters, so accents should be escaped. But... Seldom I got message from buggy mail client which ignore this rule. MSOE's message list has invalid subject (it seems like UTF8 encodings but displayed by single byte), but opened message has Subject header displayed correctly (parsed from headers part of message). So I think it has a solution. MSOE under Windows (CZE) has default code page 1250, so this is one option MSOE interpreted Subject from all message content correctly, other one is fetching of Content-Type header value (see Additional Information). The second option should be applicable for DBMail, I mean. == Relationships ID Summary -- related to 538 incorrect field cache values for messag... == -- paul - 22-Mar-07 14:42 -- This is exactly how it's done at the moment. If a header is 8bit the header string is converted to utf8. If the content-type header contains a charset specification dbmail will try to convert from the specified charset to utf8 Else dbmail will fall back to the charset specified in the DEFAULT_MSG_ENCODING config value and try to convert the string to utf8, assuming the header was encoded in that charset. If both fail dbmail will replace all 8 bit characters with '?'. -- idk - 22-Mar-07 16:25 -- mysql SELECT HEX(SUBSTRING(messageblk, 1087, 53)) FROM dbmail_messageblks WHERE physmessage_id = 273400 AND is_header = 1; 5375626A6563743A 20 566964656F70726F686C ED 646B61 20 76656C6574726875 20 72796261 F8 656E ED 20 76 20 42726E EC 20 32303037 (added spaces around a \x20 and \x7F chars) mysql SELECT SUBSTRING(messageblk, 1087, 53) FROM dbmail_messageblks WHERE physmessage_id = 273400 AND is_header = 1; Subject: Videoprohl?dka veletrhu ryba?en? v Brn? 2007 A001 UID FETCH 554133 (ENVELOPE) * 97 FETCH (UID 554133 ENVELOPE (Wed, 21 Mar 2007 18:09:41 +0100 =?UTF-8?q?Videoprohl=C3=ADdka_veletrhu_ryba=C5=99en=C3=AD_?= =?iso-8859-2?q?v_Brn=EC?= 2007 ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL undisclosed-recipients NIL)) NIL NIL NIL [EMAIL PROTECTED])) A001 OK UID FETCH completed It seems ok, because UTF(C3 AD) == WIN(ED), UTF(C5 99) == WIN(F8), ISO(EC) = WIN(EC). Do you mean bug is in MSOE mail client? Does MSOE recognize a =?UTF-8?q? prefix? Or mixed UTF8 and ISO 8859-2? I'll attach screenshots of this situation. Red underlining highlites wrong characters and green correct (at msoe.jpg you could see of font change from this position to the end of line, incl. 2007 number, but it seems like MSOE bug, squirrel (SquirrelMail 1.4.10 SVN) shows both wrong). (Note for http://www.dbmail.org/mantis/view.php?id=538: I have 2471 revision, default_msg_encoding=utf8.) -- paul - 22-Mar-07 16:56 -- Now why are you using default_msg_encoding=utf8?? Try using windows-1250 since you mentioned that is the charset that's causing the problems. -- idk - 22-Mar-07 23:48 -- Why am I UTF8 as default? You said me :) In bug http://www.dbmail.org/mantis/view.php?id=265 you wrote: ... you do need to change dbmail.conf and add two new entries: encoding=utf8 default_msg_encoding=utf8 So I did it. Nevertheless I have tried to change to WINDOWS-1250 but with the same result.
[Dbmail-dev] Future request on sieve scripts
Hello
I want to put incoming messages into folders, based on current year and month
Smth like this:
if {
fileinto some-folder;
} else {
fileinto INBOX/$YEAR/$MONTH;
}
Can this be implemented?
Thanks.
--
Oleg Lapshin
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000548]: WISH: Better parsing 8bit header characters
A NOTE has been added to this issue. == http://www.dbmail.org/mantis/view.php?id=548 == Reported By:idk Assigned To: == Project:DBMail Issue ID: 548 Category: IMAP daemon Reproducibility:N/A Severity: feature Priority: normal Status: new target: == Date Submitted: 22-Mar-07 11:23 CET Last Modified: 23-Mar-07 10:49 CET == Summary:WISH: Better parsing 8bit header characters Description: In mail header values there are valid only 7bit characters, so accents should be escaped. But... Seldom I got message from buggy mail client which ignore this rule. MSOE's message list has invalid subject (it seems like UTF8 encodings but displayed by single byte), but opened message has Subject header displayed correctly (parsed from headers part of message). So I think it has a solution. MSOE under Windows (CZE) has default code page 1250, so this is one option MSOE interpreted Subject from all message content correctly, other one is fetching of Content-Type header value (see Additional Information). The second option should be applicable for DBMail, I mean. == Relationships ID Summary -- related to 538 incorrect field cache values for messag... == -- paul - 22-Mar-07 14:42 -- This is exactly how it's done at the moment. If a header is 8bit the header string is converted to utf8. If the content-type header contains a charset specification dbmail will try to convert from the specified charset to utf8 Else dbmail will fall back to the charset specified in the DEFAULT_MSG_ENCODING config value and try to convert the string to utf8, assuming the header was encoded in that charset. If both fail dbmail will replace all 8 bit characters with '?'. -- idk - 22-Mar-07 16:25 -- mysql SELECT HEX(SUBSTRING(messageblk, 1087, 53)) FROM dbmail_messageblks WHERE physmessage_id = 273400 AND is_header = 1; 5375626A6563743A 20 566964656F70726F686C ED 646B61 20 76656C6574726875 20 72796261 F8 656E ED 20 76 20 42726E EC 20 32303037 (added spaces around a \x20 and \x7F chars) mysql SELECT SUBSTRING(messageblk, 1087, 53) FROM dbmail_messageblks WHERE physmessage_id = 273400 AND is_header = 1; Subject: Videoprohl?dka veletrhu ryba?en? v Brn? 2007 A001 UID FETCH 554133 (ENVELOPE) * 97 FETCH (UID 554133 ENVELOPE (Wed, 21 Mar 2007 18:09:41 +0100 =?UTF-8?q?Videoprohl=C3=ADdka_veletrhu_ryba=C5=99en=C3=AD_?= =?iso-8859-2?q?v_Brn=EC?= 2007 ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL undisclosed-recipients NIL)) NIL NIL NIL [EMAIL PROTECTED])) A001 OK UID FETCH completed It seems ok, because UTF(C3 AD) == WIN(ED), UTF(C5 99) == WIN(F8), ISO(EC) = WIN(EC). Do you mean bug is in MSOE mail client? Does MSOE recognize a =?UTF-8?q? prefix? Or mixed UTF8 and ISO 8859-2? I'll attach screenshots of this situation. Red underlining highlites wrong characters and green correct (at msoe.jpg you could see of font change from this position to the end of line, incl. 2007 number, but it seems like MSOE bug, squirrel (SquirrelMail 1.4.10 SVN) shows both wrong). (Note for http://www.dbmail.org/mantis/view.php?id=538: I have 2471 revision, default_msg_encoding=utf8.) -- paul - 22-Mar-07 16:56 -- Now why are you using default_msg_encoding=utf8?? Try using windows-1250 since you mentioned that is the charset that's causing the problems. -- idk - 22-Mar-07 23:48 -- Why am I UTF8 as default? You said me :) In bug http://www.dbmail.org/mantis/view.php?id=265 you wrote: ... you do need to change dbmail.conf and add two new entries: encoding=utf8 default_msg_encoding=utf8 So I did it. Nevertheless I have tried to change to WINDOWS-1250 but with the same result.
[Dbmail-dev] [DBMail 0000546]: Memory corrupted in IMAP daemon
A NOTE has been added to this issue. == http://dbmail.org/mantis/view.php?id=546 == Reported By:idk Assigned To: == Project:DBMail Issue ID: 546 Category: IMAP daemon Reproducibility:unable to reproduce Severity: minor Priority: normal Status: new target: == Date Submitted: 20-Mar-07 15:07 CET Last Modified: 23-Mar-07 11:18 CET == Summary:Memory corrupted in IMAP daemon Description: I don't know what action causes this problem, but I seldom read the dbmail.err file and I found some errors (see Additional Information). Due a nonexistency of timestamp in logfile I don't know if this three issues are relatives. == -- aaron - 23-Mar-07 02:18 -- Does this possibly happen right after a SIGHUP? I cleaned up some code in that area, but I might have missed something. -- idk - 23-Mar-07 11:18 -- From upgrading to rev. 2471 it didn't occurred. I restared by init script (service dbmail-imapd restart) many times (but this is not a SIGHUP, but stop/start, so killproc and new start). BTW often during restarting of a daemon occurrs this issue: Stopping say OK, but startning say already running with list of pids. After a while next restart: stopping say FAILED and starting say OK. No errors are logged. I have tried service dbmail-imapd reload (so SIGHUP, killproc $dbmail -HUP), process is ok and no error message was reported. Issue History Date Modified Username FieldChange == 20-Mar-07 15:07 idkNew Issue 23-Mar-07 02:18 aaron Note Added: 0001944 23-Mar-07 11:18 idkNote Added: 0001948 == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000546]: Memory corrupted in IMAP daemon
A NOTE has been added to this issue. == http://dbmail.org/mantis/view.php?id=546 == Reported By:idk Assigned To: == Project:DBMail Issue ID: 546 Category: IMAP daemon Reproducibility:unable to reproduce Severity: minor Priority: normal Status: new target: == Date Submitted: 20-Mar-07 15:07 CET Last Modified: 23-Mar-07 11:24 CET == Summary:Memory corrupted in IMAP daemon Description: I don't know what action causes this problem, but I seldom read the dbmail.err file and I found some errors (see Additional Information). Due a nonexistency of timestamp in logfile I don't know if this three issues are relatives. == -- aaron - 23-Mar-07 02:18 -- Does this possibly happen right after a SIGHUP? I cleaned up some code in that area, but I might have missed something. -- idk - 23-Mar-07 11:18 -- From upgrading to rev. 2471 it didn't occurred. I restared by init script (service dbmail-imapd restart) many times (but this is not a SIGHUP, but stop/start, so killproc and new start). BTW often during restarting of a daemon occurrs this issue: Stopping say OK, but startning say already running with list of pids. After a while next restart: stopping say FAILED and starting say OK. No errors are logged. I have tried service dbmail-imapd reload (so SIGHUP, killproc $dbmail -HUP), process is ok and no error message was reported. -- idk - 23-Mar-07 11:24 -- After SIGHUP daemon stop to listen :( Telnet to lmtp connects to a port and say # telnet localhost lmtp Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. Connection closed by foreign host. A had to restart them (imapd too). Issue History Date Modified Username FieldChange == 20-Mar-07 15:07 idkNew Issue 23-Mar-07 02:18 aaron Note Added: 0001944 23-Mar-07 11:18 idkNote Added: 0001948 23-Mar-07 11:24 idkNote Added: 0001949 == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000546]: Memory corrupted in IMAP daemon
A NOTE has been added to this issue. == http://dbmail.org/mantis/view.php?id=546 == Reported By:idk Assigned To: == Project:DBMail Issue ID: 546 Category: IMAP daemon Reproducibility:unable to reproduce Severity: minor Priority: normal Status: new target: == Date Submitted: 20-Mar-07 15:07 CET Last Modified: 23-Mar-07 11:55 CET == Summary:Memory corrupted in IMAP daemon Description: I don't know what action causes this problem, but I seldom read the dbmail.err file and I found some errors (see Additional Information). Due a nonexistency of timestamp in logfile I don't know if this three issues are relatives. == -- aaron - 23-Mar-07 02:18 -- Does this possibly happen right after a SIGHUP? I cleaned up some code in that area, but I might have missed something. -- idk - 23-Mar-07 11:18 -- From upgrading to rev. 2471 it didn't occurred. I restared by init script (service dbmail-imapd restart) many times (but this is not a SIGHUP, but stop/start, so killproc and new start). BTW often during restarting of a daemon occurrs this issue: Stopping say OK, but startning say already running with list of pids. After a while next restart: stopping say FAILED and starting say OK. No errors are logged. I have tried service dbmail-imapd reload (so SIGHUP, killproc $dbmail -HUP), process is ok and no error message was reported. -- idk - 23-Mar-07 11:24 -- After SIGHUP daemon stop to listen :( Telnet to lmtp connects to a port and say # telnet localhost lmtp Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. Connection closed by foreign host. A had to restart them (imapd too). -- idk - 23-Mar-07 11:55 -- A'll attach three mail files, original (mail about this issue), subject-8bit (original with altered Subject, only 8 bit chars stills, WIN charset) and subject-escaped (the same as subject-8bit, but encoded and escaped into ISO). mysql SELECT HEX(headervalue) FROM dbmail_headervalue WHERE headername_id = 7 AND physmessage_id IN (274672,274673,274674); 566964656F70726F686CC3AD646B612076656C65747268752072796261C599656EC3AD20762042726EC49B2032303037 C3AD20C599C3AD2078207820782078207820782078207820782078207820782078207820C49B C3AD20C599C3AD2078207820782078207820782078207820782078207820782078207820C49B mysql SELECT envelope FROM dbmail_envelope WHERE physmessage_id IN (274672,274673,274674); (Wed, 21 Mar 2007 18:09:41 +0100 =?UTF-8?q?Videoprohl=C3=ADdka_veletrhu_ryba=C5=99en=C3=AD_?= =?iso-8859-2?q?v_Brn=EC?= 2007 ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL undisclosed-recipients NIL)) NIL NIL NIL [EMAIL PROTECTED]) (Wed, 21 Mar 2007 18:09:41 +0100 =?UTF-8?b?w60gxZnDrSA=?= =?iso-8859-2?q?x_x_x_x_x_x_x_x_x_x_x_x_x_x_=EC?= ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL undisclosed-recipients NIL)) NIL NIL NIL [EMAIL PROTECTED]) (Wed, 21 Mar 2007 18:09:41 +0100 =?iso-8859-2?Q?=ED_=F8=ED_x_x_x_x_x_x_x_x_x_x_x_x_x_x_=EC?= ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL undisclosed-recipients NIL)) NIL NIL NIL [EMAIL PROTECTED]) Issue History Date Modified Username FieldChange == 20-Mar-07 15:07 idkNew Issue 23-Mar-07 02:18 aaron Note Added: 0001944 23-Mar-07 11:18 idkNote Added: 0001948 23-Mar-07 11:24 idkNote Added: 0001949 23-Mar-07 11:55 idkNote Added: 0001950 ==
[Dbmail-dev] [DBMail 0000548]: WISH: Better parsing 8bit header characters
A NOTE has been added to this issue. == http://www.dbmail.org/mantis/view.php?id=548 == Reported By:idk Assigned To: == Project:DBMail Issue ID: 548 Category: IMAP daemon Reproducibility:N/A Severity: feature Priority: normal Status: new target: == Date Submitted: 22-Mar-07 11:23 CET Last Modified: 23-Mar-07 11:56 CET == Summary:WISH: Better parsing 8bit header characters Description: In mail header values there are valid only 7bit characters, so accents should be escaped. But... Seldom I got message from buggy mail client which ignore this rule. MSOE's message list has invalid subject (it seems like UTF8 encodings but displayed by single byte), but opened message has Subject header displayed correctly (parsed from headers part of message). So I think it has a solution. MSOE under Windows (CZE) has default code page 1250, so this is one option MSOE interpreted Subject from all message content correctly, other one is fetching of Content-Type header value (see Additional Information). The second option should be applicable for DBMail, I mean. == Relationships ID Summary -- related to 538 incorrect field cache values for messag... == -- paul - 22-Mar-07 14:42 -- This is exactly how it's done at the moment. If a header is 8bit the header string is converted to utf8. If the content-type header contains a charset specification dbmail will try to convert from the specified charset to utf8 Else dbmail will fall back to the charset specified in the DEFAULT_MSG_ENCODING config value and try to convert the string to utf8, assuming the header was encoded in that charset. If both fail dbmail will replace all 8 bit characters with '?'. -- idk - 22-Mar-07 16:25 -- mysql SELECT HEX(SUBSTRING(messageblk, 1087, 53)) FROM dbmail_messageblks WHERE physmessage_id = 273400 AND is_header = 1; 5375626A6563743A 20 566964656F70726F686C ED 646B61 20 76656C6574726875 20 72796261 F8 656E ED 20 76 20 42726E EC 20 32303037 (added spaces around a \x20 and \x7F chars) mysql SELECT SUBSTRING(messageblk, 1087, 53) FROM dbmail_messageblks WHERE physmessage_id = 273400 AND is_header = 1; Subject: Videoprohl?dka veletrhu ryba?en? v Brn? 2007 A001 UID FETCH 554133 (ENVELOPE) * 97 FETCH (UID 554133 ENVELOPE (Wed, 21 Mar 2007 18:09:41 +0100 =?UTF-8?q?Videoprohl=C3=ADdka_veletrhu_ryba=C5=99en=C3=AD_?= =?iso-8859-2?q?v_Brn=EC?= 2007 ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL chytej chytej.cz)) ((NIL NIL undisclosed-recipients NIL)) NIL NIL NIL [EMAIL PROTECTED])) A001 OK UID FETCH completed It seems ok, because UTF(C3 AD) == WIN(ED), UTF(C5 99) == WIN(F8), ISO(EC) = WIN(EC). Do you mean bug is in MSOE mail client? Does MSOE recognize a =?UTF-8?q? prefix? Or mixed UTF8 and ISO 8859-2? I'll attach screenshots of this situation. Red underlining highlites wrong characters and green correct (at msoe.jpg you could see of font change from this position to the end of line, incl. 2007 number, but it seems like MSOE bug, squirrel (SquirrelMail 1.4.10 SVN) shows both wrong). (Note for http://www.dbmail.org/mantis/view.php?id=538: I have 2471 revision, default_msg_encoding=utf8.) -- paul - 22-Mar-07 16:56 -- Now why are you using default_msg_encoding=utf8?? Try using windows-1250 since you mentioned that is the charset that's causing the problems. -- idk - 22-Mar-07 23:48 -- Why am I UTF8 as default? You said me :) In bug http://www.dbmail.org/mantis/view.php?id=265 you wrote: ... you do need to change dbmail.conf and add two new entries: encoding=utf8 default_msg_encoding=utf8 So I did it. Nevertheless I have tried to change to WINDOWS-1250 but with the same result.
[Dbmail-dev] [DBMail 0000539]: Mailclient times out opening large mailboxes
The following issue has been RESOLVED.
==
http://www.dbmail.org/mantis/view.php?id=539
==
Reported By:paul
Assigned To:paul
==
Project:DBMail
Issue ID: 539
Category: IMAP daemon
Reproducibility:always
Severity: minor
Priority: normal
Status: resolved
target:
Resolution: fixed
Fixed in Version: 2.2.5
==
Date Submitted: 17-Mar-07 16:42 CET
Last Modified: 23-Mar-07 13:53 CET
==
Summary:Mailclient times out opening large mailboxes
Description:
When a mailclient like Thunderbird opens a large mailfolder with many
unread messages an error is returned to the user saying that opening the
folder takes too long.
==
--
cmayo - 19-Mar-07 20:27
--
I see the same timeouts with 2.2.4. Analysing the Postgresql 8.1.8 logs
with pgfouine updating the recent flags with:
update dbmail_messages set recent_flag = 0 where message_idnr in
is taking a lot of time.
--
paul - 19-Mar-07 22:11
--
Interesting.
As part of this bug I'm actually working on avoiding long-running queries
against the envelope and header caches. Such queries shouldn't scale 1/n
with the number of messages in a mailbox before returning some data to the
client.
At first glance however, your case smells like a different beast.
Why is postgres taking so long to run the update query that flushes recent
flags?
I assume that postgres doesn't suffer from locking issues due to mvcc.
Right?
Are you sure this is the query that is triggering timeouts in the client?
--
cmayo - 19-Mar-07 23:20
--
Sorry, looks like it was my database getting stale. It did appear to be the
updates activity that were slowing the connection - I could see them by
doing tail -f on the log file, and they would continue for a while even
after the client had timed out.
However, I'd done a vacuum analyze and a vacuum full on my database and it
seems the solution was:
reindex table dbmail_messages
--
cmayo - 21-Mar-07 20:34
--
Well, performance drops off again and another reindex speeds it up for
while and then it slows. May well be a problem with my database, which I
will keep looking for.
I ended up taking drastic action and patching dbmail-imapsession.c:
@@ -1764,7 +1764,7 @@
int dbmail_imap_session_mailbox_update_recent(struct ImapSession *self)
{
- imap_session_update_recent(self-recent);
+ /* imap_session_update_recent(self-recent); */
g_list_destroy(self-recent);
self-recent = NULL;
Hopefully this hasn't broken anything significant.
--
paul - 21-Mar-07 21:44
--
The plot thickens then. Removing that call will break rfc compliance since
the recent flag for a message must (not should) be cleared upon first
accessing a message (fetch) in a read/write selected mailbox.
Makes /me/ wonder about why postgres needs reindexing at all?? I would
wager that simply updating a int2 field shouldn't require such manual
intervention. Don't you have pg_autovacuum running?
I can, and should in fact wrap the whole sequence of update queries in a
transaction, which will most likely improve performance, but I doubt it
will influence the key autoindexing.
Perhaps some input from an avid postgres user is warrented.
--
cmayo - 22-Mar-07 22:43
--
An interesting post at:
http://postgis.refractions.net/pipermail/postgis-users/2006-December/014073.html
says that when Postgresql UPDATES a row it duplicates it (for MVCC to
work).
I did some experimentation using:
select pg_total_relation_size( 'messages_pkey' );
to monitor the size of the index and the updates are causing it to
[Dbmail-dev] [DBMail 0000544]: Segmet fault on empty message
The following issue has been RESOLVED. == http://www.dbmail.org/mantis/view.php?id=544 == Reported By:AntonZ Assigned To:paul == Project:DBMail Issue ID: 544 Category: PIPE delivery (dbmail-smtp) Reproducibility:always Severity: minor Priority: normal Status: resolved target: Resolution: fixed Fixed in Version: 2.2.5 == Date Submitted: 19-Mar-07 17:01 CET Last Modified: 23-Mar-07 13:53 CET == Summary:Segmet fault on empty message Description: dbmail-smtp -d '[EMAIL PROTECTED]' Press Ctrl-D to close input stream. == -- paul - 23-Mar-07 13:53 -- This was fixed in rev 2474 Issue History Date Modified Username FieldChange == 19-Mar-07 17:01 AntonZ New Issue 23-Mar-07 13:53 paul Note Added: 0001953 23-Mar-07 13:53 paul Assigned To = paul 23-Mar-07 13:53 paul Status new = resolved 23-Mar-07 13:53 paul Resolution open = fixed 23-Mar-07 13:53 paul Fixed in Version = 2.2.5 == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000543]: Logging does not say anything about the remote users ip
The following issue has been RESOLVED. == http://www.dbmail.org/mantis/view.php?id=543 == Reported By:menole Assigned To:paul == Project:DBMail Issue ID: 543 Category: POP3 daemon Reproducibility:always Severity: minor Priority: normal Status: resolved target: Resolution: fixed Fixed in Version: 2.2.5 == Date Submitted: 19-Mar-07 14:16 CET Last Modified: 23-Mar-07 13:54 CET == Summary:Logging does not say anything about the remote users ip Description: Failed pop3 login attempts are logged as follows: Mar 19 13:10:47 dbmail-01 dbmail/pop3d[25510]: Error user [bla] tried to login with wrong password Nice to know that there was a failed attempt, but no idea how to handle. Please add user's IP into log message: Mar 19 13:55:36 dbmail-01 dbmail/pop3d[30326]: Error user [bla] comming from [192.168.3.140] tried to login with wrong password patch for pop3.c is attached Kind Regards, Michael Mende == -- paul - 23-Mar-07 13:54 -- Fixed in rev 2474 Issue History Date Modified Username FieldChange == 19-Mar-07 14:16 menole New Issue 19-Mar-07 14:16 menole File Added: 05_pop3.dpatch 23-Mar-07 13:54 paul Note Added: 0001954 23-Mar-07 13:54 paul Assigned To = paul 23-Mar-07 13:54 paul Status new = resolved 23-Mar-07 13:54 paul Resolution open = fixed 23-Mar-07 13:54 paul Fixed in Version = 2.2.5 == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000542]: postinst script for dbmail-mysql
The following issue has been CLOSED == http://www.dbmail.org/mantis/view.php?id=542 == Reported By:lkneschke Assigned To:paul == Project:DBMail Issue ID: 542 Category: installation scripts Reproducibility:always Severity: minor Priority: normal Status: closed target: Resolution: won't fix Fixed in Version: == Date Submitted: 19-Mar-07 08:00 CET Last Modified: 23-Mar-07 13:55 CET == Summary:postinst script for dbmail-mysql Description: This patch modifies the dbmail.conf as needed, when the dbmail-mysql package got installed. [EMAIL PROTECTED]:~/src/dbmail-2.2/debian# svn diff dbmail-mysql.postinst Index: dbmail-mysql.postinst === --- dbmail-mysql.postinst (revision 2472) +++ dbmail-mysql.postinst (working copy) @@ -32,6 +32,45 @@ upgrade) ;; configure) + + . /usr/share/debconf/confmodule + db_get dbmail/do_debconf || true; DO_DEBCONF=$RET + + if [ $DO_DEBCONF = true ]; then + # fetch debconf values + db_get dbmail/dbmail/host || true; DB_HOST=$RET + db_get dbmail/dbmail/db || true; DB_DATABASE=$RET + db_get dbmail/dbmail/user || true; DB_USER=$RET + db_get dbmail/dbmail/pass || true; DB_PASS=$RET + + if [ -z $DB_PASS ]; then + if [ -x /usr/bin/pwgen ]; then + DB_PASS=`pwgen -n` + db_set dbmail/dbmail/pass $DB_PASS + fi + fi + fi + + # protect the config-file + oldmask=`umask` + umask 026 + + if [ $DO_DEBCONF = true ] [ -e $CONFIG ]; then + # edit the configs + sed -i -e s,\(^host\W*=\)\(.*\$\),\1 $DB_HOST,i \ + -e s,\(^user\W*=\)\(.*\$\),\1 $DB_USER,i \ + -e s/\(^pass\W*=\)\(.*\$\)/\1 $DB_PASS/i \ + -e s,\(^db\W*=\)\(.*\$\),\1 $DB_DATABASE,i \ + -e s,\(^driver\W*=\)\(.*\$\),\1 mysql,i \ +$CONFIG + + umask $oldmask + + fi + + db_stop + chmod 0600 $CONFIG + ;; abort-upgrade) ;; == -- paul - 19-Mar-07 09:06 -- Lars, This won't roll. The postinst files for postgres and mysql should never touch the dbmail.conf file. That was a delibirate decision. It is perfectly valid to install dbmail-pgsql on a running dbmail-mysql or dbmail-sqlite system and vice versa. You don't want a silent change of the production backend under those circumstances. -- lkneschke - 19-Mar-07 09:41 -- Hello Paul! Ok, but how can we fix it? :-) Having everything configurable from debconf just not the database backend looks a little bit incomplete for me? Should we move the debconf settings to dbmail.postinst(aka Please select database backend)? My points of view. I want to have preconfiguration of debian packages working. This is currently not possible, because you still need to edit the dbmail.conf file. If i decide to use debconf, i would expect it changing the database backend. Because i would install dbmail-mysql or dbmail-postgresql. If someone likes to have both database backends available, then he would not use debconf anyway. Just points... :-) Lars -- paul - 19-Mar-07 10:13 -- It's a bit like Peter Eisenbach (who sponsered the upload) said: too much debconf love going on. The consensus seems to be: debconf is not meant to provide a fullfledged system configuration tool. It should provide a mechanism for setting up a configuration where a sane default is not possible. Also, the debian packages currently *do* provide a working setup out-of-the-box with database autocreation albeit of the sqlite variety. It is only when you want to switch to mysql or postgresql that you need to install an additional package and edit
[Dbmail-dev] [DBMail 0000550]: Messages that are viewed in squirrelmail and thunderbird and not outlook express
A NOTE has been added to this issue.
==
http://dbmail.org/mantis/view.php?id=550
==
Reported By:jasb
Assigned To:
==
Project:DBMail
Issue ID: 550
Category: IMAP daemon
Reproducibility:always
Severity: major
Priority: normal
Status: new
target:
==
Date Submitted: 22-Mar-07 22:55 CET
Last Modified: 23-Mar-07 15:19 CET
==
Summary:Messages that are viewed in squirrelmail and
thunderbird and not outlook express
Description:
I have a few messages that are not seen in OE, althrow this are spam
messages, they could be regular messages and something important could be
lost.
So attach i have the OE log, i don't see no error info.
See if there's anything useful here, if not i'll try to get some more
other info.
Maybe the raw message will help?
Jorge
==
--
aaron - 23-Mar-07 02:16
--
Does this represent the message that cannot be seen in OE?
IMAP: 21:33:11 [rx] * 847 FETCH (INTERNALDATE 22-Mar-2007 18:10:10 +
RFC822.SIZE 5380 FLAGS (\Seen) UID 1021871 ENVELOPE (Thu, 22 Mar 2007
11:13:54 -0700 Re: [Dbmail] duplicate messages problem with outlook
((Aaron Stone NIL aaron serendipity.cx)) ((NIL NIL dbmail-bounces
dbmail.org)) ((DBMail mailinglist NIL dbmail dbmail.org))
((DBMail mailinglist NIL dbmail dbmail.org)) NIL NIL
[EMAIL PROTECTED]
[EMAIL PROTECTED]) BODY[HEADER.FIELDS (References
X-Ref X-Priority X-MSMail-Priority X-MSOESRec Newsgroups)] {92}
Also, why do you keep marking your bugs as private?
--
jasb - 23-Mar-07 10:21
--
Actualy, that message i can see it.
Well private... don't know :P please change it to public Aaron, i dont see
a place to change it.
The messages i cannot see, it's the 1st 10 (+-).
What type of info can i get you more?
--
jasb - 23-Mar-07 15:19
--
Hum... i have several messages that are not seen in OE, i was in
squirrelmail checking this, and for example, this messages does not appear
in OE, here's the full raw message:
Do you see anything strange here? this one is seen in thunderbird plus
squirrelmail, and not in OE.
Return-Path: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 29638 invoked from network); 2 Dec 2004 15:53:06 -
Received: from unknown (HELO exemplo.pt) (213.146.207.15)
by 0 with SMTP; 2 Dec 2004 15:53:06 -
Received: (qmail 3727 invoked by uid 0); 2 Mar 2004 14:56:35 -
Date: 2 Mar 2004 14:56:35 -
Message-ID: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
X-DBMail-PhysMessage-ID: 35634
criar uma tabela de cursos e acrescentar o campo para introduzir o mesmo,
depois criar uma listagem para puder tirar - listgem de forma
Issue History
Date Modified Username FieldChange
==
22-Mar-07 22:55 jasb New Issue
22-Mar-07 22:55 jasb File Added: Imap4.zip
22-Mar-07 22:55 jasb Issue Monitored: jasb
23-Mar-07 02:16 aaron Note Added: 0001943
23-Mar-07 10:21 jasb Note Added: 0001946
23-Mar-07 15:19 jasb Note Added: 0001955
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000550]: Messages that are viewed in squirrelmail and thunderbird and not outlook express
A NOTE has been added to this issue.
==
http://dbmail.org/mantis/view.php?id=550
==
Reported By:jasb
Assigned To:
==
Project:DBMail
Issue ID: 550
Category: IMAP daemon
Reproducibility:always
Severity: major
Priority: normal
Status: new
target:
==
Date Submitted: 22-Mar-07 22:55 CET
Last Modified: 23-Mar-07 15:29 CET
==
Summary:Messages that are viewed in squirrelmail and
thunderbird and not outlook express
Description:
I have a few messages that are not seen in OE, althrow this are spam
messages, they could be regular messages and something important could be
lost.
So attach i have the OE log, i don't see no error info.
See if there's anything useful here, if not i'll try to get some more
other info.
Maybe the raw message will help?
Jorge
==
--
aaron - 23-Mar-07 02:16
--
Does this represent the message that cannot be seen in OE?
IMAP: 21:33:11 [rx] * 847 FETCH (INTERNALDATE 22-Mar-2007 18:10:10 +
RFC822.SIZE 5380 FLAGS (\Seen) UID 1021871 ENVELOPE (Thu, 22 Mar 2007
11:13:54 -0700 Re: [Dbmail] duplicate messages problem with outlook
((Aaron Stone NIL aaron serendipity.cx)) ((NIL NIL dbmail-bounces
dbmail.org)) ((DBMail mailinglist NIL dbmail dbmail.org))
((DBMail mailinglist NIL dbmail dbmail.org)) NIL NIL
[EMAIL PROTECTED]
[EMAIL PROTECTED]) BODY[HEADER.FIELDS (References
X-Ref X-Priority X-MSMail-Priority X-MSOESRec Newsgroups)] {92}
Also, why do you keep marking your bugs as private?
--
jasb - 23-Mar-07 10:21
--
Actualy, that message i can see it.
Well private... don't know :P please change it to public Aaron, i dont see
a place to change it.
The messages i cannot see, it's the 1st 10 (+-).
What type of info can i get you more?
--
jasb - 23-Mar-07 15:19
--
Hum... i have several messages that are not seen in OE, i was in
squirrelmail checking this, and for example, this messages does not appear
in OE, here's the full raw message:
Do you see anything strange here? this one is seen in thunderbird plus
squirrelmail, and not in OE.
Return-Path: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 29638 invoked from network); 2 Dec 2004 15:53:06 -
Received: from unknown (HELO exemplo.pt) (213.146.207.15)
by 0 with SMTP; 2 Dec 2004 15:53:06 -
Received: (qmail 3727 invoked by uid 0); 2 Mar 2004 14:56:35 -
Date: 2 Mar 2004 14:56:35 -
Message-ID: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
X-DBMail-PhysMessage-ID: 35634
criar uma tabela de cursos e acrescentar o campo para introduzir o mesmo,
depois criar uma listagem para puder tirar - listgem de forma
--
jasb - 23-Mar-07 15:29
--
Hum... something was eated, compare the message body, i've attached this
in a file for you to see it right.
There's some bad chars, could it be this?
Anyway if it is this crazy chars, the correct is to see this on OE.
Issue History
Date Modified Username FieldChange
==
22-Mar-07 22:55 jasb New Issue
22-Mar-07 22:55 jasb File Added: Imap4.zip
22-Mar-07 22:55 jasb Issue Monitored: jasb
23-Mar-07 02:16 aaron Note Added: 0001943
23-Mar-07 10:21 jasb Note Added: 0001946
23-Mar-07 15:19 jasb Note Added: 0001955
23-Mar-07 15:29 jasb Note Added: 0001956
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] Possible minor memleaks in svn trunk 2474
Paul Aaron,
I was reviewing the current trunk 2474 from today, to see if I can help
make 2.2.5 bug free :) Anyway I came across some possible memleak issues
patch is attached. This is from valgrind I deduced the issues. Please
verify and apply to the trunk if you see fit.
Thanks,
Leif Jackson
diff -urN dbmail-svn-2.2.4-2474.orig/dbmail-message.c dbmail-svn-2.2.4-2474.new/dbmail-message.c
--- dbmail-svn-2.2.4-2474.orig/dbmail-message.c 2007-03-23 14:09:34.0 -0400
+++ dbmail-svn-2.2.4-2474.new/dbmail-message.c 2007-03-23 14:49:59.0 -0400
@@ -1109,6 +1109,7 @@
g_string_printf(q, INSERT INTO %s%sfield (id, physmessage_id, %sfield)
VALUES (%s, %llu,'%s'), DBPFX, field, field, id, physid, clean_value);
g_free(id);
+ g_free(sid);
g_free(clean_value);
if (db_query(q-str)) {
diff -urN dbmail-svn-2.2.4-2474.orig/imapd.c dbmail-svn-2.2.4-2474.new/imapd.c
--- dbmail-svn-2.2.4-2474.orig/imapd.c 2007-03-23 14:09:34.0 -0400
+++ dbmail-svn-2.2.4-2474.new/imapd.c 2007-03-23 16:59:46.0 -0400
@@ -40,6 +40,10 @@
g_mime_init(0);
openlog(PNAME, LOG_PID, LOG_MAIL);
+ //fixes valgrind Conditional jump or move depends on uninitialised value(s)
+ config.iplist = NULL;
+ config.listenSockets = NULL;
+
result = serverparent_getopt(config, IMAP, argc, argv);
if (result == -1)
goto shutdown;
diff -urN dbmail-svn-2.2.4-2474.orig/lmtpd.c dbmail-svn-2.2.4-2474.new/lmtpd.c
--- dbmail-svn-2.2.4-2474.orig/lmtpd.c 2007-03-23 14:09:33.0 -0400
+++ dbmail-svn-2.2.4-2474.new/lmtpd.c 2007-03-23 16:59:41.0 -0400
@@ -40,6 +40,10 @@
g_mime_init(0);
openlog(PNAME, LOG_PID, LOG_MAIL);
+ //fixes valgrind Conditional jump or move depends on uninitialised value(s)
+config.iplist = NULL;
+config.listenSockets = NULL;
+
result = serverparent_getopt(config, LMTP, argc, argv);
if (result == -1)
goto shutdown;
diff -urN dbmail-svn-2.2.4-2474.orig/misc.c dbmail-svn-2.2.4-2474.new/misc.c
--- dbmail-svn-2.2.4-2474.orig/misc.c 2007-03-23 14:09:34.0 -0400
+++ dbmail-svn-2.2.4-2474.new/misc.c 2007-03-23 16:58:04.0 -0400
@@ -2015,6 +2015,7 @@
}
if (subj==NULL) {
subj=g_mime_iconv_strdup(default_iconv,str_in);
+ g_mime_iconv_close(default_iconv);
}
if (subj==NULL) {
@@ -2036,6 +2037,7 @@
//char * str_out=NULL;
char * subj=NULL;
//int err_flg=1;
+ int allocated_default_iconv = 0;
static const char * base_charset=NULL;
static iconv_t base_iconv=(iconv_t)-1;
static iconv_t default_iconv=(iconv_t)-1;
@@ -2075,17 +2077,22 @@
if (default_iconv == (iconv_t)-1) {
TRACE(TRACE_DEBUG,incorrect default encoding [%s], default_charset);
}
+ allocated_default_iconv = 1;
}
- if (str_in==NULL)
+ if (str_in==NULL) {
+ if(allocated_default_iconv) g_mime_iconv_close(default_iconv);
return NULL;
+ }
if (!g_mime_utils_text_is_8bit((unsigned char *)str_in, strlen(str_in))) {
// Conversion not needed
+ if(allocated_default_iconv) g_mime_iconv_close(default_iconv);
return g_strdup(str_in);
}
if ((subj=g_mime_iconv_strdup(base_iconv,str_in))!=NULL) {
// Conversion already done by header decode ? May insert to database
+ if(allocated_default_iconv) g_mime_iconv_close(default_iconv);
return subj;
}
@@ -2117,6 +2124,9 @@
if(*p 0x80) *p='?';
}
+ if(allocated_default_iconv)
+ g_mime_iconv_close(default_iconv);
+
return subj;
}
diff -urN dbmail-svn-2.2.4-2474.orig/pop3d.c dbmail-svn-2.2.4-2474.new/pop3d.c
--- dbmail-svn-2.2.4-2474.orig/pop3d.c 2007-03-23 14:09:34.0 -0400
+++ dbmail-svn-2.2.4-2474.new/pop3d.c 2007-03-23 17:00:07.0 -0400
@@ -44,6 +44,10 @@
g_mime_init(0);
openlog(PNAME, LOG_PID, LOG_MAIL);
+//fixes valgrind Conditional jump or move depends on uninitialised value(s)
+config.iplist = NULL;
+config.listenSockets = NULL;
+
result = serverparent_getopt(config, POP, argc, argv);
if (result == -1)
goto shutdown;
diff -urN dbmail-svn-2.2.4-2474.orig/serverparent.c dbmail-svn-2.2.4-2474.new/serverparent.c
--- dbmail-svn-2.2.4-2474.orig/serverparent.c 2007-03-23 14:09:34.0 -0400
+++ dbmail-svn-2.2.4-2474.new/serverparent.c 2007-03-23 16:04:22.0 -0400
@@ -167,6 +167,7 @@
* e.g. on SIGHUP or other graceful restart condition. */
DoConfig(config, service); }
+ ClearConfig(config);
TRACE(TRACE_INFO, leaving main loop);
return 0;
}
diff -urN dbmail-svn-2.2.4-2474.orig/timsieved.c dbmail-svn-2.2.4-2474.new/timsieved.c
--- dbmail-svn-2.2.4-2474.orig/timsieved.c 2007-03-23 14:09:33.0 -0400
+++ dbmail-svn-2.2.4-2474.new/timsieved.c 2007-03-23 17:00:26.0 -0400
@@ -42,6 +42,10 @@
g_mime_init(0);
openlog(PNAME, LOG_PID, LOG_MAIL);
+//fixes valgrind Conditional jump or move depends on uninitialised value(s)
+config.iplist = NULL;
+config.listenSockets = NULL;
+
result = serverparent_getopt(config, SIEVE, argc, argv);
if (result == -1)
goto shutdown;
[Dbmail-dev] imapcommands.c again?
I just pulled a fresh copy to make sure that it wasn't me this time paul
but as I see it in trunk _ic_select in imapcommands.c
looks like this:
/* show idx of first unseen msg (if present) */
if (ud-mailbox.exists) {
if (! (key = db_first_unseen(ud-mailbox.uid))) {
dbmail_imap_session_printf(self, * BYE internal
dbase error\r\n);
return -1;
}
if ((msn = g_tree_lookup(self-mailbox-ids, key))) {
dbmail_imap_session_printf(self,
* OK [UNSEEN %llu] first unseen
message\r\n, *msn);
}
}
this re-introduces the issue with select all failing..etc as of 3/19
paul you showed they looked like:
The lines in svn look like this:
/* show idx of first unseen msg (if present) */
if (ud-mailbox.exists) { key = db_first_unseen(ud-mailbox.uid); if ( (key 0)
(msn =
g_tree_lookup(self-mailbox-ids, key))) {
dbmail_imap_session_printf(self, * OK [UNSEEN %llu] first unseen
message\r\n, *msn); }
}
any ideas?
Thanks,
leif
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
Re: [Dbmail-dev] Possible minor memleaks in svn trunk 2474
Nice work, now in SVN, except for the changes to dbmail-message.c which Paul appears to have already incorportated into renamed variables. Aaron On Fri, 2007-03-23 at 17:12 -0500, Leif Jackson wrote: Paul Aaron, I was reviewing the current trunk 2474 from today, to see if I can help make 2.2.5 bug free :) Anyway I came across some possible memleak issues patch is attached. This is from valgrind I deduced the issues. Please verify and apply to the trunk if you see fit. Thanks, Leif Jackson ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
