Mailing List Archive

Not=now



Paul,



Is there something that I can do to confirm that the queries are being
executed?

I was testing this on another machine with 3.2.0 and dbmail-util has no
effect also,



From: dbmail-bounces@dbmail.org [mailto:dbmail-bounces@dbmail.org] On Behalf
Of Jorge Bastos
Sent: domingo, 2 de Novembro de 2014 12:50
To: 'DBMail mailinglist'
Subject: [Dbmail] dbmail-util 3.1.17 not cleaning deleted emails



Hi,



Just upgraded to 3.1.17, and not dbmail-util is not cleaning up emails.



I'm cleaning as before, with:



/usr/local/sbin/dbmail-util -d -y

/usr/local/sbin/dbmail-util -p -y

/usr/local/sbin/dbmail-util -ty



Is there any sintax change or may be an issue?

Both 3 commands say that are 0 messages.





PS: Sent this do the -dev list but was not received,

Paul,



I confirm this.

Using the dbmail-util binary from 2.3.7 from my previous version, against
the DB of 3.1.17 (which has no relevant schema changes) it run's fine and
deletes messages.



Let me know what I can do to help on this.



From: dbmail-bounces@dbmail.org [mailto:dbmail-bounces@dbmail.org] On Behalf
Of Jorge Bastos
Sent: domingo, 2 de Novembro de 2014 13:30
To: 'DBMail mailinglist'
Subject: Re: [Dbmail] dbmail-util 3.1.17 not cleaning deleted emails



Not=now



Paul,



Is there something that I can do to confirm that the queries are being
executed?

I was testing this on another machine with 3.2.0 and dbmail-util has no
effect also,



From: dbmail-bounces@dbmail.org [mailto:dbmail-bounces@dbmail.org] On Behalf
Of Jorge Bastos
Sent: domingo, 2 de Novembro de 2014 12:50
To: 'DBMail mailinglist'
Subject: [Dbmail] dbmail-util 3.1.17 not cleaning deleted emails



Hi,



Just upgraded to 3.1.17, and not dbmail-util is not cleaning up emails.



I'm cleaning as before, with:



/usr/local/sbin/dbmail-util -d -y

/usr/local/sbin/dbmail-util -p -y

/usr/local/sbin/dbmail-util -ty



Is there any sintax change or may be an issue?

Both 3 commands say that are 0 messages.





PS: Sent this do the -dev list but was not received,

Am 02.11.2014 um 16:23 schrieb Jorge Bastos:
> Paul,
>
>
>
> I confirm this.
>
> Using the dbmail-util binary from 2.3.7 from my previous version,
> against the DB of 3.1.17 (which has no relevant schema changes) it run’s
> fine and deletes messages.
>
>
>
> Let me know what I can do to help on this.
>

I was just testing this here because i was curious (3.2.0 here):


you can use strace to see what SQL statements are issued:

strace -s 100 -a 160 -e trace=sendto dbmail-util -v -y -dp

will give you something like this:

....
Deleting messages with DELETE status...
sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
MSG_NOSIGNAL, NULL, 0)
= 38
sendto(3, "Q\0\0\0\27BEGIN TRANSACTION;\0", 24, MSG_NOSIGNAL, NULL, 0)

= 24
sendto(3, "Q\0\0\0/DELETE FROM dbmail_messages WHERE status=3\0", 48,
MSG_NOSIGNAL, NULL, 0)
= 48
sendto(3, "Q\0\0\0\30COMMIT TRANSACTION;\0", 25, MSG_NOSIGNAL, NULL, 0)

= 25
sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36, MSG_NOSIGNAL,
NULL, 0)
= 36
Ok. Messages deleted.

Setting DELETE status for deleted messages...
sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
MSG_NOSIGNAL, NULL, 0)
= 38
sendto(3, "Q\0\0\0\27BEGIN TRANSACTION;\0", 24, MSG_NOSIGNAL, NULL, 0)

= 24
sendto(3, "Q\0\0\0;UPDATE dbmail_messages SET status = 3 WHERE status =
2\0", 60, MSG_NOSIGNAL, NULL, 0)
= 60
sendto(3, "Q\0\0\0\30COMMIT TRANSACTION;\0", 25, MSG_NOSIGNAL, NULL, 0)

= 25
sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36, MSG_NOSIGNAL,
NULL, 0)
= 36
Ok. Messages set for deletion.
Re-calculating used quota for all users...
sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
MSG_NOSIGNAL, NULL, 0)
= 38
sendto(3, "Q\0\0\1\316SELECT usr.user_idnr, SUM(pm.messagesize),
usr.curmail_size FROM dbmail_users usr LEFT JOIN dbm"..., 463,
MSG_NOSIGNAL, NULL, 0) = 463
sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36, MSG_NOSIGNAL,
NULL, 0)
= 36
Ok. Used quota updated for all users.
....

