hi Ives,
I think the database way should be best for this problem - I know the problems your talking about and the current mail concept made me some headaches too....
Suggestion: As there (should...) be one "ready" and one crin mail for each certificate, why not just extend the certificate table by two columns to store the prepared mails. Eventually we can even create the mails directly on the RA when sending the messages out, so we dont need to store this at all and just have to add a flag "user notified"
I dont see any advantage in storing the mail somewhere, instead of create and send them in one step
Oli -- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72
smime.p7s
Description: S/MIME Cryptographic Signature
