empty envelope-from=<> vacation message from dovecot

Discussion in 'Server Operation' started by IntrISP, Jul 10, 2024.

  1. IntrISP

    IntrISP New Member

    Hello I see in my vacation message have empty envelope-from=<> , and this messages is not aceptable in gmail how fix this
    Example from email headers from mail in vacation
    Received-SPF: None (no SPF record) identity=no SPF record; client-ip=serverIP ; helo=hostname; envelope-from=<>; receiver=<UNKNOWN>
  2. pyte

    pyte Well-Known Member HowtoForge Supporter

    This is according to spec for vaction messages, to prevent mailloops.

    See: https://datatracker.ietf.org/doc/html/rfc5230#section-5.1
    till likes this.
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    The reason why Gmail rejected it is not the empty envelope-from header. Take care that the domain the email is sent from and also the hostname of your system have valid spf records, besides that, turn on DKIM signing and you might also want to create a DMARC record.
    ahrasis likes this.
  4. IntrISP

    IntrISP New Member

    Hi do you want a help my this is my header from onet mail where mail is saved in mailbox
    What's wrong ? why mail is not not saved in gmail
    • Received: from mx.poczta.onet.pl (unresolved []:51702)
    • by ps50.m5r2.onet (Ota) with LMTP id A683B1D
    • for <[email protected]>; Tue, 9 Jul 2024 13:16:03 +0200 (CEST)
    • Received-SPF: None (no SPF record) identity=no SPF record; client-ip=x.x.x.x; helo=x.x.x; envelope-from=<>; receiver=<UNKNOWN>
    • Authentication-Results: mx.poczta.onet.pl;
    • bimi=none (No BIMI records found);
    • dkim=none (no signatures found);
    • dmarc=pass policy.published-domain-policy=quarantine policy.applied-disposition=none policy.evaluated-disposition=none (p=quarantine,d=none,d.eval=none) policy.policy-from=p header.from=intratel.pl;
    • iprev=pass smtp.remote-ip=x.x.x.x (x.x.x.x);
    • spf=pass policy.authdomain=x.x.x smtp.mailfrom="" smtp.helo=x.xx.x;
    • x-ptr=pass smtp.helo=xxxx policy.ptr=xxxx;
    • x-tls=pass smtp.version=TLSv1.3 smtp.cipher=TLS_AES_256_GCM_SHA384 smtp.bits=256
    • Received: from: xxxxx (xxxx [x.x.xx])
    • (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
    • (No client certificate requested)
    • by mx.poczta.onet.pl (Onet) with ESMTPS id 4WJJMQ4LHBz3Bqm
    • for <[email protected]>; Tue, 9 Jul 2024 13:16:02 +0200 (CEST)
    • Received: by mail.intratel.pl (Postfix, from userid 5000)
    • id 4E7E2CC233F; Tue, 9 Jul 2024 13:06:09 +0200 (CEST)
    • DKIM-Filter: OpenDKIM Filter v2.10.3 xxxx 4E7E2CC233F
    • X-Sieve: Pigeonhole Sieve 0.5.15 (e6a84e31)
    • Message-ID: <dovecot-sieve-1720523169-282027-2@xxxxx>
    • Date: Tue, 09 Jul 2024 13:06:09 +0200
    • From: <xxx@xxxx>
    • To: <[email protected]>
    • Subject: Out of office reply
    • In-Reply-To: <[email protected]>
    • References: <[email protected]>
    • Auto-Submitted: auto-replied (vacation)
    • Precedence: bulk
    • X-Auto-Response-Suppress: All
    • MIME-Version: 1.0
    • Content-Type: text/plain; charset=utf-8
    • Content-Transfer-Encoding: 8bit
    • X-Authentication-Milter: Header added by Authentication Milter
    • X-ONET_PL-MDA-Version: 1.0.25
    • X-ONET_PL-MDA-Info: 050 29097 A683B1D 0.000000
    • X-ONET_PL-MDA-Spam: NO
  5. pyte

    pyte Well-Known Member HowtoForge Supporter

    Check the mail.log at /var/log/mail.log. The receiving gmail mailserver will tell you why the message got rejected.
    till likes this.

Share This Page