so what i did was check the status field in dbmail_messages before deleting,
-) after deleting (in thunderbird) => status 2
-) then after running dbmail-util to mark the deleted messages =>
status 2->3
-) after dbmail-util pruning => messages are gone

so it seems to work here.

anyway with that strace command you can debug the SQL commands easier
than setting some logging in the DB (which of course would be for more
than one executable then).

Hope this helps.

Regards
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Hi Thomas,

> you can use strace to see what SQL statements are issued:
>
> strace -s 100 -a 160 -e trace=sendto dbmail-util -v -y -dp
>
> will give you something like this:
>
> ....
> Deleting messages with DELETE status...
> sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
> MSG_NOSIGNAL, NULL, 0)
> = 38
> sendto(3, "Q\0\0\0\27BEGIN TRANSACTION;\0", 24, MSG_NOSIGNAL, NULL, 0)
>
> = 24
> sendto(3, "Q\0\0\0/DELETE FROM dbmail_messages WHERE status=3\0", 48,
> MSG_NOSIGNAL, NULL, 0)
> = 48
> sendto(3, "Q\0\0\0\30COMMIT TRANSACTION;\0", 25, MSG_NOSIGNAL, NULL, 0)
>
> = 25
> sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36, MSG_NOSIGNAL,
> NULL, 0)
> = 36
> Ok. Messages deleted.
>
> Setting DELETE status for deleted messages...
> sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
> MSG_NOSIGNAL, NULL, 0)
> = 38
> sendto(3, "Q\0\0\0\27BEGIN TRANSACTION;\0", 24, MSG_NOSIGNAL, NULL, 0)
>
> = 24
> sendto(3, "Q\0\0\0;UPDATE dbmail_messages SET status = 3 WHERE status =
> 2\0", 60, MSG_NOSIGNAL, NULL, 0)
> = 60
> sendto(3, "Q\0\0\0\30COMMIT TRANSACTION;\0", 25, MSG_NOSIGNAL, NULL, 0)
>
> = 25
> sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36, MSG_NOSIGNAL,
> NULL, 0)
> = 36
> Ok. Messages set for deletion.
> Re-calculating used quota for all users...
> sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
> MSG_NOSIGNAL, NULL, 0)
> = 38
> sendto(3, "Q\0\0\1\316SELECT usr.user_idnr, SUM(pm.messagesize),
> usr.curmail_size FROM dbmail_users usr LEFT JOIN dbm"..., 463,
> MSG_NOSIGNAL, NULL, 0) = 463
> sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36, MSG_NOSIGNAL,
> NULL, 0)
> = 36
> Ok. Used quota updated for all users.
> ....
>
> so what i did was check the status field in dbmail_messages before
> deleting,
> -) after deleting (in thunderbird) => status 2
> -) then after running dbmail-util to mark the deleted messages =>
> status 2->3
> -) after dbmail-util pruning => messages are gone
>
> so it seems to work here.
>
> anyway with that strace command you can debug the SQL commands easier
> than setting some logging in the DB (which of course would be for more
> than one executable then).

In fact I was thinking in a way to the SQL executed by -util but the only
way I figured out yet was the sql logs but during work hours it's almost
impossible to retrieve them, and the only change is to get them at very late
hours.

Haven't thinked in strace yet, but thanks for the tip :)
Will do and post.

Thanks,


_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Thomas, Paul,

Found it, strace was useful, I could see that by default without specifying
-f /etc/dbmail.conf it's reading the defaults in /usr/local/etc/dbmail.conf.
In previous dbmail-util in ~2.3.6 it was reading by default
/etc/dbmail.conf.

Paul,

Don't know how you want the behavior, so here's the info for you to
consider.
For me, I'm going to specify -f to solve it for me.


