Notifications: Mails classified as spam by gmx #1150
Comments
The spamcheck on my server reports the following:
This indicated that your sending IP is on a blacklist. |
The above Email was from the verification process. The line below is from the "private message":
|
@ammoniak nice! thx for these additional informations. So it's not only the html... |
This is a good starting point: Mailgun best practises |
@Openki/contributors who would like to take some responsibility here? |
I don't have much experience with mailgun and none at all with the current openki server setup. I'm willing to help you, but someone who's familiar with the setup/configuration should have a closer look at it. |
I see two things that could improve our situation:
The first point means setting up a mailserver and reconfiguring our app to use that. Not a biggie but it means we'll be operating a mailserver. Just another service to watch. I'm also not sure it would help much. Or maybe the paid tiers get cleaner send-hosts with Mailgun, so we could just seitch to a paid version? With the second point we would lose some liberties in layout. The fact that we include an external resource is not-nice anyway. We could either include the logo or just drop it. |
@ammoniak you can get in contact with one of us to get our mailgun credentials. Though it seems to me there is not much to find out in the interface there. |
Ok. I'll give it a shot. |
Ok. After going over the entries and configuration, etc. I came to the following conclusion:
|
@ammoniak thanks for the detailed analysis. We should try removing the external reference and see whtether that improves things. |
This could help avoid spam classification. See #1150
This could help avoid spam classification. See #1150
related: #874, #802
Html mails from Openki go into spam with reason:
6 (nemesis text pattern profiler); Detail=V3;
(most other mails recognized as Junk have same text there)I think all html mails go into spam in all gmx accounts. Can someone confirm in order to define priority of this problem?
this one didn't:
The text was updated successfully, but these errors were encountered: