Re: [Exim] how to accept a recipient address format that nor…

トップ ページ
このメッセージを削除
このメッセージに返信
著者: Robert Kehl
日付:  
To: hauser, exim-users
題目: Re: [Exim] how to accept a recipient address format that normal smtp servers reject before accepting the body/attachments
----- Original Message -----
From: "Ralf Hauser" <ralfhauser@???>
To: <exim-users@???>
Sent: Saturday, September 20, 2003 10:28 AM
Subject: RE: [Exim] how to accept a recipient address format that normal
smtp servers reject before accepting the body/attachments


> > 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.


Hm? You want the whole internet to just use your SMTP server? ;-)
If one of your users is connecting from the outside , he/she could as
well connect to any SMTP server in or outside this world. You won't have
control over that as long as you have no control over the administrative
account of that particular machine. In short: No way.
But... maybe I didn't get you right on this point?!

> > Block port 25 for outgoing traffic from your LAN, while at the same

time
[...]
> If I understand correctly, this is only useful for users that are on a
> LAN/Network inside a firewall I control.


Right you are.

> 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.


Add the dummy domain you use to your receipients' addresses. If Outlook
finds an address without a domain, it assumes a lazy user and does an
automatic search, as most email message would fail without a domain
part.

Your dummy domain would for sure never succeed when anyone uses a
different SMTP server than yours, as the dummy domain probably won't
resolve in real DNS.

Exim itself relies on fully qualified addresses and therefore is
internally working with them. If a non-qualified address arrives, the
settings of

primary_hostname
qualify_domain
qualify_receipient
sender_unqualified_hosts
receipient_unqualified_hosts

determine how the address is converted to a fully qualified one.

hth,

Robert Kehl