VoiceGuide IVR Software Main Page
Jump to content

Voiceguide 6.03003 And Sendmail

Recommended Posts

I have Voiceguide set up to send mail automatically by connecting to my SMTP server. Voiceguide indicates that the email is sent successfully, but the mail never arrives. The server logs show a good connection to the server and authentication from the Voiceguide machine, and then:

 

Jun 27 11:36:46 SERVERNAME sendmail[27093]: l5RFajEZ027093: VOICEGUIDECLIENT did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA

 

So, it appears that Voiceguide is never actually sending the email after making the connection.

 

This email contains a whole pile of $RVs (which all show correctly in the Voiceguide call log) and has a recorded wave file as an attachment.

 

Any suggestions?

Share this post


Link to post

Which version of VoiceGuide are you using?

 

Could you please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

VoiceGuide=10

 

EmailSender=10

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces and the VoiceGuide script used.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

Share this post


Link to post

Hi, sorry it took so long to get back to you - the problem was an authentication error, literally just a bad password. Now it works.

 

So, since Voiceguide was logging it as an authentication error, why was the script taking the "On {success}" branch instead of the "on {fail}" branch in the script logic? As it says in the thread title, I'm running version 6.03003.

Share this post


Link to post

Email is sent in the background and some emails may take a while to send, that is why VoiceGuide will not wait for the actual sending of the email. The IVR script needs to go to the next module without keeping the caller waiting. The module takes success path when email has been *queued* to be sent.

 

Ultimately, you never get a confirmation that an email has been received at the remote end either.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×