The KB article says nothing about this being fixed in a service pack, because this behavior is "by design". You are correct, Andy, that neither 5.5 nor 2000 prohibit sending of SMTP mail based on quota. You are also correct that the particular component which is responsible for the MAPI, POP and IMAP protocols is irrelevant, because it is SMTP that is used for sending mail, and it is not handled by the Information Store in any version of Exchange.
The only effective enforcement mechanism for POP and IMAP users is, unfortunately, prohibit send and receive. You could argue, even, that it is the only truly effective enforcement mechanism for ANY user since a savvy user who is blocked from sending by MAPI might be able to figure out that he can send by SMTP. In reality this hasn't been a problem, but it's technically true. Ed Crowley MCSE+Internet MVP kcCC+I Tech Consultant hp Services Protecting the world from PSTs and Bricked Backups! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Andy David Sent: Saturday, January 18, 2003 5:42 PM To: Exchange Discussions Subject: RE: POP3 & IMAP Prohibit Send on E2K Yes, Exchange 5.5 supports these protocols natively. I dont know if I would quite say "the Information Store was responsible for MAPI, POP3, IMAP, etc. " as you phrase it. But nonetheless, why should it have worked in 5.5? Both Pop3 and imap use SMTP to send mail yes? What mechanism is in the IMS to check the storage limits of the user and then magically send an error message back to pop3 or imap client? What if you used one server to host the mail and another to send mail? ---------- Original Message ---------------------------------- From: "Fay, Mark" <[EMAIL PROTECTED]> Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> Date: Sat, 18 Jan 2003 20:12:57 -0500 >Let me clarify. Prior to E2K the Information Store was responsible for >MAPI, POP3, IMAP, etc. In Exchange 2000 Microsoft has broken out POP3 >and IMAP4 protocols away from the Information Store. They now run as >separate services. If you chose to you could stop and disable >whichever one you chose to not support or offer given your environment. > >In EX 5.5, mailbox limits for POP and IMAP should have worked. I never >needed to test it however. According to my client, it has for them. >Higher ED with ~1,000 staff mailboxes. > >-----Original Message----- >From: Andy David [mailto:[EMAIL PROTECTED]] >Sent: Saturday, January 18, 2003 6:08 PM >To: Exchange Discussions >Subject: RE: POP3 & IMAP Prohibit Send on E2K > >I cant. >Im just not aware of any mechanism in any version of Exchange that would >prevent a pop3 or imap user from sending email if they were over their >sending limit. > > >---------- Original Message ---------------------------------- >From: "Fay, Mark" <[EMAIL PROTECTED]> >Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> >Date: Sat, 18 Jan 2003 17:17:44 -0500 > >>Your message implies that this feature did NOT work on 5.5 for POP & >>IMAP clients? >>They used the IS for their protocols, please explain your answer. >> >>-----Original Message----- >>From: Andy David [mailto:[EMAIL PROTECTED]] >>Sent: Saturday, January 18, 2003 3:49 PM >>To: Exchange Discussions >>Subject: Re: POP3 & IMAP Prohibit Send on E2K >> >>As far as I know, its still true for E2k - as it was for 5.5. >> >> >> >>---------- Original Message ---------------------------------- >>From: "Fay, Mark" <[EMAIL PROTECTED]> >>Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> >>Date: Sat, 18 Jan 2003 15:09:50 -0500 >> >>>Is this KB Article still on point, 247126? It's dated 4/11/01 and >>>only refers to E2K with no SP. I am deploying a 3,000 student E2K >>>SP3 server with POP and IMAP only clients with MB limits. Obviously >>>this will go >BUST >>>on me and I need to change the design for OWA only, MAPI won't be >>supported. >>> >>> >>>http://support.microsoft.com/default.aspx?scid=kb;en-us;247126 >>> >>>The summary of the article is POP3 and IMAP clients don't use the IS >>>as previous versions of Exchange did for sending, since now SMTP is >separated. >>>Therefore they bypass the "prohibit send" feature if the Mailbox is >>>over >>its >>>limit. >>> >>>Regards, >>> >>>Mark >>> >>>FAY CONSULTING, LLC >>>E-mail: [EMAIL PROTECTED] >>>www.fay.com >>> >>> >>> >>>_________________________________________________________________ >>>List posting FAQ: http://www.swinc.com/resource/exch_faq.htm >>>Archives: http://www.swynk.com/sitesearch/search.asp >>>To unsubscribe: mailto:[EMAIL PROTECTED] >>>Exchange List admin: [EMAIL PROTECTED] >>> >> >>_________________________________________________________________ >>List posting FAQ: http://www.swinc.com/resource/exch_faq.htm >>Archives: http://www.swynk.com/sitesearch/search.asp >>To unsubscribe: mailto:[EMAIL PROTECTED] >>Exchange List admin: [EMAIL PROTECTED] >> >>_________________________________________________________________ >>List posting FAQ: http://www.swinc.com/resource/exch_faq.htm >>Archives: http://www.swynk.com/sitesearch/search.asp >>To unsubscribe: mailto:[EMAIL PROTECTED] >>Exchange List admin: [EMAIL PROTECTED] >> > >_________________________________________________________________ >List posting FAQ: http://www.swinc.com/resource/exch_faq.htm >Archives: http://www.swynk.com/sitesearch/search.asp >To unsubscribe: mailto:[EMAIL PROTECTED] >Exchange List admin: [EMAIL PROTECTED] > >_________________________________________________________________ >List posting FAQ: http://www.swinc.com/resource/exch_faq.htm >Archives: http://www.swynk.com/sitesearch/search.asp >To unsubscribe: mailto:[EMAIL PROTECTED] >Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
