because of code-signing we digg around in secure timestamps according
to RFC 3161. This is a extension which is used to solve the problem of
expired certificates and the need to know if the certificate was valid
at time of signing.
As far as i know this would also apply to S/MIME so signed messages
can be validated even if the certificate in question is expired.
Does anybody know if this would be useful or even supported by mailclients.
If yes it may be worth to be added to Djigzo in the future?
i suppose that one of our partners has a misconfigured email infrastructure.
when trying to relay emails over djigzo, i get the following response: "5.7.1
relaying not allowed"
but if the mails are sent directly to the recipient the email went through.
i have figured out that they have two mx records
if i connect to server1 i get the message "please try again later"
if i connect to server2 i get the message "5.7.1 relaying not allowed"
so my suggestion is, that djigzo refuses the email after connecting to the
how can i change this behavior?
Transline Deutschland Dr.-Ing. Sturz GmbH