dkim

Firstly, I AM NOT A SPAMMER :) I am a legitimate developer, working for a company who is currently developing an enewsletter sending system for our clients. Now, we sent out a campaign for one of our clients to 80k solicited emails, and we got a huge amount blocked due to spam, even though our client has used ymlp.com to send similar campaigns to the same mailing list in the past with no problems. I have stumbled across a few nuggets of information such as: How to send 100,000 emails weekly? http://www.codinghorror.com/blog/2010/04/so-youd-like-to-send-some-email-through-code.html So I have

I'm trying to figure out how to send mails using the MailGun Golang API without having it sent 'on behalf of'. This is how the From address currently looks (where foo.com is the sender's email domain and bar.com is my domain): john=foo.com@mail.bar.com on behalf of John Smith <john@foo.com> What do I need to do so that it looks like this instead: John Smith <john@foo.com> I've set up SPF and DKIM according to the MailGun instructions and everything passes as being correct. I've also used SetDKIM(true) when I'm sending out the mail. Is there some setting I'm missing or additional validation I

I am attempting to use PHP-DKIM to send DKIM signed emails. Its a little old so I've had to change some things, but this stumps me: Warning: openssl_sign() [function.openssl-sign]: supplied key param cannot be coerced into a private key in /.../pages/user/dkim.php on line 66 Cannot sign Relevant section of code (note I've added the $pkeyid, originally the private key was just passed straight to the open_ssl function which also didn't work) $pkeyid = openssl_get_privatekey($open_SSL_priv); if (openssl_sign($s, $signature, $pkeyid)) return base64_encode($signature) ; else die("Cannot sign") ; So

I'm writing a Nodejs app that needs to be able to send email. So far, I've used Postfix in conjunction with a Nodejs module called Nodemailer to send my email through Amazon SES. Postfix has been handling the DKIM signing, but now I wish to get rid of postfix and just use Nodemailer to send emails through Amazon SES. My only problem now is finding a way to sign emails within Nodejs. I've thought of running a opendkim command using "exec" in node but haven't been able to figure that out. From searching, there looks to be no modules for this either. Can anyone help me on this? Latest version of

Please explain about differences between DomainKeys vs DKIM DomainKeys Identified Mail (DKIM) is the successor to Yahoo DomainKeys. Being very similar in functionality to DomainKeys, DKIM has additionally adopted aspects from Cisco’s Identified Internet Mail standard (IIM), and the result has been an enhanced standard that provides more flexibility and security than its predecessor. Some of the differences between DomainKeys and DKIM include: Multiple signature algorithms (as opposed to just one available with DomainKeys) More options with regard to canonicalization, that validates both header

I'm writing an application that allows users to send email to dynamically-created mailing lists. For example, a user can send an email to my-team@site.com (the site is a league management site for sports leagues) and the email will be sent to everyone on that users's team. I'm trying to figure out what the email headers should be to deliver the email correctly and make all the From and To fields look right. In Gmail, when you get an email from a mailing list (I'm looking at an email from google groups), it says that it came from the person who sent it and that it was sent to the list address,

I have written an program in C# which sends out emails. Now I have a requirement to sign outbound emails using Dominkeys/DKIM, but I'm not sure how to do it. I have set up all keys, but I don't know how to get those and hwo to include them in the email header. jstedfast There is a fundamental problem with trying to do DKIM signatures with System.Net.Mail.MailMessage and System.Net.Mail.SmtpClient which is that in order to sign the message, you need to poke the internals of SmtpClient in order to hash the message body as one of the steps in generating the DKIM-Signature header. The problem