The following issue has been SUBMITTED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=398 
====================================================================== 
Reported By:                agrde
Assigned To:                
====================================================================== 
Project:                    DBMail
Issue ID:                   398
Category:                   Database layer
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
target:                      
====================================================================== 
Date Submitted:             18-Aug-06 23:29 CEST
Last Modified:              18-Aug-06 23:29 CEST
====================================================================== 
Summary:                    Duplicate values in References field cause
transaction failures
Description: 
Some mail clients construct mails which contain duplicate values in the
References header, like

   References: <[EMAIL PROTECTED]>
               <[EMAIL PROTECTED]>

Duplicate values are inserted more than once into the
dbmail_referencesfield table. This causes the transaction to fail because
the index (dbmail_referencesfield_1 in PostgreSQL schema) is created as
UNIQUE:

   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"
     ]

Therefore, duplicate values should not be inserted more than once.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
18-Aug-06 23:29 agrde          New Issue                                    
======================================================================

Reply via email to