RE: [cpx] Mail System Administrator

["Martin Fischer" <martin.fischer@xxxxxxxxxxxxx>]

Scott and everybody else, 

1) Priority to clear basic bugs
2) fixing ASCII > 127 in Subject Line Bug
3) fixing Autoreply  bugs
4) fixing message size limitations (at least 1 GB)


Thanks

Martin

-----Original Message-----
From: owner-cpx@xxxxxxxxxxxxx [mailto:owner-cpx@xxxxxxxxxxxxx] On Behalf Of Scott Flinders
Sent: Tuesday, August 14, 2007 11:31 PM
To: cpx@xxxxxxxxxxxxx
Subject: RE: [cpx] Mail System Administrator

Mark (and everybody else),

Your perceptions are probably well-founded, but things are different now
and I hope to change your perception as we move forward. The fact is,
CPX is a high priority for us. We are making some good progress on it
and have big plans for the future. We have fixed (and continue to
address) many of the defects considered high priority by our customers,
we recently added configuration managers for SpamAssassin and ClamAV,
made CPX compatible with Dovecot, improved and updated the Japanese
language elements and we are currently overhauling the mail system
administration and webmail client, updating the UI and we're working on
a handful of other enhancements we're not ready to announce yet.

We also have plans for many more improvements. I want to make sure we're
focusing on the defects and new features that are the most important to
you and I appreciate the lists that are currently being compiled along
those lines.

Speaking of those lists, I'm going to be offline the rest of this week,
but I'd like to bring some closure (at least for now) to those lists. Do
you think, as a group, you could finalize and come to some sort of
solidarity on the prioritization of those items?

I will then compare your lists with what we're already looking at and
make adjustments to our plan as necessary.

Thanks,

Scott Flinders
Sr. Product Manager
Verio Inc.

-----Original Message-----
From: owner-cpx@xxxxxxxxxxxxx [mailto:owner-cpx@xxxxxxxxxxxxx] On Behalf
Of Mark A. Sharkey
Sent: Monday, August 13, 2007 12:41 PM
To: cpx@xxxxxxxxxxxxx
Subject: Re: [cpx] Mail System Administrator

Hi Scott,

First, thanks for taking the time to post and get feedback from
resellers.

In doing your research, please keep in mind that many of the request 
that you will see, have been submitted (and resubmitted, and 
resubmitted) for over 3 years to many different product managers.  So, 
it is important that Verio understands that they not only have a hurdle 
to jump concerning adding features and fixing bugs; but, they also have 
a responsibility to repair the perception that many of us have that our 
requests concerning CPX are ignored by Verio. (Maybe "ignored" is not 
the right word; but, certainly CPX has not been given resources by Verio

to make it a high priority project for the reseller community).

I noticed that your original post only asked for comments on the "Mail 
Sytem Administrator".  Are you only looking to improve the mail portion 
of CPX at this point?  Or, are you taking responsibility and 
accountability for all features of CPX?

I look forward to seeing CPX being a viable option for our clients!

Mark




Scott Flinders wrote:
> Hello all,
>  
> Let me start with a quick introduction. I am a fairly new product 
> manager at Verio, and, among my responsibilities, is the CPX control 
> panel. Based on feedback from customers, we are currently working on a

> project to improve and streamline the VPS and MPS mail system. I have 
> spoken with many customers already about what they like and dislike in

> the current system. I'd also like to reach out to this list and get
your 
> feedback.
>  
> The main suggestions I've heard so far regarding the mail system are
>  
>  - improve performance of the mail system
>  - allow end users to go directly to the webmail client without 
> requiring them to go through CPX
>  - improve/replace the current webmail client to make it more feature 
> rich and improve the user experience
>  - allow the primary VPS or MPS admin to delegate administration of
the 
> mail system (per domain) to another user (i.e., create a "mail system 
> administrator")
>  
> We are addressing all of these issues, but the last one in particular 
> has brought up some good questions as we seek an appropriate design.
If 
> any of you on this list are among those that would like to delegate 
> administration of the mail system to another user, please tell me if
you 
> would want the user with mail system administration rights to be able
to
>  
>  - add users? (If so, should they only be able to add them as email 
> users, or should they be able to manage all user attributes such as
ftp 
> access rights, overall disk quota (as opposed to mailbox quota only),
etc.?)
>  - authenticate to any user mailbox (without knowing or modifying the 
> user's password)?
>  - change users' passwords?
>  - configure SpamAssassin and ClamAV settings?
>  - manage virtmaps?
>  - manage "catchalls" (wildcard mappings)?
>  - manage aliases?
>  - manage server-level autoresponders?
>  - adjust MX, TTL settings?
>  
> I appreciate your feedback.
>  
> Thanks,
>  
> Scott Flinders
> Sr. Product Manager
> Verio Inc.
>  
======================================================================
This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
Before posting a question, please search the archives (see above URL).

======================================================================
This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
Before posting a question, please search the archives (see above URL).

======================================================================
This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
Before posting a question, please search the archives (see above URL).