|
|
|
date: Tue, 11 Mar 2008 02:04:00 -0700,
group: microsoft.public.exchange2000.general
back
Re: E-mail non-delivery reports
Mark,
I fully appreciate what you say, however this is a real issue for us. I work
in a Barristers chambers and the barristers do not want their home e-mail
addresses being revealed. The Barristers on the whole are not technically
aware and so this sort of thing happens from time to time. It would be a good
thing for us to stop our Exchange server relaying back NDRs generated from
the likes of Virgin/Hotmail etc. In this instance, it is because the e-mails
are classed as SPAMs or virus, so the ISP rejecting the e-mails is causing
this problem.
Do you think this is possible? The only single point of contact is our
Exchange Server, hence this posting. It would be good to be able to catch and
dump such externally generated messages to original senders.
We are moving to Exch 2007 in the next few weeks if that makes it easier.
Thanks
Dellboy
"Mark Arnold [MVP]" wrote:
> On Tue, 11 Mar 2008 02:04:00 -0700, Dellboy <Dellboy@community.nospam>
> wrote:
>
> >Hi,
> >
> >we have an Exchange 2000 (Ent Ed) server running on Windows2000.
> >
> >The problem we have is this:
> >
> >We autoforward e-mails on for some of our users to their personal home
> >e-mail addresses. This works fine until there is a problem with their home
> >e-mail address delivery, whereby a non-delivery report gives out the home
> >e-mail address that the e-mail could not reach. We would like to keep these
> >e-mail addresses confidential and in truth would like to suppress all
> >bounceback messages relating to forwarded e-mails.
> >
> >NDRs etc for our domain must still work, we would just like to suppress any
> >NDRs etc from the forwarded e-mails. In other words, we want people to know
> >when our domain doesn't work, but don't want them to know when the forwarding
> >to home fails for whatever reason.
> >
> >Thanks
>
> You're asking a question in a Microsoft Exchange forum about how to
> stop NDRs being generated by a client application in someone's home
> that isn't connected to your Exchange in any way.
>
> If you forward to an email address that is so unreliable as to
> generate NDRs you need to fix where you send it to rather than try and
> botch up something on your Exchange server.
>
date: Tue, 11 Mar 2008 06:16:00 -0700
author: Dellboy am
Re: E-mail non-delivery reports
On Tue, 11 Mar 2008 06:16:00 -0700, Dellboy <Dellboy@community.nospam>
wrote:
>Mark,
>
>I fully appreciate what you say, however this is a real issue for us. I work
>in a Barristers chambers and the barristers do not want their home e-mail
>addresses being revealed. The Barristers on the whole are not technically
>aware and so this sort of thing happens from time to time. It would be a good
>thing for us to stop our Exchange server relaying back NDRs generated from
>the likes of Virgin/Hotmail etc. In this instance, it is because the e-mails
>are classed as SPAMs or virus, so the ISP rejecting the e-mails is causing
>this problem.
>
>Do you think this is possible? The only single point of contact is our
>Exchange Server, hence this posting. It would be good to be able to catch and
>dump such externally generated messages to original senders.
>
>We are moving to Exch 2007 in the next few weeks if that makes it easier.
>
>Thanks
>
>Dellboy
First off there's little point having Exchange 2007 if all you're
going to do is to use AD to forward messages on to a private sender.
Anyway, your system shouldn't be generating NDRs in this situation. If
you forward a received message to a Virgin customer that's the last
your Exchange server sees of it. You're not going to get the NDR back
from Virgin to you and then back to the original sender - it just
doesn't work like that.
So, what do you do? Well, you give the barristers OWA access or RPC
over HTTPS access to the system or Terminal Services into your
network, whatever, it just doesn't matter.
Or, you have an ISP account that doesn't go down, has enough storage
not to generate "mailbox full" messages or whatever back to the
original intended sender. Gmail accounts are obviously good candidates
here.
Either your explanation of the problem isn't complete or your
understanding of what is happening is wrong.
date: Tue, 11 Mar 2008 10:00:41 -0400
author: Mark Arnold [MVP]
Re: E-mail non-delivery reports
Mark,
I am fairly sure that it is our Exchange server (which we use in the normal
way AND to pass on e-mails to home addresses in addition) that does generate
the non-delivery reports when it cannot cmplete a delivery. Here is an
example:
Reporting-MTA: dns;EXCHANGE.abcd.local
Received-From-MTA: dns;mail.abcd.co.uk
Arrival-Date: Mon, 10 Mar 2008 15:54:11 +0000
Final-Recipient: rfc822;another@virgin.net
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;571 Requested action not taken: Message was spam or
contained virus
00
250-ETRN
250-ENHANCEDSTATUSCODES
250 8BITMIME
250-8BITMIME
250 DSN
have no reverse-DNS (PTR record) assigned.
addresses which
220 have no reverse-DNS (PTR record) assigned.
ddresses which
220 have no reverse-DNS (PTR record) assigned.
which
220 have no reverse-DNS (PTR record) assigned.
tions from IP addresses which
220 have no reverse-DNS (PTR record) assigned.
X-Display-Name: another (Home)
Thanks
Dellboy
"Mark Arnold [MVP]" wrote:
> On Tue, 11 Mar 2008 06:16:00 -0700, Dellboy <Dellboy@community.nospam>
> wrote:
>
> >Mark,
> >
> >I fully appreciate what you say, however this is a real issue for us. I work
> >in a Barristers chambers and the barristers do not want their home e-mail
> >addresses being revealed. The Barristers on the whole are not technically
> >aware and so this sort of thing happens from time to time. It would be a good
> >thing for us to stop our Exchange server relaying back NDRs generated from
> >the likes of Virgin/Hotmail etc. In this instance, it is because the e-mails
> >are classed as SPAMs or virus, so the ISP rejecting the e-mails is causing
> >this problem.
> >
> >Do you think this is possible? The only single point of contact is our
> >Exchange Server, hence this posting. It would be good to be able to catch and
> >dump such externally generated messages to original senders.
> >
> >We are moving to Exch 2007 in the next few weeks if that makes it easier.
> >
> >Thanks
> >
> >Dellboy
>
> First off there's little point having Exchange 2007 if all you're
> going to do is to use AD to forward messages on to a private sender.
>
> Anyway, your system shouldn't be generating NDRs in this situation. If
> you forward a received message to a Virgin customer that's the last
> your Exchange server sees of it. You're not going to get the NDR back
> from Virgin to you and then back to the original sender - it just
> doesn't work like that.
>
> So, what do you do? Well, you give the barristers OWA access or RPC
> over HTTPS access to the system or Terminal Services into your
> network, whatever, it just doesn't matter.
>
> Or, you have an ISP account that doesn't go down, has enough storage
> not to generate "mailbox full" messages or whatever back to the
> original intended sender. Gmail accounts are obviously good candidates
> here.
>
> Either your explanation of the problem isn't complete or your
> understanding of what is happening is wrong.
>
date: Tue, 11 Mar 2008 08:01:00 -0700
author: Dellboy am
|
|
