Nabble - DBMail

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T15:48:27Z

A NOTE has been added to this issue.
======================================================================
http://www.dbmail.org/mantis/view.php?id=736
======================================================================
Reported By: niki
Assigned To: netvulture
======================================================================
Project: DBMail
Issue ID: 736
Category: Database layer
Reproducibility: always
Severity: block
Priority: normal
Status: acknowledged
target:
======================================================================
Date Submitted: 20-Nov-08 22:08 CET
Last Modified: 21-Nov-08 00:48 CET
======================================================================
Summary: DBMail consuming db connections, and stops
responding
Description:
Just updated DBMail to 2.3.4 "official" dbmail experimental

When I connect with Evo, dbmail starts to consume connections up until 32
(have configred it to to max 50) while logging some db errors, after it
has stopped at 32 db connections it, I can still filter a couple of ails
into folders before it dops all connections to the db.

Lmtp is still running fine.
The db is Postgres 8.3.3 (Debian)
======================================================================

----------------------------------------------------------------------
niki - 20-Nov-08 22:38
----------------------------------------------------------------------
Her is a log with log level 128

----------------------------------------------------------------------
netvulture - 20-Nov-08 22:45
----------------------------------------------------------------------
Can you please post the new log using these settings.

FILE_LOGGING_LEVELS = 511
errorlog = /path/to/log/file

Your last log file only said SQLException: a bunch of times. Syslog
probably cut off the messages.

Also, is your database running on the same box, or a different host? If
over the network, describe the connection (10? 100? 1000? mbit LAN, or
other?).
How many connections is your db server set to handle? Try setting it to
150 using max_connections(150) in the db config file.

----------------------------------------------------------------------
niki - 20-Nov-08 22:56
----------------------------------------------------------------------
The 2nd file I uploaded is a copy of the dbmail error log at loglevel 128
(dbmail-2.err.bz2), but I'll get you a copy of the same file at log leve
511 in a sec, I'll just answer a couple of you questions first.

Postgres is running on a dedicated host, right next to the mail server,
connected via an ethernet switch (all of it is 100M), and the dbmail user
is set to have no connection limit in Postgres.

----------------------------------------------------------------------
niki - 20-Nov-08 23:20
----------------------------------------------------------------------
Here is the log at loglevel 511, and max connections set to 150.

When Evo connects, dbmail starts to consume connections again, and it
still stops at 32 connections, when it's done I can manually do 5
successful filter actions, when I hit Ctrl+y the 6th time, Evo returns
with an error saying it couldn't complete the action.

http://www.guldbrand.net/dbmail-3.err.bz2

----------------------------------------------------------------------
paul - 20-Nov-08 23:34
----------------------------------------------------------------------
this smell very much like a libzdb buglet.
Could you please test the attached patch?

----------------------------------------------------------------------
niki - 20-Nov-08 23:40
----------------------------------------------------------------------
I will, but I don't have that mutch experience with debian package
building, stay tuned.

----------------------------------------------------------------------
netvulture - 20-Nov-08 23:43
----------------------------------------------------------------------
I was wanting you to make sure that your database server was setup to
handle 150 connections. max_db_connections in dbmail.conf should be
something like 20 or 25. IDLE clients will use the excess connections. If
you have trouble with log entries saying could get a db connection, try
[5] with a lot of active clients. Then increase this by about 5 at a time
until it goes away.

----------------------------------------------------------------------
netvulture - 21-Nov-08 00:48
----------------------------------------------------------------------
>From my initial look at it. There are 30 database connections not closed
for this single client connection.

>From the count of commands issued, log
http://www.dbmail.org/mantis/view.php?id=3 shows 23 UID commands. During a
UID COPY I did see some db_con_clear double ups.

Issue History
Date Modified Username Field Change
======================================================================
20-Nov-08 22:08 niki New Issue
20-Nov-08 22:08 niki File Added: dbmail-1.log
20-Nov-08 22:38 niki Note Added: 0002636
20-Nov-08 22:38 niki File Added: dbmail-2.err.bz2
20-Nov-08 22:45 netvulture Note Added: 0002637
20-Nov-08 22:45 netvulture Assigned To => netvulture
20-Nov-08 22:45 netvulture Status new => acknowledged
20-Nov-08 22:56 niki Note Added: 0002638
20-Nov-08 23:20 niki Note Added: 0002639
20-Nov-08 23:34 paul Note Added: 0002640
20-Nov-08 23:35 paul File Added:
0001-workaround-connection-leakage.patch
20-Nov-08 23:40 niki Note Added: 0002641
20-Nov-08 23:43 netvulture Note Added: 0002642
21-Nov-08 00:48 netvulture Note Added: 0002643
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T14:43:53Z