> -----Original Message-----
> From: dbmail-bounces@dbmail.org [mailto:dbmail-bounces@dbmail.org] On
> Behalf Of Jorge Bastos
> Sent: quinta-feira, 6 de Novembro de 2014 09:42
> To: 'DBMail mailinglist'
> Subject: Re: [Dbmail] dbmail-util 3.1.17 not cleaning deleted emails
>
> Hi Thomas,
>
> > you can use strace to see what SQL statements are issued:
> >
> > strace -s 100 -a 160 -e trace=sendto dbmail-util -v -y -dp
> >
> > will give you something like this:
> >
> > ....
> > Deleting messages with DELETE status...
> > sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
> > MSG_NOSIGNAL, NULL, 0)
> > = 38
> > sendto(3, "Q\0\0\0\27BEGIN TRANSACTION;\0", 24, MSG_NOSIGNAL, NULL,
> 0)
> >
> > = 24
> > sendto(3, "Q\0\0\0/DELETE FROM dbmail_messages WHERE status=3\0", 48,
> > MSG_NOSIGNAL, NULL, 0)
> > = 48
> > sendto(3, "Q\0\0\0\30COMMIT TRANSACTION;\0", 25, MSG_NOSIGNAL, NULL,
> > 0)
> >
> > = 25
> > sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36,
> > MSG_NOSIGNAL, NULL, 0)
> > = 36
> > Ok. Messages deleted.
> >
> > Setting DELETE status for deleted messages...
> > sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
> > MSG_NOSIGNAL, NULL, 0)
> > = 38
> > sendto(3, "Q\0\0\0\27BEGIN TRANSACTION;\0", 24, MSG_NOSIGNAL, NULL,
> 0)
> >
> > = 24
> > sendto(3, "Q\0\0\0;UPDATE dbmail_messages SET status = 3 WHERE status
> > = 2\0", 60, MSG_NOSIGNAL, NULL, 0)
> > = 60
> > sendto(3, "Q\0\0\0\30COMMIT TRANSACTION;\0", 25, MSG_NOSIGNAL, NULL,
> > 0)
> >
> > = 25
> > sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36,
> > MSG_NOSIGNAL, NULL, 0)
> > = 36
> > Ok. Messages set for deletion.
> > Re-calculating used quota for all users...
> > sendto(3, "Q\0\0\0%SET statement_timeout TO 300000;\0", 38,
> > MSG_NOSIGNAL, NULL, 0)
> > = 38
> > sendto(3, "Q\0\0\1\316SELECT usr.user_idnr, SUM(pm.messagesize),
> > usr.curmail_size FROM dbmail_users usr LEFT JOIN dbm"..., 463,
> > MSG_NOSIGNAL, NULL, 0) = 463
> > sendto(3, "Q\0\0\0#SET statement_timeout TO 3000;\0", 36,
> > MSG_NOSIGNAL, NULL, 0)
> > = 36
> > Ok. Used quota updated for all users.
> > ....
> >
> > so what i did was check the status field in dbmail_messages before
> > deleting,
> > -) after deleting (in thunderbird) => status 2
> > -) then after running dbmail-util to mark the deleted messages =>
> > status 2->3
> > -) after dbmail-util pruning => messages are gone
> >
> > so it seems to work here.
> >
> > anyway with that strace command you can debug the SQL commands easier
> > than setting some logging in the DB (which of course would be for
> more
> > than one executable then).
>
> In fact I was thinking in a way to the SQL executed by -util but the
> only way I figured out yet was the sql logs but during work hours it's
> almost impossible to retrieve them, and the only change is to get them
> at very late hours.
>
> Haven't thinked in strace yet, but thanks for the tip :) Will do and
> post.
>
> Thanks,
>
>
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Am 06.11.2014 um 23:37 schrieb Jorge Bastos:
> Found it, strace was useful, I could see that by default without specifying
> -f /etc/dbmail.conf it's reading the defaults in /usr/local/etc/dbmail.conf

which is correct if you use prefix=/usr/local for build

> In previous dbmail-util in ~2.3.6 it was reading by default
> /etc/dbmail.conf.

AFAIR intentional

> Don't know how you want the behavior, so here's the info for you to
> consider. For me, I'm going to specify -f to solve it for me

why don't you move the pysical file to /usr/local/etc/dbmail.conf and
make a symlink in /etc/ to avoid that?

> Am 06.11.2014 um 23:37 schrieb Jorge Bastos:
> > Found it, strace was useful, I could see that by default without
> > specifying -f /etc/dbmail.conf it's reading the defaults in
> > /usr/local/etc/dbmail.conf
>
> which is correct if you use prefix=/usr/local for build
>
> > In previous dbmail-util in ~2.3.6 it was reading by default
> > /etc/dbmail.conf.
>
> AFAIR intentional
>
> > Don't know how you want the behavior, so here's the info for you to
> > consider. For me, I'm going to specify -f to solve it for me
>
> why don't you move the pysical file to /usr/local/etc/dbmail.conf and
> make a symlink in /etc/ to avoid that?

