Eric - any plans to create an rpm for the new autorespond 2.06 version?

I've also opened a new issue with it at GitHub: messages containing
scandinavian letters are quoted wrong in the replies generated by the
autoresponder.

Best,
Peter

On Thu, Jan 18, 2018 at 6:14 AM, Jeff Koch <[email protected]> wrote:
> There is a new version of autorespond on GITHUB - version 2.06 - patched
> April 2016 that fixes the MessageID.
>
> The original code in existence since 2001 creates the MessageID as follows:
>
> fprintf(fdm,"Date: %u %s %u %02u:%02u:%02u -0000\nMessage-ID:
> <%lu.%u.blah>\n"
> ,dt->tm_mday,montab[dt->tm_mon],dt->tm_year+1900,dt->tm_hour,dt->tm_min,dt->tm_sec,msgwhen,getpid()
> );
>
> with the word 'blah'.
>
> The correction is:
>
>
> fprintf(fdm,"Date: %u %s %u %02u:%02u:%02u -0000\nMessage-ID:
> <%lu.%u.autorespond@%s>\n
> ,dt->tm_mday,montab[dt->tm_mon],dt->tm_year+1900,dt->tm_hour,dt->tm_min,dt->tm_sec,msgwhen,getpid(),getenv("LOCAL")
>
> using LOCAL which is the domain name followed by the user name.
>
> You can just download the code, unzip it, run 'make' followed by 'make
> install' and your autoresponder is fixed.
>
> Jeff
>
>
> On 1/17/2018 2:41 PM, Jeff Koch wrote:
>
>
> I have been testing the vacation message function on the moduser page in
> qmailadmin. The autoresponses generated by the vacation message option end
> up in my spam folders because the Message ID generated by the autoresponder
> do not include a domain name and, as a result, violate RFC 2822.
>
> These two issues give the message 4.3 points for spamassassin and the
> message ends up as junk.
>
> Here's the MessageID generated by the vacation responder:
>
> Message-ID: <1516217515.27282.blah>
>
> I don't have a clue where 'blah' comes from. All we need is a domain name to
> put in there - doesn't even need to be valid.
>
> Does anyone know how to change 'blah' to something else?
>
> Regards, Jeff
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to