Michael Peddemors
2022-Jan-03 14:47 UTC
feature-request: make received-header on submission optional or at least drop the ip in it
On 2022-01-01 11:04 a.m., dc-ml at dvl.werbittewas.de wrote:> because the client-ip is covered by GDPR as personal data and so it > should never shown to others without a certain reason, we want to hide > it, but there's no "submission_add_received_header"-option like for lmtp > and it doesn't seem to be any other option to hide this information.Using your email system IS the reason, simply make sure that you inform customers why this is presented. The world will thank you ;) Sorry, but while an IP has been described as personal data in various privacy legislation, just like to stop the spreading of misinformation that you 'cannot' include that information. You can include personal information, as long as the person is aware (SLA, Terms and Conditions etc) and it has a valid use, eg for security purposes. Oh, but no flames please, this is almost getting off topic as it is. -- "Catch the Magic of Linux..." ------------------------------------------------------------------------ Michael Peddemors, President/CEO LinuxMagic Inc. Visit us at http://www.linuxmagic.com @linuxmagic A Wizard IT Company - For More Info http://www.wizard.ca "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd. ------------------------------------------------------------------------ 604-682-0300 Beautiful British Columbia, Canada This email and any electronic data contained are confidential and intended solely for the use of the individual or entity to which they are addressed. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company.
dc-ml at dvl.werbittewas.de
2022-Jan-03 15:15 UTC
feature-request: make received-header on submission optional or at least drop the ip in it
Am 03.01.22 um 15:47 schrieb Michael Peddemors:> Using your email system IS the reason, simply make sure that you informno, it's not. and:> (SLA, Terms and Conditions etc) and it has a valid use, eg for security > purposes.for security_reasons it's completly ok, to store this information *locally* on the server for some time, but not to push this information together with date+time towards the world. sorry, if you don't have an idea of privacy-needs, you should not post about this topic and then say something about "no flames please"...> Oh, but no flames please, this is almost getting off topic as it is.well, then let's come back to the origin topic. There's an need for it (as I noticed meanwhile at least back to 2019: https://dovecot.org/pipermail/dovecot/2019-August/116865.html ) and until it breaks no existing thing (which is expected due to *optional* settings ), there's no reason to discuss about that need itself. ( You won't be forced to enable it for Your mail-server ) @others: due to the importance of it for us, I'm currently trying to implement it, but because that's my first deeper view in dovecots code, maybe I'll need some help. d.