Thanks for taking the time to look at this, Ted.
No, I didn't frame my question very well.
I think it boils down to this:
whatever host name I tell exim to use, I assume that
a recipient's MTA will always think we
are relaying for s15917281.onlinehome-server.info.
(And whatever I tell my DNS SPF records are allowed hosts.)
Because, even though:
If uname -a gives Linux coombe.villagenet.info 3.2.0-24-generic ...
and hostname -f gives:
coombe.villagenet.info
and I set up my SPF records to allow clients' mail from
coombe.villagenet.info
and I tell exim:
...
primary_hostname = coombe.villagenet.info
...
qualify_domain = villagenet.info
qualify_recipient = villagenet.info
...
I was hoping not to have so much mail rejected.
But, because we rent our server I have to accept that ....
cat /etc/hosts gives
127.0.0.1 localhost.localdomain localhost
82.165.46.221 s15917281.onlinehome-server.info s15917281
82.165.46.221 s391547658.onlinehome.info
and nslookup 82.165.46.221 gives
221.46.165.82.in-addr.arpa name = s15917281.onlinehome-server.info.
Is there anything I can do to have recipients' MTAs verify
coombe.villagenet.info instead?
On 1 May 2012, at 06:00, Ted 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 1&1
>> where I run our.nonprofit.com and a couple of others. Most
>> recipients' MTAs produce no such rejections ... is it an issue with
>> our exim's setup or their MTA's setup?
>
> You've redacted everything that would be useful to anyone attempting to
> actually diagnose your problem with any sort of certainty. As such, here
> are some random guesses.
>
> Your server is either being blocked by the target servers in question,
> or they do not accept mail for the recipients even though the MX records
> say they should. The domains may have expired or the users may have
> moved on. The single error message provided seems to come from the
> remote end.
>
> SPF is IP based so it just needs to have something resolving to all the
> IP addresses you want to send mail from if you're using it. Including
> the different hostnames all pointing the same IP address serves to add
> nothing.
>
> All of the email addresses must have accepted the confirmation opt-in
> email at some point right? You'd have records of when they confirmed.
>
>
> --
> ## List details at https://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
