[exim-dev] [Bug 1750] New: transfer acl_m and acl_c variable…

Góra strony
Delete this message
Reply to this message
Autor: admin
Data:  
Dla: exim-dev
Nowe tematy: [exim-dev] [Bug 1750] transfer acl_m and acl_c variables to bounces and autoreplies
Temat: [exim-dev] [Bug 1750] New: transfer acl_m and acl_c variables to bounces and autoreplies
https://bugs.exim.org/show_bug.cgi?id=1750

            Bug ID: 1750
           Summary: transfer acl_m and acl_c variables to bounces and
                    autoreplies
           Product: Exim
           Version: N/A
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Delivery in general
          Assignee: nigel@???
          Reporter: bjornar.ness@???
                CC: exim-dev@???


When a bounce or autoreply is generated, it does not copy the
original messages acl_m and acl_c variables. It would be of great
help to more complex configurations if a setting would allow this
to be done if wanted.

For example, say exim takes some routing/transport decisions based
on incoming ip address, and a database lookup based on that.

What I have to do at the moment is the following:

1) transfer the information I need to bounce/dsn/autoreply messages
through message headers (have to be encoded, and max length)
2) instead of ${extract{brand}{$acl_m_server}} in routers/transport
I have to make a acl

  get_brand:
    accept  condition      = ${if def:acl_c_scfg}
            message        = ${extract{brand}{$acl_c_scfg}{$value}fail}


    accept  condition      = ${if def:h_x-brand:}
            message        = $h_x-brand:
    deny


Is there strong opinions about not implementing this?

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