A NOTE has been added to this issue.
======================================================================
http://www.dbmail.org/mantis/view.php?id=736
======================================================================
Reported By: niki
Assigned To: netvulture
======================================================================
Project: DBMail
Issue ID: 736
Category: Database layer
Reproducibility: always
Severity: block
Priority: normal
Status: acknowledged
target:
======================================================================
Date Submitted: 20-Nov-08 22:08 CET
Last Modified: 20-Nov-08 23:43 CET
======================================================================
Summary: DBMail consuming db connections, and stops
responding
Description:
Just updated DBMail to 2.3.4 "official" dbmail experimental

When I connect with Evo, dbmail starts to consume connections up until 32
(have configred it to to max 50) while logging some db errors, after it
has stopped at 32 db connections it, I can still filter a couple of ails
into folders before it dops all connections to the db.

Lmtp is still running fine.
The db is Postgres 8.3.3 (Debian)
======================================================================

----------------------------------------------------------------------
niki - 20-Nov-08 22:38
----------------------------------------------------------------------
Her is a log with log level 128

----------------------------------------------------------------------
netvulture - 20-Nov-08 22:45
----------------------------------------------------------------------
Can you please post the new log using these settings.

FILE_LOGGING_LEVELS = 511
errorlog = /path/to/log/file

Your last log file only said SQLException: a bunch of times. Syslog
probably cut off the messages.

Also, is your database running on the same box, or a different host? If
over the network, describe the connection (10? 100? 1000? mbit LAN, or
other?).
How many connections is your db server set to handle? Try setting it to
150 using max_connections(150) in the db config file.

----------------------------------------------------------------------
niki - 20-Nov-08 22:56
----------------------------------------------------------------------
The 2nd file I uploaded is a copy of the dbmail error log at loglevel 128
(dbmail-2.err.bz2), but I'll get you a copy of the same file at log leve
511 in a sec, I'll just answer a couple of you questions first.

Postgres is running on a dedicated host, right next to the mail server,
connected via an ethernet switch (all of it is 100M), and the dbmail user
is set to have no connection limit in Postgres.

----------------------------------------------------------------------
niki - 20-Nov-08 23:20
----------------------------------------------------------------------
Here is the log at loglevel 511, and max connections set to 150.

When Evo connects, dbmail starts to consume connections again, and it
still stops at 32 connections, when it's done I can manually do 5
successful filter actions, when I hit Ctrl+y the 6th time, Evo returns
with an error saying it couldn't complete the action.

http://www.guldbrand.net/dbmail-3.err.bz2

----------------------------------------------------------------------
paul - 20-Nov-08 23:34
----------------------------------------------------------------------
this smell very much like a libzdb buglet.
Could you please test the attached patch?

----------------------------------------------------------------------
niki - 20-Nov-08 23:40
----------------------------------------------------------------------
I will, but I don't have that mutch experience with debian package
building, stay tuned.

----------------------------------------------------------------------
netvulture - 20-Nov-08 23:43
----------------------------------------------------------------------
I was wanting you to make sure that your database server was setup to
handle 150 connections. max_db_connections in dbmail.conf should be
something like 20 or 25. IDLE clients will use the excess connections. If
you have trouble with log entries saying could get a db connection, try
[5] with a lot of active clients. Then increase this by about 5 at a time
until it goes away.

Issue History
Date Modified Username Field Change
======================================================================
20-Nov-08 22:08 niki New Issue
20-Nov-08 22:08 niki File Added: dbmail-1.log
20-Nov-08 22:38 niki Note Added: 0002636
20-Nov-08 22:38 niki File Added: dbmail-2.err.bz2
20-Nov-08 22:45 netvulture Note Added: 0002637
20-Nov-08 22:45 netvulture Assigned To => netvulture
20-Nov-08 22:45 netvulture Status new => acknowledged
20-Nov-08 22:56 niki Note Added: 0002638
20-Nov-08 23:20 niki Note Added: 0002639
20-Nov-08 23:34 paul Note Added: 0002640
20-Nov-08 23:35 paul File Added:
0001-workaround-connection-leakage.patch
20-Nov-08 23:40 niki Note Added: 0002641
20-Nov-08 23:43 netvulture Note Added: 0002642
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T14:40:04Z

