Sorry for belated reply - I'm new to James, but not DKIM, which is pretty much essential these days if you want the mega providers to not put your email in spam boxes.
Firstly, DKIM is a per domain thing. You cannot put a single DKIM TXT record in your server's DNS and expect that will work for all the domains you have on that server. I've got it working fine, admittedly for a single domain only and I've included how to do this in a write up on line (mainly so I remember how to do it myself!). I *think* you can probably extrapolate from what I've done to make it work with multiple domains on a single James smtp instance. My nameservers use tinyDNS which has it's own way of doing things so you may well need to do some more hunting around to get the correct format for the TXT record to suit whatever nameserver service you use. While you're at it, you also need to put up SPF and DMARC records, but they are easier, being purely DNS TXT record things as opposed to DKIM, which has two parts:- 1)james is set up to sign outgoing email for your domain(s) with private key(s) https://dmatthews.org/java_email.html 2)the remote server uses the corresponding public key in your domain's TXT record to make sure the mail came from your domain and has not been tampered with in transit https://dmatthews.org/email_auth.html#dkim Finally if your mail is actually being bounced rather than just silently being put into spam boxes, I would worry that your ip address has gotten onto a DNSBL. -- David Matthews m...@dmatthews.org --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
