ConfigServer Community Forum

Mailwatch uses a mysql database named "mailscanner" (this is a systemwide database not tied to any particular domain).

Because of the late situation with Mailwatch, I believe that we will be forced to uninstall Mailwatch sooner or later.

To understand the consequences of that I need some information:

1) Was the "mailscanner" database originally created by Mailscanner itself or by Mailwatch?
2) Is the "mailscanner" database used by Mailscanner or MFE?
3) Is it used by Mailcontrol?
4) Will this "mailscanner" database be erased when we finally uninstall Mailwatch?

Thanks in advance for any answers provided

Hello Sarah, are you able to help me with the above question?

hilario wrote: ↑02 Dec 2018, 15:35 Mailwatch uses a mysql database named "mailscanner" (this is a systemwide database not tied to any particular domain).

Because of the late situation with Mailwatch, I believe that we will be forced to uninstall Mailwatch sooner or later.

To understand the consequences of that I need some information:

1) Was the "mailscanner" database originally created by Mailscanner itself or by Mailwatch?
2) Is the "mailscanner" database used by Mailscanner or MFE?
3) Is it used by Mailcontrol?
4) Will this "mailscanner" database be erased when we finally uninstall Mailwatch?

1) The database was (and still is) created by our MailScanner front-end installer script and was used by Mailwatch
2) The MailScanner Front-End uses it
3) Yes
4) No

Hope this helps.

Regards,
Sarah

Thanks for the help Sarah!

hilario wrote: ↑02 Dec 2018, 15:35
Because of the late situation with Mailwatch, I believe that we will be forced to uninstall Mailwatch sooner or later.

What's the late situation with Mailwatch?

As far as I can understand from the above thread, configserver.com is not going to support Mailwatch any more.
You will probably have to install manually (not integrated with cpanel) and taking care to create a different mysql database to avoid conflicts with MFE (Mailscanner Front End) and Mailcontrol.