A NOTE has been added to this issue.
======================================================================
http://www.dbmail.org/mantis/view.php?id=736
======================================================================
Reported By: niki
Assigned To: netvulture
======================================================================
Project: DBMail
Issue ID: 736
Category: Database layer
Reproducibility: always
Severity: block
Priority: normal
Status: acknowledged
target:
======================================================================
Date Submitted: 20-Nov-08 22:08 CET
Last Modified: 20-Nov-08 23:40 CET
======================================================================
Summary: DBMail consuming db connections, and stops
responding
Description:
Just updated DBMail to 2.3.4 "official" dbmail experimental

When I connect with Evo, dbmail starts to consume connections up until 32
(have configred it to to max 50) while logging some db errors, after it
has stopped at 32 db connections it, I can still filter a couple of ails
into folders before it dops all connections to the db.

Lmtp is still running fine.
The db is Postgres 8.3.3 (Debian)
======================================================================

----------------------------------------------------------------------
niki - 20-Nov-08 22:38
----------------------------------------------------------------------
Her is a log with log level 128

----------------------------------------------------------------------
netvulture - 20-Nov-08 22:45
----------------------------------------------------------------------
Can you please post the new log using these settings.

FILE_LOGGING_LEVELS = 511
errorlog = /path/to/log/file

Your last log file only said SQLException: a bunch of times. Syslog
probably cut off the messages.

Also, is your database running on the same box, or a different host? If
over the network, describe the connection (10? 100? 1000? mbit LAN, or
other?).
How many connections is your db server set to handle? Try setting it to
150 using max_connections(150) in the db config file.

----------------------------------------------------------------------
niki - 20-Nov-08 22:56
----------------------------------------------------------------------
The 2nd file I uploaded is a copy of the dbmail error log at loglevel 128
(dbmail-2.err.bz2), but I'll get you a copy of the same file at log leve
511 in a sec, I'll just answer a couple of you questions first.

Postgres is running on a dedicated host, right next to the mail server,
connected via an ethernet switch (all of it is 100M), and the dbmail user
is set to have no connection limit in Postgres.

----------------------------------------------------------------------
niki - 20-Nov-08 23:20
----------------------------------------------------------------------
Here is the log at loglevel 511, and max connections set to 150.

When Evo connects, dbmail starts to consume connections again, and it
still stops at 32 connections, when it's done I can manually do 5
successful filter actions, when I hit Ctrl+y the 6th time, Evo returns
with an error saying it couldn't complete the action.

http://www.guldbrand.net/dbmail-3.err.bz2

----------------------------------------------------------------------
paul - 20-Nov-08 23:34
----------------------------------------------------------------------
this smell very much like a libzdb buglet.
Could you please test the attached patch?

----------------------------------------------------------------------
niki - 20-Nov-08 23:40
----------------------------------------------------------------------
I will, but I don't have that mutch experience with debian package
building, stay tuned.

Issue History
Date Modified Username Field Change
======================================================================
20-Nov-08 22:08 niki New Issue
20-Nov-08 22:08 niki File Added: dbmail-1.log
20-Nov-08 22:38 niki Note Added: 0002636
20-Nov-08 22:38 niki File Added: dbmail-2.err.bz2
20-Nov-08 22:45 netvulture Note Added: 0002637
20-Nov-08 22:45 netvulture Assigned To => netvulture
20-Nov-08 22:45 netvulture Status new => acknowledged
20-Nov-08 22:56 niki Note Added: 0002638
20-Nov-08 23:20 niki Note Added: 0002639
20-Nov-08 23:34 paul Note Added: 0002640
20-Nov-08 23:35 paul File Added:
0001-workaround-connection-leakage.patch
20-Nov-08 23:40 niki Note Added: 0002641
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T14:34:57Z

