A couple of customers use Orcon and have had issues with mails getting delivered. Both times they've noticed that Orcon has flagged their mails as spam using DSPAM, and suggested that this may be the cause.
This raised a few questions for me, and I'd love to get some informed answers from the Orcon tech team.
1. What benefits are there for Orcon customers in having some emails be marked as spam without notification?
2. Does outbound spam flagging provide any meaningful data to remote systems?
Presumably if any remote system trusted another host's spam assessment, every spambot would add headers flagging mails as NOT SPAM before sending it. I don't see why any mail host would believe the labels applied by a remote system (unless it was specifically told to trust that system).
3. If the idea is to protect the Orcon network reputation by reducing spam, why even deliver emails which are flagged as spam?
4. Wouldn't it make more sense to notify customers that their IP had sent emails which appeared to be spam, either by refusing to send the messages, or by quarantining / flagging and delivering a notification to the account holder or sender?
5. If nothing else, wouldn't it help to engage the X-DSPAM-factors header for outbound mail? That way customers who are flagged as spam can learn that the issue is with their ADSL IP address being blacklisted, or their email containing suspicious keywords, or whatever.
I do understand that protecting the ISPs reputation is important, and that there may be situations or reasons I'm unaware of.
I also realise that there may be other reasons for mail not being delivered, even which are unrelated to the DSPAM headers Orcon adds sometimes.
I hope to learn why this current situation exists, and to ask whether it's the best possible arrangement for Orcon customers.
I'd also like to know which (if any) ISPs add spam detection headers to outbound messages. Is it common practice?