Hi Ken,
their particular bug is that their account registration email is sent
as a base64-encoded text/html part (which SHOULD be fine) but rather
than break the base64 encoding at the recommended 76 characters, it's
all sent as one line and so an intervening SMTP server is breaking the
line at approximately 1024 characters and inserting a ! character
Sendmail used to do that when I dealt with it years ago.
which ends up breaking the base64 encoding.
Yes. Have you pointed out to them that even without producing invalid
base64, the RFC-breaking long lines raise its probability of being spam
in SpamAssassin's eyes? (Other spam detectors are available.)
There's two tests, one for just a little over, and the other for beyond
that.
https://wiki.apache.org/spamassassin/Rules/BASE64_LENGTH_78_79
https://wiki.apache.org/spamassassin/Rules/BASE64_LENGTH_79_INF
Complaints that Mellow don't keep their customers informed are only
going to be made worse if the emails end up unseen in spam folders.
If anyone has a back-channel into Mellow, please let me know!
I had a bit of a dig, but could only come up with these three people,
and no email addresses for any of them.
https://www.linkedin.com/in/joaoricardomachado/
Software Team Lead at Mellow Inc. UI/UX Designer
https://twitter.com/joaorm
https://www.facebook.com/joaoricardomachado
https://www.linkedin.com/in/pfeitor/
https://www.linkedin.com/in/analuisaamaromartins/
Android and iOS for Mellow
http://www.analuisamartins.com/
https://twitter.com/anaamaromartins
If the "supportwall" is still proving impenetrable then it might be
worth going over the top.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers