Fork me on GitHub

DKIM Support?  Bottom

  • When sending out newsletters from my Zikula-based community site I've found that they don't get through (not even as far as a spam email box) to Yahoo email accounts. Significant investigation later shows that this is likely down to Yahoo using DomainKeys to filter potential spam. Is there any chance of adding DKIM support to mailer because it looks like, without it, newsletters simply won't get through to a significant proportion of the userbase.

    There is a PHP implementation of it on Sourceforge that looks like it could be reasonably simple to integrate into mailer for someone with familiarity of the codebase: http://sourceforge.net/projects/php-dkim/files/
  • Thought that was somethign that had to be set on the system, not in the app.

    --
    Home Page | Find on Facebook | Follow on Twitter
  • Domain keys are one of those useless anti spam technics, where more false positives are created than spam is reduced.
    Instead tell Yahoo to drop it, or let your users go to another email provider.
    Greetings,
    Chris

    --
    an operating system must operate
    development is life
    my repo
  • HalbrookTech

    Thought that was somethign that had to be set on the system, not in the app.

    It requires a key to be entered into the mail headers and this is then compared to one entered into your DNS information. That's why it needs the code mod too sadly. The system that Microsoft use for live mail (SenderID) just requires the DNS stuff so was no problem.

    slam

    Domain keys are one of those useless anti spam technics, where more false positives are created than spam is reduced.
    Instead tell Yahoo to drop it, or let your users go to another email provider.

    I completely agree that such systems are a waste of time. I wouldn't mind if they just moved the emails into the user's junk directory but sadly they have taken it upon themselves to be the overlords of what their users can and cannot have in their inboxes. Telling Yahoo to drop it would be a waste of time and effort and telling users to go to another email provider just because my CMS of choice doesn't support this is far from reasonable. We build community sites for the community and demanding they leave one of the world's biggest email providers simply because we don't support their anti-spam tech is just as bad as Yahoo including such a ridiculous system in the first place.

This list is based on users active over the last 60 minutes.