A NOTE has been added to this issue.
======================================================================
http://www.dbmail.org/mantis/view.php?id=736
======================================================================
Reported By: niki
Assigned To: netvulture
======================================================================
Project: DBMail
Issue ID: 736
Category: Database layer
Reproducibility: always
Severity: block
Priority: normal
Status: acknowledged
target:
======================================================================
Date Submitted: 20-Nov-08 22:08 CET
Last Modified: 20-Nov-08 23:34 CET
======================================================================
Summary: DBMail consuming db connections, and stops
responding
Description:
Just updated DBMail to 2.3.4 "official" dbmail experimental

When I connect with Evo, dbmail starts to consume connections up until 32
(have configred it to to max 50) while logging some db errors, after it
has stopped at 32 db connections it, I can still filter a couple of ails
into folders before it dops all connections to the db.

Lmtp is still running fine.
The db is Postgres 8.3.3 (Debian)
======================================================================

----------------------------------------------------------------------
niki - 20-Nov-08 22:38
----------------------------------------------------------------------
Her is a log with log level 128

----------------------------------------------------------------------
netvulture - 20-Nov-08 22:45
----------------------------------------------------------------------
Can you please post the new log using these settings.

FILE_LOGGING_LEVELS = 511
errorlog = /path/to/log/file

Your last log file only said SQLException: a bunch of times. Syslog
probably cut off the messages.

Also, is your database running on the same box, or a different host? If
over the network, describe the connection (10? 100? 1000? mbit LAN, or
other?).
How many connections is your db server set to handle? Try setting it to
150 using max_connections(150) in the db config file.

----------------------------------------------------------------------
niki - 20-Nov-08 22:56
----------------------------------------------------------------------
The 2nd file I uploaded is a copy of the dbmail error log at loglevel 128
(dbmail-2.err.bz2), but I'll get you a copy of the same file at log leve
511 in a sec, I'll just answer a couple of you questions first.

Postgres is running on a dedicated host, right next to the mail server,
connected via an ethernet switch (all of it is 100M), and the dbmail user
is set to have no connection limit in Postgres.

----------------------------------------------------------------------
niki - 20-Nov-08 23:20
----------------------------------------------------------------------
Here is the log at loglevel 511, and max connections set to 150.

When Evo connects, dbmail starts to consume connections again, and it
still stops at 32 connections, when it's done I can manually do 5
successful filter actions, when I hit Ctrl+y the 6th time, Evo returns
with an error saying it couldn't complete the action.

http://www.guldbrand.net/dbmail-3.err.bz2

----------------------------------------------------------------------
paul - 20-Nov-08 23:34
----------------------------------------------------------------------
this smell very much like a libzdb buglet.
Could you please test the attached patch?

Issue History
Date Modified Username Field Change
======================================================================
20-Nov-08 22:08 niki New Issue
20-Nov-08 22:08 niki File Added: dbmail-1.log
20-Nov-08 22:38 niki Note Added: 0002636
20-Nov-08 22:38 niki File Added: dbmail-2.err.bz2
20-Nov-08 22:45 netvulture Note Added: 0002637
20-Nov-08 22:45 netvulture Assigned To => netvulture
20-Nov-08 22:45 netvulture Status new => acknowledged
20-Nov-08 22:56 niki Note Added: 0002638
20-Nov-08 23:20 niki Note Added: 0002639
20-Nov-08 23:34 paul Note Added: 0002640
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T14:20:45Z

From forum: dbmail dev

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T13:56:11Z

From forum: dbmail dev

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T13:45:19Z

The following issue has been ACKNOWLEDGED.
======================================================================
http://www.dbmail.org/mantis/view.php?id=736
======================================================================
Reported By: niki
Assigned To: netvulture
======================================================================
Project: DBMail
Issue ID: 736
Category: Database layer
Reproducibility: always
Severity: block
Priority: normal
Status: acknowledged
target:
======================================================================
Date Submitted: 20-Nov-08 22:08 CET
Last Modified: 20-Nov-08 22:45 CET
======================================================================
Summary: DBMail consuming db connections, and stops
responding
Description:
Just updated DBMail to 2.3.4 "official" dbmail experimental

