Exchange Server 2013 - AntiSpam Agents on Mailbox Server

I'm interested in blocking additional spam messages coming through by use of the antispamagents.ps1 on my mailbox servers. Our current setup is the following:
Internet> 3rd party email filter> Exchange Mailbox server
My question is, if I turn on the antispamagents.ps1 and add spamhaus as a blocklist provider, will it block based on blacklisted IPs? My concern is that it won't do anything because it's not the next hop from the Internet.
Our current 3rd party email filter isn't really doing a good job. I've analyzed the headers and the sending IP is confirmed as blacklisted according to SpamHaus Zen.
Thanks in advance!

If you only have 1 Exchange server, then I assume you do not have a Edge transport server in your environment. The Edge role is the only role that has the Connection Filtering agent which is the agent that allows for RBL/DNSBL. So you might be out of luck
anyway. But to answer your question, Exchange will only see the IP of your 3rd party filter.
Or you can try a new 3rd party filter
http://www.appriver.com/services/
DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

Similar Messages

Exchange Server 2013: incoming messages are not delivered into user mailboxes occasionally

Exchange Server 2013 CU1, two mailbox servers (DAG, only one mail database), two CAS servers (NLB cluster). Two Sendmail/CentOS-based SMTP relays route mail between Exchange servers and Internet (incoming mail is routed to NLB cluster name).
Usually mail flow is OK: messages are sent and received normally. However, I've got several complains from different users. They state that occasionally they don't receive messages that were sent to them from outside. Tomorrow morning I've decided to
investigate the issue.
So, we have a message sent from Gmail account that was not delivered in user mailbox. It was received and routed to Exchange by Sendmail host:
Jun 27 22:06:37 MX01 sendmail[12169]: r5RG6HC8012166: to=<USER_ADDRESS>, delay=00:00:19, xdelay=00:00:19, mailer=smtp, pri=124702, relay=NLB-FQDN [NLB-IP], dsn=2.0.0, stat=Sent (<CAHgK_sjEkj41htuVsutMP3XhgR5RRDs8-EgSC-UfHoaiHWFj=A@mail.gmail.com>
[InternalId=13069585481819] Queued mail for delivery)
Running Get-MessageTrackingLog applet on the mailbox servers displayed the followed log entries for the message:
DB Server #1:
    22:11:18 HAREDIRECT
    22:11:18 RECEIVE
    22:11:18 AGENTINFO
DB Server #2:
    22:11:18 HARECEIVE
    22:12:44 HADISCARD
So, we can see that the message was placed into shadow queues, but was NOT delivered into mailbox (no DELIVER status entries). Also pay attention to the timing. Time on all the servers is in sync, but Sendmail timestamp is 22:06, and Exchange timestamps
are 5 minutes behind it.
Today a message sent to the same address from the same Google mailbox was received by Exchange and placed into user mailbox with no glitches.
We use Exchange antispam system activated on Exchange mailbox servers. Spam is never dropped silently. It is either returned to sender (SCL 9) or placed into quarantine mailbox (SCL 6 and above). I'm pretty sure that the lost message was not in the quarantine
mailbox this morning, and the sender didn't receive any NDRs.
Any ideas what to investigate next?

Hi,
Do you mean the emails are placed in the Shadow Redundancy queue?
Shadow Redundancy
http://technet.microsoft.com/en-us/library/dd351027(v=exchg.150).aspx
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

Hi Team,
Need urgent help in resolution of following error:
Environment Details: VMware ESXi 5.5 (vMotion)
Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
Prerequisites: Installed
Error: Installation gives Error at Step 10 during installation of Mailbox Service
Error Details Below:
Error:
The following error was generated when "$error.Clear();
if ([Environment]::OSVersion.Version.Major -ge 6)
$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
$reg= join-path (join-path $env:SystemRoot system32) reg.exe;
$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
if ((get-service wsbexchange).Status -eq "Running")
Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
Exchange /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
" was run: "Process execution failed with exit code 1.".

Resolved ! :)
Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
Thanks to all.

Best practice on mailbox database size & we need how many server for deployment exchange server 2013

