On Monday 27 February 2006 10:12 pm, Peter Bowyer wrote:
> Directors no longer exist in Exim 4.x, so the origin of your config
> file is getting on for 4 years old. As Bill says, this isn't
> necessarily a Bad Thing because the convert script probably did a
> reasonable job of updating the file for 4.x, but it does suggest that
> the config might be sub-optimal.
Okay ... I'm the "Jeff" that Bradley referred to. I wrote the
exim.conf file in question.
I sent this once already, but it went to you rather than the list.
Probably because you have a reply-to set in your posts; that overrides
the list default response mechanism, and I didn't notice.
Sorry about that.
The "Directors" references in my file are strictly headers left over
from the configuration DirectAdmin wrote... that one was built
automatically from the convert script, and it did have headers in it
referring to directors, though it changed them all to routers.
And I left the headers in; even prettified them, not thinking much about
the fact that they weren't directors anymore <frown>. But if you look
below those headers you'll see that those are routers, not directors.
So the only important questions are "is the Spam Assassin router
(actually identified as the spamcheck director in the comment, though
it's really a router) badly written?" and "Is the spamcheck transport
badly written?" Probably one or both are, but I'd like to know how to
write it better and still leave in all it's functionality.
If you or anyone can point me in the right direction I certainly can
learn.
But just telling me it's not optimal isn't helping. We know that; if it
was it wouldn't be causing those bsmtp errors.
Thanks.
> It's always difficult to give useful support to users of the various
> auto-generated config systems which use Exim, because (and this is no
> criticism of yourself) the user hasn't written the config themselves
> and so is unable to answer all the 'show us your xxx router' and 'why
> did you write it like that' questions that inevitably follow, and
> it's also often difficult to make small changes to the config for
> debug purposes without breaking the auto config mechanism.
I didn't write the Spam Assassin router myself. I didn't write the
spamcheck transport which looks like this:
<snip>
spamcheck:
driver = pipe
batch_max = 100
command = /usr/sbin/exim -oMr spam-scanned -bS
current_directory = "/tmp"
group = mail
home_directory = "/tmp"
log_output
message_prefix =
message_suffix =
return_fail_output
no_return_path_add
transport_filter = /usr/bin/spamc -u
${lookup{$domain}lsearch*{/etc/virtual/domainowners}{$value}}
use_bsmtp
user = mail
# must use a privileged user to set $received_protocol on the way back
in!
</nsip>
and which isn't working... it's causing those bsmtp errors.
So that's what we have to rewrite. Help greatly appreciated.
Thanks.
Jeff
--
Jeff Lasman, Nobaloney Internet Services
1254 So Waterman Ave., Suite 50, San Bernardino, CA 92408
Our blists address used on lists is for list email only
Phone +1 909 266-9209, or see: "
http://www.nobaloney.net/contactus.html"
