Just as I was for my domain, but if that server is configured locally, it's not going to bother looking you up and bypass itself.
On Nov 30, 2010, at 4:53 PM, David Camm wrote:
> jody - we ARE the authoritative dns for the domain. i wish it was that easy :-)
>
> david camm
> advanced web systems
> keller, tx
>
> Jody McAlister wrote:
>> Had something similar. The person moved their webhosting to godaddy, but kept their mail with us. Their designer set up the account in a generic way which created dns and mail entries for the domain when I was running dns and email for them. The server was doing everything local so it never looked outside for the real information.
>> On Nov 30, 2010, at 1:59 PM, David Camm wrote:
>>> this may be off-topic, but it's driving me crazy.
>>>
>>> customer has an email account called info. works perfectly normally. used for receiving and is not sent from (although it could send).
>>>
>>> customer's website is hosted by godaddy. their contact form's program sends an email toHIDDEN@omain.com from an account called HIDDEN@@domain.com'. the domain's spf record allows the web server to send mail for the domain (a mx -all).
>>>
>>> mailer is, of course, defined in surgemail.
>>>
>>> the emails never arrive. none of the surgemail logs show any signs of emails fromHIDDEN@@domain.
>>>
>>> however, when the program is modified to send emails to, say, HIDDEN@main', it works perfectly.
>>>
>>> i've never encountered anything like this before. i have to believe good old godaddy is doing SOME sort of outbound filtering.
>>>
>>> does anyone have a clue? i HATE unsolved puzzles!
>>>
>>> david camm
>>> advanced web systems
>>> keller, tx
>>>
>>>
>
|
