-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, 30 Jan 2007, Vincent Bernat wrote:
,---- | 2.10.3. Message Uniqueness in a Mailbox | | | Implementations SHOULD NOT deliver a message to the same folder more | than once, even if a script explicitly asks for a message to be | written to a mailbox twice. | | The test for equality of two messages is implementation-defined. | | If a script asks for a message to be written to a mailbox twice, it | MUST NOT be treated as an error. `----
Well, with a single invocation, the sentence "The test for equality of two messages is implementation-defined." is a non-sense since messages cannot be modified. This is why I think that the prohibition spans multiple script invocations.
Messages spooled into a mailbox may be immutable, but the same message may take different paths to arrive one particular mailbox, say, through different mailing lists or recipients, remailed or forwarded. I would _not_ like to see these duplicates discarded. However, it makes no sense to me, if the message of one delivery attempt is spooled twice into the same folder. (Actually I can imaging just one need to spool it into two boxes, hence, it could issue an overridable warning.)
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBRcBBUi9SORjhbDpvAQKwpAgAtT3DWhSu7az9sV2V/v6Fq8+TpqsXzakM BHCW+ruxT/PE/mawp/uwbESzyZChmKt5iQu1PtKnk8uFY9g76Cljpp4z8DXe1l2R +dI7zQPMqDzaEBIRgIjxJCAyxBTg3qzaViHNQRzq5B9VO8X6niETRFvxG4ncJCni TCyJyCI1wNx+Pc/aXr4EnNHbj0hbTZMkbkedaWatGat9PreJy7r4gFmz/XlgThwK 75Ii7CN/q75Nlo0qjUgQ2Di+LsEMthNnvaemxnsaHFfTkQHnzQmvoH4nWy/SnpyO dKjGtHfexiZz3oFPlDGmKTAXRPBoDLEypFL1m6vxqbU357mNWtw3Ow== =8zFc -----END PGP SIGNATURE-----