Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The return-path is generated, first from the value used by your smtp client at the mail from: command, but also can encode values with the use of <a href="http://www.zrinity.com/xms/docs/xms.filter.data.attributemapfilter.html" rel="nofollow">AttributeMapFilter</a> and <a href="http://www.zrinity.com/xms/docs/xms.filter.bounce.verpbouncefilter.html" rel="nofollow">VerpBounceFilter</a>.</p> <p>AttributeMapFilter (inside SMTPService)</p> <pre><code> &lt;filter class="xms.filter.data.AttributeMapFilter" attributemap="verpmap" remove="false" /&gt; </code></pre> <p>The map would have entries, such as </p> <p>camid=X-camid</p> <p>VerpBounceFilter (inside SMTPService)</p> <pre><code> &lt;filter class="xms.filter.bounce.VerpBounceFilter" feedbackaddresslist="Feedback Addresses" verpprefix="verpprefix" verpvariables="env_recipient,camid" action="accept" domainlist="Local Domains"&gt; &lt;action class="xms.action.DBAction" datasource="mydatasource" event="*"&gt; &lt;sql&gt; &lt;![CDATA[ INSERT INTO bounce (recipientaddress, env_from, bounceaddress, message, bouncetype, camid) VALUES(?,?,?,?,${bounce_type},${verp_camid?default(-1)}); ]]&gt; &lt;/sql&gt; &lt;param&gt;${verp_env_recipient?default('')}&lt;/param&gt; &lt;param&gt;${env_from?default('')}&lt;/param&gt; &lt;param&gt;${env_recipient}&lt;/param&gt; &lt;param&gt;${bounce_message}&lt;/param&gt; &lt;/action&gt; &lt;/filter&gt; </code></pre> <p>If you generate messages with TemplateSerice, add an instance of VerpBounceFilter to the job, without an action.</p> <p></p> <p>In that configuration, camid would be supplied by one of the providers in the job.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload