Facebook
Twitter
Running latest Plesk Obsidian on a Windows Datacenter 2019 Server - MailEnable Professional for Mail Service.
Domain configured on server was set to "DISABLED" - according to documentation, this is to disable ALL services with associated domain.
At approx 7:00am EST (GMT-0500), a spammer broke into an email account on the disabled domain and proceeded to spool 20,000 spam messages, which the mail server happily started to send out.
This domain has been "disabled" for 4 months. It was my understanding that disabling a subscription disables that domains POST OFFICE, MAILBOXES, MAIL SERVICES, ETC.
Upon investigation, it has been found that certain settings in Mail do not correspond with expected behavior such as "disabling" a mailbox only sets the Mail server to "Cannot Authenticate" but does not actually "disable" the mailbox. Other issues like this are present.
AS AN ADVISORY TO DEVELOPERS: I am sorting out over 20k spam complaints because the software did NOT disable a domain in Mailserver when set in Plesk. Additionally the Plesk configuration has been "checked" using the supplied tools (plesk repair / plesk reconfigurator) on multiple occasions since this particular domain was disabled and no errors were found. Meaning when Plesk verified it's configuration, it did not see that there was discrepancy between mail server settings and plesk settings - which if a subscription is disabled in plesk, it should be disabled in the Mail server...
Domain configured on server was set to "DISABLED" - according to documentation, this is to disable ALL services with associated domain.
At approx 7:00am EST (GMT-0500), a spammer broke into an email account on the disabled domain and proceeded to spool 20,000 spam messages, which the mail server happily started to send out.
This domain has been "disabled" for 4 months. It was my understanding that disabling a subscription disables that domains POST OFFICE, MAILBOXES, MAIL SERVICES, ETC.
Upon investigation, it has been found that certain settings in Mail do not correspond with expected behavior such as "disabling" a mailbox only sets the Mail server to "Cannot Authenticate" but does not actually "disable" the mailbox. Other issues like this are present.
AS AN ADVISORY TO DEVELOPERS: I am sorting out over 20k spam complaints because the software did NOT disable a domain in Mailserver when set in Plesk. Additionally the Plesk configuration has been "checked" using the supplied tools (plesk repair / plesk reconfigurator) on multiple occasions since this particular domain was disabled and no errors were found. Meaning when Plesk verified it's configuration, it did not see that there was discrepancy between mail server settings and plesk settings - which if a subscription is disabled in plesk, it should be disabled in the Mail server...
