Exchange Email Set-up

I am setting up RT for the first time. We use a small business server
for email. Currently I am able to send email to RT through SBS to
create a ticket. RT is also sending email to users in our domain just
fine. I am having a problem sending email from RT to users outside of
our domain. I think I see the error in the event log on SBS as

Event Type: Error

Event Source: MSExchangeTransport

Event Category: NDR

Event ID: 3030

Time: 3:02:47 PM

User: N/A

Computer: computer

Description:

A non-delivery report with a status code of 5.6.1 was generated for
recipient rfc822;user@otherdomain.com (Message-ID
rt-3.8.7-20582-1301090796-773.58-12-0@ubuntuRT.rt.com).

Any suggestions are greatly appreciated

This email was Virus checked by Clark’s Nutrition’s Astaro Security Gateway.

The information contained in this e-mail is intended only for use of
the individual or entity named above. This e-mail, and any documents,
files, previous e-mails or other information attached to it, may contain
confidential information that is legally privileged. If you are not the
intended recipient of this e-mail, or the employee or agent responsible
for delivering it to the intended recipient, you are hereby notified
that any disclosure, dissemination, distribution, copying or other use
of this e-mail or any of the information contained in or attached to it
is strictly prohibited. If you have received this e-mail in error,
please immediately notify us by return e-mail or by telephone at
(951)321-1960, and destroy the original e-mail and its attachments
without reading or saving it in any manner. Thank you.

Might be a dumb question – but is your exchange box allowing RT to relay?From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Carl Palmer
Sent: Friday, March 25, 2011 4:05 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Exchange Email Set-up

I am setting up RT for the first time. We use a small business server for email. Currently I am able to send email to RT through SBS to create a ticket. RT is also sending email to users in our domain just fine. I am having a problem sending email from RT to users outside of our domain. I think I see the error in the event log on SBS as

Event Type: Error
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3030
Date: 3/25/2011
Time: 3:02:47 PM
User: N/A
Computer: computer
Description:
A non-delivery report with a status code of 5.6.1 was generated for recipient rfc822;user@otherdomain.com (Message-ID rt-3.8.7-20582-1301090796-773.58-12-0@ubuntuRT.rt.com).

Any suggestions are greatly appreciated

This email was Virus checked by Clark’s Nutrition’s Astaro Security Gateway.

The information contained in this e-mail is intended only for use of

the individual or entity named above. This e-mail, and any documents,

files, previous e-mails or other information attached to it, may contain

confidential information that is legally privileged. If you are not the

intended recipient of this e-mail, or the employee or agent responsible

for delivering it to the intended recipient, you are hereby notified

that any disclosure, dissemination, distribution, copying or other use

of this e-mail or any of the information contained in or attached to it

is strictly prohibited. If you have received this e-mail in error,

please immediately notify us by return e-mail or by telephone at

(951)321-1960, and destroy the original e-mail and its attachments

without reading or saving it in any manner. Thank you.

Carl,

The message below is to tell you that your exchange server is not allowing relaying. it is doing that because it has been abused in the past (not you specifically, but “out there”).

There are 2 ways you can solve that problem:

· The first is to, like suggested by someone else, allow that machine to relay email outside the domain.

o This will work. Just be sure that you only allow the RT host to relay email, not any other hosts (especially if your exchange machine is exposed to the internet).

· The second option is to setup your RT machine to use a service account (authentication) when it connects to the send the mail through exchange.

o Setup a service account, and setup your RT machine to use those credentials to send email. if the email is authenticated, exchange will trust the source and allow the relaying.

The first one is going to be a pure exchange solution (there are plenty of details online to enable relaying to specific hosts from powershell), where are the second is going to be mostly a sendmail/postfix/whatever on the RT side (except for the service account bit).

I hope this puts you on the right track…

Thanks,
JokFrom: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Carl Palmer
Sent: Friday, March 25, 2011 4:05 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Exchange Email Set-up

I am setting up RT for the first time. We use a small business server for email. Currently I am able to send email to RT through SBS to create a ticket. RT is also sending email to users in our domain just fine. I am having a problem sending email from RT to users outside of our domain. I think I see the error in the event log on SBS as

Event Type: Error
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3030
Date: 3/25/2011
Time: 3:02:47 PM
User: N/A
Computer: computer
Description:
A non-delivery report with a status code of 5.6.1 was generated for recipient rfc822;user@otherdomain.com (Message-ID rt-3.8.7-20582-1301090796-773.58-12-0@ubuntuRT.rt.com).

Any suggestions are greatly appreciated

This email was Virus checked by Clark’s Nutrition’s Astaro Security Gateway.

The information contained in this e-mail is intended only for use of

the individual or entity named above. This e-mail, and any documents,

files, previous e-mails or other information attached to it, may contain

confidential information that is legally privileged. If you are not the

intended recipient of this e-mail, or the employee or agent responsible

for delivering it to the intended recipient, you are hereby notified

that any disclosure, dissemination, distribution, copying or other use

of this e-mail or any of the information contained in or attached to it

is strictly prohibited. If you have received this e-mail in error,

please immediately notify us by return e-mail or by telephone at

(951)321-1960, and destroy the original e-mail and its attachments

without reading or saving it in any manner. Thank you.

I wanted to thank you for your input and share the solution that I
finally came to.

After adding the ip address of the RT server to the SMTP relay on our
Small Business Server I started to get an error

The message contains a content type that is not supported
<domain.com #5.6.1 smtp;554 5.6.1 Body type not supported by Remote
Host>

It turned out to be a problem with exchange listening for 8bitmime.
After I edited this setting on the SBS using adsiedit.msc and navigating
to

Configuration > CN=config > CN=services > CN=Microsoft Exchange >
CN=Domain > CN=AdminGroups > CN=firstadmingroup > CN=Servers >
CN=computername > CN=Protocols > CN=SMTP > CN=1

And then changing the value of MSExchInboundCommand to reduce the
default number of 7697601 by 4194304. Here is an link that talks about
this field: http://support.microsoft.com/?kbid=257569. It now works

This email was Virus checked by Clark’s Nutrition’s Astaro Security Gateway.

The information contained in this e-mail is intended only for use of
the individual or entity named above. This e-mail, and any documents,
files, previous e-mails or other information attached to it, may contain
confidential information that is legally privileged. If you are not the
intended recipient of this e-mail, or the employee or agent responsible
for delivering it to the intended recipient, you are hereby notified
that any disclosure, dissemination, distribution, copying or other use
of this e-mail or any of the information contained in or attached to it
is strictly prohibited. If you have received this e-mail in error,
please immediately notify us by return e-mail or by telephone at
(951)321-1960, and destroy the original e-mail and its attachments
without reading or saving it in any manner. Thank you.