ServerFiles.com is a server software & hardware directory for Network administrators & IT professionals, listing networking & server software for Windows 2003, Windows 2000, NT and Linux; and now also listing networking hardware solutions focused on server based computing.
Exchange 2007/2010 does not provide any option on the Send Connectors or Transport rules to set sender based routing. The RouteBySender application allows you to route outgoing emails based on sender group membership or based on the sender's domain.
Typical usage scenario: Let's assume that your Exchange 2007/2010 server has only one send connector "Internet Connector" using DNS for the address space *. All messages leaving the organization will use this connector. Let's further assume that you want to route messages from members of a certain group to a smarthost instead of using DNS. RouteBySender utility will help you to solve this problem.
Exchange mailbox may have multiple SMTP addresses. For outgoing messages Exchange server always uses the primary SMTP address. For example, John Doe has a mailbox with email@example.com primary SMTP address and firstname.lastname@example.org secondary smtp address. John Doe can easily receive the message addressed both to email@example.com and firstname.lastname@example.org, but he can not send the message as email@example.com because this behaviour is by design in Exchange server.
ChooseFrom for Microsoft Exchange 2007/2010 application allows users to send a message with any of their own SMTP addresses as the From address.
Read Receipts Remover for MS Exchange 2000/2003 application can remove the read receipt request from each inbound e-mail message delivered to default Inbox folder of user's personal mailbox. So the Read Notification will never be sent back to the message originator.
Consider a firm ABC runinng Exchange 2000/2003. The Accounting department staff has their own mailboxes (firstname.lastname@example.org) and they are Outlook users. Their e-mail is handled through generic department distribution group (email@example.com), which ensures that all users receive each e-mail message. For internal mail they want to be able to send e-mail as each individual user, however when this user sends e-mail out of the office, the From address needs to be set to the address of the distribution group (firstname.lastname@example.org). This should be done automatically on Exchange server side. SendAsGroup application can solve that problem.
SelectiveOOF for Exchange 2000/2003 application allows the Exchange administrator to suppress Out of Office replies to the Internet selectively based on sender and recipient e-mail domains. The application can be installed on any Exchange 2000/2003 server.
This application allows the Exchange administrator to set Message Journaling on per-mailbox basis. He can, for example, archive the messages addressed to the only user or to the group of users. Also for any given mailbox only ingoing messages or only outgoing messages archiving (journaling) can be set.
Exchange 2000/2003 users often wish to forward e-mail sent to their Exchange mailboxes automatically to an external e-mail address (for example, email@example.com). Using AD Users and Computers tool, the Exchange administrator can do that.
However, suppose that the Exchange administrator has to turn on/turn off these forwarding options several times a week for users who are sick or on holiday. Every time when administrator turns that off, the link between the internal user account and the external forwarding address just dropped. To re-establish it, administrator must select the associated external address from the list of Active Directory contacts. The CentralForwarder for MS Exchange 2000/2003 application is developed to solve this problem. Using the application, you can turn on/turn off e-mail forwarding with a single mouse click.
An Exchange 2000/2003 mailbox may have multiple SMTP addresses associated with it. For example, John Doe has a mailbox with a primary SMTP Address of firstname.lastname@example.org and secondary SMTP address of email@example.com. John wishes for emails sent to his secondary SMTP address to be automatically placed in the separate folder he has created. To do that he can define in his Outlook a rule like this: Apply this rule after the message arrives with firstname.lastname@example.org in the message header Move it to john2 folder
So far so good. But if a message sender uses BCC option or when John Doe gets a SMTP e-mail addressed to distribution group, his e-mail address is not placed in the To: or the CC: fields. Even more, his e-mail address does not appear anywhere in the message headers at all. As a result, the rule above can not work.
XRecipientList application inserts the actual (SMTP envelope) recipients to the mail header. The application adds a new header field named X-RecipientList to each inbound e-mail. X-RecipientList field contains the list of the SMTP envelope recipients. Based on this header information, user will be able to set rules using his/her e-mail client software (i.e. MS Outlook).
HeaderToCategory for Exchange 2000/2003 application converts all SMTP mail headers to categories for each incoming message. That allows users to easily create rules to differentiate important e-mails automatically using multiple colors and fonts based on e-mail header information.