The Exchange 2007 Wiki

Transport FAQs

This FAQ page is devoted to Mailflow/Transport-configuration related questions (primarily moved from Ask a Question page).


Q: How can I change the language of the read and delivery receipts? I tried this command, but it doesn't seem to have any effect:   set-transportserver -ExternalDsnDefaultLanguage pt-BR -InternalDsnDefaultLanguage pt-BR -Identity ABC23 
A: The DNS languages is keyed off of this thing called “content language”. Its per recipient. Now, how does one know what their content language is? Its basically the language set on their mailbox. So, agnitap is English. Everyone in US Microsoft is English. In Europe its set to their respective languages.
This ExternalDsnDefaultLanguage default is what the admin sets for cases where there’s no content language. Exchange Store always stamps the content language, but if a message came from foo.com and they had sendmail, maybe there’s no content language set. In that case, if Exchange has to generate a NDR back to foo.com, then it would use the ExternalDsnDefaultLanguage to do that
If an admin wants to force the use of InternalDsnDefaultLanguage / ExternalDsnDefaultLanguage, they can set ExternalDsnLanguageDetectionEnabled / InternalDsnLanguageDetectionEnabled to false.  Setting these to false will ignore the language stamped on the messages.

Q: How can I add a disclaimer to all outbound mail?
A: How to add a disclaimer to all outbound messages

Q: How do you enable the BadMail directory and the ability to keep your BadMail in Exchange 2007?
A: BadMail is always discarded by Exchange 2007 transport. There's no way to optionally retain it to disk (via reg key setting, etc) like there was in Exchange 2003.

Q: In Exchange 2003 you were able to send all mail with unresolved recipients to a specified host. How do you do the same in 2007?
A: It’s the same as a non-authoritative domain.  Simply specify the domain as internal relay, and configure a Send Connector to forward mail for that domain to a smart host.  See: http://technet.microsoft.com/en-us/library/aa996910.aspx
 

Q: Exchange 2007 & Archiving? We currently use Exchange 2003 and KVS Enterprise Vault. We're looking to migrate to Exchange 2007, but I sort of remember somewhere that Exchange either has built-in archiving capabilities just like KVS, or that there are snap-ins that do the job. Am I correct?
A: There is NO support like KVS in Exchange 2007

Q: How can I set up a catch-all with Exchange 2007? I'd like all mail to a particular domain to be directed to a single mailbox.  In addition, how can you set Exchange 2007 to forward mail to an unrecognized recipient in a domain to a mailbox?  (For example, bob@example.com has a mailbox, so mail will go there, but jen@example.com is not a mailbox, so I want it to go to a catchall mailbox like catchall@example.com).  I think it can be done with Hub Transport Rules at Organization level but I can't figure it out for the life of me.  Anyone can solve this please?
A: There is not a simple way to do exactly this using Hub Transport rules.  But you can make sure that a copy of every 5.1.1 DSN (invalid recipient) gets sent to a particular user.  You can also suppress 5.1.1 DSNs.  You can also forward unresolved messages to another host. Or you can write a transport agent to do this (which would need to run before recipient filtering).
Be warned that catch all mailboxes are dangerous in this day and age because you are opening yourself to a DOS attack.

Q: How do I setup Receive Connectors to support both ESMTP and SMTPS?  What are the corresponding Outlook Express configuration settings to test this? 
A: Not sure what is meant by this question, but Exchange supports ESMTP and SMTP.  It only supports explicit TLS connections.  Meaning the client must connect and issue a STARTTLS command to be secured.  Exchange does not support implicit TLS (SMTPS) on port 465.  Outlook Express only supports explicit TLS on port 25 and 587, so do not change the port numbers in Outlook Express or Exchange.

Q: Is there a way to disable NDRs sent to external senders? (Like Exchange 2000 & 2003 could)
A: Set-RemoteDomain <domain> -NDREnabled:$False. The default domain (*) will control behavior for all domains and the default behavior can be overridden by specifying explicit domains.

Q: How do you share SMTP domain names between an Exchange 2007 environment and a foreign mail system?  This was easy achieved in exchange 2000/2003, but I can't find a similar method in 2007.
A: Good news, it is even easier in Exchange 2007.  All you do is change the accepted domain type.  See http://technet.microsoft.com/en-us/bb124423.aspx for more information.