Dear all,
We have an server that runs Microsoft exchange server 2007 with the following specification:
4 servers: Hub&CAS1 & Hub&CAS2 & Mailbox1 & Mailbox2
Operating System : Microsoft Windows Server 2003 R2 Enterprise x64
6 mailbox databases
1500 Mailboxes
We need to upgrade our exchange server from 2007 to 2013 to fulfill the following requirment:
I want to upgrade the exchange server 2007 to exchange server 2013 and implement the following details:
1500 mailboxes
10GB or 15GB mailbox quota for each user
How many
servers and databases are
required for this migration<ins cite="mailto:Mohammad%20Ashouri" datetime="2014-05-18T22:41"></ins>?
Number of the servers:
Number of the databases:
Size of each database:
Many thanks.

You will also need to check server role requirement in exchange 2013. Please go through this link to calculate the server role requirement : http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
2TB is recommended maximum database size for Exchange 2013 databases.
Here is the complete checklist to upgrade from exchange 2007 to 2013 : http://technet.microsoft.com/en-us/library/ff805032%28v=exchg.150%29.aspx
Meanwhile, to reduce the risks and time consumed during the completion of migration process, you can have a look at this proficient application(http://www.exchangemigrationtool.com/) that would also be
a good approach for 1500 users. It will help you to ensure the data security during the migration between exchange 2007 and 2013.

Exchange server 2013 supported mailbox databases and public folder databases

I want to know about Exchange server 2013 SP1 Standard and Enterprise version support how many Mailbox databases and Public folder Databases? Total Mailbox and Public folder databases supported information.
I Know as below but not clear:
1) Exchange server 2013 SP1 Sandard edition support 5 Databases, It's include Public folder databases, total=5 or 5 mailbox databases+5 public folder databases=10 databases
2) Exchange server 2013 SP1 Enterprise edition support 100 Databases, It's include Public folder databases, total=100 or 100 mailbox databases+100 public folder databases=200 databases
kindly let me know. Thanks.
Babu

Hi Babu,
Please check this link too.
http://blogs.technet.com/b/exchange/archive/2013/06/04/per-server-database-limits-explained.aspxhttp://blogs.technet.com/b/exchange/archive/2013/06/04/per-server-database-limits-explained.aspx
Thanks & Regards S.Nithyanandham

How to get list of Users[MailBoxes] in Exchange Server 2013 by using EWS Managed API

Hi all,
I need list of Users exists in my Exchange server 2013 , i.e Mail Box Users login name.
I was created Full Access permissions of all users to Admin user account, to access each user Mailbox programatically
i need the list of Mailboxes in exchange server .
MailBox mailbox = new MailBox("user");
Please share your ideas

Hi,
We can run the following command in Exchange Management Shell to get all user mailboxes name and export it to a .csv file:
Get-Mailbox -ResultSize Unlimited | Select Name,Alias,RecipientTypeDetails | Export-Csv c:\Users.csv
If you want to retrieve the list of users by using EWS Managed API, I suggest you can ask a question in Exchange Development forum for more suggestion:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads
Regards,
Winnie Liang
TechNet Community Support

Exchange Server 2013 to 2010 mailbox proxy is not working

I have exchange server 2013 and exchange server 2010 in co-exist. I have 3 cas server and 3 mbx server 2013 on windows server 2012 standard, 2 hub/cas server and 2 mbx server 2010 on windows server 2008 r2. when I try to access owa of exchange server 2010
mailbox using exchange 2013 url, I am getting the error as "something went wrong. sorry, we can't get that information right now, please try again later. If the problem continues please contact your helpdesk"
Vishal C. Kalal | MCITP: Exchange 2010-2007 | Windows Server 2008

Hi,
To narrow down the cause, I recommend the following troubleshooting:
Check if the issue happens on all users.
Try to directly login OWA 2010 and check if it works well.
Check the IIS log on CAS 2013 server and find the error related to OWA.
Thanks,
Angela Shi
TechNet Community Support

Mails struck in Drafts folder after Transport Agent installed in Exchange Server 2013

