I would like to give some feedback,
I updated my qmail from 1.03-2.1 to 1.03-3.1, retested vacation message
using manasieve filter and it worked with Gmail, the Return-Path now is
only "<>" like it should be.
Thank you all.
Em 14/05/2019 14:20, Leonardo Porto escreveu:
Hi Eric,
The Last Modified information about the qmail rpms are still from 2018
so I thought they were not updated yet.
I only need download qmail-1.03-3.1.qt.el7.x86_64.rpm and install on
my system to correct the null sender, right?
Regards.
Em 13/05/2019 18:22, Eric's mail escreveu:
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/development/x86_64/
<http://ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/development/x86_64/>
Get Outlook for Android <https://aka.ms/ghei36>
On Mon, May 13, 2019 at 2:05 PM -0600, "Leonardo Porto"
<[email protected] <mailto:[email protected]>> wrote:
Hi Eric,
Is that already available for download?
Em 21/03/2019 12:10, Eric Broch escreveu:
This patch is in the latest qmail rpm (CentOS 7) in the
development tree.
Thanks, Roberto!
On 3/21/2019 1:36 AM, Roberto Puzzanghera wrote:
Have a look here
https://notes.sagredo.eu/qmail-notes-185/qmail-inject-sieve-vacationreject-messages-trouble-133.html
Il giorno mer 20 mar 2019 alle ore 21:30 Leonardo Porto
<[email protected] <mailto:[email protected]>> ha
scritto:
Hi,
Gmail is rejecting my vacation messages set in managesive
filters, when I look qmail-send logs I find this:
2019-03-20 11:59:22.717746500 info msg 100921151: bytes 690
from <<>@my.default.domain> qp 12303 uid 89
2019-03-20 11:59:24.229429500 delivery 2: failure:
Connected_to_64.233.190.27_but_sender_was_rejected./Remote_host_said:_555_5.5.2_Syntax_error._v3si1315429qth.170_-_gsmtp/
Hotmail accept it so I look in the message source code and
find out the Return-Path is "<>"@my.default.domain.
It seems the null sender <> is the default and recommended
behaviour to prevent loops but apparently my problem is the
something in the process is adding my default qmail domain
after it.
By the way, the email account used in this case belongs to
another domain, not the default domain.
Does anyone have a clue why this is happening?
Thanks.
--
Eric Broch
White Horse Technical Consulting (WHTC)
