> Your comment makes sense. However, if XO does provide such a server they
> have hidden it from me, at least 5 of their tech support reps, 2 second
[quoted text clipped - 120 lines]
>>>>>>>>>>
>>>>>>>>>> Joe M
Thanks for your help. Please see my responses inline.
> OK, so the net result as I read that is that you have tried a lot of
> things I have no reason to believe will work but _at least_ one thing I
[quoted text clipped - 3 lines]
> smtp.<domain>.com.xohost.com. I suggested the _absolute_, _literal_ names
> mail.njd.xo.com or smtp.concentric.net.
No, you did not. I tried to make it clear that the others were suggested by
XO. I apologize if I said anything that implied that I thought that you did.
I tried the two names you suggested and also two others that XO support reps
mentioned. I expected low odds of success with the others, but I was in
there messing around and the extra cost was not much.
> I don't know. Maybe XO are anal retards. 'Technical Support' _can_ be
> expected to say 'hang on, I'll go ask' if you ask them 'what server can I
> use as smarthost?' but if you ask them 'What outgoing mail server should I
> use in outlook?' it would be very unusual for them to give you other than
> the name of the server you can use as 'smarthost'.
I had long since abandoned the term "smart host" when dealing with them. The
problem is that the answer to "What outgoing mail server should I use in
Outlook?" is very different from "What outgoing/relay mail server should I
connect to from Exchange?". They have an answer for the former -- similar to
the normal POP3/SMTP type of service. It requires pre-registration of an
email address and authentication using that email address and a password.
Once the connection is established, it will _only_ accept email with the
same From address. Usable from Outlook. Not usable for a relay from Exchange
with emails from multiple addresses within the domain.
> NOTE: Ask this question of the ISP, do not ask the 'web/mail hosting'
> branch of the ISP, do not ask your 'account rep'(who may have
[quoted text clipped - 7 lines]
> 'hosted domain' but through your ISP's 'general server'), AFAIK they
> haven't confirmed nor denied success.
I will try the ISP side. I had directed the calls the the mail/hosting side.
XO only services business accounts and requires the account number/name
before they will talk to you. Pretending to be a single user would be tough.
Note from above that they _do_ have an answer for a single user or many
single users -- each with a _separate_ connection to a mail server to
transfer mail _solely_ for the authenticated user.
Thanks,
Joe M
Joe_M - 09 Jan 2008 21:31 GMT
FYI - for closure.
I tried the ISP side of XO tech support who quickly transfered me to the
hosting/email side. Still no useful server name or methodology to relay
outgoing email through XO. They are "working on it."
I set up an account with AuthSMTP.com and set an SMTP connector to route all
outgoing email for Yahoo.com through the AuthSMTP server. This seems to have
solved the problem of Yahoo's dumping/rejecting the emails. We will direct
other problem sites through it as they arise. We may direct all outgoing
email through AuthSMTP if it continues to work, we have problems with other
sites, and avoiding the administrative hassle is worth the higher cost
subscription.
I believe that a relay through any large and generally trusted relay would
have solved our problem with Yahoo.
Joe M
Anteaus - 17 Jan 2008 12:37 GMT
Just as an aside, I think this thread highlights an industry-wide problem
whereby spamfilter providers are dictating that small business mailsites
shall adopt policies which are generally only available to leased-line
coprporate users. Since most domain-registrars make no provisions for
anything beyond A and MX records, it follows that their demands for PTR
records, etc. are unreasonable and impractical.
The issue with using a smarthost is firstly that many are of poorer
reliability than an onsite server. Also, you have no way of tracing an email
once it leaves your premises. (which it will do even if undeliverable) The
ridiculously long timeouts (5 days) on most smarthosts are archaic in origin,
and unacceptable for most business users. If a message cannot be delivered
within say 24hrs, we need to be able to CANCEL that message, unfortunately
you cannot do so when at the mercy of a smarthost.
Just my thoughts on the matter.
> I set up an account with AuthSMTP.com