[exim-dev] [Bug 2890] New: allow autoreply driver to send re…

Startseite
Nachricht löschen
Nachricht beantworten
Autor: admin
Datum:  
To: exim-dev
Neue Treads: [exim-dev] [Bug 2890] allow autoreply driver to send replies with non empty (settable) sender address, [exim-dev] [Bug 2890] autoreply driver: return_path option not working for that driver, [exim-dev] [Bug 2890] autoreply driver: return_path option not working for that driver, [exim-dev] [Bug 2890] autoreply driver: return_path option not working for that driver, [exim-dev] [Bug 2890] autoreply driver: return_path option not working for that driver, [exim-dev] [Bug 2890] autoreply driver: return_path option not working for that driver
Betreff: [exim-dev] [Bug 2890] New: allow autoreply driver to send replies with non empty (settable) sender address
https://bugs.exim.org/show_bug.cgi?id=2890

            Bug ID: 2890
           Summary: allow autoreply driver to send replies with non empty
                    (settable) sender address
           Product: Exim
           Version: 4.95
          Hardware: All
                OS: All
            Status: NEW
          Severity: wishlist
          Priority: medium
         Component: Transports
          Assignee: unallocated@???
          Reporter: arekm@???
                CC: exim-dev@???


This feature request is about making "return_path" option working with
autoreply transport.


autoreply transport currently sends emails with empty "<>" sender, always.

That is "To reduce the possibility of message cascades".

There is no way to change that. Generic transport option "return_path" has no
effect for autoreply transport.

That leads to some issues where for example gmail rejects such messages (with
<> sender) when DMARC is on and only SPF is used (no DKIM).

Also user that has autoreply feature activated doesn't get any bounces
(obviously) for failed autoreply-mail deliveries and can never be sure which
autoreplies were delivered and which did not.

Also we could just want to have these send with real sender address.

Working "return_path" transport option would allow autoreply messages fulfill
one of above needs, adding flexibility to autoreply feature.

For preventing message cascades - once & once_repeat, with some non 0 time,
should do the job, too.

--
You are receiving this mail because:
You are on the CC list for the bug.