MSExchange won't send out mail using the exchange account
Have a problem where users cannot send out email, when the account used for the outgoing message is exchange, started 6+days ago.
Can you help w/ how/why my MSE won't send out messages...!
Using MSOutlook 2010 at workstation, send a message and it appears to go out, resides in Sent Items, but never received by recipient, and the sender receives a delivery status notification (Delay), or an undeliverable:.... Using the MSO client, I can choose a different account to send the message, such as the POP3 for this user, and it goes out; but not when using the local MSE account.
The local office here has MSE.6.5.x on an SBS2003standard, clients are MSOutlook 2010 & 2007.
Nothing should have changed on the server (BUT something did change w/the smtp host whose address I was using...; sbs2003 won't send out smtp from the client when using the default MSE account, but will at the client if I choose the POP account for sending... it of course does.
POINT, on MSE had smtp-connector with a smtp.frontiernet.net and NOW last week, frontier went over to partner w/yahoo... but one could still use the pop account setting in a MSO client, but would need to login at yahoo and change your password (something like that)... SO, at that time (beginning of last week) is when my MSE outgoing messages stopped.
Now, I realized this Friday morning, and changed the smtp-connector to smtpout.secureserver.net, which is for godaddy... and can't get the mail at the client to go out usning the MSE account.
--I had been using smtp.frontiernet.net for long time (we have other acct's w/them) even though all clients were not using frontier... so it apparently kept sending on thier system; up until frontier buddied up w/yahoo. (my delayed/failed mssg returns refleceted this smtp.frontiernet.net address)
--I changed the smtp-connector to use godaddy's smtp.secureserver.net, and thus far, no outgoing w/client, though I shoud see some undeliverable/delayed mssg returns, and I'll look for the server it's using/referencing.
thanks for some feedback / heading toward resolution.
---I'll post another EE item about the MSE not completing a backup w/SBS2003 backup tool (lame to use, I suppose, but nonetheless, it does not complete)
Can you help w/ how/why my MSE won't send out messages...!
Using MSOutlook 2010 at workstation, send a message and it appears to go out, resides in Sent Items, but never received by recipient, and the sender receives a delivery status notification (Delay), or an undeliverable:.... Using the MSO client, I can choose a different account to send the message, such as the POP3 for this user, and it goes out; but not when using the local MSE account.
The local office here has MSE.6.5.x on an SBS2003standard, clients are MSOutlook 2010 & 2007.
Nothing should have changed on the server (BUT something did change w/the smtp host whose address I was using...; sbs2003 won't send out smtp from the client when using the default MSE account, but will at the client if I choose the POP account for sending... it of course does.
POINT, on MSE had smtp-connector with a smtp.frontiernet.net and NOW last week, frontier went over to partner w/yahoo... but one could still use the pop account setting in a MSO client, but would need to login at yahoo and change your password (something like that)... SO, at that time (beginning of last week) is when my MSE outgoing messages stopped.
Now, I realized this Friday morning, and changed the smtp-connector to smtpout.secureserver.net, which is for godaddy... and can't get the mail at the client to go out usning the MSE account.
--I had been using smtp.frontiernet.net for long time (we have other acct's w/them) even though all clients were not using frontier... so it apparently kept sending on thier system; up until frontier buddied up w/yahoo. (my delayed/failed mssg returns refleceted this smtp.frontiernet.net address)
--I changed the smtp-connector to use godaddy's smtp.secureserver.net, and thus far, no outgoing w/client, though I shoud see some undeliverable/delayed mssg returns, and I'll look for the server it's using/referencing.
thanks for some feedback / heading toward resolution.
---I'll post another EE item about the MSE not completing a backup w/SBS2003 backup tool (lame to use, I suppose, but nonetheless, it does not complete)
ASKER
oh boy, here we go w/my ignorance on the matter...
1-yes, static IP.
I don't know where to look at the queues... need to find that...
Also, need to find where is the message tracking...
thanks so far simon.
matt
1-yes, static IP.
I don't know where to look at the queues... need to find that...
Also, need to find where is the message tracking...
thanks so far simon.
matt
ASKER
ok, working on this:::
To open Queue Viewer, follow these steps:1.Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2.Expand the Servers container. The Servers container may be located under the Administrative Groups container, depending on the options that are enabled on your server.
3.Expand the server that contains the queues that you want to view.
4.Click Queues to start Queue Viewer.
To open Queue Viewer, follow these steps:1.Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2.Expand the Servers container. The Servers container may be located under the Administrative Groups container, depending on the options that are enabled on your server.
3.Expand the server that contains the queues that you want to view.
4.Click Queues to start Queue Viewer.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes, mssg's in queue... (38pcs)
Oh, on bottom of Queues window, see under Additional queue information:
The remote SMTP service rejected AUTH negotiation.
---I would suppose this related to the authorization for smtpout.secureserver.net..
Oh, on bottom of Queues window, see under Additional queue information:
The remote SMTP service rejected AUTH negotiation.
---I would suppose this related to the authorization for smtpout.secureserver.net..
ASKER
Hey, it's solved... thanks,,,
fyi: turns out the smtp connector which had frontiernet.net has to KEEP that there, as our ISP is frontiernet.net... and if it's not there... they think/block becasue of potential spamming... Sooooo, when frontiernet.net buddied up w/yahoo... the 'main account' w/frontier ---that user / user name--- changed 'his' password.
I returned the smtp connector to frontier
I went to advanced tab > outbound security, and changed the password to the new password (which had changed...) and WALA... outgoing works AGAIN.... perfect.
thanks for your input... it got me thinking about that which I once knew, and casually forget...
have a great day.
fyi: turns out the smtp connector which had frontiernet.net has to KEEP that there, as our ISP is frontiernet.net... and if it's not there... they think/block becasue of potential spamming... Sooooo, when frontiernet.net buddied up w/yahoo... the 'main account' w/frontier ---that user / user name--- changed 'his' password.
I returned the smtp connector to frontier
I went to advanced tab > outbound security, and changed the password to the new password (which had changed...) and WALA... outgoing works AGAIN.... perfect.
thanks for your input... it got me thinking about that which I once knew, and casually forget...
have a great day.
ASKER
if using the "outbound security" w/an email account, and the password for that account changes, the password must be changed accordingly in the outbound security section also.
Are the messages in the queues? If not, look in Message Tracking to see what Exchange has done with the messages.
Simon.