I thought so, but it isn’t. The wording is different, and changing vm_email.inc has no effect
I have found that putting entries in voicemail.conf overrides the default
e.g.
fromstring=Asterisk on XXXX
emailsubject=Voicemail ${VM_MSGNUM}, Length ${VM_DUR}, CLI ${VM_CALLERID}
emailbody=\nCLI\t${VM_CALLERID}\n\nLength\t${VM_DUR}\n\n
but I would dearly love to know where the original format resides
do that to voicemail.conf and then nobody can change there password for voicemail. you’ll also not get any new extensions added, bust the directory service, etc…
Voicemail.conf is supposed to change, the routines for processing the file are supposed to read the file into ram, if a extension is being deleted remove it from ram, if adding a new one add to the end and re-write the file. (edit’s/changes same basic process they only touch the line that is being changed).
Many processes use that file so changing it’s ownership is a good way to break many things.
NOTE: Asterisk has to edit this file to change a user’s password. This does not currently work with the "#include " directive for Asterisk configuration files, nor when using realtime static configuration. Do not use them with this configuration file.
I am not sure what this means. Does it mean I should not add