[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Scott Silva
Subject: Re: [monit] Alerts and HELO/MessageID hostname issue
Date: Fri, 01 Feb 2008 09:40:07 -0800
User-agent: Thunderbird (Windows/20071031)

on 1/31/2008 1:30 PM Athan Dimoy spake the following:
The host where monit runs ( also hosts my mail server ( This server is used my monit to send alerts using smtp (mailserver Monit is using gethostname() function which returns the hostname 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 MX is 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 ( 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 with hostname 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 also.

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

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]