Re: [cpx] CPX Bug Question & Comment

[Chris Hess <chris@xxxxxxxxxx>]

Hi Rus,

In reading the usability concern you noted, you implemented the 
feature as was requested. So I see it as a missing thought/feature in 
the original usability concern. Users will quickly hit their quotas 
with this functionality.

As Steve noted, if there could be a - SpamAssassin on/off and a 
ClamAV on/off and it would not be a problem. Or if I could have also 
choose an option to have the Junk and Quarantine boxes cleared of old 
mail that's 5 days old it would be no problem. I've actually 
commented on all of these features a number of times to various Verio 
addresses in the past. I'll send this to support and hope it gets to 
the CPX folks - and then hopefully to you Rus.

I don't know about everyone else but my thousands of email users are 
demanding a basic free spam service more and more every day now - 
filters, access to view filtered spam if needed, whitelisting, and a 
auto delete option after a message is 5 days old. Seems pretty 
standard these days but CPX is not quite there - getting closer 
though. Having users login to CPX on a regular basis to clear these 
boxes from my experience never works and ends up making them mad when 
the box fills. I recently lost some more business because I don't 
have a complete anti-spam option included with my services. Only a 
few are wiling to pay more for a third party service.

As always, thank you for the response Rus and help with this. I'll 
follow your instructions and submit my requests to support. If anyone 
agrees with these comments please do the same.

Thank you,

Chris Hess
chris@xxxxxxxxxx
Outer Banks Internet, Inc.


> On Mon, Jun 11, 2007 at 11:51:45AM -0400, Chris Hess wrote:
> >  Subject: [cpx] CPX Bug Question & Comment
> >
> >  CPX Question/Comment:
> >  When I setup a new end User I offer the User SpamAssassin and Clam
> >  AntiVirus (check boxes). However, when I do this it also enables them
> >  both SpamAssassin and Clam AntiVirus at the default settings.
> >  Although I really, really like the idea of being able to enable and
> >  disable these applications at the Server Admin level, it does pose
> >  problems. Without some sort of auto-clear option for the Junk and
> >  Quarantine folders, we find that users quickly fill their quota -
> >  they always forget to, or don't want to, login to clear them manually.
> >
> >  However, I was pretty sure the functionality was that if I offered
> >  these to the user they had to login and enable them in their user
> >  account. Can anyone comment on if this is a bug or new CPX
> >  functionality?
> >
> >  Thank you,
> >
> >  --
> >  Chris Hess
> >  chris@xxxxxxxxxx
> >  Outer Banks Internet, Inc.
>
> Chris,
>
> Yes, this is a change in CPX behavior with the latest dist.  I made the
> changes myself per a usability concern (USE08994) raised by QA and then
> endorsed by PM.  The usability case notes state the concern as follows:
>
>   As a server admin or domain admin when creating/editing a user, there
>   is a section saying:
>
>      "Offer the End User the following mail-related applications
>       and services:"
>
>         [] SpamAssassin (junk mail filtering)
>         [] Clam AntiVirus (virus protection)
>
>   The customer may think that by selecting these services, they are
>   enabling the service (neither service is actually enabled). Selecting
>   these merely gives the created user the "opportunity" to enable the
>   service.  Most customers creating the user would expect/want the
>   service enabled by default when the service made available.
>
>
> If you want this behavior reversed, you should send a note to support.
> You can even cite the usability concern by case number (USE08994) if you
> like.  This may be one of those things where 50% of the CPX users want
> it one way, and the other 50% want it the other way.  *shrug*
>
> cheers.
>
> --rus.
>
>
> ========================================================================
> Rus Berrett                                                    NTT/Verio
>                  See Perl. See Perl Run. Run Perl, Run!
>
> ======================================================================
> This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
> Before posting a question, please search the archives (see above URL).