> > > It seems like the only advantage of that preferential ordering is for > the > > snmp counter, as the 'rid' return value from that query is not used > > anywhere else, and the other 4 return values are all from the msgs table > > (static for multiple recipients).. Unless I'm missing something, I'm > happy > > here. > > You are missing the point. There may be multiple msgs records > matching a current mail message, some may match by mail address only, > some may match by message-id only, and some by both. The relevant > piece of information is msgs.time_num, which serves to compute age > and subsequently score points. It is desirable to match the most > relevant message from the history, even if it is older than > some other more loose match. > > Mark, well, I was busy typing up on how I am not 100% understanding the scenario where a lookup can have multiple message-ids.. (I could picture multiple msgs entries for a single message-id where some client split up the multi-recipient transfer, but even then the difference in time_num would be negligible (compared to the default half-life of a week!). So, the rid-preference seems to come into play when multiple message-ids are used in the lookup.)
Then something prompted me to examine the headers of your reply! There it was. So, in a type of email with a conversation thread history that could span days, even weeks, preferential treatment to the referenced message-id that actually matches the email address in question. nice to end the week on an enlightening note. thanks for the help! Riaan ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
