On Tue, 2006-08-01 at 14:00 +0200, Armin Größlinger wrote: > 1. duplicate References headers in mails: > > After the schema upgrade (which worked without problems) I ran > dbmail-util -ay > to generate the header caches etc. dbmail-util started giving errors 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" > ] > > Obviously, some mails have duplicate entries in the References header. I > aborted dbmail-util and changed to the dbmail_referencesfield_1 index (which > is created as "UNIQUE INDEX") _not_ to be UNIQUE which made the problem go > away.
I posted about this a few months ago, when I upgraded my main production machine, and found that Gmime was mis-parsing older messages with multipart attachments. The multipart boundary was being entered at a header name. Paul put through a fix for that and all was well. Your errors are coming from the References field. Interesting. We might need to wait for Paul to return because I don't have a strong grasp of that section of code. If your workaround is OK, then I wouldn't worry about it much :-) Aaron
