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

Comments

  1. 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
  2. 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
  3. 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
  4. how can i disable pop3 from more than 1000 users

    ReplyDelete
    Replies
    1. 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

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 

Ports that need to be open on Firewall for Edge Transport servers

Ports that need to be open on firewall for Edge Server subscription with Hub Server to function properly: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server) Since Edge server needs to communicate with Hub server it is important that it can resolve Hub transport servers by FQDN and Hub transport servers must be able to resolve Edge servers by its FQDNs. To accomplish this you need to either open 53 (DNS) port and configure internal network adapter to use internal DNS but as a security precaution I would suggest to enter DNS records for Edge servers on local DNS manually and to fill hosts file on Edge servers with FQDNs for Hub transport servers.