Hi Professionals,
I want to know all the DNSBL listed domain and ip addreses, how do i get that all the information.
I am using Trend IMSS 7.1, a particular IP listed in Email Reputation Services but i want to know whether its cateogrized by Trend are its globally.
If its globally we will have discussion with Trend.
Its soo urgent pls help me...
Thanks, Venkatesh. "Hardwork Never Fails"
i just upgrade to 2013 and the upgrade process went great.
but if i leave the server running for a while (over 12 hours) i cant receive external email.
when i reboot i can then receive external email for a while.
does anyone have any ideas?
My organization is running Exchange Server 2010 SP2. We have Exchange On-Premises and Office 365 in our Exchange environment. Office 365 only has a few accounts in it as we have barely begun the migration process and we don't want to continue until we know on premises is working properly. Right now we are seeing e-mails getting stuck in the queues and the Transport Service keeps stopping.
Has anyone dealt with this and if so, how did they fix it?
Thanks.
If we deploy Exchange 2013 in co-exist envt with Exch 2007 and have to shut down Exch 2013 for some maintenance / update, does Ex-2007 takes care of the mail flow for the users who are still on Ex-2007 and not migrated over to Ex-2013?
I know there won't be any issue for outgoing email. I am not sure for incoming emails. Any suggestion?
Thanks.
Like any organisation, I have a number of devices ranging from routers to switches, printers to multifunction centers, and some applications/scripts that send email via SMTP.
Some devices have no authentication mechanism in their software, while others offer windows credentials, and some support TLS. I have been doing quite a bit of research on this and some suggestions either don't work, or are ill advised. On one MS forum the "Moderator" confessed they had no idea how or if it could be done.
So what is the best way, and can it be provided as a step by step method. I've set them up in the past with since Exchange 5.5, 2000, 2003, 2007, 2010 but cant crack it in 2013. Judging by the number of hits on topics around this I am not in the minority.
I manage many sites that have the same types of devices making migration to Exchange 2013 a risk - so is it possible at all with Exchange 2013 - or do we exercise our downgrade rights to 2010 so that our major devices like the Multifunction centres can work in the way intended.?
To date I have tested Receive Connectors with the following properties
This is the error message that I can see in my Exchange Queue,
My queue are reaching to 1000.
Hi There,
I've a retention policy in my organization for purging the items from deleted items folder after 3 days of getting deleted from the inbox. The policy is also working fine for the emails which are being deleted from the inbox. But when it comes to deleting a folder from the inbox, eventhough the retention policy gets applied the folder still remains in the deleted items folder but all the emails inside it gets purged normally.
Can some one please let me know if this is the default behaviour of how the MRM works or is this somekind of a bug. Also please let me know if there are any fix to this issue such that the folder should also get purged along with the mails as per the MRM policy.
I'd like to check the mailflow from my back end Exchange 2013 server through the front end Exchange 2013 server.
How can I do that?
I have a C# application that sends to distribution lists via the System.Net.Mail.SmtpClient class.
The distribution lists are pulled using an LDAP query, and I store both the outlook name for the distribution list as well as the actual email of the distribution list for use.
For example: I store both #TEST Users (name) and #testusers@mycompany.com (actual email address for the distribution list)
I've run several tests with multiple distribution lists without any problems. Emails send fine without any problems.
One of my distribution lists, however, #XYZApp Users, refuses to send to anyone. This distribution list has a total of 546 recipients. None of the other lists are that large, however, I did successfully send an email with two separate distribution lists that totalled 744 recipients (one list had 438 the other 306).
Any ideas why one distribution list would work and others would not? Is there a cap on the number of recipients in a distribution list when sending emails over SMTP?
Hi,
We have hybrid environment setup for migrating mailboxes to Office 365. There are old Exchnage 2003 and new installed Exchange 2010 hybrid servers setup for migration. So far we have migrated 10+ users to Office 365. The problem that we are facing is delay in emails being received by Office 365 users.
We have checked email headers and email flow is something like this..
Mail from On-prem users to Office 365 -> On-prem Exchange 2003 server ->[DELAY] -> Mail filtering solution (mailcontrol) -> FOPE (bigfish.com -> Office 365 cloud
Mail from External user to Office 365 -> Mail filtering solution (websense) ->On-prem Exchange 2003 server-> [DELAY] Mail filtering solution (mailcontrol) -> FOPE (bigfish.com -> Office 365 cloud
Emails sent to Office 365 never get routed through Exchange 2010 hybdrid servers and that could be causing a delay.
How to resolve this ?
Thanks..
Hi
We have Exchange 2007 Standard in our organization, one end user is complains that he receives same email multiple times.
This is happening for only for one user.
Any suggestions.
Tx
Regards Anilk
Hello,
I am being blocked by Yahoo with the error message: 451.4.4.0 Primary IP address responded with "421 4.7.1 [TS03] All message from x.x.x.x will be permanently deferred; Retrying will NOT succeed. See http://postmaster blah blah blah.
I found that this is a problem with the DKIM and I used https://github.com/Pro/dkim-exchange open source to try and remedy this but I was unsuccessful. I don't think I am doing anything wrong as I followed the instructions to the letter.
These are the results of the auth-results@verifier.port25.com email.
==========================================================
Summary of Results
==========================================================
SPF check: pass
DomainKeys check: neutral
DKIM check: neutral
Sender-ID check: pass
SpamAssassin check: ham
==========================================================
Don't know what other info to give...
Please help...
I've asked this question on another forum without an answer so I thought I would try here.
This relates to Exchange 2013. During Friday through to Monday I am picking up thousands of spam items sent frominboundproxy@inboundproxy.com and up to five HealthMailboxes are involved. The healthmailboxes have accounts in AD and appeared during the Exchange installation.
Here is and example -
Diagnostic information for administrators:
Generating server: EXCHANGE2.xxxxx.yyyyyyyy.yy.yy
HealthMailbox168a97e4814144848b101e39c3482fca@xxxxx.yyyyyyyy.yy.yy
#550 5.2.1 Content Filter agent quarantined this message ##
Original message headers:
Received: from EXCHANGE2.xxxxx.yyyyyyyy.yy.yy (192.168.0.72) by
EXCHANGE2.xxxxx.yyyyyyyy.yy.yy (192.168.0.72) with Microsoft SMTP Server
(TLS) id 15.0.516.32; Mon, 19 Nov 2012 19:20:48 +0000
Received: from InboundProxyProbe (::1) by EXCHANGE2.xxxxx.yyyyyyyy.yy.yy
(::1) with Microsoft SMTP Server id 15.0.516.32 via Frontend Transport; Mon,
19 Nov 2012 19:20:48 +0000
Subject: Inbound proxy probe
Message-ID: <2e1d9dd2-d71e-4c23-9b5a-b8e12c109e57@EXCHANGE2.xxxxx.yyyyyyyy.yy.yy>
From: <inboundproxy@inboundproxy.com>
To: Undisclosed recipients:;
Return-Path: inboundproxy@inboundproxy.com
Date: Mon, 19 Nov 2012 19:20:48 +0000
MIME-Version: 1.0
Content-Type: text/plain
Received-SPF: Fail (EXCHANGE2.xxxxx.yyyyyyyy.yy.yy: domain of
inboundproxy@inboundproxy.com does not designate ::1 as permitted sender)
receiver=EXCHANGE2.xxxxx.yyyyyyyy.yy.yy; client-ip=::1;
helo=InboundProxyProbe;
Can anyone spread light on this, is it normal behaviour and if not how can I stop it? The exchange installation is on a green field domain. The exchange server is an OOTB installation on a single VM.
WE have issue a weird issue. Something to do with permissions most probably.
Have an ASP website that uses forget password feature for members to send them new password.
The domain user who has mailbox and can send and receive email is coded into the website and port used is 2525 for SMTP. We receive the message : Mailbox unavailable. The server response was: 5.7.1 Unable to relay
When try to send to a user who is not part of our domain or is not internal user. But if we reset password who has internal mailbox or is part of domain it works fine.
But here is the tricky bit. IF we give this user enterprise admin permission, the relay is not a concern. Seems like it works fine. So same user with normal domain user access cannot dispatch the reset password email to external mailboxes but can when he is enterprise admin. I cannot figure out where or what role/permission needs to be given to this user so he can be taken off the enterprise admin group but still relay emails via the smtp exchange server.
WE are using exchange 2013 server.
Any assistance or direction would be great.
Cheers
We have a few groups (HR and Legal) that provide services for a few different companies. I would like the groups to be able to send/receive messages from multiple email domains, but I would like to avoid each user having multiple Mailboxes on the system (each with multiple calendars, contact lists, GAL entries, etc)
It is so easy to add additional inbound alias, but I for the life of me cannot find a good solution for sending Outbound via an alias.
Does anyone have any suggestions for how they've done something similar in their own org?
We're running Exchange 2010 and Outlook 2013.
I installed 2013 cu1(full roles), it created 5 connectors by default(2 HubTransport,3 FrontendTransport)
I gave "Default Frontend XXX" anonymouse permission, and then I logon another email system and send to 2013 Exchange server.
It was failed, the error was "451 4.7.0 Temporary server error. Please try again later. PRX2", but 1 hour later, the
mail was deliveried and I can read this email on 2013 server's owa. After that the 2013 server can get email immdeiately. But after I restart MStransport service, the issues occoured again and it restored in 1 hour.
If I disable all Frontend Transport and bound port 25 to "Default XXX(Hub Transport)", there was no issues of receive on
2013.
Anyone has ideas WHY the FrontendTrandTransport cannot work immdeiately?
BTW, my exchange envrioment is hybird(2010 sp3)
Tks!!!
All,
I had a problem where application servers that were relaying SMTP through the Exchange server were failing. It turned out to be that the person who had configured the receive connectors had entered them like 10.10.10.10-255.255.255.255. The intent was to specify one specific IP address by using a /32 subnet mask, but really was allowing the entire range. But it worked properly for 7 months before it started to fail. The problem is resolved, adding specific IP addresses instead of a range got it working properly. But why would that configuration be a problem? That is, what, ultimately, caused it to stop working?
Much thanks for any pertinent information!
