Application server with VM Pro: VM to Email not working

[jameswarner]

Issue: Application Server with VoiceMMail Pro: Voicemail to Email is not working

Solution:Voicemail Pro Client Administration, Preferences, General, Email, SMTP Sender: 1st entry Domain and Server populated with IP address of SMTP Server, Port 25, Valid email address, 2nd entry Domain name (example avaya.com) Server IP address, Port 25 and Valid email address, SMTP Receiver, Internal, Port used, Domain IP address

Comments: If still failing go into the Application Server using Putty and login to root. cd .. cd /etc ls –l, Change Disablebinarymime = N to Disablebinarymime = Y, Then reboot the application server = init 6

[ktkendall]

Great info, thanks!

[aarnol]

Voicemail Email Multi Part MIME Message

I am running vmpro 9.0 SP2 and I am having an issue where the voicemail email is being sent but as a plain text Multi Part MIME email. I have done the above solution setting DisableBinaryMine=Y. This does not change the behavior of the received message.

Any help would be much appreciated.

Here is a sample of the received email message

This is a multi-part message in MIME format.

--{b89729a8-52fd-7646-9be2-4e5ff75c6392}
Content-Type: text/plain;
    charset=o-8859-1
Content-Transfer-Encoding: quoted-printable

IP Office Voicemail redirected message

--{b89729a8-52fd-7646-9be2-4e5ff75c6392}
Content-Type: audio/wav;
    name=SG00028.WAV"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
    filename=SG00028.WAV"

UklGRqr2AABXQVZFZm10IBAAAAABAAEAQB8AAIA+AAACABAAQUxDSBIMAABBdmF5YQAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAEkAADM5MDkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAYWphcm5v
bGQ+RFRHIElOAAAAAAAAAAAAAAAAAAAAAADXk2zVAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAADIwMQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGFqYXJub2xkAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAARFRHIElOAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIIAAABWb2ljZQAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAEF1dG9SZWNvcmRpbmdJbmNvbWluZ0h1bnRHcm91cAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAERURyBJTgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASAAAAEgAAAAwIG1p
bjozIHNlYwAAAAAAAAAAAAAAAAAAAAAAAAAAAHZtLmdvZHRnLmNvAAAAAAAAAAAAAAAAAAAAAAAA

[danburns]

Are you using Office 365? It seems quite consistent with this issue caused by Microsoft-

https://support.avaya.com/ext/index?page=content&id=S:SOLN276890