Q: Sharing of SMTP domains (continued). I have looked at the link supplied and fail to see how to do it. Situation is that some users have mailboxes on an Exchange 2007 server and some users have mailboxes on a foreign mail system and all users share the same SMTP domain name. As I understand it, if I understand Exchange 2007 to be authoritative for the domain it won't deliver mails to users on the foreign maiulsystem and if I configure a relay domain Exchange 2007 will forward mails for all users to the foreign system.
In Exchange 2003 you could configure a non-authoritative domain and have mails for unresolved users sent to the foreign mail system. It is this functionality I am looking for.
A: Sounds like you want to set your accepted domain to be "Internal Relay". There's more information in the link provided above.

Q: If I am using MessageLabs or EHS is it worth me having an Edge server or should I get MessageLabs or EHS to deliver to a HubTransport server?
A:  An Edge server provides several features that third party products don't do.  One of these features is Office Outlook Safe-list aggregation.  

Q: How do you go about changing how Exchange creates a message-id?  Currently it is creating messages ids with a subdomain in the FQDN at the end of the id.  I just want to have my the domain on the end of it.  Also when a message is submitted to the server that doesn't have a message id, does Exchange create one, and if so how can I set the format of message id.
A:  Is there a reason you want to change the message id? This is not something that's readily configurable.

Q: My users are sending out large mails. 2mb each in total. What is happening is that when users send out 2mb x 40mb= 80mb. The mails comeback and says that it was delayed. but the receipiant received the same message about 10 times. so all in all there is about 800mb in total going. I checked for viruses and spam but can't seem to find anything.  We do have a slow connection though.  512kb down and 256kb up.
A: (attempted answer)  Have you looked closely at the queue to watch the messages as the mail server attempts to deliver the messages? If the messages are getting held up for any reason, most likely they'll be in there, and you'll usually be able to understand the error.  We had almost the exact same problem... the user gets a message that the email was delayed, but the recipient does receive it. I had assumed our delivery problems were an attachment size problem as well, but when I looked closer at the queue, I found that our ISP had incorrectly configured our mail server's reverse lookup entry.  One way to check is to go to dnsstuff.com and put the external IP address of your mail server in the reverse lookup box.  They'll tell you whether or not it's configured.  The short answer, peek at the queue, it's pretty helpful.

Q: How do you create a new transport agent?  For example in MS Outlook you can send a message in this format [smtp:someone@somewhere.com].  I would like to create one that takes the format [fax:someone/somecompany@phonenumber] and then routes the email to a faxserver.
A: This MSDN link talks about creating transport and protocol agents: http://msdn2.microsoft.com/en-us/library/bb204097.aspx

Q: We have exchange 2003 environment & lately we install exchange 2007. After that we configure the two-way routing group connector, we tried to send test mail from user his mailbox stored on exchange 2007 to another user on exchange 2003. We found that the email stuck in the queues, we tried to force the connection and we found the mail was delivered. We try the same thing twice and still we have the same problem, so can anybody help us?
A: What's the error reason listed for the messages when they're stuck in the queue? Is there anything in the event viewer on either side?

Q: Can anyone please tell me how to adjust the allowances for outgoing and incoming mail (allot of our attachments are over 40mb, sent and received) I have used the Set-TransportConfig command to no avail.
A: There are also max size limits configured on the receive connector. If your goal is to INCREASE these values, make sure you're not still restricting the maximum size at the receive connector (Get/Set-ReceiveConnector)

Q: How can I add HTML tags to disclaimers? (For example a clickable link in the disclaimer)

A: E2K7 does not allow HTML markup in disclaimers.

Q: Why does Exchange 2007 need to be authoritative for any domain for which it receives email? Right now our Exchange 2003 system is not authoritative for our email domains, which allows Exchange to relay unknown addresses to UNIX mail relays, which either accept, forward, or bounce the mail.  It seems like this is not possible in Exchange 2007, or am I missing something? 
A: Exchange 2007 doesn't have to be authoritative for the domain, it just have to have an "accepted domain" defined. You can create an accepted domain of "relay" type (either internal relay or external relay) to accomplish what you're asking - each of these options has slightly different routing effect. Actually, you can only set EAPs for "Internal Relay " relay domains, not external.

Q: How do you allow users to change the display name of an email they are sending to? For example, users send their emails to an exchange mailbox but enter their own unique display name, for example:  
My Personal List 
doNotReply@domain.com. In Exchange 2000, this was allowed, but 2007 now strips off the custom display name and uses the one from AD
A: This is something you'll get in Exchange 2007 RTM when you're sending SMTP from POP/IMAP client. This is a bug and is fixed in SP1.  