Reindl,

Don't like allot of symlinks...
That was the reason to leave SuSE (along with RPM's) back in 1999/2000 and
move to Debian!
But yes, I may start configure'ing it with --sysconfdir=/etc

_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Am 07.11.2014 um 22:23 schrieb Jorge Bastos:
>> Am 06.11.2014 um 23:37 schrieb Jorge Bastos:
>>> Found it, strace was useful, I could see that by default without
>>> specifying -f /etc/dbmail.conf it's reading the defaults in
>>> /usr/local/etc/dbmail.conf
>>
>> which is correct if you use prefix=/usr/local for build
>>
>>> In previous dbmail-util in ~2.3.6 it was reading by default
>>> /etc/dbmail.conf.
>>
>> AFAIR intentional
>>
>>> Don't know how you want the behavior, so here's the info for you to
>>> consider. For me, I'm going to specify -f to solve it for me
>>
>> why don't you move the pysical file to /usr/local/etc/dbmail.conf and
>> make a symlink in /etc/ to avoid that?
>
> Don't like allot of symlinks...

that's no technical qualified reason

> That was the reason to leave SuSE (along with RPM's) back in 1999/2000 and
> move to Debian!
> But yes, I may start configure'ing it with --sysconfdir=/etc

or just accept if you use --prefix=/somewhere the install layout starts
there and /somewhere/etc, /somewhere/bin are the expected locations

hence i build always packages and so just use prefix=/usr

> >>> Don't know how you want the behavior, so here's the info for you to
> >>> consider. For me, I'm going to specify -f to solve it for me
> >>
> >> why don't you move the pysical file to /usr/local/etc/dbmail.conf
> and
> >> make a symlink in /etc/ to avoid that?
> >
> > Don't like allot of symlinks...
>
> that's no technical qualified reason

For me, links are garbage :)
Why have links when I can have direct locations.

_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Am 08.11.2014 um 17:01 schrieb Jorge Bastos:
>>>>> Don't know how you want the behavior, so here's the info for you to
>>>>> consider. For me, I'm going to specify -f to solve it for me
>>>>
>>>> why don't you move the pysical file to /usr/local/etc/dbmail.conf
>> and
>>>> make a symlink in /etc/ to avoid that?
>>>
>>> Don't like allot of symlinks...
>>
>> that's no technical qualified reason
>
> For me, links are garbage :)

sounds like a windows user :-)

> Why have links when I can have direct locations

why enter long path's if i can have symlinks?
below a typical root home for me

* login
* nano dbmail.conf

