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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Vm-email on App server 3

Status
Not open for further replies.

elalich

Vendor
Apr 5, 2006
25
US
Hey folks, just been playing with the new linux toy and can't seem to get the voicemail to email function working correctly. When I look in the log I see it trying to open the smtp session to the domain of the email address and not to the ip address entered in the server and domain information. Anyone got an idea where I screwed up? I've rebuilt the whole virtual machine 4 different times now since scratch seems to be the best place to begin with this thing.

And just in case anyone on Avaya Olympus is watching...the mortals could really use a vmpro debugger for this!
 
hey, can you post logs for this?

one log:
grep vmpro /var/log/messages > /log.txt

the other:
/opt/vmpro/vmpro.log

also, do you have a DNS server configured?
 
hey there, found that if I set up a telnet session from root on app server to smtp server on port 25 then issue ehlo, mail from, rcpt to, then quit commands and get good reponses back it will work from then on. Proved in the lab and out on site. Cool huh? However, it still won't generate the log archives....
 
DBrewsky,
Have you gotten any resolution from Avaya on this? Seems that my fix works for a while then intermittently starts failing again.
 
I heard today that you cannot use a smtp server to relay the messages. Apparentaly all the messages attempt a direct delivery to the domain name in user email address, an example being: test.user@abccomp.com will attempt direct delivery to abccomp.com.

Unfortunately I have to deal directly with a Tier 3 tech and I believe there is some things that are lost in translation.

But as I learn more, I will keep this thread updated.




--DB

Remote Support Specialist
 
Well, if you can't use SMTP and MAPI is not not supported then how are you supposed to get vm to email to work? lol
 
Wierd things happened during trial of the Apps Server. I got lots of email setup problems, but they did get resolved. Are you sure you are using the GA install??

Jamie Green

Football is not a matter of life and death-It is far more important!!!!
 
Yeah, here's a snipit of the smtp log (ip's changed)... See how it first tries to connect to the sending email addresses domain, fails, then connects to the smtp ip address that was specified in the client. Before I setup a telnet session from root to the smtp server it would try only domain.com (which was never specified anywhere) then would stop and not attempt to connect to any other specified smtp server. After setting up a good telnet session it tries the others but it's a hit and miss affair, very undependable. Is this what you guys are seeing as well?
12/01/2011 14:09:58.071 - Attempting to connect to host caprinbonds.com on port 25, local bound address is (null)
12/01/2011 14:13:07.123 - bool CSMTPConnection::Connect(SQLUINTEGER&, const TCHAR*, CSMTPConnection::LoginMethod, const TCHAR*, const TCHAR*, int, const TCHAR*, int): Could not connect to the SMTP server caprinbonds.com on port 25. Error 110 [0x6e] (Connection timed out)
12/01/2011 14:13:07.226 - Attempting to connect to host 8.8.8.8 on port 25, local bound address is (null)
12/01/2011 14:13:07.339 - Successfully connected to host 8.8.8.8 on port 25
12/01/2011 14:13:07.392 - < 220 CAPRINSBS.caprinbonds.local Microsoft ESMTP MAIL Service ready at Wed, 12 Jan 2011 14:14:11 -0500
12/01/2011 14:13:07.445 - ######## START OF CHUNK ######
12/01/2011 14:13:07.497 - > EHLO voicemail
12/01/2011 14:13:07.499 - ######## END OF CHUNK ######
12/01/2011 14:13:07.511 - < 250-CAPRINSBS.caprinbonds.local Hello
 
OK.. I got it to work.. Even got it to send to gmail.

The first entry in the SMTP sender is dedicated to exchange information between multiple VM Pro servers. Set the SMTP Receiver tab to Internal with some internal IP address, I used our CCR Server/SMTP Relay Server (which SMTP Relay is not required, but does work. But that's another subject)

The rest of the entries in the SMTP Sender tab are for SMTP servers where you're users have email addresses. Example: If you have a user at gmail.com then you will need an SMTP entry for gmail. If you have another user at avaya.com, then you will need an smtp server that accepts messages for avaya.com.

As for gmail, or companies that use Google Apps for Business, you will need to setup an smtp sender to: aspmx.l.google.com port 25. This smtp will validate the recipient and allow the message, but will deny all others.

So, in summary, the first entry is used to exchange information between vm pro servers, and you MUST have an SMTP Sender entry for each seperate SMTP server that is required for your users. The match is defined by the domain name of the user. If you have user@abc.com and user@xyz.com that both use Google Apps for Business, you will need two SMTP sender entries. One for abc.com to use aspmx.l.google.com (port 25) and then a seperate entry for xyz.com to use aspmx.l.google.com (port 25).

Now this application does NOT support TLS. So any SMTP server you use as a SMTP Sender must support non-TLS email recipients. Example, I had a test email on a domain (names changed to protect the innocent), Testuser-AT-mydomain.com, and I can send messages using the username and password of that account, then I can allow that to relay messages for me. Just make sure it's using port 25.

If you want to look into a way to relay an SSL/TLS email, have a look here: They talk about using a program called STunnel that will convert a NON-SSL email to good SSL email. I didn't try this, but maybe something to look into.


I know this is long winded, but it took me 2 weeks of troubleshooting, one public IP SPAM-watch I had to get removed, and a whole lot of late nights to get this information.

I hope this helps.


--DB

Remote Support Specialist
 
I'll give this a try and post the results. Thanks for the late nights and spam-watching!
 
When i read this and the help within VMPro then i get confused.
Can you provide some screen shots with it?


When you pay peanuts, you get monkeys!

I'm not insane, my mother had me tested!
 
As requested. This is the only screenshot you will need. I have blurred out some information, but hopefully you will get the idea.

Entry 1: This is really a null entry and, again, is only needed for information between servers and does not help you get your desired result. BUT IT IS REQUIRED!!

Entry 2:
Domain: companyabc.com - This is matched against the domain name in the email for the user. In this case the user email could be anyuser@companyabc.com

Server: FQDN or IP Address of the SMTP server of where you are sending your email through. In the case of google, it is: aspmx.l.google.com

Port: Port number used by the server address above. With Google (gmail or a customer that uses Google Apps for Business) it only requires port 25.

Identifier: An generic identifier of who is sending the message. For gmail, this must be a valid user on the companies Google Apps for Business account. When using my personal domain, I could use any identifier I wanted.

Auth: Required on if the SMTP server requires user validation to send the email. In the case of Google Apps for Business, this is not required. But when I used by personal domain email account, it was required.

User/Password: If you selected AUTH above, then this is where the username and password of the SMTP server you are sending the email gets the required validation.


Hope this helps.

--DB

Remote Support Specialist
 
It worked! Now what? LOL You guys seeing any issues with the logs? Got a few restarts marked "voicemail IPOfficeWatchdog[2221]: vmpro problem detected. Restarting.". All the core dumps are broken or garbled.... but the darn vm to email works!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top