Set-ActiveSyncMailboxPolicy -identity “POLICYNAME” -MaxInactivityTimeDeviceLock:00:00:00
This script allows you to use instant “lock” on your phone…
Set-ActiveSyncMailboxPolicy -identity “POLICYNAME” -MaxInactivityTimeDeviceLock:00:00:00
This script allows you to use instant “lock” on your phone…
get-mailbox -ResultSize Unlimited | where {$_.RecipientType -eq [Microsoft.Exchange.Data.Directory.Recipient.RecipientType]::UserMailbox } | update-safelist
Set Public folder primary SMTP address:
Set-MailPublicFolder -Identity PublicFolder@contoso.com -PrimarySmtpAddress info@contoso.com
Set Public folder permissions
Add-PublicFolderClientPermission -Identity “public@folder.com” -User Username -AccessRights Editor
Add-IPBlockListProvider -Name zen.spamhaus.org -LookupDomain zen.spamhaus.org -AnyMatch $True -Enabled $True -RejectionResponse “Your IP is blacklisted! http://www.spamhaus.org“
This script adds new provider called zen.spamhaus.org, makes lookups to zen.spamhaus.org and it works on any reply (127.0.0.1,2 …), it does enable this provider and it sets response that is sent to sender.
http://technet.microsoft.com/en-us/library/bb125165.aspx – How to prepare certificate request
http://technet.microsoft.com/en-us/library/aa995942.aspx – How to create certificate for mutiple hosts and how to configure certificate for specific service in Exchange 2007
http://technet.microsoft.com/en-us/library/bb201700.aspx – Modifying Outlook web access on Exchange 2007
It is possible that dedicated servers come in a cheap web hosting deal. However you might need to make certain compromises where the web design or the domain name registration is concerned.
I am often asked whcih blocklist providers do I use / trust not to get mail filtered becouse of bad blacklist provider.
On my servers I am using three lists (sorted by quality – my personal opinion 🙂 ):
zen.spamhaus.org – a combination of three spamhaus.org lists (SBL, XBL and PBL)
bl.spamcop.net – Spamcop blacklist
list.dsbl.org – Distributed sender blackhole list
I use this three lists without getting in troubles – at least for now. I suggest that you regularly check your SMTP logs to see how list are working.
I always notify sender that it was blocked by a blacklist.
Here is an example from and Exchange 2007 SMTP recieve log:
> “220 mail.mydomain.com Microsoft ESMTP MAIL Service ready”
< EHLO [87.69.94.190],
> 250-mail.mydomain.com Hello [87.69.94.190],
< MAIL FROM:<cathiFerm@flagpeakproperties.com> SIZE=656,
> 250 2.1.0 Sender OK,
< RCPT TO:<xxx.xxx@mydomain.com>,
> 550 5.7.1 Your IP is blacklisted. http://www.spamhaus.org,
< QUIT
> 221 2.0.0 Service closing transmission channel
After updating some SBS servers 2003 I noticed that Exchange System manager crashes if I do click help. The problem is that Internet explorer 7 – which was installed during Windows Update changes the version of Psapi.dll which is used by Exchange system manger (older version) and by IE7. To solve this problem you just need to / Po posodobitvah sistemov SBS 2003 sem ugotovil, da se Exchange System Manager “obesi”, ce v njem pritisnem na tipko Help. Tezava je v tem, da tako IE7 kot Exchange 2003 izkoriscata Psapi.dll, ki se pa med njima razlikuje. Za rešitev težave sledite spodnjim navodilom:
1. Stop the Microsoft Exchange System Attendant service (dependent services wil be also stopped) / Zaustavite servis Microsft Exchange System Attendant (pri tem sem bodo zaustavili še “odvisni” servisi).
2. Stop the IIS Admin Service (dependent services will be also stopped) / Zaustavite servis IIS Admin Service (pri tem se bodo zaustavili še “odvisni” servisi).
3. Rename the file Psapi.dll to Psapi.dll.tmp (or whatever) which can be found in your .Exchsrvrbin directory // Preimenujte Psapi.dll v Psapi.dll.tmp, datoteko pa najdete v mapi .Exchsrvrbin. <be> 4. Start stopped services / Ponovno poženite zaustavljene servise