Re: Bunch of SMTP connectors - why ?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 10/18/04 

Date: Mon, 18 Oct 2004 13:54:56 -0400

Daniel Mendes wrote:
> Lanwench,
>
> Thank you for your (quick!) reply.
>
> Examples of the messages on the queue are:
>
> Sender "=?iso-8859-1?Q?f=E1bio_Silva?= <tvplasma2@hotmail.com>",
>
> Envelope Recipients:
> SMTP:abitron@abitron.com.br; SMTP:ctprimos@terra.com.br;
> SMTP:inetmidia@inetmidia.com.br; SMTP:matrix@matrixsite.com.br;

<snip>

> And they just keep getting through. Our server is not accepting relay
> - just tested it on www.abuse.net/relay.html.

That probably isn't checking for authenticated relay - and if you're seeing
outbound messages originating from domains you don't control in your queues,
it really looks like you are being used for relay.
>
> Anonymous access on the SMTP Virtual Server is NOT selected (basic and
> integrated Windows authentication methods are).

Well, you do need anonymous access enabled unless you have another relay
server somewhere that's sending mail to your server. Relay and connections
are two different things entirely. Leave the connection settings as they
were.
>
> Relay restrictions on the SMTP Virtual Server lists only 192.168.16.2
> (our internal LAN), 127.0.0.1 and 200.204.179.15 (external LAN)

What do you mean by "external LAN"? That's a public IP address - what's it
assigned to? Do you have two NICs in this server? No need to put it in
there.
 Who needs to relay through this server at all? Do you have POP clients? I
would have them use their ISP's SMTP server instead of yours, if so. And
your Outlook/MAPI clients on your LAN don't need to be allowed relay rights.
Nor does your own server need to be specified there, public or private IP,
really.

> as
> computers who might relay; the "allow all computers which
> successfully authenticate ..." is NOT selected.

Do you have any SMTP connectors in use?
>
> The connection control wasn't showing any restrictions, so I've just
> applied "192.168.16.2" to be the single one allowed to use it.

Do you mean in the relay settings?
>
> Finally, on the "Delivery" tab, "Outbound security", anonymous access
> is granted.

Again, not related.
>
<snip>

Relevant Pages

  • RE: Getting many 7004 Event IDs on Exchange 2003 FE server
    ... connection to fail. ... The FE server failed to relay message through the host "80.237.132.137". ...
    (microsoft.public.exchange.admin)
  • Re: Sites that block dynamic/dialups
    ... >> outbound server would be connecting to you, but since it has no inbound mail ... if you meant to say that the verification connection would be to ANY server ... In fact, without that, it acts as an open relay. ...
    (comp.os.linux.networking)
  • Re: SBC rejects email...sometimes
    ... Part of the Internet Connection Wizard (SBS On the To Do List) it asks you do you want to route via DNS or relay off another server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Identity
    ... and the verbose message is often sufficient for me to figure ... Here is an example I get when I deliberately try an unauthorized relay: ... > Server: 'smtp.compuserve.com', ... The connection was denied by the remote server. ...
    (microsoft.public.security)
  • Re: SuSe 10.2 and PostFix setup
    ... The original message has been removed from the bounce message. ... By sending it to a mail server here. ... Which then, quite rightly, said I'm not a relay so don't try relaying ...
    (alt.os.linux.suse)