I’ve been testing out nextcloud calendar’s “meeting proposals” feature, and am really liking it! One thing I noticed however is that the email notifications are landing in spam for one of my test email addresses.
I did a mail-tester.com test and was informed that the email was just about perfect (8.7/10) but the “Dear foo@bar” heading was flagged by spamassassin, docking 1.499 points:
-1.499 DEAR_EMAIL Message contains Dear email address -0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid This rule is automatically applied if your email contains a DKIM signature but other positive rules will also be added if your DKIM signature is valid. See immediately below. 0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Great! Your signature is valid 0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author’s domain Great! Your signature is valid and it’s coming from your domain name 0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.001 HTML_MESSAGE HTML included in message No worry, that’s expected if you send HTML emails -0.001 SPF_HELO_NONE SPF: HELO does not publish an SPF Record 0.001 SPF_PASS SPF: sender matches SPF record Great! Your SPF is valid
It also flagged some other small issues:
- html is weighty - only 10% of the message content is actual text
- no list-unsubscribe header
My personal feeling is that the notifications are indeed a bit heavy on html just for a calendar notification. The template could be redesigned to be simpler, free of html and less clunky.
And yes, the “Dear foo@bar, a proposed meeting has been updated” does come across as spammy, especially if the recipient has never seen it before which is possible given this can be sent to an external email address being invited to a nextcloud calendar event.