I'm trying to fix an issue with an email in my own system, it's from Google Maps. When my import script works it doesn't import a style attribute on the second table element in the email. However when I view the raw email in RoundCube the style attribute is present.
To add further complications I can't find the raw email message in the file system:
grep -r "c0fc8624ffa42b5..." / -s
That is an issue with Dovecot somehow. So while I figure out which deep dark dank cave has a computer with IRC access so I can ask them a question I have a question here:
Does RoundCube have any established policies to "fix" emails, at least from major providers, that are too lazy or incompetent to fix themselves?
Again, I'm trying to cover all bases while I deal with Dovecot having the email but not the file system (because that makes perfect sense 🙄�). Thank you in advance.
Well, it turns out that somehow my mail system is deleting the style attribute. Some Dovecot commands I learned in IRC:
Dovecot version:
dovecot --version Search (will output hash and UID to use in third command):
doveadm search -u [email protected] MAILBOX INBOX HEADER Message-ID '<[email protected]>'Echo raw message:
doveadm fetch -u [email protected] body mailbox-guid 674b4221102d7d66fd3900006dd16ccc uid 2354The HexChat IRC client worked in case anyone else is having trouble figuring out a free/working IRC client in 2025 to get Dovecot support.
For the sake of others who will come across this thread, I suppose my question still remains valid: does RoundCube modify email contents for any reason e.g. to fix compatibility issues)?
Roundcube "washes" HTML content of emails before rendering. This process has a few different functions. First security, preventing XSS and warning or blocking references to external resources for example. It also does things like ensure any IDs or class names used in the message are unique - Roundcube is web based so element identifiers used in the message should not clash with the application.