Q: How to test an AllowList Provider... I would like to know how to be sure that incoming connection are tested against IP Allow list provider. As I created a list called si-whitelist.mostovna.com I am not able to see the results. Is a message that originates from IP Allow List Providers treated the same as a message that originates from IP Allow List? The second one has a SCL: -1 the first is processed "normally".
A: If the Originating IP is on the allow list provider's list, then the message is not given an SCL value of -1. For verification, you can take a look at performance counters. Performance counter category for allow list provider is MSExchange Connection Filtering and the counter that you should look at is Messages with Originatin IP on Allow List Providers.  

Q: How do you go about changing how Exchange 2007 creates a message-id? I just want to have my Internet domain XYZ@Mydomain.com ) on the end of it and not my internal domain (Local). Because this message-id is insert in the SMTP header.
A: This is going to require a custom agent.  

Q: I have just implemented exchange 2007, we already have exim mail server on Unix machine, I’m facing a problem with my setup described as the following. 1- all mails sent from exchange should be forwarded to our Unix edge servers for processing
A: This is a simple configuration on the Edge server. You just modify the Send connector to use a smart host instead of DNS for external mail delivery and specify the IP address of the UNIX hub for the smart host. Details: http://technet.microsoft.com/en-us/library/aa998836.aspx
2- when a user on exchange send e-mail to another user on the same exchange server, message are not being forwarded to the Unix edge server, message are being processed on the exchange edge server, i was wondering if there is a way to force all e-mail that are sent from exchange to be forwarded to the non exchange edge server? keep in mind that the setup works fine when exchange users send e-mail to non exchange user.
A: This is not possible. For all messages to go through the UNIX hub as required, you would have to remove the default domain for the recipients from the accepted domains list. However, that would prevent all inbound traffic as well.  

Q: How do you stop users from forwarding from Exchange to external addresses. i.e. stop filtering of mail and sending to an external account (e.g. from Exchange to Hotmail)?
A: You could use Exchange 2007 transport rules to accomplish this  

Q: Is there a way to import an address space collection from a csv to a sendconnector?
A: Just import-csv and dump the domain names into the pipeline, then use the "+=" operator to add the new domain name values to teh AddressSpaces collection. This could look something like this: $a = (Get-SendConnector sendconnector1).AddressSpaces import-csv file.csv | % { $a += $_.domainname } Set-SendConnector sendconnector1 -AddressSpaces $a  

Q: How does one setup domainKeys with Exchange 2007?  
A: At this time there is no native way to do this. Exchange currently supports SenderID natively. 

Q: We are currently using Sendmail and want to move our staff and faculty to Exchange 2007, but we also want to leave our students and generic email accounts on Sendmail, What is the best way to accomplish this with 2 Exchange servers and one sendmail server. All accounts are on the same SMTP domain.
A:
http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/exchange-2007-smtp-namespace-sharing-different-relay-domain-types.html  or see http://technet.microsoft.com/en-us/bb124423.aspx for more information. 

Comments

From ScottMSFT - 5/29/07 10:14 AM

I am not even sure I see the need to make this domain internal-relay.  If all of your users are either mailboxes or contacts, then you can (and should be) authoritative.  This allows your server to generate an NDR if a message is sent to someone that is neither a contact or a mailbox.  This prevents a possible loop.  Of course, only one system needs to be "authoritative" so if the external server is authoritative, then internal-relay will work just fine.

From Snowdon - 5/24/07 12:38 PM

Sharing SMTP domain, aka namespace sharing, is something I've researched quite a bit, as I'm about to embark on it. I've got a project where my client is sloooowly :) migrating his hosted email into his own Exchange 2007 Server. There are 8 to 10 SMTP domains, plus one that is to be common for all users. During the migration period, some users will be accessing email through the hosted service, while migrated users will use Outlook / Exchange combo. All email delivery has to run smoothly. Luckily, the hosted service uses global dns for routing email, so by redirecting ALL email to ALL SMTP domains into the Exchange server, I hope to be able to "filter" out the already migrated users from the ones still using the hosted service...

I accomplish the namespace sharing by enabling mailbox users on the Exchange server for all migrated users. I then created contacts for all the users that aren't migrated yet. I configured the Accepted domain as Internal Relay. I created a Send Connector that routes email for the shared SMTP domain through a Smart Host, which is the SMTP server of the hosted service.

Site

Changes
Index
Search

 

User

 

Log In
Register

 
 

Last Modified 3/11/08 8:59 AM