The following issue has been RESOLVED.
======================================================================
http://www.dbmail.org/mantis/view.php?id=398
======================================================================
Reported By: agrde
Assigned To: paul
======================================================================
Project: DBMail
Issue ID: 398
Category: Database layer
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
target:
Resolution: fixed
Fixed in Version: 2.1.8
======================================================================
Date Submitted: 18-Aug-06 23:29 CEST
Last Modified: 30-Sep-06 19:48 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.
======================================================================
----------------------------------------------------------------------
paul - 30-Sep-06 19:48
----------------------------------------------------------------------
This is fixed in rev 2284.
Issue History
Date Modified Username Field Change
======================================================================
18-Aug-06 23:29 agrde New Issue
30-Sep-06 19:48 paul Note Added: 0001428
30-Sep-06 19:48 paul Assigned To => paul
30-Sep-06 19:48 paul Status new => resolved
30-Sep-06 19:48 paul Resolution open => fixed
30-Sep-06 19:48 paul Fixed in Version => 2.1.8
======================================================================