I respect your perspective, but I don't think you are taking into account the way other people might elect to work.
Most of my customers are companies that use more than one device to access their email accounts and prefer to have the emails stored on their local machines and NOT on the server.
To that end, they tend to set up POP3 accounts to download their mail and process it on their own computers and devices, and elect to just store mail on the server for a few days until all their devices in use have had a chance to download it.
If Spambox were to be enabled by default, they would have to set up an additional POP3 account for every email spambox that they needed to monitor, effectively doubling the number of POP3 accounts to set up on each device, and potentially doubling the amount of polls made to the server.
Additionally, not everyone uses the webmail interfaces that Gmail etc provide for them.
I have had Gmail accounts for a long time, and have never logged into their webmail interface after setting everything up - I prefer to poll the Gmail account using POP3 from my Thunderbird web client.
I am not stating that any one method is correct, nor attempting to convince anyone that one approach is better than another - merely pointing out that different people use the facilities in different ways, and enabling anything by default will always provoke discussion as to its relative merits.
So the question is -
Should spambox be enabled by default and force those customers that don't want it to have to log into their cPanel and disable it ?
OR
Should spambox be left disabled and leave it up to the customer to enable it if they want to ?
The answer is obviously 42 !
