There are a couple workarounds to this limitation: - Create more users with aliases. Use either the email routing feature or Gmail's forwarding feature to forward the mail to the intended recipient.
http://www.google.com/support/a/bin/answer.py?answer=77182 http://mail.google.com/support/bin/answer.py?answer=10957 - Use + addresses. http://mail.google.com/support/bin/answer.py?answer=12096 -alex On Nov 26, 2:51 pm, "Ryan Shelley" <[EMAIL PROTECTED]> wrote: > Sam, > > But at the same time, you have to ask yourself, if there is a limit and a > user is hitting that limit, is the user using that function as it's designed > or is your limit unreasonable? Just because you can technically make > something unlimited doesn't mean you should. Quite possibly the limit is > there not to increase performance or for readability/layout, but to ensure > that the resource is used properly and not abused. > > To use your example, if I'm a professor, and I teach 5 classes per semester, > and I need a nickname for each class I'm teaching, and you've run out of > nicknames, then obviously the nicknames that were used for classes I taught > several semesters ago haven't been removed. Alternately, maybe a mailing > list would be a better option. > > Just playing devil's advocate, that's all! > > -Ryan > > On Nov 26, 2007 12:41 AM, Sam Johnston <[EMAIL PROTECTED]> wrote: > > > Ryan, > > > While I too am interested in this particular use case, I've lost count of > > the number of times that I've been affected by arbitrary limits like this > > and it's impossible to predict what people all the weird and wonderful > > things people will want to use the tools for. If there's a good reason for > > such limits (eg limiting the number of users sharing a spreadsheet for > > performance or the number of recipients of a mail message for spam) then > > fair enough but I'd also be interested in the rationale behind selecting 30 > > as the limit in this case. One possible use case would be having addresses > > for course administrators at a school/university - with only a single > > recipient mailing lists are not necessary (and may also be subject to > > similar limits) and it's conceivable that one person administers more than > > 30 courses! > > > My point in this rant is simply to think long and hard before implementing > > arbitrary limits, > > > Sam > > > On 11/26/07, Ryan Shelley < [EMAIL PROTECTED]> wrote: > > > > Why does a single person need more than 30 nicknames? > > > > On Nov 23, 2007 9:24 PM, alex94040 < [EMAIL PROTECTED]> wrote: > > > > > That sucks, and I totally don't understand why that limit is in place. > > > > Are you worried about abuse? Can you increase that limit to, say, > > > > 200? > > > > > On Oct 5, 1:48 pm, "Austin (Google)" < [EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > Yes, the max number of nickname per user is 30. You should be > > > > getting > > > > > a error code 1501-TooManyNicknamesForUser when you are creating > > > > beyond > > > > > 30 nicknames. > > > > > > Austin > > > > > > On Oct 3, 11:09 pm, alex94040 <[EMAIL PROTECTED] > wrote: > > > > > > > I'm trying to add a number of nicknames to a test account we've > > > > set up > > > > > > on our domain; i'm getting a "server error" once I try to add > > > > > > nicknames past 30. Does anyone know why? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
