Re: [monit] Alerts and HELO/MessageID hostname issue

[Scott Silva]

on 1/31/2008 1:30 PM Athan Dimoy spake the following:
> The host where monit runs (example.com) also hosts my mail server 
> (mail.example.com). This server is used my monit to send alerts using smtp 
> (mailserver mail.example.com). Monit is using gethostname() function which 
> returns the hostname example.com. Next, this hostname is used my monit, both 
> as HELO (EHLO) and MessageID trail.
>
> Unfortunately, my ISP, as well as my company mailserver, use a backscatter 
> protection that reject monit alerts as forged mail. The reason is, that 
> example.com MX is mail.example.com and that is what is expected as HELO 
> message and MessageID trail.
>
> The only solution I've found so far, is to hardcode the desired hostname 
> (mail.example.com) in sendmail.c.
>
> Could you please consider implementing an additional mailserver entry that 
> will allow users to set the exact hostname to be used for HELO/EHLO and 
> MessageID generation? For example: "set mailserver mail.example.com with 
> hostname mail.example.com with timeout 30 seconds"
Your hostname is not a FQDN. You shouldn't use your domain name as the 
complete hostname. A FQDN needs a machine name in addition to the domain name. 
So your machine could just be named mail.example.com also.

--
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!

signature.asc
Description: OpenPGP digital signature