comment on

Now I feel like the bad guy, either we leave things as they are, allowing service to deteriorate until unusable (BAD). We could place some stricture on mail volume like quotas (BACKLASH?).

The problem you're facing is as much political as it is technical, and you're positioning yourself to be the bad guy. You can get out from under by shifting part of the burden onto your users, and enlisting their help. Make the case now that service is going to deteriorate as the organization scales unless people can limit the amount of email they keep on the server, and ask your users what they think a reasonable retention policy might be. You won't get answers from everyone, and some folks will complain, but if you get a couple of good answers, you can always say "we asked, and the answer was X" if people complain later.

You'll still have technical problems to deal with, but setting reasonable limits now might give you some more breathing room.

In reply to Re: (OT) Giving users what they want / My mail administration dilemma by dws
in thread (OT) Giving users what they want / My mail administration dilemma by submersible_toaster

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks