How can I change the default text editor for MailEnable (e.g. log files)?
My default editor for .log files is Notepad++ but opening a .log from MailEnable (Enterprise 8.6.0) notepad.exe is used.
Thanks.
Logs editor (viewer)
-
- Site Admin
- Posts: 9321
- Joined: Mon Mar 22, 2004 4:44 am
- Location: Melbourne, Victoria, Australia
Re: Logs editor (viewer)
HI,
This is configured within Windows under the "Default programs" options (Control Panel\All Control Panel Items\Default Programs). You need to associate the file .log with Notepad++.
This is configured within Windows under the "Default programs" options (Control Panel\All Control Panel Items\Default Programs). You need to associate the file .log with Notepad++.
Regards,
Ian Margarone
MailEnable Support
Ian Margarone
MailEnable Support
Re: Logs editor (viewer)
Hi Ian,
Notepad++ is already the default program for opening .log files ; this system setting works everywhere except from MailEnable msc, so I thought there was some special setting.
Notepad++ is already the default program for opening .log files ; this system setting works everywhere except from MailEnable msc, so I thought there was some special setting.
-
- Site Admin
- Posts: 9321
- Joined: Mon Mar 22, 2004 4:44 am
- Location: Melbourne, Victoria, Australia
Re: Logs editor (viewer)
Hi,
I tried this on my machine and was able to change the default program for the file extension .log from notepad to word and vice versa. When changed to word it would open word to view the log in the administration console.
I tried this on my machine and was able to change the default program for the file extension .log from notepad to word and vice versa. When changed to word it would open word to view the log in the administration console.
Regards,
Ian Margarone
MailEnable Support
Ian Margarone
MailEnable Support
Re: Logs editor (viewer)
Thank you,
maybe it's a problem with Windows 2003 because it is present on three different installations of MailEnable with W2K3 as operating system.
Fortunately, they will be updated.
maybe it's a problem with Windows 2003 because it is present on three different installations of MailEnable with W2K3 as operating system.
Fortunately, they will be updated.