Exchange Server - report on recieving domain
Asked By pgartner
04-Feb-10 11:35 AM
We have an exchange 2007 server that hosts 2 domains (a.com and
b.com), one of them (a.com) we are in the process of move away from.
What I=92m trying to find out is, who is still sending email to the old
email address
If I could get an idea of the sender, recipient, date/message subject,
I could then get my users to advise their contact to update their
files to reflect our new domain name.
Example, if a message is received address to paul@a.com, I want to be
able to tell my user to get their contact to start sending the email
to paul@b.com
Any ideas on how to do that?
Paul
Report
(1)
SMTP
(1)
Havethat
(1)
Sender
(1)
Cmdlet
(1)
Grep
(1)
MCSE
(1)
Rich Matheisen [MVP] replied to pgartner
Either the SMTP protocol logs or the message tracking logs will have
that information.
---
Rich Matheisen
MCSE+I, Exchange MVP
pgartner replied to Rich Matheisen [MVP]
any ideas on how to extract that info? is there a powershell command?
Paul
Rich Matheisen [MVP] replied to pgartner
[ snip ]
The SMTP log files are text files. You can use grep to find what you
need (or at least get the line number and file name) and then use a
text editor to have a look.
For the message tracking logs, use the Message Tracking tool in the
EMC "Tools" container. If you want to use a cmdlet, look at the bottom
of the Message Tracking UI and you can copy the cmdlet from there.
However, using the output is not always as easy as it looks. Some
things do not export easily because their textual representation is not
the contents of a property, but the name of the .Net object type.
---
Rich Matheisen
MCSE+I, Exchange MVP
have all my messages queued. There is no way to change tcp port on the SMTP connectior, but there is a way to do it on the Virtual SMTP. If I change the tcp port on SMTP server I will be able to send, but will not be able to recive since my smtp server will not be listening on port 25. What can I do in this suttuation? 2 virual SMTP servers with different tcp ports? Thanks Exchange Admin Discussions Virtual Server (1) SMTP server (1) SMTP relay (1) Tab (1) Exchange (1) SMTP (1) Outbound port (1) Tcp port (1) Hello: Interesting situation. I have never run into
Can not Email 17mb file outside our SMTP connector Exchange Server I am having an issue where we can not email large files to smtp addresses. We have Outlook / Exchange 2003, I have Changed the Routing Group Connector, Virtual SMTP, Message Delivery, and Mailbox Store send / receive limits to unrestriced. All users are using default not email the file to someone on the internet. Nothing is being written to the SMTP logs, so it doesnt make it that far. Does anyone have an idea here? Are point of failure? Thanks for your help! Exchange Admin Discussions Virtual Server (1) Outlook (1) SMTP server (1) Routing Group Connector (1) Restrictions (1) Ed Crowley (1) Exchange (1) Store (1) By sending to "smtp addresses" do you mean recipients in your Exchange organization or externally? There is also a Yes, absolutely. the message has our server name and there is no communication in the smtp logs. The message says: Host> That message says that the remote host your server communicated you mentioned a routing group connector, you have me wondering. Does your organization have an SMTP Connector, and, if so, does it have a limit? If not, you should have one
checked the Message Tracking Log and there is such information: 2010.04.20 23:17 SMTP: Message Submitted to Advanced Queuing 2010.04.20 23:17 SMTP: Started Message Submission to Advance Queue 2010.04.20 23:17 SMTP: Message Submitted to Categorizer 2010.04.20 23:17 SMTP: Message Categorized and Queued for Routing 2010.04.20 23:17 SMTP: Non-Delivery Report (NDR) Generated Other e-mails (from the same email address) which were sent earlier were delivered to user mailbox. I checked SMTP log, but I didn?t find information about this (non-delivered mail) transaction. The time Maybe someone had similar problem? BR, Mindaugas Exchange Admin Discussions Microsoft Certified Partner Hi John Sender (1) Exchange Server 2003 (1) SMTP Message (1) Backup (1) Queue (1) Report (1) SMTP
organization. That could get you on several DNSBLs. You could give everyone a new primary SMTP address (keeping their old SMTP address) and synchronize the directories, assigning the "other" company's old domain as the target Still try to figure out your solution. 1) give both companies' users the new primary SMTP address and definetely keep old address 2) > assigning the "other" company's old domain as After reading more and testing on two methods of 3 you proposed: Method1 - the shared SMTP address: Here are what I did: Here are steps I did on both exchange organizations Organization is sresponsible for all mail delivery to this address" is NOT set 2) Create SMTP connector defined called "abshare" where the "Forward all mail through this connector to the following do not know why external domain (yahoo.com) to company B users for this shared SMTP address failed and the only difference is that ab.com MX record points to company new email address ab.com. to get it to work, I have to use shared SMTP address to make ab.com nonauthoriative. From my testing, I have to combine two methods cannot find user B@AB.com it should send the message to serverB (using the SMTP Connector with the address space "ab.com". If you are going to provide a unified
be reached: 'JDoe@recipientdomain.com' on 5 / 27 / 2010 5:34 PM There was a SMTP communication problem with the recipient's email server. Please contact your system administrator. Denied (Mode record is true, how can I correct this? Exchange Admin Discussions Virtual Server (1) Exchange SMTP (1) Outlook 2007 (1) SMTP server (1) Deferred (1) External DNS (1) Encoding (1) Backend (1) Only the admin at different (see below). My issue was fixed when I changed the FQDN of my Exchange SMTP Virtual Server to match the external host name. There is some debate about what I Here are some notes that I made when I fixed my issue: - -- -- -- -- -- -- -- -- Go to the SMTP VS properties - -> Delivery tab - -> Advanced button. The FQDN is what shows up in the message It appears that some recipient systems will reject messages if the FQDN of the sending SMTP server is not a valid server for the sending domain. This does not make a reverse DNS lookup of its IP address. Under "Myth 3b: Modifying The FQDN of the SMTP Virtual Server" on http: / / msexchangeteam.com / archive / 2005 / 02 / 25 / 380481.aspx, it advises against changing the FQDN of the default SMTP VS. If you do go ahead and change the FQDN, the SMTPSVC SPN must be