Skip to main content

Disable POP3 for ALL users

To disable POP3 for all users with mailboxes on exchange 2007 (only this was executed this time; probably it works in a mixed environment too) you need to execute following command:

Get-CASMailbox | Set-CASMailbox -PopEnabled $False

POP3I

In the same way the script can be executed to enable/disable:

  • OWA
    Get-CASMailbox | Set-CASMailbox -OWAEnabled $False
  • ActiveSync
    Get-CASMailbox | Set-CASMailbox -ActiveSyncEnabled $False
  • IMAP
    Get-CASMailbox | Set-CASMailbox -IMAPEnabled $False
  • MAPI
    Get-CASMailbox | Set-CASMailbox -MAPIEnabled $False
Labels:

Comments

  1. AnonymousFebruary 11, 2009 at 9:44 PM

    Thanks a lot!

    ReplyDelete
  2. AnonymousMarch 10, 2009 at 2:50 AM

    good find..however how do have pop disabled for all new users? as soon as you create a new account pop is enabled...how can it be set by default that all pop is disabled...

    ReplyDelete
  3. TomMay 19, 2009 at 10:47 PM

    Nice concise article, great reference. To check your work, run "Get-CASMailbox | more". You'll see which accounts have which services enabled.

    Also, I'd love to know how to set defaults on this as well, perhaps more googling is in my future.

    ReplyDelete
  4. Ytsejamer1December 9, 2010 at 8:14 PM

    What if I wanted to run it only on a single Exchange 2007 server? I can't quite get the command correct.

    But as an FYI...the command as posted in the blog applies to both Exchange 2007 and Legacy 2003 Mailboxes.

    Thanks for the good info!

    ReplyDelete
  5. UnknownAugust 26, 2012 at 8:54 AM

    how can i disable pop3 from more than 1000 users

    ReplyDelete
    Replies
    1. DuĊĦan SoraviaAugust 26, 2012 at 6:15 PM

      Add -resultsize unlimited to your script... In your case it would be Get-CASMailbox -resultsize unlimited | Set-CASMailbox -POPEnabled $False

      Delete

Post a Comment

Popular posts from this blog

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi
1 comment
Read more

Exchange Admin Center language

Depending on your computer language settings, Exchange Admin Center can take those and open in a language you actually don't want to use. You'll Google that this can be changed if administrator/ admin user has mailbox by openening OWA settings and changing Regional parameters. But usually Admin user does not have mailbox or you don't want her/him to have it. You will search again and find that you can add mkt=en-US (as an example) to the URL of the Exchange Admin Center (https://yourexchangehostname/ecp?ExchClientVer=15&mkt=en-US) Third option you have is opening Internet Explorer settings (I am using Windows 2016) Click languages Click Set Language Preferences Add language you want to use by clicking Add language Use Move up or Move Down options to put desired language on top Close Internet Explorer Open it again and login again to Exchange Admin Center
Post a Comment
Read more

Free/Busy missing - Cloud to On-Premises

We had a problem where M365 users could not retreive Free/Busy information from on-premise Exchange server. Hybrid setup was run and everything was working fine except this. After research I found out that TargetSharingEpr is the way to look at. There are many sites out there that are pointing to the same setting but only Set-OrganizationRelationship is used to change the value. The problem is, this value is available for two commands: Set-IntraOrganizationConnector Set-OrganizationRelationship While we changed the value in  Set-OrganizationRelationship it didn't work until we changed the value in  Set-IntraOrganizationConnector too. By default it should work with just  TargetAutodiscoverEpr but for us it didn't. Finally we ran this command on Intra Organization Connector which is used from Cloud to On-prem:  Set-IntraOrganizationConnector -TargetSharingEpr   https://mail.domain.com/ews/exchange.asmx And it worked.
Post a Comment
Read more