[Top][All Lists]

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

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

From: Martin Pala
Subject: Re: [monit] Alerts and HELO/MessageID hostname issue
Date: Tue, 19 Feb 2008 23:30:54 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20080129 Iceape/1.1.8 (Debian-1.1.8-2)


the new "hostname" option was added which allows to override the default outgoing hostname used in EHLO/HELO and Message-ID header.

Example syntax:

  set mailserver
    with timeout 30 seconds
    using hostname ""

The change is in CVS ( and will be part of next monit release.


Athan Dimoy wrote:
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"


To unsubscribe:

reply via email to

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