Robert Nicholson wrote:
> When I want to toggle b/w logging and no logger I simply comment out
> the logfile command in my .forward
>
> Can you tell me if exim has a problem with doing this and still
> leaving logwrites uncommented?
>
No need to wait for 'you' ('us') *Exim* has just told you so.
Exigrep / grep and you should find the same thing recorded in (one of)
your logs as the far-end reports having seen.
> Because my ISP tells me they see the following in their log
>
>> [email protected] <[email protected]> R=userforward
>> defer (-17): error in filter file: attempt to obey "logwrite"
>> command without a previous "logfile"
>> Looks like you have an issue in your scripts/.forward
>
> Can this affect the delivery of mail?
It just did!
The far-end gets only a '250 Ok' for traffic you accept.
Any other message is the result of a defer or deny.
Instead of switching the log file out of existence, better to redirect
it to a throw-away file that you can have cron purge periodically.
If/as/when you need to look at it for debugging, a few hours of
retention may be enough. Or you can suspend the purging for days while
checking.
BTW - you might wish to change your configure on another score as well.
That is not the sort of message you ordinarily want a 'stranger' to see,
as it can reveal UID and PWD in some circumstances..
Properly set up, they will see only what you choose to tell them, and/or
'Temporary local problem....'
See: smtp_return_error_details
Also compare the functionality of 'message', 'log_message', and
'logwrite', and rtfm in re 'custom' messages.
HTH,
Bill
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