Hi all,
I created Transport Agent and installed successfully in exchange server 2013.
After that mails are struck in drafts folder.
I thought because of My Custom transport Agent , then i Uninstall Transport agent.
but still no use.
I restart Microsoft Exchange Transport Service and restart my server also.
Here is the code i used
public sealed class MyAgentFactory : RoutingAgentFactory
public override RoutingAgent CreateAgent(SmtpServer server)
return new MyAgent();
public class MyAgent : RoutingAgent
public MyAgent()
this.OnSubmittedMessage += new SubmittedMessageEventHandler(this.MySubmittedMessageHandler);
public void MySubmittedMessageHandler(SubmittedMessageEventSource source, QueuedMessageEventArgs e)
e.MailItem.Message.Subject = "This message passed through my agent: " + e.MailItem.Message.Subject;
I search in google about mails struck in drafts folder, all replies are
restore Default Receive Connectors. How can i restore it.
here is the link i see
http://community.spiceworks.com/topic/309145-exchange-2013-messages-stuck-in-drafts

Hi Martina
Miskovic,
Here I am facing some weird situation.
Mails again stuck in Drafts folder.
i didn't installed anything. just checking again after some
time gap .
I tried again by restarting all services
, but no use.

Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

Hello guys,
I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
What should I check and configure to make it work?

Hi,
I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact EMC supplier to improve it.
By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Recover mailbox from Exchange server 2010 information store to exchange server 2013

I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
I would like to recover a couple of mailboxes to an exchange server 2013.
Can anyone give me a detailed walk through of how I can accomplish this?
Thank in advance

Well if your AD is messed up that leaves you in a jam for sure because;
1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
3. Here is a good article on how to accomplish
http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB. We make a product that can do this (DigiScope), however if you don't
have any budget to handle its a non-issue.
The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
BTW if you AD is messed up, where are you putting this new 2013 server?
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Mailbox Recovery From Disaster Exchange Server 2013

I have to exchange server EX01 and EX02. Now EX01 have to down didn't run anyway. Default database on EX01 that have to Administrator mailbox and the default database was not member of dag. now i can't move administrator database another database location.
Md. Ramin Hossain

Hi Ramin,
Thank you for your question.
By our understanding, Ex01 didn’t run any way, we could take a disaster recovery by the following steps:
Reset the computer account for the down server;
Install the operating system and name on the new server with the same name as the lost server. Recovery won't succeed if the server on which recovery is being performed doesn't have the same name as the lost server;
Join the server to the same domain as the lost server;
Install the necessary prerequisites and operating system components;
Log on to the server being recovered and open a command prompt;
Navigate to the Exchange 2013 installation files, and run the following command:
Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms
7. After Setup has completed, but before the recovered server is put into production, reconfigure any custom settings that were previously present on the server, and then restart the server.
The following link is about Exchange 2013 prerequisites:
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
We could learn more about Exchange 2013 disaster recovery by the following link:
http://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx
Then, we could recovery database from a backup or copy of a database by the following steps:
Create the recovery database;
This example creates the recovery database RDB2 on the Mailbox server MBX1 using a custom path for the database file and log folder:
New-MailboxDatabase -Recovery -Name RDB2 -Server MBX1 -EdbFilePath "C:\Recovery\RDB2\RDB2.EDB" -LogFolderPath "C:\Recovery\RDB2"
   2. Copy a recovered database and its log files, or restore a database and it log files, to the location we will use for our recovery database.
   3. Use Eseutil to bring that database into a clean shutdown state.
In the following example, EXX is the log generation prefix for the database (for example, E00, E01, E02, and so on).
Eseutil /R E01 /l E:\Databases\RDB1 /d E:\Databases\RDB1
4. Create a recovery database. Give the recovery database a unique name, but use the name and path of the database file for the EdbFilePath parameter, and the location of the recovered log files for the LogFolderPath parameter.
The following example illustrates creating a recovery database that will be used to recover DB1.edb and its log files, which are located at E:\Databases\RDB1.
     New-MailboxDatabase -Recovery -Name <RDBName> -Server <ServerName> -EdbFilePath " E:\Databases\RDB1\DB1.EDB" -LogFolderPath "E:\Databases\RDB1"
