Unfortunately the spammers are forcing IT world to be better protected. DKIM is one of most used methods to prevent SPAM. Most of public mail service providers require the sent mail to be signed. At the moment customer must implement some 3rd party software to have DKIM signed messages. This means management from two places, not comfortable, not easy. As a workaround we recommend to use postfix and dkim milter, but it is not usable in enterprise environment.

Comments

  • Seeing that yahoo and aol now block all email we send, we have two choices: dump GroupWise or setup postfix and dkim milter. Do you have good clear detailed instructions how to do this?

  • Just for whoever may read this and draw the wrong conclusions: Nobody, and certainly not yahoo or aol block anybody for not supporting dkim. FTR: Neither Exchange nor Domino support dkim natively at this point in time.

  • massimo, do you not think, it's a good idea to start with the "idea"(!) now, to have it implemented in let's say approx. 2 years or so (especially as we all know the flood of ideas being entered within this portal and on the opposite the dev-ressources of the gw-team...), when it then "suddenly" will be wide accepted standard and used by exchange/domino/yahoo/aol/...?!
    if you start with the idea here, when others are already having the feature, - you'll be lost!

  • I did not oppose the idea per se, but the inherited statement that DKIM would be urgently necessary and that big mailservices would block mail otherwise now or in the immediate future. And especially the implied statement that Grupwise would in whatever way be behind other mailservers in that regard.

    OTOH, DKIM and all similar "solutions" in the past and in the future that require universal code changes to all currently existing MTAs in the world to be useful will inevitably fail. But that's a different story.

  • 8 months on and I think you'll find that the majority of MTAs support the receiving of DKIM signed emails and validation (SPF, DMARC, etc). In fact, some of the most major email hosting SaaS look very favourably on this and are not too far from quarantining all non-DMARC passed emails.

  • I'd like to see it also implemented in GroupWise, many of our customers are asking for it.

  • It would be a definite advantage to have DKIM in Groupwise. We pass our Email via an externally provided Baracuda spam filter which allows DKIM to be set up there.

  • The Micro Focus Enterprise Messaging (on-Prem or Cloud) offering has the DKIM feature in the SMTP transport.

  • That's a pretty misleading information. Enterprise Messaging (which doesn't even exist yet), is a bundle of many products, one of which is the former GWAVA, now Secure Messaging Gateway product, which includes DKIM even today if you purchase it separately. It changes nothing natively for Groupwise (which is still and also a part of Enterprise Messaging).

  • The Micro Focus Secure Messaging Gateway version 7 supports DKIM. This can be purchased separately or is included in Micro Focus Enterprise Messaging. https://www.microfocus.com/products/enterprise-messaging/ Enterprise Messaging is set to ship the week of Dec 11th. This is where we will support DKIM and currently do not have any plans to add it directly to the GWIA.