Larry Rungren
asked on
Database Mail
I have some scripts that run every night in SQL Server 2008 that send emails to specific customers using Ipswitch Imail. These scripts have been running for several years. We use a product called GroupMail that also utilizes Imail to send bulk emails.
GroupMail works correctly. It resides on the same server as Imail
When sending mail from SQL Server machine using dbmail..... Nothing. Dbmail when sending a test email says the job was queued but never gets to the server. The only difference since this stopped working is the Imail server was virtualized, nothing changed just virtualized.
GroupMail works correctly. It resides on the same server as Imail
When sending mail from SQL Server machine using dbmail..... Nothing. Dbmail when sending a test email says the job was queued but never gets to the server. The only difference since this stopped working is the Imail server was virtualized, nothing changed just virtualized.
ASKER
The day this stopped working an outside consultant installed a new domain controller and change the domain name from mcle_nt to mcle.local. No other processes in the company has been effected.
ASKER
This is really a HUGE, HUGE problem. I have shut down the virtual system and brought the old server back on line and still nothing is working. The only thing I can't account for is the new Domain Controller and the change in the domain name. If anyone has any ideas or could take a minute to call 617-896-1178. This is causing a huge problem in the day to day operation of our business.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I see the items as unsent.
1. SMTP server is Ipswitch Imail on server mcleftp01old Can ping from SQL Server.
2 Ipswitch Imail domain is mail-mcle.org.
3. Imail user is "customerservice2", email account is "customerservice@mail-mcle .org"
4. Password is correct.
5. return email is "customerservice@mcle.org" (Office365 email account)
6. I am using the correct credentials am I not?
1. SMTP server is Ipswitch Imail on server mcleftp01old Can ping from SQL Server.
2 Ipswitch Imail domain is mail-mcle.org.
3. Imail user is "customerservice2", email account is "customerservice@mail-mcle
4. Password is correct.
5. return email is "customerservice@mcle.org"
6. I am using the correct credentials am I not?
Okay, if I interpret correctly, the mail isn't leaving the SQL server... so the problem is between the the SQL Server and the first SMTP server. (I assume Group Mail receives the email after IMail?)
"Ping mcleftp01old" from the SQL box lets us know that (1) name resolution is working, and (2) there exists a path between the systems. (On the SQL box, I'd normally "Telnet mcleftp01old 25" to confirm that an SMTP server responds.)
Do you have logging enabled on IMail? Can you see if IMail is receiving a connection attempt from the SQL server and is failing the connection for authentication or some other reason?
"Ping mcleftp01old" from the SQL box lets us know that (1) name resolution is working, and (2) there exists a path between the systems. (On the SQL box, I'd normally "Telnet mcleftp01old 25" to confirm that an SMTP server responds.)
Do you have logging enabled on IMail? Can you see if IMail is receiving a connection attempt from the SQL server and is failing the connection for authentication or some other reason?
ASKER
Once we had proven the mail wasn't leaving the server, and there was no obvious configuration problem I went to the nuclear option, I deleted all profiles in dbmail, recreated a new profile, et voila, dbmail is back and running. Modified the stored procedure to use the new profile and all missing emails have been sent.
Thanks for getting me looking in the right place, it always helps.
Kudos
Thanks for getting me looking in the right place, it always helps.
Kudos
Another thing that could have happening is that if this application is using Authenticated to send email, then maybe the account is locked out or disabled or possibly deleted.
Will.