Re: RBL filtering configuration
From: Charlie M (CharlieM_at_discussions.microsoft.com)
Date: 03/14/05
- Next message: Mark Arnold [MVP]: "Re: Folder Cleanup Issue"
- Previous message: Bob: "Question RE: Help Desk Permissions"
- In reply to: Geoff Pearce: "Re: RBL filtering configuration"
- Next in thread: Geoff Pearce: "Re: RBL filtering configuration"
- Reply: Geoff Pearce: "Re: RBL filtering configuration"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 14 Mar 2005 12:41:07 -0800
Geoff,
Thank you for your reply.
The article ID that you referenced is the problem. The article says that
you can create exceptions based upon the SMTP address. But when you go to
Exchange 2003 System Manager> Global Settings> Message Delivery>Properties>
Connection Filtering> Exceptions and hit Help it is stated that this
Exception is for a receipent's SMTP address.
Charlie
"Geoff Pearce" wrote:
> Read the following link
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;823866&Product=exch2003
>
> The following sections will answer your question
>
> . SMTP command:
>
> EHLO domain.com
> . SMTP command:
>
> MAIL FROM: joe@domain.com
>
> Mail flow process that occurs: 1. Exchange Server checks the Global
> Accept and Deny List Configuration settings on the Connection Filtering tab
> of the Message Delivery Properties dialog box: . If the sender's IP address
> appears in the Accept List dialog box, the message is flagged as having
> passed the Deny list and the RBL.
> . If the sender's IP address appears in the Deny List
> dialog box, Exchange Server closes the connection, and then returns the
> following error message to the sender:
> 550 5.7.0 Access Denied
>
> 2. Exchange Server checks the Senders list on the Sender
> Filtering tab of the Message Delivery Properties dialog box. If the sender's
> IP address appears in this list, Exchange Server closes the connection, and
> then returns the following error message to the sender:
> 554 5.1.0 Sender Denied
>
> . SMTP command:
>
> RCPT TO: sally@contoso.org
>
> Mail flow process that occurs: 1. Exchange Server checks the SMTP
> addresses in the exceptions list to the block list service rules. To view
> this list, click Exceptions on the Connection Filtering tab of the Message
> Delivery Properties dialog box. If the sender's SMTP address appears in this
> list, Exchange Server bypasses the RBL.
> 2. Exchange Server checks the recipients that appear in the
> Recipients list on the Recipient Filtering tab of the Message Delivery
> Properties dialog box. If the message recipient appears in this list,
> Exchange Server returns the following error message to the sender:
> 550 5.7.1 Requested action not taken: mailbox not available
> 3. Exchange Server checks the RBL. If the sender is from a
> blocked domain, Exchange Server closes the connection, and then returns the
> following error message to the sender:
> 550 5.7.1 169.254.1.253 has been blocked by default.
> 4. Exchange Server determines whether the Filter recipients who
> are not in the Directory check box is selected on the Recipient Filtering
> tab of the Message Delivery Properties dialog box. If this check box is
> selected, and if the recipient does not appear in the Active Directory
> directory service, Exchange Server returns the following error message to
> the sender:
> 550 5.1.1 User unknown
> In this scenario, Exchange Server does not close the connection,
> and the sender can continue to try to deliver mail to other e-mail
> addresses.
>
>
> Geoff Pearce
>
> "Charlie M" <CharlieM@discussions.microsoft.com> wrote in message
> news:58D15B9D-7BDD-4DF0-8D4C-E0D880543258@microsoft.com...
> > Artical ID 823866 states:
> > "This functionality (Exceptions to the connection filter) permits you to
> > override the RBL settings. This is helpful when you want to permit a
> > domain
> > that has just been removed from an RBL site to send e-mail to the local
> > domain.
> >
> > To permit delivery based on the SMTP address, follow these steps: 1. In
> > the
> > Message Delivery Properties dialog box, on the Connection Filtering tab,
> > click Exception, and then click Add.
> > 2. Type an SMTP address, or use wildcard characters to permit all the
> > users
> > who are in a specific domain to send e-mail to your organization. For
> > example, to accept all messages from contoso.com, type *@contoso.com."
> >
> > But when you go to the Conection Filtering > Exceptions and click on
> > 'Help"
> > it reads:
> >
> > "Block List Service Configuration Settings
> > Use the Block List Service Configuration Settings dialog box to configure
> > exceptions to your connection filter rules. Specifically you can add an
> > SMTP
> > address in your organization to which users can send messages, regardless
> > of
> > whether those users' IP addresses appear on a block list. Exceptions apply
> > to
> > all filter rules. This is useful if you want legitimate organizations to
> > be
> > able to contact the postmaster account to communicate with your
> > administrators. For example, suppose a legitimate company has a server
> > inadvertently configured to allow open relaying; therefore, e-mail sent
> > from
> > this company to any of your users would be blocked. If you add your
> > postmaster's SMTP address as an exception, then the company's
> > administrator
> > can e-mail your postmaster account to inform you of the company's
> > situation
> > or find out why they cannot send e-mail to your organization."
> >
> > Am I missing something?
> >
> > Thanks in advance.
> >
> > Charlie
> >
>
>
>
- Next message: Mark Arnold [MVP]: "Re: Folder Cleanup Issue"
- Previous message: Bob: "Question RE: Help Desk Permissions"
- In reply to: Geoff Pearce: "Re: RBL filtering configuration"
- Next in thread: Geoff Pearce: "Re: RBL filtering configuration"
- Reply: Geoff Pearce: "Re: RBL filtering configuration"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|