On Wed, Apr 6, 2011 at 11:45 PM, Glen <gpecats@???> wrote:
Glen, it's not a bug in exim. It's a limitation in the way that you
have exim configured.
> # Put simple tests first. A good one is to check for the presence of a
> # Message-Id: header, which RFC2822 says SHOULD be present. Some broken
> # or misconfigured mailer software occasionally omits this from genuine
> # messages too, though -- although it's not hard for the offender to fix
> # after they receive a bounce because of it.
> #
> deny condition = ${if !def:h_Message-ID: {1}}
!hosts = nwildsearch;/path/to/msgid_exclusions.txt
> message = RFC2822 says that all mail SHOULD have a Message-ID
> header.\n\
> Most messages without it are spam, so your mail has been
> rejected.
> Is there any way around this - we do not want to disable this check entirely ?
> A bugfix perhaps or any suggestions for recoding the ACL ?
It's not a bugfix, add the line above, modifying the path to suit your
environment, then in that msgid_exclusions.txt, put the ip addreses
you do not want this check to be done for. For example:
192.168.* # this is all your internal hosts
10.* # more internal hosts
*.gpecats.com # All of the machines you control
Note that I put the comments there to explain them, you'll need to
remove them in actual operation.
You can test it with 'exim -bh $IP' where $IP is the ip address you
want to test this acl on (you'll need to do the HELO, the MAIL FROM,
and RCPT TO and DATA).
--
Regards... Todd
"It is the nature of the human species to reject what is true but
unpleasant and to embrace what is obviously false but comforting."
"You might be a skeptic if you have pedantically argued the topic of pedantry."
