> -----Original Message-----
> From: Robert Kehl [mailto:mailinglists@robertkehl.de]
> > From: "Ralf Hauser" <ralfhauser@???>
> > 3) Not having a domain for a certain set of recipients is intentional
> > because I want people NOT to send mails via any other SMTP server than
> > mine (TLS protected, etc.). How would you implement this otherwise
> > that sending a
> > message to any smtp typically fails (prior to sending the message
> > body/attachments over the wire!!!) while it succeeds with mine?
>
> You must be using any kind of firewall, aren't you? To stop your users
> emailing with a server other than yours, I suggest you use your firewall
> in the primary place.
My goal is to have this not just for the users on my LAN, but also arbitrary
outside users.
>
> Block port 25 for outgoing traffic from your LAN, while at the same time
> allowing any kind of traffic from/to your exim box. You might
> additionally try to redirect all LAN traffic arriving at port 25 and
> being meant for the outside to land up on your exim box. Probably, any
> kind of authentication won't succeed in that case as it were meant for
> other servers, but you may then create some kind of alerting mechanism.
> Combined with a firewall log watcher you'll achieve quite convenient
> control over your user's email traffic.
If I understand correctly, this is only useful for users that are on a
LAN/Network inside a firewall I control.
Also, in the meantime I noticed that Outlook doesn't allow me to send just
"local_parts" because it automatically starts a contact list lookup. So, I
guess I really need further ideas.
