Re: Confirming SPAM/HAM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jan 29, 2007, at 2:18 PM, Torsten Stauder wrote:

> Sorry, I didn't recognize there's a new version online.
Thought  
> 1.0.2 is
> already installed on my system. Initially I started
using trunk,  
> because
> I had some problems with the stable version that didn't
occur with  
> trunk.
>
> However... 1.0.2 is running now, but the error stills
occures.
> expire-quarantine-cache.pl is executed every night. I
also ran it
> manually but unfortunately this doesn't fix the
problem. Currently  
> I've
> got 149 HAMs and 724 SPAMs as cache content.
>
> Here's the sql-trace you requested:
>
> [29-Jan-2007 21:12:50] maia: set_item_confirmations  DB
Error: already
> exists UPDATE maia_mail_recipients SET type = ?,
token=CONCAT 
> ('expired',
> recipient_id, mail_id) WHERE recipient_id = ? AND
mail_id IN
>
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?
,?,?,?,?,? 
> ,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
>


That's really odd.... of course the rows already exist.  
That's why  
it's updating...  :(

The only thing I can think of is if there are duplicate
messages when  
it updates.

I think I see a possible problem in that routine, though I'm
not sure  
it's related.

Could you look in maia_db.php for the set_item_confirmations
  
function, and change the sql_check line to this:

         sql_check($res,"set_item_confirmations",
"$update  $user_id   
" . implode(",",$mail_id) );

and see what that displays?

I'm wondering if somehow it is coming up with a duplicate
token field.



David Morton
Maia Mailguard http://www.maiamailguard
.com
mortondadgrmm.net



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFvorxUy30ODPkzl0RAgu6AKCd/C3GvLuAlL32hpJPVQdh7EXdTACg
i4fB
UmLiGIsFv+XlKYdk+0coifI=
=hI7o
-----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

Ok I did. Here's the output so far:
[30-Jan-2007 12:11:52] maia: set_item_confirmations  DB
Error: already 
exists UPDATE maia_mail_recipients SET type = ?,
token=CONCAT('expired', 
recipient_id, mail_id) WHERE recipient_id = ? AND mail_id IN

(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?
,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) 
  2 
69159,66923,72767,66994,67282,71707,69343,68857,68869,68883,
72616,72635,72652,72474,72482,72488,72502,73215,72411,72418,
72427,72345,72350,72358,72368,69162,71266,71268,71271,71272,
71274,71256,71262,71264,65554,65551,71241,71246,71249,69974,
71225,71229,71232,72993,70759,69026,71253,67422,67068,68328

But there was another strange thing: today I was able to
delete the 
first batch (50 Spams). Then the old behaviour was shown
:-(


[...]
> That's really odd.... of course the rows already exist.
  That's why 
> it's updating...  :(
> 
> The only thing I can think of is if there are duplicate
messages when it 
> updates.
> 
> I think I see a possible problem in that routine,
though I'm not sure 
> it's related.
> 
> Could you look in maia_db.php for the
set_item_confirmations  function, 
> and change the sql_check line to this:
> 
>        
sql_check($res,"set_item_confirmations",
"$update  $user_id  " . 
> implode(",",$mail_id) );
> 
> and see what that displays?
> 
> I'm wondering if somehow it is coming up with a
duplicate token field.
> 
> 
> 
> David Morton
> Maia Mailguard http://www.maiamailguard
.com
> mortondadgrmm.net
> 
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> 
>
iD8DBQFFvorxUy30ODPkzl0RAgu6AKCd/C3GvLuAlL32hpJPVQdh7EXdTACg
i4fB
> UmLiGIsFv+XlKYdk+0coifI=
> =hI7o
> -----END PGP SIGNATURE-----
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users