[Dbmail-dev] [DBMail 0000792]: Lock timeout on lmtpd message insertation during nightly dbmail-util
The following issue has been SUBMITTED. == http://dbmail.org/mantis/view.php?id=792 == Reported By:jasb Assigned To: == Project:DBMail Issue ID: 792 Category: LMTP daemon Reproducibility:have not tried Severity: major Priority: normal Status: new target: == Date Submitted: 24-Jul-09 10:24 CEST Last Modified: 24-Jul-09 10:24 CEST == Summary:Lock timeout on lmtpd message insertation during nightly dbmail-util Description: Hi, During the nightly dbmail-util, when it is running, new messages wont get in. My question is: i believe they don't really get inserted, i ask, are the transaction really being restarted/were this messages really delivered? Log of lmtpd below. == Issue History Date ModifiedUsername FieldChange == 24-Jul-09 10:24 jasb New Issue == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000792]: Lock timeout on lmtpd message insertation during nightly dbmail-util
A NOTE has been added to this issue. == http://dbmail.org/mantis/view.php?id=792 == Reported By:jasb Assigned To: == Project:DBMail Issue ID: 792 Category: LMTP daemon Reproducibility:have not tried Severity: major Priority: normal Status: new target: == Date Submitted: 24-Jul-09 10:24 CEST Last Modified: 24-Jul-09 19:01 CEST == Summary:Lock timeout on lmtpd message insertation during nightly dbmail-util Description: Hi, During the nightly dbmail-util, when it is running, new messages wont get in. My question is: i believe they don't really get inserted, i ask, are the transaction really being restarted/were this messages really delivered? Log of lmtpd below. == -- (0002842) netvulture (developer) - 24-Jul-09 19:01 http://dbmail.org/mantis/view.php?id=792#c2842 -- From the logs, it would appear that you are running a partlists cleanup operation when the message came in. I am not sure if the query was successfully canceled or did finally go through when the partlists table was unlocked. If you use the filelog version of these lines, you should be able to see the phymessage_id it was for, and then do a select * from dbmail_partlists where phymessage_id=x; If you see the part_* that were trying to be inserted, then they were, however with out more of the log I couldn't tell you if the message failed for insertion and returned an error to the MTA or not. Issue History Date ModifiedUsername FieldChange == 24-Jul-09 10:24 jasb New Issue 24-Jul-09 19:01 netvulture Note Added: 0002842 == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000786]: Fields DATE/INTERNALDATE have wrong timezone
The following issue has been ASSIGNED.
==
http://dbmail.org/mantis/view.php?id=786
==
Reported By:idk
Assigned To:netvulture
==
Project:DBMail
Issue ID: 786
Category: IMAP daemon
Reproducibility:always
Severity: minor
Priority: normal
Status: assigned
target:
==
Date Submitted: 01-Jul-09 15:01 CEST
Last Modified: 24-Jul-09 19:06 CEST
==
Summary:Fields DATE/INTERNALDATE have wrong timezone
Description:
A message in its headers has for example
Received: by mail.example.com id 4693188293;
Wed, 1 Jul 2009 11:06:19 +0200 (CEST)
Date: Wed, 01 Jul 2009 11:06:19 +0200
In a database there are
dbmail_physmessage.internal_date = 2009-07-01 11:06:19
dbmail_headervalue.headervalue = Wed, 01 Jul 2009 11:06:19 +0200
dbmail_datefield.datefield = 2009-07-01 09:06:19
The IMAP daemon replies to
A001 UID FETCH 1603363 (INTERNALDATE BODY.PEEK[HEADER.Fields (Date)])
as
* 273 FETCH (INTERNALDATE 01-Jul-2009 11:06:19 + UID 1603363
BODY[HEADER.FIELDS (Date)] {41}
date: Wed, 01 Jul 2009 11:06:19 +0200
)
A001 OK UID FETCH completed
So the internaldate's timezone is wrong. Unfortunatelly clients such as MS
Outlook/Express interpret it as a time two hours ahead (because my users
are in CEST +0200 TZ).
==
Issue History
Date ModifiedUsername FieldChange
==
01-Jul-09 15:01 idkNew Issue
24-Jul-09 19:06 netvulture Status new = assigned
24-Jul-09 19:06 netvulture Assigned To = netvulture
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000786]: Fields DATE/INTERNALDATE have wrong timezone
The following issue has been RESOLVED.
==
http://dbmail.org/mantis/view.php?id=786
==
Reported By:idk
Assigned To:netvulture
==
Project:DBMail
Issue ID: 786
Category: IMAP daemon
Reproducibility:always
Severity: minor
Priority: normal
Status: resolved
target:
Resolution: fixed
Fixed in Version: 2.2 branch
==
Date Submitted: 01-Jul-09 15:01 CEST
Last Modified: 24-Jul-09 19:09 CEST
==
Summary:Fields DATE/INTERNALDATE have wrong timezone
Description:
A message in its headers has for example
Received: by mail.example.com id 4693188293;
Wed, 1 Jul 2009 11:06:19 +0200 (CEST)
Date: Wed, 01 Jul 2009 11:06:19 +0200
In a database there are
dbmail_physmessage.internal_date = 2009-07-01 11:06:19
dbmail_headervalue.headervalue = Wed, 01 Jul 2009 11:06:19 +0200
dbmail_datefield.datefield = 2009-07-01 09:06:19
The IMAP daemon replies to
A001 UID FETCH 1603363 (INTERNALDATE BODY.PEEK[HEADER.Fields (Date)])
as
* 273 FETCH (INTERNALDATE 01-Jul-2009 11:06:19 + UID 1603363
BODY[HEADER.FIELDS (Date)] {41}
date: Wed, 01 Jul 2009 11:06:19 +0200
)
A001 OK UID FETCH completed
So the internaldate's timezone is wrong. Unfortunatelly clients such as MS
Outlook/Express interpret it as a time two hours ahead (because my users
are in CEST +0200 TZ).
==
--
(0002843) netvulture (developer) - 24-Jul-09 19:09
http://dbmail.org/mantis/view.php?id=786#c2843
--
This issue was corrected post 2.2.11-RELEASE. You can use git to checkout
the dbmail_2_2 branch and then compile to get this change until 2.2.12 is
released.
See the bottom of http://www.dbmail.org/index.php?page=download for how to
get the dbmail_2_2 branch from git.
Issue History
Date ModifiedUsername FieldChange
==
01-Jul-09 15:01 idkNew Issue
24-Jul-09 19:06 netvulture Status new = assigned
24-Jul-09 19:06 netvulture Assigned To = netvulture
24-Jul-09 19:09 netvulture Note Added: 0002843
24-Jul-09 19:09 netvulture Status assigned = resolved
24-Jul-09 19:09 netvulture Fixed in Version = 2.2 branch
24-Jul-09 19:09 netvulture Resolution open = fixed
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000785]: ignored QUERY_STRING parameter
The following issue has been ASSIGNED. == http://dbmail.org/mantis/view.php?id=785 == Reported By:doker Assigned To:paul == Project:DBMail Issue ID: 785 Category: Authentication layer Reproducibility:always Severity: minor Priority: normal Status: assigned target: == Date Submitted: 11-Jun-09 09:22 CEST Last Modified: 24-Jul-09 19:14 CEST == Summary:ignored QUERY_STRING parameter Description: MSLdap windows 2003 server , dbmail-2.3.5_2 dbmail.conf [DBMAIL] authdriver=ldap [LDAP] PORT = 389 VERSION = 3 HOSTNAME = dc1.domen.ru BIND_DN = CN=dbmail,OU=Services,DC=domen,DC=ru BIND_PW = 1234567 SCOPE = SubTree BASE_DN = OU=Users,DC=domen,DC=ru QUERY_STRING=(memberOf=CN=GMU,CN=Users,DC=shipyard-yantar,DC=ru) USER_OBJECTCLASS = person FIELD_PASSWD = userPassword FIELD_UID = sAMAccountName FIELD_NID = uSNCreated FIELD_CID = gidNumber FIELD_MAIL = userPrincipalName FIELD_QUOTA = mailQuota ### when I try to get userlist the QUERY_STRING parameter is being totally ignored debug.log dbmail/pop3d[45007]: [0x288202e0] Debug:[auth] __auth_get_config(+83): key QUERY_STRING section LDAP var _ldap_cfg.query_string value [(memberOf=CN=GMU,CN=Users,DC=domen,DC=ru)] # == -- (0002822) doker (reporter) - 11-Jun-09 09:25 http://dbmail.org/mantis/view.php?id=785#c2822 -- * QUERY_STRING=(memberOf=CN=GMU,CN=Users,DC=domen,DC=ru) -- (0002823) paul (administrator) - 11-Jun-09 09:45 http://dbmail.org/mantis/view.php?id=785#c2823 -- This is not a bug, but a feature. The query_string parameter is not used for filtering the list of users/forwards. It's only used during delivery. In your case, if you want to limit email delivery to the group mentioned in the filter you should use something like: query_string=((userPrincipleName=%s)(memberOf=CN=GMU,CN=Users,DC=domen,DC=ru)) assuming userPrincipleName contains a valid email address -- (0002824) doker (reporter) - 11-Jun-09 10:31 http://dbmail.org/mantis/view.php?id=785#c2824 -- we have followed your recommendations, but invoking dbmail-users -l results in displaying the list of all users (no matter if user belongs to GMU group or not) and authorisation through e-mail client is always successful even after removal of that user from the GMU group for your information: there is truncated string in debug.log : dbmail/pop3d[8403]: [0x288202e0] Debug:[auth] __auth_get_config(+83): key QUERY_STRING section LDAP var _ldap_cfg.query_string val ue [((userPrincipleName=%s)(memberOf=CN=GMU,CN=Users,DC -- (0002825) paul (administrator) - 11-Jun-09 10:56 http://dbmail.org/mantis/view.php?id=785#c2825 -- They maybe able to authenticate, but they wont be able to receive email. Point is dbmail doesn't support what you are trying to achieve (yet). You will have to use a subtree for your dbmail users, or use a objectclass to distinguish them from the other users. -- (0002826) doker (reporter) - 11-Jun-09 13:02 http://dbmail.org/mantis/view.php?id=785#c2826 -- Point is dbmail doesn't support what you are trying to achieve (yet). Is it already planned to add support for this (during authorisation stage)? And if it is planned then do you know the release version or date? Issue History Date ModifiedUsername FieldChange == 11-Jun-09 09:22 doker New Issue 11-Jun-09 09:23 doker Issue Monitored: doker 11-Jun-09 09:24 doker Issue End Monitor: doker 11-Jun-09 09:25 doker Note
[Dbmail-dev] [DBMail 0000792]: Lock timeout on lmtpd message insertation during nightly dbmail-util
The following issue has been ASSIGNED. == http://dbmail.org/mantis/view.php?id=792 == Reported By:jasb Assigned To:netvulture == Project:DBMail Issue ID: 792 Category: LMTP daemon Reproducibility:have not tried Severity: major Priority: normal Status: assigned target: == Date Submitted: 24-Jul-09 10:24 CEST Last Modified: 24-Jul-09 19:22 CEST == Summary:Lock timeout on lmtpd message insertation during nightly dbmail-util Description: Hi, During the nightly dbmail-util, when it is running, new messages wont get in. My question is: i believe they don't really get inserted, i ask, are the transaction really being restarted/were this messages really delivered? Log of lmtpd below. == -- (0002842) netvulture (developer) - 24-Jul-09 19:01 http://dbmail.org/mantis/view.php?id=792#c2842 -- From the logs, it would appear that you are running a partlists cleanup operation when the message came in. I am not sure if the query was successfully canceled or did finally go through when the partlists table was unlocked. If you use the filelog version of these lines, you should be able to see the phymessage_id it was for, and then do a select * from dbmail_partlists where phymessage_id=x; If you see the part_* that were trying to be inserted, then they were, however with out more of the log I couldn't tell you if the message failed for insertion and returned an error to the MTA or not. Issue History Date ModifiedUsername FieldChange == 24-Jul-09 10:24 jasb New Issue 24-Jul-09 19:01 netvulture Note Added: 0002842 24-Jul-09 19:22 netvulture Status new = assigned 24-Jul-09 19:22 netvulture Assigned To = netvulture == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000789]: dbmail-imapd crash with invalid pointer reason
The following issue has been ASSIGNED. == http://dbmail.org/mantis/view.php?id=789 == Reported By:jasb Assigned To:netvulture == Project:DBMail Issue ID: 789 Category: IMAP daemon Reproducibility:have not tried Severity: crash Priority: normal Status: assigned target: == Date Submitted: 21-Jul-09 23:51 CEST Last Modified: 24-Jul-09 19:23 CEST == Summary:dbmail-imapd crash with invalid pointer reason Description: Hi, After this commit on GIT HEAD: http://git.dbmail.eu/cgit/cgit.cgi/paul/dbmail/commit/?id=02b0fe06c4947fb50bdcbe3ac39661006f78aa07 imapd crashes with invalid pointer on this. Attached there's the GDB trace for this. == -- (0002837) waza123 (reporter) - 22-Jul-09 14:02 http://dbmail.org/mantis/view.php?id=789#c2837 -- i have many crashes in all sectors. dbmail-imapd dbmail-pop3d dbmail-lmtpd v2.3.6 -- (0002838) pschmiel (reporter) - 23-Jul-09 12:55 http://dbmail.org/mantis/view.php?id=789#c2838 -- I have the same problem with a crashing imapd. Backtrace is attached. -- (0002839) pschmiel (reporter) - 23-Jul-09 16:30 http://dbmail.org/mantis/view.php?id=789#c2839 -- I think the following changes did the trick. No more crashes since this modification: if(D-data != NULL) g_free(D-data); if(D != NULL) g_free(D); -- (0002840) waza123 (reporter) - 23-Jul-09 16:37 http://dbmail.org/mantis/view.php?id=789#c2840 -- yes, you have to check if it exists before free it -- (0002841) pschmiel (reporter) - 23-Jul-09 18:02 http://dbmail.org/mantis/view.php?id=789#c2841 -- got another crash a few minutes ago. looks like the pointer points to an invalid address location so it is not NULL but nevertheless it can't be freed... Issue History Date ModifiedUsername FieldChange == 21-Jul-09 23:51 jasb New Issue 21-Jul-09 23:51 jasb File Added: imapd_invalid_pointer.txt 22-Jul-09 14:02 waza123Note Added: 0002837 23-Jul-09 12:55 pschmiel File Added: backtrace.txt 23-Jul-09 12:55 pschmiel Note Added: 0002838 23-Jul-09 13:22 pschmiel Issue Monitored: pschmiel 23-Jul-09 16:30 pschmiel Note Added: 0002839 23-Jul-09 16:36 waza123Note Added: 0002840 23-Jul-09 16:37 waza123Note Edited: 0002840 23-Jul-09 18:02 pschmiel Note Added: 0002841 24-Jul-09 19:23 netvulture Status new = assigned 24-Jul-09 19:23 netvulture Assigned To = netvulture == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000789]: dbmail-imapd crash with invalid pointer reason
The following issue has been ACKNOWLEDGED. == http://dbmail.org/mantis/view.php?id=789 == Reported By:jasb Assigned To:netvulture == Project:DBMail Issue ID: 789 Category: IMAP daemon Reproducibility:have not tried Severity: crash Priority: normal Status: acknowledged target: == Date Submitted: 21-Jul-09 23:51 CEST Last Modified: 24-Jul-09 19:25 CEST == Summary:dbmail-imapd crash with invalid pointer reason Description: Hi, After this commit on GIT HEAD: http://git.dbmail.eu/cgit/cgit.cgi/paul/dbmail/commit/?id=02b0fe06c4947fb50bdcbe3ac39661006f78aa07 imapd crashes with invalid pointer on this. Attached there's the GDB trace for this. == -- (0002837) waza123 (reporter) - 22-Jul-09 14:02 http://dbmail.org/mantis/view.php?id=789#c2837 -- i have many crashes in all sectors. dbmail-imapd dbmail-pop3d dbmail-lmtpd v2.3.6 -- (0002838) pschmiel (reporter) - 23-Jul-09 12:55 http://dbmail.org/mantis/view.php?id=789#c2838 -- I have the same problem with a crashing imapd. Backtrace is attached. -- (0002839) pschmiel (reporter) - 23-Jul-09 16:30 http://dbmail.org/mantis/view.php?id=789#c2839 -- I think the following changes did the trick. No more crashes since this modification: if(D-data != NULL) g_free(D-data); if(D != NULL) g_free(D); -- (0002840) waza123 (reporter) - 23-Jul-09 16:37 http://dbmail.org/mantis/view.php?id=789#c2840 -- yes, you have to check if it exists before free it -- (0002841) pschmiel (reporter) - 23-Jul-09 18:02 http://dbmail.org/mantis/view.php?id=789#c2841 -- got another crash a few minutes ago. looks like the pointer points to an invalid address location so it is not NULL but nevertheless it can't be freed... -- (0002844) netvulture (developer) - 24-Jul-09 19:25 http://dbmail.org/mantis/view.php?id=789#c2844 -- I think I might have triggered the crash on my system by using IDLE and then reading messages fairly fast, switching from IDLE to OPERATION and BACK in short order. Will try to reproduce this weekend under gdb operation. Issue History Date ModifiedUsername FieldChange == 21-Jul-09 23:51 jasb New Issue 21-Jul-09 23:51 jasb File Added: imapd_invalid_pointer.txt 22-Jul-09 14:02 waza123Note Added: 0002837 23-Jul-09 12:55 pschmiel File Added: backtrace.txt 23-Jul-09 12:55 pschmiel Note Added: 0002838 23-Jul-09 13:22 pschmiel Issue Monitored: pschmiel 23-Jul-09 16:30 pschmiel Note Added: 0002839 23-Jul-09 16:36 waza123Note Added: 0002840 23-Jul-09 16:37 waza123Note Edited: 0002840 23-Jul-09 18:02 pschmiel Note Added: 0002841 24-Jul-09 19:23 netvulture Status new = assigned 24-Jul-09 19:23 netvulture Assigned To = netvulture 24-Jul-09 19:25 netvulture Note Added: 0002844 24-Jul-09 19:25 netvulture Status assigned = acknowledged ==
[Dbmail-dev] [DBMail 0000791]: Several LMTPD problems on delevery
The following issue requires your FEEDBACK. == http://dbmail.org/mantis/view.php?id=791 == Reported By:jasb Assigned To:netvulture == Project:DBMail Issue ID: 791 Category: LMTP daemon Reproducibility:have not tried Severity: minor Priority: normal Status: feedback target: == Date Submitted: 23-Jul-09 16:45 CEST Last Modified: 24-Jul-09 19:27 CEST == Summary:Several LMTPD problems on delevery Description: I'm chasing now LMTPD for some problems that is has. Below there's some of them, i believe it's some of folowing that is causing the problem of missing rfcsize/envelope/un-cached values that are corrected by dbmail-util, i say this 'cause at the moment this happened i had some problematic messages. Jul 23 15:25:35 lira dbmail/lmtpd[19475]: [0x8f53b08] Warning:[message] dbmail_message_store(+1318): Failed to store mimeparts Jul 23 15:25:35 lira dbmail/lmtpd[19475]: [0x8f53b08] Error:[db] db_copymsg(+2678): error getting size for message [6073908] Jul 23 15:25:35 lira dbmail/lmtpd[19475]: [0x8f53b08] Error:[message] sort_deliver_to_mailbox(+2132): error copying message to user [657] Jul 23 15:25:36 lira dbmail/lmtpd[19475]: [0x8f53b08] Error:[message] insert_messages(+2437): unknown temporary failure in sort_and_deliver for useridnr [657] Jul 23 15:27:32 lira dbmail/lmtpd[19475]: [0x8f53b08] Warning:[message] dbmail_message_store(+1318): Failed to store mimeparts Jul 23 15:27:32 lira dbmail/lmtpd[19475]: [0x8f53b08] Error:[db] db_copymsg(+2678): error getting size for message [6073922] Jul 23 15:27:32 lira dbmail/lmtpd[19475]: [0x8f53b08] Error:[message] sort_deliver_to_mailbox(+2132): error copying message to user [657] Jul 23 15:27:32 lira dbmail/lmtpd[19475]: [0x8f53b08] Error:[message] insert_messages(+2437): unknown temporary failure in sort_and_deliver for useridnr [657] == -- (0002845) netvulture (developer) - 24-Jul-09 19:27 http://dbmail.org/mantis/view.php?id=791#c2845 -- Still waiting on those logs. Issue History Date ModifiedUsername FieldChange == 23-Jul-09 16:45 jasb New Issue 24-Jul-09 19:27 netvulture Note Added: 0002845 24-Jul-09 19:27 netvulture Assigned To = netvulture 24-Jul-09 19:27 netvulture Status new = feedback == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000790]: dbmail-lmtpd crash
The following issue has been ASSIGNED.
==
http://dbmail.org/mantis/view.php?id=790
==
Reported By:waza123
Assigned To:netvulture
==
Project:DBMail
Issue ID: 790
Category: LMTP daemon
Reproducibility:always
Severity: crash
Priority: normal
Status: assigned
target:
==
Date Submitted: 23-Jul-09 16:09 CEST
Last Modified: 24-Jul-09 19:30 CEST
==
Summary:dbmail-lmtpd crash
Description:
Very unstable dbmail-lmtpd (and pop3d and imapd)
0xb7fb89c6 in client_session_set_timeout (session=0x80c2e10, timeout=60)
at clientsession.c:143
143 if (session (session-state CLIENTSTATE_ANY)
session-ci session-ci-timeout) {
==
Issue History
Date ModifiedUsername FieldChange
==
23-Jul-09 16:09 waza123New Issue
23-Jul-09 16:09 waza123File Added: crash_report_lmtpd.txt
23-Jul-09 16:12 jasb Issue Monitored: jasb
24-Jul-09 19:30 netvulture Status new = assigned
24-Jul-09 19:30 netvulture Assigned To = netvulture
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000790]: dbmail-lmtpd crash
A NOTE has been added to this issue.
==
http://dbmail.org/mantis/view.php?id=790
==
Reported By:waza123
Assigned To:netvulture
==
Project:DBMail
Issue ID: 790
Category: LMTP daemon
Reproducibility:always
Severity: crash
Priority: normal
Status: assigned
target:
==
Date Submitted: 23-Jul-09 16:09 CEST
Last Modified: 24-Jul-09 19:32 CEST
==
Summary:dbmail-lmtpd crash
Description:
Very unstable dbmail-lmtpd (and pop3d and imapd)
0xb7fb89c6 in client_session_set_timeout (session=0x80c2e10, timeout=60)
at clientsession.c:143
143 if (session (session-state CLIENTSTATE_ANY)
session-ci session-ci-timeout) {
==
--
(0002846) netvulture (developer) - 24-Jul-09 19:32
http://dbmail.org/mantis/view.php?id=790#c2846
--
Please try inserting
TRACE(TRACE_DEBUG,setting timeout on client session [%p],session);
on line 143 of clientsession.c just before the if statement and try to
reproduce. If you can get it to crash, the log file should have the address
of client session in it. My thought is we are trying to set a timeout on an
invalid session.
Issue History
Date ModifiedUsername FieldChange
==
23-Jul-09 16:09 waza123New Issue
23-Jul-09 16:09 waza123File Added: crash_report_lmtpd.txt
23-Jul-09 16:12 jasb Issue Monitored: jasb
24-Jul-09 19:30 netvulture Status new = assigned
24-Jul-09 19:30 netvulture Assigned To = netvulture
24-Jul-09 19:32 netvulture Note Added: 0002846
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000790]: dbmail-lmtpd crash
The following issue requires your FEEDBACK.
==
http://dbmail.org/mantis/view.php?id=790
==
Reported By:waza123
Assigned To:netvulture
==
Project:DBMail
Issue ID: 790
Category: LMTP daemon
Reproducibility:always
Severity: crash
Priority: normal
Status: feedback
target:
==
Date Submitted: 23-Jul-09 16:09 CEST
Last Modified: 24-Jul-09 19:33 CEST
==
Summary:dbmail-lmtpd crash
Description:
Very unstable dbmail-lmtpd (and pop3d and imapd)
0xb7fb89c6 in client_session_set_timeout (session=0x80c2e10, timeout=60)
at clientsession.c:143
143 if (session (session-state CLIENTSTATE_ANY)
session-ci session-ci-timeout) {
==
--
(0002846) netvulture (developer) - 24-Jul-09 19:32
http://dbmail.org/mantis/view.php?id=790#c2846
--
Please try inserting
TRACE(TRACE_DEBUG,setting timeout on client session [%p],session);
on line 143 of clientsession.c just before the if statement and try to
reproduce. If you can get it to crash, the log file should have the address
of client session in it. My thought is we are trying to set a timeout on an
invalid session.
Issue History
Date ModifiedUsername FieldChange
==
23-Jul-09 16:09 waza123New Issue
23-Jul-09 16:09 waza123File Added: crash_report_lmtpd.txt
23-Jul-09 16:12 jasb Issue Monitored: jasb
24-Jul-09 19:30 netvulture Status new = assigned
24-Jul-09 19:30 netvulture Assigned To = netvulture
24-Jul-09 19:32 netvulture Note Added: 0002846
24-Jul-09 19:33 netvulture Status assigned = feedback
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000792]: Lock timeout on lmtpd message insertation during nightly dbmail-util
The following issue requires your FEEDBACK. == http://dbmail.org/mantis/view.php?id=792 == Reported By:jasb Assigned To:netvulture == Project:DBMail Issue ID: 792 Category: LMTP daemon Reproducibility:have not tried Severity: major Priority: normal Status: feedback target: == Date Submitted: 24-Jul-09 10:24 CEST Last Modified: 24-Jul-09 19:38 CEST == Summary:Lock timeout on lmtpd message insertation during nightly dbmail-util Description: Hi, During the nightly dbmail-util, when it is running, new messages wont get in. My question is: i believe they don't really get inserted, i ask, are the transaction really being restarted/were this messages really delivered? Log of lmtpd below. == -- (0002842) netvulture (developer) - 24-Jul-09 19:01 http://dbmail.org/mantis/view.php?id=792#c2842 -- From the logs, it would appear that you are running a partlists cleanup operation when the message came in. I am not sure if the query was successfully canceled or did finally go through when the partlists table was unlocked. If you use the filelog version of these lines, you should be able to see the phymessage_id it was for, and then do a select * from dbmail_partlists where phymessage_id=x; If you see the part_* that were trying to be inserted, then they were, however with out more of the log I couldn't tell you if the message failed for insertion and returned an error to the MTA or not. Issue History Date ModifiedUsername FieldChange == 24-Jul-09 10:24 jasb New Issue 24-Jul-09 19:01 netvulture Note Added: 0002842 24-Jul-09 19:22 netvulture Status new = assigned 24-Jul-09 19:22 netvulture Assigned To = netvulture 24-Jul-09 19:38 netvulture Status assigned = feedback == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
[Dbmail] client groups, group quotas, ldap etc.
Hello, I've read this (quite old) http://www.nabble.com/Group-quotas-td7814443.html#a7814443 What's the current status of this ? client_idnr column is still present, and there's field_cid in ldap configuration in dbmail.conf Can I ask some up-to-date explanation how this works with field_quota, if still does? My groups are based on posix gidNumber. Regards, Piotr -- View this message in context: http://www.nabble.com/client-groups%2C-group-quotas%2C-ldap-etc.-tp24639408p24639408.html Sent from the dbmail users mailing list archive at Nabble.com. ___ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
[Dbmail] dbmail looses mail address in From: header
Is this a know bug? When I receive mail from this guy, in Zarafa/Outlook it stores the header like this: From: =?windows-1252?Q?M._Oostergo?= m.ooste...@zarafa.com But when received over dbmail, the mail part is lost: From: =?windows-1252?Q?M._Oostergo?= This is dbmail-2.2.11. mfg zmi -- // Michael Monnerie, Ing.BSc- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: curl -s http://zmi.at/zmi.asc | gpg --import // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4 signature.asc Description: This is a digitally signed message part. ___ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
Re: [Dbmail] client groups, group quotas, ldap etc.
Piotr Wadas wrote: Hello, I've read this (quite old) http://www.nabble.com/Group-quotas-td7814443.html#a7814443 What's the current status of this ? client_idnr column is still present, and there's field_cid in ldap configuration in dbmail.conf Can I ask some up-to-date explanation how this works with field_quota, if still does? My groups are based on posix gidNumber. Regards, Piotr As it sits now, there are no group quotas or per mailbox(folder) quotas. Only the entire storage of a user has a quota on it. We do not have a table to store the group quota information at this point. You could probably script something together to make a psuedo group quota by taking the sum of the used space on your users and comparing against your target limit. If it exceeds your limit, you could set a per user quota equal to thier current usage to stop insertion of messages until it falls below that limit. When the script runs again and finds it lower than your target, set their quota back to 0 (off). I have a couple of goals already to get into the 2.3.x branch, but I think we can look at improving the quota handling and maybe work on getting per-user, per-mailbox, and per-group all in there and setup an automatic message to appear in the mailbox when the quota is exceeded. This message would not be able to be deleted or moved. The body of the message could be user configurable. That is my thought on that, but not this week. -Jon -- Scanned for viruses and dangerous content by MailScanner ___ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
Re: [Dbmail] dbmail looses mail address in From: header
Michael Monnerie wrote: Is this a know bug? When I receive mail from this guy, in Zarafa/Outlook it stores the header like this: From: =?windows-1252?Q?M._Oostergo?= m.ooste...@zarafa.com Is this when you retrieve the message from a non-dbmail pop3/imap server? But when received over dbmail, the mail part is lost: From: =?windows-1252?Q?M._Oostergo?= Is this when the message is inserted via dbmail-smtp/dbmail-lmtp or an IMAP APPEND? Is it ok when first inserted, but then the client changes it? -Jon -- Scanned for viruses and dangerous content by MailScanner ___ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
Re: [Dbmail] dbmail looses mail address in From: header
On Freitag 24 Juli 2009 Jonathan Feally wrote: Michael Monnerie wrote: Is this a know bug? When I receive mail from this guy, in Zarafa/Outlook it stores the header like this: From: =?windows-1252?Q?M._Oostergo?= m.ooste...@zarafa.com Is this when you retrieve the message from a non-dbmail pop3/imap server? Yes. Over Zarafa (MDA) read with Outlook or IMAP (MTA). But when received over dbmail, the mail part is lost: From: =?windows-1252?Q?M._Oostergo?= Is this when the message is inserted via dbmail-smtp/dbmail-lmtp or an IMAP APPEND? Is it ok when first inserted, but then the client changes it? Received via dbmail-lmtp from postfix. I didn't know the client could change the headers. Do you mean I'd have to read the message from the DB before accessing it via kmail? I could try to read the message via IMAP from Outlook instead kmail, but I doubt it's kmail. Wasn't there a bug im dbmail once with wrong interpreted headers? Something with the lib used to en/decode those strings? mfg zmi -- // Michael Monnerie, Ing.BSc- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: curl -s http://zmi.at/zmi.asc | gpg --import // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4 signature.asc Description: This is a digitally signed message part. ___ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
