Smtp - allow trusted users on internet to route mail only thru server 1

[F1lby]

Hi,
Does anyone know a way of implementing a way to allow only trusted users on the internet to route mail thru an Exchange2K server?
I wish to let users out in the 'big bad world' to route mail through my Exchange2K server. Problem is I can't find a way to authenticate on sending.
All mail clients feature a facility that ensures that to send a mail through a server, the client has to logon first, BEFORE transmission occurs. Does Exchange2K have this feature?
I have also seen POP BEFORE SMTP (Unix) that modifies access.db (trusted IP addresses) to include the trusted POP3 users IP address when a user does a successful POP3 login - this means that a trusted POP3 user CAN send mail.

Either (or a different solution) would be fine. I just cant find a way to implement them on Exchange2K.

I am restricted to staying with Exchange and cannot use address blocking on the firewall as the IP addresses used on the clients are dynamically assigned.

 

[Xybertron]

You set this up on the relay section of the SMTP Virtual Server. Dan
Microsoft Exchange Support @ Microsoft

 

[F1lby]

ok......... and what mechanism is used to determine whether a user is trusted or not?
Sorry Dan, but need a little more info.

Rgds

Phil Blythe

 

[F1lby]

Dan!
Many thanks - I'm no great expert with Exch2K, but finally made it!!!! MANY MANY THANKS!!!

 

[F1lby]

Errrmm. Had to put things back the way they were, as doing this stopped mail from coming in, as it caused our server to require authentication EVEN to route mail to a local domain - so it seems to be an 'all or nothing' approach which looks like I'd need a 2nd server...

Any ideas on authentication, BUT still allowing mail in?

I need something like 'allow mail to route if domainname=US but require authentication if domainname=NOTUS'.

So near.... but so far.........

But in practice, this DOES work.

 

[F1lby]

Errrmm. Had to put things back the way they were, as doing this stopped mail from coming in, as it caused our server to require authentication EVEN to route mail to a local domain - so it seems to be an 'all or nothing' approach which looks like I'd need a 2nd server...

Any ideas on authentication, BUT still allowing mail in?

I need something like 'allow mail to route if domainname=US but require authentication if domainname=NOTUS'.

So near.... but so far.........