Ok. Thanks for those responses.
I am currently in the process of migrating my mail systems from Exim
3.3 to Exim 4.1 on a new server. As a part of this process, I am
trialing the new server by forwarding all of my (personal) mail
through it (everyone else's mail is still being delivered by the old
server). Part of this migration will be to move my mailing list
server (mailman) to the new box too but this I have not yet done.
Looking through the logs on the new server, I can see messages with
rejected senders from the mailing list software. Presumably this is
because the sender appears to be on the local domain so Exim is
trying to look it up in it's own lists and because I have not yet
moved mailman to the new box, cannot resolve the addresses.
Is this indeed the case, and so I don't need to worry yet, or is
something more serious broken?
Many thanks
Chris
- -----Original Message-----
From: Mills Mr C P [
mailto:C.P.Mills@rmcs.cranfield.ac.uk]
Sent: 15 August 2002 12:56
To: 'exim-users@???'
Subject: [Exim] To verify or not...
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
...that is the question.
I have just installed Exim 4 and am using sender verify. Examining
the logs, I can see a couple of messages that were refused due to
being unable to verify the sender. Admitedly these messages look like
spam, and anything I can do to reduce spam the better.
But, is there any situation that anyone knows of when a legitimate
address might get refused due to Exim not being able to verify the
sender address? The last thing I want to do is block legit e-mail.
I am using mailscanner and spamassassin so this also helping me to
identify (rather than reduce) spam so would I be better accepting all
mail and letting spam assassin do it's work and basically let the
user decide what to do with it?
Please help
Chris Mills
-
- --
## List details at
http://www.exim.org/mailman/listinfo/exim-users
Exim details at
http://www.exim.org/ ##
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8
iQA/AwUBPVvbrUrgSYTumc6KEQICiACg10HquPnG+Uh6VVtKMu7bY5LoEvIAoK9X
drmDcPqg4cv6frl0mMEpE9VG
=6d81
-----END PGP SIGNATURE-----
