Thanks for taking the time guys! I appreciate it very much
you spelling it out so clearly.
exim (and the recipients' MTAs) use these host names from
so many different sources. So i was quite confused before.
As a result I've made several changes that test out well.
I am hopeful (confident
Cooper wrote:
On 30/04/12 19:03, Iain Houston wrote:
We are getting a percentage of Not configured to relay rejections
when we send out our newsletters. I rent a Cloud Server from 11
where I run our.nonprofit.com and a couple of others. Most
recipients' MTAs produce no such rejections
?
I'd be very grateful for the benefit of greater experience than mine as I am
about to go live
with another nonprofit client's website with a much larger set of newsletter
recipients.
Best regards - iain Houston
Some diagnostic data
Nigel, Thank you for taking the trouble to help.
Now that I have moved the private key file to /etc/exim4 all is working fine:
outgoing emails are being signed properly.
Great! But I don't understand why.
(Don't feel obliged to reply . but I'd love to know!)
On 24 Mar 2012, at 19:51, Nigel
Hi,
I looked in the FAQs and Googled the problem I'm having - without avail.
I'd be very grateful for any help in resolving it.
Best regards - Iain Houston.
Problem:
exim reports: 1SBE1H-FZ-4l unable to open private key file for reading:
/etc/ssl/private/dkim.private.key
yet I believe
