On Thu, May 06, 2004 at 11:47:08AM -0700, Paul Yeatman wrote:
| ->>In response to your message<<-
| --received from Derrick 'dman' Hudson--
| >
| > On Wed, May 05, 2004 at 04:50:43PM -0700, Paul Yeatman wrote:
| > [...]
| >
| > | Yet the problem isn't with messages containing spam or a virus as much
| > | as such messages being sent to someone else's mail server, being
| > | detected as such, and then being returned to a bogus user on my
| > | server.
| >
| > Look in your logs and find out how the message managed to get into
| > your queue in the first place.
| >
| > | I think Ronny and now myself are more asking if anyone
| > | has a clever way of dealing with these.
| >
| > Don't accept mail for non-existant users. I don't remember all the
| > details with exim, but you need to put a check in your rcpt acl. I
| > expect there is plenty of information on the web, particularly if you
| > search the exim-users archives.
FYI ACLs were added in exim 4 (some 2 years ago or so).
| I found in an FAQ for my Exim version (3.3, I think)
Find out what version you have installed :
$ dpkg -l exim
Get the documentation
$ apt-get install exim-doc
-or-
$ firefox http://www.exim.org/
(they may still have the exim3 docs available, but they may
have removed them because exim3 is so obsolete)
| that this can be set in the exim.conf with
|
| "receiver_verify = true".
That sounds reasonable. I remember the exim 3 details less than exim4
now (the effect of a periods of disuse).
-D
--
Microsoft has argued that open source is bad for business, but you
have to ask, "Whose business? Theirs, or yours?" --Tim O'Reilly
www: http://dman13.dyndns.org/~dman/ jabber: dman@dman13.dyndns.org
Attachment:
signature.asc
Description: Digital signature