[Dbmail-dev] [DBMail 0000542]: postinst script for dbmail-mysql
The following issue has been SUBMITTED. == http://www.dbmail.org/mantis/view.php?id=542 == Reported By:lkneschke Assigned To: == Project:DBMail Issue ID: 542 Category: installation scripts Reproducibility:always Severity: minor Priority: normal Status: new target: == Date Submitted: 19-Mar-07 08:00 CET Last Modified: 19-Mar-07 08:00 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) ;; == Issue History Date Modified Username FieldChange == 19-Mar-07 08:00 lkneschke New Issue == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000540]: wrong port for sieve in dbmail.conf
The following issue has been RESOLVED. == http://www.dbmail.org/mantis/view.php?id=540 == Reported By:lkneschke Assigned To: == Project:DBMail Issue ID: 540 Category: Sieve (delivery, dbmail-sievecmd, dbmail-timsieved) Reproducibility:always Severity: major Priority: normal Status: resolved target: Resolution: fixed Fixed in Version: == Date Submitted: 19-Mar-07 07:54 CET Last Modified: 19-Mar-07 08:59 CET == Summary:wrong port for sieve in dbmail.conf Description: There is a wrong port for the sieve daemon in dbmail.conf. This patch should fix the problem: [EMAIL PROTECTED]:~/src/dbmail-2.2# svn diff dbmail.conf Index: dbmail.conf === --- dbmail.conf (revision 2472) +++ dbmail.conf (working copy) @@ -216,7 +216,7 @@ # # Port to bind to. # -PORT = 2 +PORT = 2000 [LDAP] PORT = 389 == -- paul - 19-Mar-07 08:59 -- fixed Issue History Date Modified Username FieldChange == 19-Mar-07 07:54 lkneschke New Issue 19-Mar-07 08:59 paul Note Added: 0001919 19-Mar-07 08:59 paul Status new = resolved 19-Mar-07 08:59 paul Resolution open = fixed == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000541]: the user gets not created when installing the package and sieve get's not started
The following issue has been RESOLVED. == http://www.dbmail.org/mantis/view.php?id=541 == Reported By:lkneschke Assigned To: == Project:DBMail Issue ID: 541 Category: installation scripts Reproducibility:always Severity: major Priority: normal Status: resolved target: Resolution: fixed Fixed in Version: == Date Submitted: 19-Mar-07 07:58 CET Last Modified: 19-Mar-07 09:00 CET == Summary:the user gets not created when installing the package and sieve get's not started Description: The dbmail user gets not added, when doing a fresh install. The sieve daemon gets not started, even the user requested it in debconf. This patch fixed both problems: [EMAIL PROTECTED]:~/src/dbmail-2.2/debian# svn diff dbmail.postinst Index: dbmail.postinst === --- dbmail.postinst (revision 2472) +++ dbmail.postinst (working copy) @@ -46,6 +46,7 @@ create_user ;; configure) + create_user . /usr/share/debconf/confmodule db_get dbmail/do_debconf || true; DO_DEBCONF=$RET @@ -63,7 +64,7 @@ db_get dbmail/start_imapd || true; START_IMAPD=$RET db_get dbmail/start_lmtpd || true; START_LMTPD=$RET db_get dbmail/start_pop3d || true; START_POP3D=$RET - db_get dbmail/sieve/start_sieve || true; START_SIEVE=$RET + db_get dbmail/start_sieve || true; START_SIEVE=$RET if [ $AUTHDRIVER = ldap ]; then db_get dbmail/ldap/HOSTNAME || true; LDAP_HOST=$RET == -- paul - 19-Mar-07 09:00 -- fixed Issue History Date Modified Username FieldChange == 19-Mar-07 07:58 lkneschke New Issue 19-Mar-07 09:00 paul Note Added: 0001920 19-Mar-07 09:00 paul Status new = resolved 19-Mar-07 09:00 paul Resolution open = fixed == ___ 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 ACKNOWLEDGED. == 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: acknowledged target: == Date Submitted: 19-Mar-07 08:00 CET Last Modified: 19-Mar-07 09:06 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. Issue History Date Modified Username FieldChange == 19-Mar-07 08:00 lkneschke New Issue 19-Mar-07 09:06 paul Note Added: 0001921 19-Mar-07 09:06 paul Assigned To = paul 19-Mar-07 09:06 paul Status new = acknowledged 19-Mar-07 09:06 paul Resolution open = won't fix == ___ 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
A NOTE has been added to this issue. == 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: acknowledged target: == Date Submitted: 19-Mar-07 08:00 CET Last Modified: 19-Mar-07 09:41 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 Issue History Date Modified Username FieldChange == 19-Mar-07 08:00 lkneschke New Issue 19-Mar-07 09:06 paul Note Added: 0001921 19-Mar-07 09:06 paul Assigned To = paul 19-Mar-07 09:06 paul Status new = acknowledged 19-Mar-07 09:06 paul Resolution open = won't fix 19-Mar-07 09:41 lkneschke Note Added: 0001922 == ___ Dbmail-dev mailing list
[Dbmail-dev] [DBMail 0000542]: postinst script for dbmail-mysql
A NOTE has been added to this issue. == 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: acknowledged target: == Date Submitted: 19-Mar-07 08:00 CET Last Modified: 19-Mar-07 10:13 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.conf. Finally, let's please keep debian related issues
[Dbmail-dev] [DBMail 0000542]: postinst script for dbmail-mysql
A NOTE has been added to this issue. == 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: acknowledged target: == Date Submitted: 19-Mar-07 08:00 CET Last Modified: 19-Mar-07 10:37 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.conf. Finally, let's please keep debian related issues
[Dbmail-dev] Prague IETF for a week
Hey folks, just wanted to give a heads up that I'm in Prague until 3/25, for the IETF meeting. One particular highlight is going to be a Sieve interop session. We'll be doing it in person and with a Jabber room. Anybody who would like to participate, please email me off-list and I'll share the details when I find out when/where this will take place. I might also reply to emails on the flip side of my usual schedule (ha, as though I ever go more than a 6 hours without checking my email :-P) Cheers, Aaron ___ 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 SUBMITTED. == http://dbmail.org/mantis/view.php?id=543 == Reported By:menole Assigned To: == Project:DBMail Issue ID: 543 Category: POP3 daemon Reproducibility:always Severity: minor Priority: normal Status: new target: == Date Submitted: 19-Mar-07 14:16 CET Last Modified: 19-Mar-07 14:16 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 == 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 == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000508]: vacation sieve script always sends reply instead of just once
A NOTE has been added to this issue.
==
http://dbmail.org/mantis/view.php?id=508
==
Reported By:Anne
Assigned To:
==
Project:DBMail
Issue ID: 508
Category: Sieve (delivery, dbmail-sievecmd, dbmail-timsieved)
Reproducibility:always
Severity: minor
Priority: normal
Status: new
target:
==
Date Submitted: 16-Feb-07 16:48 CET
Last Modified: 19-Mar-07 15:44 CET
==
Summary:vacation sieve script always sends reply instead of
just once
Description:
Starting version 2.2.2 the vacation sieve script always sends a reply even
when the recipient has already been cached in dbmail_replycache.
==
--
Tarick - 19-Mar-07 15:44
--
I confirm, 2.2.4 still has this problem. From dbmail.err:
Debug:[sql] dbpgsql.c,db_query(+281): [SELECT lastseen FROM
dbmail_replycache WHERE to_addr = '[EMAIL PROTECTED]' AND f
rom_addr = '[EMAIL PROTECTED]' AND handle = '4257e0eca3659acfbf3cf8f3c964289c'
AND lastseen (NOW() - INTERVAL '1 DAY')]
Debug:[delivery] pipe.c,parse_and_escape(+54): parsing address
[EMAIL PROTECTED]
Debug:[delivery] pipe.c,parse_and_escape(+54): parsing address
[EMAIL PROTECTED]
Info:[delivery] pipe.c,send_mail(+144): opening pipe to
[/usr/sbin/sendmail -f [EMAIL PROTECTED] [EMAIL PROTECTED]
Debug:[delivery] pipe.c,send_mail(+152): pipe opened
Debug:[delivery] pipe.c,send_mail(+173): pipe closed
Info:[delivery] pipe.c,send_mail(+178): sendmail exited normally
Debug:[sql] dbpgsql.c,db_query(+281): [SELECT lastseen FROM
dbmail_replycache WHERE to_addr = '[EMAIL PROTECTED]' AND f
rom_addr = '[EMAIL PROTECTED]' AND handle=
'4257e0eca3659acfbf3cf8f3c964289c' ]
Debug:[sql] dbpgsql.c,db_query(+281): [INSERT INTO dbmail_replycache
(to_addr, from_addr, handle, lastseen) VALUES
('[EMAIL PROTECTED]','[EMAIL PROTECTED]','4257e0eca3659acfbf3cf8f3c964289c',
CURRENT_TIMESTAMP)]
Info:[sort] sortsieve.c,sort_vacation(+145): Sending vacation to
[EMAIL PROTECTED] from [EMAIL PROTECTED] handle [425
7e0eca3659acfbf3cf8f3c964289c] repeat days [1]
Issue History
Date Modified Username FieldChange
==
16-Feb-07 16:48 Anne New Issue
19-Mar-07 15:44 Tarick Note Added: 0001925
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000544]: Segmet fault on empty message
The following issue has been SUBMITTED. == http://dbmail.org/mantis/view.php?id=544 == Reported By:AntonZ Assigned To: == Project:DBMail Issue ID: 544 Category: PIPE delivery (dbmail-smtp) Reproducibility:always Severity: minor Priority: normal Status: new target: == Date Submitted: 19-Mar-07 17:01 CET Last Modified: 19-Mar-07 17:01 CET == Summary:Segmet fault on empty message Description: dbmail-smtp -d '[EMAIL PROTECTED]' Press Ctrl-D to close input stream. == Issue History Date Modified Username FieldChange == 19-Mar-07 17:01 AntonZ New Issue == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000508]: vacation sieve script always sends reply instead of just once
A NOTE has been added to this issue.
==
http://dbmail.org/mantis/view.php?id=508
==
Reported By:Anne
Assigned To:
==
Project:DBMail
Issue ID: 508
Category: Sieve (delivery, dbmail-sievecmd, dbmail-timsieved)
Reproducibility:always
Severity: minor
Priority: normal
Status: new
target:
==
Date Submitted: 16-Feb-07 16:48 CET
Last Modified: 19-Mar-07 17:30 CET
==
Summary:vacation sieve script always sends reply instead of
just once
Description:
Starting version 2.2.2 the vacation sieve script always sends a reply even
when the recipient has already been cached in dbmail_replycache.
==
--
Tarick - 19-Mar-07 15:44
--
I confirm, 2.2.4 still has this problem. From dbmail.err:
Debug:[sql] dbpgsql.c,db_query(+281): [SELECT lastseen FROM
dbmail_replycache WHERE to_addr = '[EMAIL PROTECTED]' AND f
rom_addr = '[EMAIL PROTECTED]' AND handle = '4257e0eca3659acfbf3cf8f3c964289c'
AND lastseen (NOW() - INTERVAL '1 DAY')]
Debug:[delivery] pipe.c,parse_and_escape(+54): parsing address
[EMAIL PROTECTED]
Debug:[delivery] pipe.c,parse_and_escape(+54): parsing address
[EMAIL PROTECTED]
Info:[delivery] pipe.c,send_mail(+144): opening pipe to
[/usr/sbin/sendmail -f [EMAIL PROTECTED] [EMAIL PROTECTED]
Debug:[delivery] pipe.c,send_mail(+152): pipe opened
Debug:[delivery] pipe.c,send_mail(+173): pipe closed
Info:[delivery] pipe.c,send_mail(+178): sendmail exited normally
Debug:[sql] dbpgsql.c,db_query(+281): [SELECT lastseen FROM
dbmail_replycache WHERE to_addr = '[EMAIL PROTECTED]' AND f
rom_addr = '[EMAIL PROTECTED]' AND handle=
'4257e0eca3659acfbf3cf8f3c964289c' ]
Debug:[sql] dbpgsql.c,db_query(+281): [INSERT INTO dbmail_replycache
(to_addr, from_addr, handle, lastseen) VALUES
('[EMAIL PROTECTED]','[EMAIL PROTECTED]','4257e0eca3659acfbf3cf8f3c964289c',
CURRENT_TIMESTAMP)]
Info:[sort] sortsieve.c,sort_vacation(+145): Sending vacation to
[EMAIL PROTECTED] from [EMAIL PROTECTED] handle [425
7e0eca3659acfbf3cf8f3c964289c] repeat days [1]
--
Tarick - 19-Mar-07 17:30
--
I switched to 2.2.1, succesfully sent bunch of messages and had one
autoreply. But when I changed subject of message, handle changed also and
I've got another autoreply. I don't think this is intentional behaviour.
Issue History
Date Modified Username FieldChange
==
16-Feb-07 16:48 Anne New Issue
19-Mar-07 15:44 Tarick Note Added: 0001925
19-Mar-07 17:30 Tarick Note Added: 0001926
==
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] dbmail 2.2.4 svn 2472 issue with server dropping connections on non-error
This was a show stopper when I did an upgrade used svn to get the other
minor fixes, this was first talked about for dbmail 2.2.3 did this somehow
get back into svn? I found it at
http://www.mail-archive.com/dbmail-dev@dbmail.org/msg08488.html anyway
when a user was selecting their Sent mailbox is was doing a SELECT ALL for
non-seen messages and the DB sent back NULL which was correct but the code
below was disconnecting the client rather than showing 0 msgs as
not-seen..etc.
diff -urN dbmail-svn-2.2.4-2472.orig/imapcommands.c
dbmail-svn-2.2.4-2472.new/imapcommands.c
--- dbmail-svn-2.2.4-2472.orig/imapcommands.c 2007-03-17
23:21:45.0 -0400
+++ dbmail-svn-2.2.4-2472.new/imapcommands.c2007-03-19
13:37:38.0 -0400
@@ -240,7 +240,7 @@
/* show idx of first unseen msg (if present) */
if (ud-mailbox.exists) {
- if (! (key = db_first_unseen(ud-mailbox.uid))) {
+ if ((key = db_first_unseen(ud-mailbox.uid)) == (u64_t)
(-1)) {
dbmail_imap_session_printf(self, * BYE internal
dbase error\r\n);
return -1;
}
Thanks,
Leif Jackson
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
Re: [Dbmail-dev] dbmail 2.2.4 svn 2472 issue with server dropping connections on non-error
Leif,
You're tree is not in sync. This patch doesn't apply to 2472 at all.
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);
}
}
Leif Jackson wrote:
This was a show stopper when I did an upgrade used svn to get the other
minor fixes, this was first talked about for dbmail 2.2.3 did this somehow
get back into svn? I found it at
http://www.mail-archive.com/dbmail-dev@dbmail.org/msg08488.html anyway
when a user was selecting their Sent mailbox is was doing a SELECT ALL for
non-seen messages and the DB sent back NULL which was correct but the code
below was disconnecting the client rather than showing 0 msgs as
not-seen..etc.
diff -urN dbmail-svn-2.2.4-2472.orig/imapcommands.c
dbmail-svn-2.2.4-2472.new/imapcommands.c
--- dbmail-svn-2.2.4-2472.orig/imapcommands.c 2007-03-17
23:21:45.0 -0400
+++ dbmail-svn-2.2.4-2472.new/imapcommands.c2007-03-19
13:37:38.0 -0400
@@ -240,7 +240,7 @@
/* show idx of first unseen msg (if present) */
if (ud-mailbox.exists) {
- if (! (key = db_first_unseen(ud-mailbox.uid))) {
+ if ((key = db_first_unseen(ud-mailbox.uid)) == (u64_t)
(-1)) {
dbmail_imap_session_printf(self, * BYE internal
dbase error\r\n);
return -1;
}
Thanks,
Leif Jackson
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlandshttp://www.nfg.nl
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000539]: Mailclient times out opening large mailboxes
A NOTE has been added to this issue. == 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: assigned target: == Date Submitted: 17-Mar-07 16:42 CET Last Modified: 19-Mar-07 22:11 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? Issue History Date Modified Username FieldChange == 17-Mar-07 16:42 paul New Issue 17-Mar-07 16:42 paul Status new = assigned 17-Mar-07 16:42 paul Assigned To = paul 19-Mar-07 20:27 cmayo Note Added: 0001927 19-Mar-07 20:28 cmayo Issue Monitored: cmayo 19-Mar-07 22:11 paul Note Added: 0001928 == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
Re: [Dbmail-dev] dbmail 2.2.4 svn 2472 issue with server dropping connections on non-error
Thanks Paul,
I have no idea how this got corrupted the current 2472 svn tree seems to
work fine with regards to this issue.
-leif
On Mon, March 19, 2007 2:29 pm, Paul J Stevens wrote:
Leif,
You're tree is not in sync. This patch doesn't apply to 2472 at all.
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); }
}
Leif Jackson wrote:
This was a show stopper when I did an upgrade used svn to get the other
minor fixes, this was first talked about for dbmail 2.2.3 did this
somehow get back into svn? I found it at
http://www.mail-archive.com/dbmail-dev@dbmail.org/msg08488.html anyway
when a user was selecting their Sent mailbox is was doing a SELECT ALL
for non-seen messages and the DB sent back NULL which was correct but
the code below was disconnecting the client rather than showing 0 msgs
as not-seen..etc.
diff -urN dbmail-svn-2.2.4-2472.orig/imapcommands.c
dbmail-svn-2.2.4-2472.new/imapcommands.c ---
dbmail-svn-2.2.4-2472.orig/imapcommands.c 2007-03-17
23:21:45.0 -0400
+++ dbmail-svn-2.2.4-2472.new/imapcommands.c2007-03-19
13:37:38.0 -0400
@@ -240,7 +240,7 @@
/* show idx of first unseen msg (if present) */
if (ud-mailbox.exists) { - if (! (key =
db_first_unseen(ud-mailbox.uid))) { + if ((key =
db_first_unseen(ud-mailbox.uid)) == (u64_t) (-1)) {
dbmail_imap_session_printf(self, * BYE internal dbase error\r\n); return
-1;
}
Thanks,
Leif Jackson
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlandshttp://www.nfg.nl
___
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
[Dbmail-dev] [DBMail 0000539]: Mailclient times out opening large mailboxes
A NOTE has been added to this issue. == 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: assigned target: == Date Submitted: 17-Mar-07 16:42 CET Last Modified: 19-Mar-07 23:20 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 Issue History Date Modified Username FieldChange == 17-Mar-07 16:42 paul New Issue 17-Mar-07 16:42 paul Status new = assigned 17-Mar-07 16:42 paul Assigned To = paul 19-Mar-07 20:27 cmayo Note Added: 0001927 19-Mar-07 20:28 cmayo Issue Monitored: cmayo 19-Mar-07 22:11 paul Note Added: 0001928 19-Mar-07 23:20 cmayo Note Added: 0001929 == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
[Dbmail-dev] [DBMail 0000545]: Security hole
The following issue has been SUBMITTED. == http://www.dbmail.org/mantis/view.php?id=545 == Reported By:maenaka Assigned To: == Project:DBMail Issue ID: 545 Category: IMAP daemon Reproducibility:always Severity: block Priority: normal Status: new target: == Date Submitted: 20-Mar-07 02:08 CET Last Modified: 20-Mar-07 02:08 CET == Summary:Security hole Description: In dbmail_imap_session_handle_auth() in dbmail-imapsession.c, when auth_validate() returns -1, TRACE(TRACE_ERROR, db-validate ...) is called with the unescaped raw IMAP password along with the IMAP username. == Issue History Date Modified Username FieldChange == 20-Mar-07 02:08 maenakaNew Issue 20-Mar-07 02:08 maenakaFile Added: patch-dbmail-imapsession.c == ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