When I connect with Evo, dbmail starts to consume connections up until 32
(have configred it to to max 50) while logging some db errors, after it
has stopped at 32 db connections it, I can still filter a couple of ails
into folders before it dops all connections to the db.

Lmtp is still running fine.
The db is Postgres 8.3.3 (Debian)
======================================================================

----------------------------------------------------------------------
niki - 20-Nov-08 22:38
----------------------------------------------------------------------
Her is a log with log level 128

----------------------------------------------------------------------
netvulture - 20-Nov-08 22:45
----------------------------------------------------------------------
Can you please post the new log using these settings.

FILE_LOGGING_LEVELS = 511
errorlog = /path/to/log/file

Your last log file only said SQLException: a bunch of times. Syslog
probably cut off the messages.

Also, is your database running on the same box, or a different host? If
over the network, describe the connection (10? 100? 1000? mbit LAN, or
other?).
How many connections is your db server set to handle? Try setting it to
150 using max_connections(150) in the db config file.

Issue History
Date Modified Username Field Change
======================================================================
20-Nov-08 22:08 niki New Issue
20-Nov-08 22:08 niki File Added: dbmail-1.log
20-Nov-08 22:38 niki Note Added: 0002636
20-Nov-08 22:38 niki File Added: dbmail-2.err.bz2
20-Nov-08 22:45 netvulture Note Added: 0002637
20-Nov-08 22:45 netvulture Assigned To => netvulture
20-Nov-08 22:45 netvulture Status new => acknowledged
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T13:38:07Z

From forum: dbmail dev

[DBMail 0000736]: DBMail consuming db connections, and stops responding

2008-11-20T13:08:11Z

The following issue has been SUBMITTED.
======================================================================
http://www.dbmail.org/mantis/view.php?id=736
======================================================================
Reported By: niki
Assigned To:
======================================================================
Project: DBMail
Issue ID: 736
Category: Database layer
Reproducibility: always
Severity: block
Priority: normal
Status: new
target:
======================================================================
Date Submitted: 20-Nov-08 22:08 CET
Last Modified: 20-Nov-08 22:08 CET
======================================================================
Summary: DBMail consuming db connections, and stops
responding
Description:
Just updated DBMail to 2.3.4 "official" dbmail experimental

When I connect with Evo, dbmail starts to consume connections up until 32
(have configred it to to max 50) while logging some db errors, after it
has stopped at 32 db connections it, I can still filter a couple of ails
into folders before it dops all connections to the db.

Lmtp is still running fine.
The db is Postgres 8.3.3 (Debian)
======================================================================

Issue History
Date Modified Username Field Change
======================================================================
20-Nov-08 22:08 niki New Issue
20-Nov-08 22:08 niki File Added: dbmail-1.log
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000735]: wrong message count in IDLE mode

2008-11-20T06:34:30Z

The following issue has been CLOSED
======================================================================
http://www.dbmail.org/mantis/view.php?id=735
======================================================================
Reported By: dirixmjm
Assigned To:
======================================================================
Project: DBMail
Issue ID: 735
Category: IMAP daemon
Reproducibility: always
Severity: trivial
Priority: normal
Status: closed
target:
Resolution: no change required
Fixed in Version:
======================================================================
Date Submitted: 20-Nov-08 15:12 CET
Last Modified: 20-Nov-08 15:34 CET
======================================================================
Summary: wrong message count in IDLE mode
Description:
Hi,

I'm not 100% sure if I misunderstood the RFC. But I think this is a bug.
If I have 2 IMAP clients of which one uses IDLE, and the other deletes
messages. If the second client deletes multiple messages i.e. message 1
and 7 the IDLE client receives:
* 1 EXPUNGE
* 7 EXPUNGE
Which looks ok. Now if the other client deletes messages 14, 13 and 12 the
IDLE client receives:
* 12 EXPUNGE
* 12 EXPUNGE
* 12 EXPUNGE

Is this right? Should not 14, 13 and 12 be listed?
======================================================================

----------------------------------------------------------------------
paul - 20-Nov-08 15:34
----------------------------------------------------------------------

Actually it's the first response that is broken, not the latter.

This is all fixed in 2.3.x

please read:
http://tools.ietf.org/html/rfc3501#section-7.4.1
for more information.

