<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name="Redirect to http" enabled="true" patternSyntax="Wildcard" stopProcessing="true">
<match url="*" negate="false" />
<conditions logicalGrouping="MatchAny">
<add input="{HTTPS}" pattern="off" />
</conditions>
<action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Found" />
</rule>
</rules>
</rewrite>
</system.webServer>
</configuration>
Category Archives: Microsoft
Code Snippets ASP.Net IISSSL Redirect URL, rewrite rule
22 de Junho de 2018 – 11:10
MRS Proxy Error “The connection to the server could not be completed”
6 de Junho de 2018 – 15:21
Check MRS endpoint user and password.
Exchange 2013 not receiving external emails
6 de Junho de 2018 – 10:14
Remote Server returned ‘550 5.1.8 Access denied, bad outbound sender
12 de Abril de 2018 – 17:22
Remote Server returned ‘550 5.1.8 Access denied, bad outbound sender’
Solution:
–Non-Office 365 user use this https://sender.office.com (self-service delisting portal) to remove themselves from the blocked senders list.
–Office 365 user, as an admin you can unblock your blocked Office 365 email account via using Exchange admin center.
• Go to the EAC, navigate to protection > action center.
• Select the Search icon and enter the SMTP address of the blocked user.
• Click Unblock Account in the description pane.
• Click Yes to confirm the change.
For more detailed information, please refer to the article: Removing a user, domain, or IP address from a block list after sending spam email
421 4.4.2 message submission rate for this client has exceeded the configured limit
26 de Fevereiro de 2018 – 10:09
Solved after run the command Set-receiveconnector “Server Name\Client Connector” -Messageratelimit 100.
550 5.7.1 Message rejected as spam by Content Filtering
24 de Janeiro de 2018 – 15:37
Content Filtering has been enabled on the recipients’ mail server. This configuration is incompatible with GFI MailEssentials when installed as a relay server, all email filtering should happen on the relay server. For more information on Content Filtering and how to disable it, please see the following:
If the mail server is Microsoft Exchange 2013 and 2016 server:
If the mail server is Microsoft Exchange 2010 server:
If the mail server is Microsoft Exchange 2007 server:
UnobtrusiveValidationMode requires a ScriptResourceMapping for ‘jquery’ – Asp.NET
9 de Janeiro de 2018 – 17:23
erro:
Erro de Servidor no Aplicativo '/'.
WebForms UnobtrusiveValidationMode requer um ScriptResourceMapping para 'jquery'. Adicione um jquery nomeado de ScriptResourceMapping (diferencia maiúsculas de minúsculas). Descrição: Ocorreu uma exceção sem tratamento durante a execução da atual solicitação da Web. Examine o rastreamento de pilha para obter mais informações sobre o erro e onde foi originado no código.
Adicionar no web.config
<appSettings>
<add key="ValidationSettings:UnobtrusiveValidationMode" value="None"/>
</appSettings><span style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" data-mce-type="bookmark" class="mce_SELRES_start"></span>
Enable antispam functionality on Mailbox servers
9 de Novembro de 2017 – 12:45
Applies to: Exchange Server 2016
Topic Last Modified: 2016-03-28
Use the Install-AntispamAgents.ps1 PowerShell script to install and enable the built-in Exchange antispam agents on a Mailbox server.
The following antispam agents are available in the Transport service on Exchange 2016 Mailbox servers, but they aren’t installed by default:
- Content Filter agent
- Sender Filter agent
- Sender ID agent
- Protocol Analysis agent for sender reputation
You can install these antispam agents on a Mailbox server by using an Exchange Management Shell script, which is important if these agents are your only defense to help prevent spam. Typically, you don’t need to install the antispam agents on a Mailbox server when your organization uses other types of antispam filtering on incoming mail.
 Note: |
|---|
| Although the Recipient Filter agent is available on Mailbox servers, you shouldn’t configure it. When recipient filtering on a Mailbox server detects one invalid or blocked recipient in a message that contains other valid recipients, the message is rejected. The Recipient Filter agent is enabled when you install the antispam agents on a Mailbox server, but it isn’t configured to block any recipients. For more information, see Recipient filtering procedures on Edge Transport servers. |
- Estimated time to complete this task: 15 minutes
- You can only use PowerShell to perform this procedure. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see Open the Exchange Management Shell.
- The Connection Filtering agent and the Attachment Filtering agent aren’t available on Mailbox servers. They’re only available on Edge Transport servers, and they’re installed and enabled there by default. However, the Malware agent is installed and enabled by default on Mailbox servers. For more information, see Anti-malware protection.
- If you have other Exchange antispam agents operating on the messages before they reach the Mailbox server (for example, an Edge Transport server in the perimeter network), the antispam agents on the Mailbox server recognize the antispam X-header values that already exist in messages, and those messages pass through without being scanned again.
- You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the “Transport configuration” entry in the Mail flow permissions topic.
- For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
 Tip: |
|---|
| Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection. |
PowerShell: Get-ADUser to retrieve password last set and expiry information
2 de Novembro de 2017 – 12:03
Get-ADUser -identity username -properties *
get-aduser -filter * -properties passwordlastset, passwordneverexpires |ft Name, passwordlastset, Passwordneverexpires
get-aduser -filter * -properties passwordlastset, passwordneverexpires | sort name | ft Name, passwordlastset, Passwordneverexpires
Export the list to CSV so we can work on it in Excel. In this example we substitute, format table (ft) for select-object.
Type:
Get-ADUser -filter * -properties passwordlastset, passwordneverexpires | sort-object name | select-object Name, passwordlastset, passwordneverexpires | Export-csv -path c:\temp\user-password-info-20131119.csv
PowerShell: Get-ADUser to retrieve password last set and expiry information
Turn Exchange Anonymous Relay On or Off or View Connector Status
12 de Outubro de 2017 – 11:06
This EMS script for Exchange 2007-2016 allows Exchange Administrators to toggle anonymous external relay permissions on front-end Receive Connectors. Connectors listed in Yellow allow anonymous SMTP emails to any internal or external recipients. Connectors listed in White only
Toggle-ExternalRelayReceiveConnectors
C:\_tmp>.\Toggle-ExternalRelayReceiveConnectors.ps1 Toggle External Relay 1 - SRV-EXCH2\Client Frontend EXSERVER1 2 - SRV-EXCH2\Default Frontend EXSERVER1 3 - SRV-EXCH2\Outbound Proxy Frontend EXSERVER1 X - Exit Which Receive Connector to toggle:
This EMS script for Exchange 2007-2016 allows Exchange Administrators to toggle anonymous external relay permissions on front-end Receive Connectors. Connectors listed in Yellow allow anonymous SMTP emails to any internal or external recipients. Connectors listed in White only allow SMTP emails to internal recipients. Run this script from the Exchange Management Shell.
See my blog for more information: http://www.expta.com/2016/01/turn-exchange-anonymous-relay-on-or-off.html
Home