5. Restart the Microsoft Exchange Information Store service:
Restart-Service MSExchangeIS
6. Mount the recovery database:
    Mount-database <RDBName>
We could refer to the following link:
http://technet.microsoft.com/en-us/library/dd876954(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Exchange Server 2013 Mailbox - High CPU Usage

Hi,
We are having an issue with our Exchange 2013 Mailbox Server.
The process Microsoft.Exchange.Store.Worker consumes most of the CPU utilization.
Have anyone encountered this issue? How were you able to resolve it?
Thanks

Hi,
According to your description, your database is not active. And to understand more about the issue, I’d like to confirm if there is some user experience slow connection or other performance issue.
However, since in Exchange 2013 single Store Worker Process is only responsible for one database, we can firstly confirm if the specific mailbox database causes the high CPU:
http://msexchangeteam.in/how-to-identify-which-microsoft-exchange-store-worker-process-is-owned-by-mailbox-database-in-exchange-server-2013/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Copy emails (entire mailbox) to another exchange server 2013

Hi,
We are a hosted Exchange server 2013 solution provider, and we want to migrate customer mailboxes (from exchange 2007, 2010) to Exchange 2013 using some API, as we have a web portal for other admin tasks too. Someone told us that we can use EWS Managed API
for this purpose.
Is there any article in this regard, which can help us?
Or, is there any other API which we can use?
Thanks in anticipation.
Regards, David Johnson

Hi,
Glen thanks a lot for your reply. You are always a great help.
We are currently exporting\importing using powershell manually, but there are some difficulties in automating it using a web based app, as we don't want our customers to do any manual changes, while also, from our server, we cannot execute powershell commands
on remote Exchange 2007 servers.
Automating Cross forest migration is also very diificult, as you know that it has many steps, which are hard to automate, and also there is no api for MRS, as we know.
We have seen some migration utilities doing migration using EWS API, like CodeTwo, and also Transend
Migrator. Can you please tell, if you know, how they are doing it.
Thanks.
Regards, David Johnson

How can i get newly added contacts for a Mailbox User in Exchange Server 2013

Hi all,
I need to synchronize contacts in Exchange Server and Sugar CRM Application, for that
i need to get newly added contacts for a User in Exchange Server 2013 by using EWS Managed API.
I know how get the list of all contacts for a particular user , but in the list how i can find
new contacts ?

Hi Dora,
that's the fun thing:
You add your own property (and it'll be invisible to outlook users, not to worry).
Extended Properties allow you to define custom property on Exchange Items. And it has a
method for setting those too.
Here's a short post doing a very simple intro on using Extended Properties.
Glen's Exchange Blog is a generally useful resource when working with EWS, I'm confident you'll be able to find lots of tips there as well.
Cheers,
Fred
There's no place like 127.0.0.1

Get list of User Mailboxes in Exchange server 2013 by using EWS managed API

Hi all,
I need list of Users exists in my Exchange server 2013 , i.e Mail Box Users log in name.
i know the command in Powershell to get list, but i need this using code[ ews managed API].
How can i achieve this ?
Please share your ideas

Hi Glen,
i follow your suggested links i wrote below code ,
here i am getting error
The term 'Get-Users' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
SecureString password = new SecureString();
string str_password = "EIS2014!@#";
string username = "[email protected]";
foreach (char x in str_password) { password.AppendChar(x); }
PSCredential credential = new PSCredential(username, password);
WSManConnectionInfo connectionInfo = new WSManConnectionInfo(new Uri("http://ExchangeServer.admin.com/powershell"), "http://schemas.microsoft.com/powershell/Microsoft.Exchange", credential);
//connectionInfo.AuthenticationMechanism = AuthenticationMechanism.Basic;
Runspace runspace = RunspaceFactory.CreateRunspace(connectionInfo);
PowerShell powershell = PowerShell.Create();
PSCommand command = new PSCommand();
command.AddCommand("Get-Users");
command.AddParameter("ResultSize", 50);
powershell.Commands = command;
runspace.Open();
powershell.Runspace = runspace;
var aa = powershell.Invoke();
Please help me.

Exchange Server 2013 - AntiSpam Agents on Mailbox Server

Similar Messages

Maybe you are looking for