Issue History
Date Modified Username Field Change
======================================================================
20-Nov-08 15:12 dirixmjm New Issue
20-Nov-08 15:34 paul Note Added: 0002635
20-Nov-08 15:34 paul Status new => closed
20-Nov-08 15:34 paul Resolution open => no change
required
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000735]: wrong message count in IDLE mode

2008-11-20T06:12:13Z

The following issue has been SUBMITTED.
======================================================================
http://www.dbmail.org/mantis/view.php?id=735
======================================================================
Reported By: dirixmjm
Assigned To:
======================================================================
Project: DBMail
Issue ID: 735
Category: IMAP daemon
Reproducibility: always
Severity: trivial
Priority: normal
Status: new
target:
======================================================================
Date Submitted: 20-Nov-08 15:12 CET
Last Modified: 20-Nov-08 15:12 CET
======================================================================
Summary: wrong message count in IDLE mode
Description:
Hi,

I'm not 100% sure if I misunderstood the RFC. But I think this is a bug.
If I have 2 IMAP clients of which one uses IDLE, and the other deletes
messages. If the second client deletes multiple messages i.e. message 1
and 7 the IDLE client receives:
* 1 EXPUNGE
* 7 EXPUNGE
Which looks ok. Now if the other client deletes messages 14, 13 and 12 the
IDLE client receives:
* 12 EXPUNGE
* 12 EXPUNGE
* 12 EXPUNGE

Is this right? Should not 14, 13 and 12 be listed?
======================================================================

Issue History
Date Modified Username Field Change
======================================================================
20-Nov-08 15:12 dirixmjm New Issue
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000734]: SEgfault when pop-ing emails from THunderbird

2008-11-20T03:37:58Z

A NOTE has been added to this issue.
======================================================================
http://www.dbmail.org/mantis/view.php?id=734
======================================================================
Reported By: grosjo
Assigned To: paul
======================================================================
Project: DBMail
Issue ID: 734
Category: POP3 daemon
Reproducibility: always
Severity: crash
Priority: normal
Status: acknowledged
target:
======================================================================
Date Submitted: 19-Nov-08 17:49 CET
Last Modified: 20-Nov-08 12:37 CET
======================================================================
Summary: SEgfault when pop-ing emails from THunderbird
Description:

dbmail2.3.4 pop3d gives me:

dbmail-pop3d[20593]: segfault at 0 ip 00007f70f0c5b010 sp 00007ffffa798a00
error 4 in libdbmail.so.0.0.0[7f70f0c47000+55000]

(linux 2.6.27.5, Mysql 5.1.29)

======================================================================

----------------------------------------------------------------------
grosjo - 19-Nov-08 21:12
----------------------------------------------------------------------
Additional info:

Testing from the console (telnet localhost 110)

dbmail-pop3d crash (segfault) when downloading (RETR xx) an email which is
not in INBOX but in a subdirectory INBOX/blabla (i.e. an IMAP-created
folder)

----------------------------------------------------------------------
grosjo - 20-Nov-08 07:35
----------------------------------------------------------------------
Switiching back to 2.3.3 solve the issue.

So, this is a regression in 2.3.4

----------------------------------------------------------------------
paul - 20-Nov-08 08:55
----------------------------------------------------------------------
Using pop3 you should never be able to access any mailbox other than INBOX,
so what is going on here?
Other than that, segfaults should never happen. I'll look into it.

----------------------------------------------------------------------
paul - 20-Nov-08 12:37
----------------------------------------------------------------------
Please provide logs with
SYSLOG_LOGGING_LEVELS=511

Issue History
Date Modified Username Field Change
======================================================================
19-Nov-08 17:49 grosjo New Issue
19-Nov-08 21:12 grosjo Note Added: 0002629
19-Nov-08 21:23 grosjo Issue Monitored: grosjo
20-Nov-08 07:35 grosjo Note Added: 0002632
20-Nov-08 08:55 paul Note Added: 0002633
20-Nov-08 08:55 paul Status new => assigned
20-Nov-08 08:55 paul Assigned To => paul
20-Nov-08 08:55 paul Status assigned => acknowledged
20-Nov-08 12:37 paul Note Added: 0002634
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

Re: Re: [DBMail 0000719]: Patch to enable SQL auth with other hash algorithms

2008-11-20T02:48:35Z

