Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
IP Office instead of VM Pro on Windows to send Email?
- Thread starter voxvar
- Start date
holdmusic34
Vendor
Not unless you go System> Voicemail>Embedded.
Try this:
Set up a gmail account and enable imap in gmail settings. Set the gmail sender account in VMPRo client as per below.
Save and make live. RESTART the SERVER (this will force the dns to get the right smtp.gmail address).
See if it makes a difference. use the debug trace. It might not be the Avaya.
Dulce et decorum pro Avaya mori
Try this:
Set up a gmail account and enable imap in gmail settings. Set the gmail sender account in VMPRo client as per below.
Save and make live. RESTART the SERVER (this will force the dns to get the right smtp.gmail address).
See if it makes a difference. use the debug trace. It might not be the Avaya.
Dulce et decorum pro Avaya mori
Voicemail Pro is usually easier for me on installs,
looks like your not going to use the VM Pro if you switch to embedded. Unless there is a trick to embedded sling-shoting to the VM PRO server. ( I never claim to know it all just what I've done and messed up before)
The trick to VM Pro is to have a SMTP outbound server that will allow relay. From experience Gmail does not want to allow mail out, or its a fight to get it to allow it out. problem could be on the business platform of Gmail, I never tried a personal account.
The most reliable test for me is authsmtp.com for outbound service, I am guessing if everything is definitely set correctly in your VM Pro client under administration=> preferences => general => email=> smtp sender, as holdmusic34 said it may not be Avaya but how mail is allowed/ handled by the mail server( either in-house or hosted)
Authsmtp is a paid service for outbound mail ( pretty cheap for a whole year) I use it to as a solid server sending out when troubleshooting other email server configurations that are fighting back. Lets me know if it is me because it has a console to see mail sent out and an error log if you do have something wrong as in ports or credentials or even address mistypes.
This is just a direction to head into if you want to dig into it deeper and see more. ( especially if you don't understand the monitor in IP Office. Its kind of like drinking from a fire hose if your not familiar with it.)
Jerrberr
looks like your not going to use the VM Pro if you switch to embedded. Unless there is a trick to embedded sling-shoting to the VM PRO server. ( I never claim to know it all just what I've done and messed up before)
The trick to VM Pro is to have a SMTP outbound server that will allow relay. From experience Gmail does not want to allow mail out, or its a fight to get it to allow it out. problem could be on the business platform of Gmail, I never tried a personal account.
The most reliable test for me is authsmtp.com for outbound service, I am guessing if everything is definitely set correctly in your VM Pro client under administration=> preferences => general => email=> smtp sender, as holdmusic34 said it may not be Avaya but how mail is allowed/ handled by the mail server( either in-house or hosted)
Authsmtp is a paid service for outbound mail ( pretty cheap for a whole year) I use it to as a solid server sending out when troubleshooting other email server configurations that are fighting back. Lets me know if it is me because it has a console to see mail sent out and an error log if you do have something wrong as in ports or credentials or even address mistypes.
This is just a direction to head into if you want to dig into it deeper and see more. ( especially if you don't understand the monitor in IP Office. Its kind of like drinking from a fire hose if your not familiar with it.)
Jerrberr
In my experience, and I know because it's working currently just peachy,
use gmail.com for the mail domain; smtp.gmail.com for the mail server. 465 for the port number, and enable authentication. If you have 2 factor authentication enabled, you'll need to use an "application password" in gmail, rather than your gmail password. I've made it work this way *many* times without fail.
-Austin
ACE: Implement IP Office
use gmail.com for the mail domain; smtp.gmail.com for the mail server. 465 for the port number, and enable authentication. If you have 2 factor authentication enabled, you'll need to use an "application password" in gmail, rather than your gmail password. I've made it work this way *many* times without fail.
-Austin
ACE: Implement IP Office
- Status
