Ok, now I understand. Dbmail should be fixed here. Please file a bug if you don't mind, so we can start tracking and fixing this before 2.1.8/2.2.0
Armin Größlinger wrote: > Hello, > > another note on the duplicate References fields I saw when I ran > dbmail-util -ay > on my upgrade to DBMail 2.1.7. I got error messages like > > Error dbpgsql.c, db_query: Error executing query [INSERT INTO > dbmail_referencesfield (physmessage_id, referencesfield) VALUES > (4933,'[EMAIL PROTECTED]')] : > [ERROR: duplicate key violates unique constraint > "dbmail_referencesfield_1" > ] > > I don't think it is Gmime mis-parsing the message. Looking at > dbmail_messageblks, it turned out that the mail in question is not multipart, > but contains > > References: <[EMAIL PROTECTED]> > <[EMAIL PROTECTED]> > > in its header, i.e., the same value for the References field is listed twice > in > the mail, so I think Gmime is right to return that value twice. But > dbmail-util > should not insert the value twice into the index dbmail_referencesfield_1 when > it is created as UNIQUE. To my understanding, either the index shouldn't be > UNIQUE or DBMail should make sure not to insert the same value for the > References field more than once, right? > > Regards, > Armin > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