Indeed. No change in ldap is *required*. But currently using
dbmail-users to manage ldap passwords will result in cleartext passwords
being stored in ldap. It should be trivial to use ldap_passwd_s rather
than ldap_modify_s, but I can't get it to work properly: the password is
changed, but I can't validate the result.

Aaron Stone wrote:

> I see no problem enabling additional hashes for SQL auth that are not
> supported on LDAP auth. We would simply need to document this.
>
> Aaron
>
>
> On Wed, 2008-11-19 at 15:08 -0800, Daniel Bakken wrote:
>> Problems which make mhash support difficult to implement for LDAP:
>>
>> Currently the authldap module verifies passwords by binding to the
>> LDAP server as the user. This would be problematic since LDAP doesn't
>> support all the mhash algorithms. We would also have to add a "hash
>> type" attribute to the LDAP schema unless we prepend the hash type to
>> the password, e.g. userPassword="{WHIRLPOOL}..." which would break
>> LDAP standards.
>>
>> I welcome thoughts on how best to do this without breaking standards,
>> or if it's even worthwhile to attempt.
>>
>> Daniel Bakken
>> www.populiweb.com
>>
>>
>> On Wed, Nov 19, 2008 at 12:20 PM, <bugtrack@...> wrote:
>>> ----------------------------------------------------------------------
>>> paul - 19-Nov-08 21:20
>>> ----------------------------------------------------------------------
>>>
>>> Patch merged. Thanks.
>>>
>>> If you could look into ldap that would be great. The required change
>>> should be trivial: use ldap_passwd instead of ldap_modify as is currently
>>> the case.
>> _______________________________________________
>> Dbmail-dev mailing list
>> Dbmail-dev@...
>> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@...
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>

--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000734]: SEgfault when pop-ing emails from THunderbird

2008-11-19T23:55:56Z

The following issue has been ACKNOWLEDGED.
======================================================================
http://www.dbmail.org/mantis/view.php?id=734
======================================================================
Reported By: grosjo
Assigned To: paul
======================================================================
Project: DBMail
Issue ID: 734
Category: POP3 daemon
Reproducibility: always
Severity: crash
Priority: normal
Status: acknowledged
target:
======================================================================
Date Submitted: 19-Nov-08 17:49 CET
Last Modified: 20-Nov-08 08:55 CET
======================================================================
Summary: SEgfault when pop-ing emails from THunderbird
Description:

dbmail2.3.4 pop3d gives me:

dbmail-pop3d[20593]: segfault at 0 ip 00007f70f0c5b010 sp 00007ffffa798a00
error 4 in libdbmail.so.0.0.0[7f70f0c47000+55000]

(linux 2.6.27.5, Mysql 5.1.29)

======================================================================

----------------------------------------------------------------------
grosjo - 19-Nov-08 21:12
----------------------------------------------------------------------
Additional info:

Testing from the console (telnet localhost 110)

dbmail-pop3d crash (segfault) when downloading (RETR xx) an email which is
not in INBOX but in a subdirectory INBOX/blabla (i.e. an IMAP-created
folder)

----------------------------------------------------------------------
grosjo - 20-Nov-08 07:35
----------------------------------------------------------------------
Switiching back to 2.3.3 solve the issue.

So, this is a regression in 2.3.4

----------------------------------------------------------------------
paul - 20-Nov-08 08:55
----------------------------------------------------------------------
Using pop3 you should never be able to access any mailbox other than INBOX,
so what is going on here?
Other than that, segfaults should never happen. I'll look into it.

Issue History
Date Modified Username Field Change
======================================================================
19-Nov-08 17:49 grosjo New Issue
19-Nov-08 21:12 grosjo Note Added: 0002629
19-Nov-08 21:23 grosjo Issue Monitored: grosjo
20-Nov-08 07:35 grosjo Note Added: 0002632
20-Nov-08 08:55 paul Note Added: 0002633
20-Nov-08 08:55 paul Status new => assigned
20-Nov-08 08:55 paul Assigned To => paul
20-Nov-08 08:55 paul Status assigned => acknowledged
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000734]: SEgfault when pop-ing emails from THunderbird

2008-11-19T23:55:40Z