drwx------ 2 root root 4,0K 2014-10-16 13:24 scripts
lrwxrwxrwx 1 root root 15 2010-01-29 16:48 conf -> /etc/httpd/conf
lrwxrwxrwx 1 root root 10 2011-02-02 12:45 fstab -> /etc/fstab
lrwxrwxrwx 1 root root 41 2009-12-30 17:38 ifcfg-eth0 ->
/etc/sysconfig/network-scripts/ifcfg-eth0
lrwxrwxrwx 1 root root 41 2009-12-30 18:06 ifcfg-eth1 ->
/etc/sysconfig/network-scripts/ifcfg-eth1
lrwxrwxrwx 1 root root 31 2013-02-23 21:09 _logs ->
/Volumes/dune/www-servers/_logs
lrwxrwxrwx 1 root root 16 2009-12-30 18:41 maillog -> /var/log/maillog
lrwxrwxrwx 1 root root 17 2008-11-15 03:20 messages -> /var/log/messages
lrwxrwxrwx 1 root root 30 2010-03-26 00:04 repo ->
/Volumes/dune/buildserver/repo
lrwxrwxrwx 1 root root 15 2009-12-30 19:12 secure -> /var/log/secure
lrwxrwxrwx 1 root root 29 2009-12-30 19:24 sites_enabled ->
/etc/httpd/conf/sites_enabled
lrwxrwxrwx 1 root root 19 2011-06-16 00:08 systemd-services ->
/lib/systemd/system
lrwxrwxrwx 1 root root 20 2012-03-23 10:20 main.cf ->
/etc/postfix/main.cf
lrwxrwxrwx 1 root root 22 2012-03-23 10:20 master.cf ->
/etc/postfix/master.cf
lrwxrwxrwx 1 root root 28 2014-10-17 16:42 clam-milter.conf ->
/etc/mail/clamav-milter.conf
lrwxrwxrwx 1 root root 38 2014-10-17 16:43 clam-milter-whitelist.conf
-> /etc/mail/clamav-milter-whitelist.conf
lrwxrwxrwx 1 root root 22 2014-10-17 16:43 clam-scan.conf ->
/etc/clamd.d/scan.conf
lrwxrwxrwx 1 root root 16 2012-02-23 19:23 dbmail.conf ->
/etc/dbmail.conf
lrwxrwxrwx 1 root root 25 2012-02-23 19:18 dovecot.conf ->
/etc/dovecot/dovecot.conf
lrwxrwxrwx 1 root root 25 2010-10-20 16:14 openvpn.conf ->
/etc/openvpn/openvpn.conf
lrwxrwxrwx 1 root root 39 2014-01-31 13:38 proxy-ssl-certs.conf ->
/etc/trafficserver/ssl_multicert.config
lrwxrwxrwx 1 root root 17 2012-06-05 18:38 rsyslog.conf ->
/etc/rsyslog.conf
lrwxrwxrwx 1 root root 31 2014-10-17 16:43 spamd-local.conf ->
/etc/mail/spamassassin/local.cf
lrwxrwxrwx 1 root root 42 2014-10-17 16:43 spamd-milter.conf ->
/etc/systemd/system/spamass-milter.service
lrwxrwxrwx 1 root root 16 2012-05-21 17:29 sysctl.conf ->
/etc/sysctl.conf
lrwxrwxrwx 1 root root 33 2013-08-01 17:15 records.config ->
/etc/trafficserver/records.config
lrwxrwxrwx 1 root root 31 2013-08-01 17:41 remap.config ->
/etc/trafficserver/remap.config
lrwxrwxrwx 1 root root 25 2013-03-30 21:38 modsecurity.d ->
/etc/httpd/modsecurity.d/
lrwxrwxrwx 1 root root 18 2013-08-01 17:42 hosts.dnsmasq ->
/etc/hosts.dnsmasq
lrwxrwxrwx 1 root root 19 2012-02-10 17:57 dbmail.err ->
/var/log/dbmail.err
lrwxrwxrwx 1 root root 23 2010-02-05 05:12 php-apache.ini ->
/etc/httpd/conf/php.ini
lrwxrwxrwx 1 root root 12 2011-02-09 01:22 php-cli.ini -> /etc/php.ini
lrwxrwxrwx 1 root root 49 2009-12-23 12:10 apache_access.log ->
/Volumes/dune/www-servers/_logs/apache_access.log
lrwxrwxrwx 1 root root 48 2009-12-23 12:10 apache_error.log ->
/Volumes/dune/www-servers/_logs/apache_error.log
lrwxrwxrwx 1 root root 21 2014-10-16 13:24 firewall.log ->
/var/log/firewall.log
lrwxrwxrwx 1 root root 47 2009-12-30 16:44 mysql_error.log ->
/Volumes/dune/www-servers/_logs/mysql_error.log
lrwxrwxrwx 1 root root 47 2013-06-18 13:45 mysql_query.log ->
/Volumes/dune/www-servers/_logs/mysql_query.log
lrwxrwxrwx 1 root root 52 2009-12-30 16:44 mysql_slow_query.log ->
/Volumes/dune/www-servers/_logs/mysql_slow_query.log
lrwxrwxrwx 1 root root 45 2009-12-23 12:01 php_error.log ->
/Volumes/dune/www-servers/_logs/php_error.log
lrwxrwxrwx 1 root root 29 2013-05-12 02:43 roundcube_errors.log ->
/var/log/roundcubemail/errors
lrwxrwxrwx 1 root root 22 2014-10-19 11:31 sa-update.log ->
/var/log/sa-update.log
lrwxrwxrwx 1 root root 32 2013-10-05 19:23 trafficserver.log ->
/var/log/trafficserver/diags.log
lrwxrwxrwx 1 root root 16 2008-11-26 10:28 yum.log -> /var/log/yum.log
lrwxrwxrwx 1 root root 26 2014-01-30 20:55 iptables.sh ->
/usr/local/bin/iptables.sh
-rw-r--r--. 1 root root 13K 2014-07-23 23:09 packages.txt