Hello, good afternoon.
I would like to ask a question. In Roundcube, I have the options for Delivery Receipt and Read Confirmation.
The Read Confirmation is working normally, but the Delivery Receipt is not working.
Can you help me enable this service? I read in some forums that this can potentially compromise the server due to spam issues. Could someone with more experience explain the reason?
If it is not insecure, I would like to enable it.
Thank you, everyone.
Hi @molero.renan,
A Delivery Receipt must be configured in the recipient’s mail server and most of them don’t do it.
You could configure Exim to answer to these requests (it’s a header in the message) but it could be “useful” to people sending mail to your users but not for your users sending mails to another mail servers.
Said that, I don’t like it, there is no need to send delivery receipts, if the mail server didn’t bounce the message, that was delivered (another thing will be that the message will be read, discarded, moved to spam…) but the mail was delivered. Also, implementing it in your server will confirm the existence of a user with that mail address and maybe that info could be used by spammers to create “better” victim’s mail lists.
Thank you very much.
It really doesn’t make much sense to enable the delivery receipt. I will even remove this option from my Roundcube.
I appreciate it a lot, your response was very enlightening. Thank you again.
Whether it is necessary to receive the exim4 notification that you successfully delivered the email or not. If you use email to play games it is one thing, but when you use it professionally it is necessary to legally prove that it was sent to you, this legal risk is complicating, I don’t know if I was clear because of the language barrier. Please be professional and respond because the international RFC standard for DSN is not met?.
It isn’t 
I’m sorry but legally, a mail delivery notification means nothing, maybe you can receive a delivery notification if you are lucky and recipient’s mail server implements it, but that doesn’t mean that the mail was received by the recipient, just that the mail server received it and that means nothing. Also, doesn’t proof what was the content of the message that was delivered.
If you want proof, save the sent email and the logs from your own mail server… but again, that only means that the other mail server received the message, that’s all.
If you implement DSN in your mail server you should follow the guidelines of the corresponding RFC but that DSN RFC IS NOT mandatory to operate a mail server, indeed, most of the mail servers out there don’t implement it.
That said, nobody prevents you from implementing it on your mail server.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.