The following issue has been ASSIGNED.
======================================================================
http://www.dbmail.org/mantis/view.php?id=734
======================================================================
Reported By: grosjo
Assigned To: paul
======================================================================
Project: DBMail
Issue ID: 734
Category: POP3 daemon
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
target:
======================================================================
Date Submitted: 19-Nov-08 17:49 CET
Last Modified: 20-Nov-08 08:55 CET
======================================================================
Summary: SEgfault when pop-ing emails from THunderbird
Description:

dbmail2.3.4 pop3d gives me:

dbmail-pop3d[20593]: segfault at 0 ip 00007f70f0c5b010 sp 00007ffffa798a00
error 4 in libdbmail.so.0.0.0[7f70f0c47000+55000]

(linux 2.6.27.5, Mysql 5.1.29)

======================================================================

----------------------------------------------------------------------
grosjo - 19-Nov-08 21:12
----------------------------------------------------------------------
Additional info:

Testing from the console (telnet localhost 110)

dbmail-pop3d crash (segfault) when downloading (RETR xx) an email which is
not in INBOX but in a subdirectory INBOX/blabla (i.e. an IMAP-created
folder)

----------------------------------------------------------------------
grosjo - 20-Nov-08 07:35
----------------------------------------------------------------------
Switiching back to 2.3.3 solve the issue.

So, this is a regression in 2.3.4

----------------------------------------------------------------------
paul - 20-Nov-08 08:55
----------------------------------------------------------------------
Using pop3 you should never be able to access any mailbox other than INBOX,
so what is going on here?
Other than that, segfaults should never happen. I'll look into it.

Issue History
Date Modified Username Field Change
======================================================================
19-Nov-08 17:49 grosjo New Issue
19-Nov-08 21:12 grosjo Note Added: 0002629
19-Nov-08 21:23 grosjo Issue Monitored: grosjo
20-Nov-08 07:35 grosjo Note Added: 0002632
20-Nov-08 08:55 paul Note Added: 0002633
20-Nov-08 08:55 paul Status new => assigned
20-Nov-08 08:55 paul Assigned To => paul
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev

[DBMail 0000734]: SEgfault when pop-ing emails from THunderbird

2008-11-19T23:55:35Z

A NOTE has been added to this issue.
======================================================================
http://www.dbmail.org/mantis/view.php?id=734
======================================================================
Reported By: grosjo
Assigned To:
======================================================================
Project: DBMail
Issue ID: 734
Category: POP3 daemon
Reproducibility: always
Severity: crash
Priority: normal
Status: new
target:
======================================================================
Date Submitted: 19-Nov-08 17:49 CET
Last Modified: 20-Nov-08 08:55 CET
======================================================================
Summary: SEgfault when pop-ing emails from THunderbird
Description:

dbmail2.3.4 pop3d gives me:

dbmail-pop3d[20593]: segfault at 0 ip 00007f70f0c5b010 sp 00007ffffa798a00
error 4 in libdbmail.so.0.0.0[7f70f0c47000+55000]

(linux 2.6.27.5, Mysql 5.1.29)

======================================================================

----------------------------------------------------------------------
grosjo - 19-Nov-08 21:12
----------------------------------------------------------------------
Additional info:

Testing from the console (telnet localhost 110)

dbmail-pop3d crash (segfault) when downloading (RETR xx) an email which is
not in INBOX but in a subdirectory INBOX/blabla (i.e. an IMAP-created
folder)

----------------------------------------------------------------------
grosjo - 20-Nov-08 07:35
----------------------------------------------------------------------
Switiching back to 2.3.3 solve the issue.

So, this is a regression in 2.3.4

----------------------------------------------------------------------
paul - 20-Nov-08 08:55
----------------------------------------------------------------------
Using pop3 you should never be able to access any mailbox other than INBOX,
so what is going on here?
Other than that, segfaults should never happen. I'll look into it.

Issue History
Date Modified Username Field Change
======================================================================
19-Nov-08 17:49 grosjo New Issue
19-Nov-08 21:12 grosjo Note Added: 0002629
19-Nov-08 21:23 grosjo Issue Monitored: grosjo
20-Nov-08 07:35 grosjo Note Added: 0002632
20-Nov-08 08:55 paul Note Added: 0002633
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@...
http://twister.fastxs.net/mailman/listinfo/dbmail-dev

From forum: dbmail dev