Re: E-mail

Ahhh.

You're under 'NDA' attack ;-/.

Your Exchange server is configured to accept all email destined for your
domain. When an email is received, but does not match a recipient in your
organization, Exchange attempts to inform the sender that no such address
exists. The problem is, the *sender* doesn't exist, so exchange eventually
gives up trying to notify them and you get the NDR you posted.

99.9% of the time, mail that fits this pattern is spam, sent by an
undesireable person who has spoofed thier return address so you can't find
them. What to do?

Use the Active Directory filtering capabilities of Exchange to simply refuse
all incoming email where the recipient does not match an email address that
exists on your system.

'Filter Recipients who are not in the Directory'.


1. In ESM | Global Settings | Message Delivery > r-click and select
properties.
2. On the Recipient Filtering tab > Select 'Filter recipients who are not in
the Directory'
3. Press the Help button to read the effect of this setting, and the caveat
(which is not much of a caveat, IMHO).
4. Click Apply and OK your way out (or deselect the box if you don't want
this).


If elect to filter, enable the filter on your Default SMTP Virtual Server.


1. ESM | Servers | Servername | Protocols | Default SMTP Virtual Server


>rclick > properties.


2. On the General tab, click Advanced and then select the Apply Recipient
Filter box.
3. OK your way out, click Apply and close the properties box.
4. Right click the Default SMTP server to stop, then start it.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !


"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E7D88A25-5333-4E9E-AD6E-D47C0811DF03@xxxxxxxxxxxxxxxx
> Let me see if I can help. I receive about 30 of these a day from the
> postmaster to officeadmin which are forwarded to me.
>
> Undeliverable:RE: We have a hot alert for morning. Big News just came out
> System Administrator
> Your message did not reach some or all of the intended recipients.
>
> Subject: RE: We have a hot alert for morning. Big News just came out
> Sent: 7/14/2005 11:01 AM
>
> The following recipient(s) could not be reached:
>
> Dusty Silver on 7/14/2005 11:04 AM
> There was a SMTP communication problem with the recipient's
> email server. Please contact your system administrator.
> <BenevaGroup.com #5.5.0 smtp;550 <rieuffg@xxxxxxxxxxxxxxxxxx>:
> User unknown>
>
>
> "Les Connor [SBS Community Member - SBS M" wrote:
>
>> Sorry, I don't understand what 'randomly generated' means, unless you're
>> trying to configure a spam engine.
>>
>> Generating an NDR for an unreachable recipient is the intended behaviour,
>> and if sgijss isn't a valid email address, then ....
>>
>> --
>> Les Connor [SBS Community Member - SBS MVP]
>> -----------------------------------------------------------
>> SBS Rocks !
>>
>>
>> "Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:AC0060BA-7FE5-4E5B-A199-742EB5E02857@xxxxxxxxxxxxxxxx
>> > They are randomly generated.
>> >
>> > "Les Connor [SBS Community Member - SBS M" wrote:
>> >
>> >> Hi Sean,
>> >>
>> >> Who/where is sgijss ? What is the email address associated with this
>> >> recipient?
>> >>
>> >> --
>> >> Les Connor [SBS Community Member - SBS MVP]
>> >> -----------------------------------------------------------
>> >> SBS Rocks !
>> >>
>> >>
>> >> "Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:EF16AF91-7956-4179-872B-200F74AF05F7@xxxxxxxxxxxxxxxx
>> >> > I am receiving NDR's from our server....ex:
>> >> >
>> >> > Your message did not reach some or all of the intended recipients.
>> >> >
>> >> > Subject: RE: Request Information (benevagroup.com)
>> >> > Sent: 7/14/2005 8:37 AM
>> >> >
>> >> > The following recipient(s) could not be reached:
>> >> >
>> >> > sgjjss on 7/14/2005 8:39 AM
>> >> > The e-mail account does not exist at the organization
>> >> > this
>> >> > message was sent to. Check the e-mail address, or contact the
>> >> > recipient
>> >> > directly to find out the correct address.
>> >> > <BenevaGroup.com #5.1.1>
>> >> >
>> >> > Headers = Microsoft Mail Internet Headers Version 2.0
>> >> > From: postmaster@xxxxxxxxxxxxxxx
>> >> > To: OfficeAdmin@xxxxxxxxxxxxxxx
>> >> > Date: Thu, 14 Jul 2005 08:39:20 -0400
>> >> > MIME-Version: 1.0
>> >> > Content-Type: multipart/report; report-type=delivery-status;
>> >> > boundary="9B095B5ADSN=_01C57F45A7460202000010AFBenevaGroup.com"
>> >> > X-DSNContext: 335a7efd - 4523 - 00000001 - 80040546
>> >> > Message-ID: <HWNncfIMx00000092@xxxxxxxxxxxxxxx>
>> >> > Subject: Delivery Status Notification (Failure)
>> >> >
>> >> > --9B095B5ADSN=_01C57F45A7460202000010AFBenevaGroup.com
>> >> > Content-Type: text/plain; charset=unicode-1-1-utf-7
>> >> >
>> >> > --9B095B5ADSN=_01C57F45A7460202000010AFBenevaGroup.com
>> >> > Content-Type: message/delivery-status
>> >> >
>> >> > --9B095B5ADSN=_01C57F45A7460202000010AFBenevaGroup.com
>> >> > Content-Type: message/rfc822
>> >> >
>> >> > MIME-Version: 1.0
>> >> > Content-Type: application/ms-tnef;
>> >> > name="winmail.dat"
>> >> > Content-Transfer-Encoding: binary
>> >> > Content-class: urn:content-classes:message
>> >> > Subject: RE: Request Information (benevagroup.com)
>> >> > X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
>> >> > Date: Thu, 14 Jul 2005 08:37:19 -0400
>> >> > Message-ID:
>> >> > <A9AF8E293274C541816FA99C66FBD2E71D90F2@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>> >> > X-MS-Has-Attach:
>> >> > X-MS-TNEF-Correlator:
>> >> > <A9AF8E293274C541816FA99C66FBD2E71D90F2@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
>> >> > Thread-Topic: Request Information (benevagroup.com)
>> >> > Thread-Index: AcWIcBYsx73p25nKSFmYILz/7q6ntAAALBUv
>> >> > From: "Office Admin" <OfficeAdmin@xxxxxxxxxxxxxxx>
>> >> > To: <sgjjss>
>> >> >
>> >> >
>> >> > --9B095B5ADSN=_01C57F45A7460202000010AFBeneva
>> >> >
>> >> > Any suggestions or correspondence would be greatly appreciated.
>> >> > Thank you,
>> >> > Sean Lansberry
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>


.