Bug#448519: marked as done (libdspam7-drv-mysql: CVE-2007-6418 cron job may disclose dspam database password to users)

2008-07-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Jul 2008 09:40:28 + with message-id [EMAIL PROTECTED] and subject line Bug#448519: fixed in dspam 3.6.8-5etch1 has caused the Debian Bug report #448519, regarding libdspam7-drv-mysql: CVE-2007-6418 cron job may disclose dspam database password to users to be marked

Bug#448519: marked as done (libdspam7-drv-mysql: CVE-2007-6418 cron job may disclose dspam database password to users)

2008-04-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Apr 2008 19:52:26 + with message-id [EMAIL PROTECTED] and subject line Bug#448519: fixed in dspam 3.6.8-5etch1 has caused the Debian Bug report #448519, regarding libdspam7-drv-mysql: CVE-2007-6418 cron job may disclose dspam database password to users to be marked

Bug#448519: marked as done (libdspam7-drv-mysql: CVE-2007-6418 cron job may disclose dspam database password to users)

2008-01-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Jan 2008 14:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#448519: fixed in dspam 3.6.8-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#448519: marked as done (libdspam7-drv-mysql: CVE-2007-6418 cron job may disclose dspam database password to users)

2008-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2008 17:47:03 + with message-id [EMAIL PROTECTED] and subject line Bug#448519: fixed in dspam 3.6.8-5.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now