It's not clear to me what the fix is that will arrive, but it looks as if it might just be documentation in the README.Debian. If so, I'd like to put in a word for doing a bit more. It really shouldn't be necessary for the administrator to mess around with the configuration (other than enabling mail delivery) to make things work in a standard setup.
Here are some possible, untested solutions, based on my having spent too much time recently with exim4. 1. I suspect that fail2ban is delivering over TCP (127.0.0.1). I believe that if it delivers "locally" in exim speak, which means using the exim aka sendmail command to send the message directly, addresses will be eligible for automatic addition of domain name. 2. Alternately, fail2ban could lookup and use the host FQDN. 3. Possibly aliases or rewrite rules would address this problem, but they may happen too late to do any good. 4. You could drop a custom snippet in /etc/exim4/conf.d/... This seems unappealing, since it won't help people with a monolithic configuration (the recommended setup for a newbie) of exim4 (unless you add logic to mess with the monolithic file). And it's exim4 specific. 5. Other packages, e.g., logcheck, manage to get around this problem. I don't know how, but they might be a model. However, most of them do create a user, which may be overkill. 6. You could use different values for the envelope sender and the "From" field. e.g., sender is root, but From: is fail2ban. This raises other issues (e.g., are you allowed to set the envelope sender?). -- Ross Boylan wk: (415) 514-8146 185 Berry St #5700 [EMAIL PROTECTED] Dept of Epidemiology and Biostatistics fax: (415) 514-8150 University of California, San Francisco San Francisco, CA 94107-1739 hm: (415) 550-1062 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
