Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

...

The Universal Messenger supports the following sender address options and can be configured in cmsbs.bounce.verp.envelopeFrom:

VERP (Variable Envelope Return Path)

  • Sender address consists of a static and a variable part, e.g. newsletter-ABC1235XYZ@mydomain.com.

  • You can define the pattern in the UM configuration cmsbs.bounce.verp.envelopeFrom as newsletter-%@mydomain.com

  • Your mail server must be able to put all received Emails matching that pattern into the same mailbox. Whether this is possible or not depends on the mail server software used.

    • Usually works: Exim/courier, postfix/dovecot

    • Usually doesn’t work: Exchange, Lotus Domino/Notes

      • Workaround: Catch-All rule for subdomain

  • The Universal Messenger will create a unique pattern as the variable part for every single Email it sends out and keeps a record to remember which address was used for which Email.

...

Sender address is fixed and will be used for every Email sent by Universal Messenger regardless of which address is set in FROM header. In that case, just set that Email address in property cmsbs.bounce.verp.envelopeFrom.

Use FROM address

If you do not define a technical sender address the one used in the FROM header will be used by default. Note that if this address will receive all technical messages like vacation replies or bounce messages. For this option do net set property cmsbs.bounce.verp.envelopeFrom.

Bounce management

It is important to detect whether a single Email could be delivered and find out the reasons why not. If an Email cannot be delivered your mail server will usually get a reply: a bounce message.

...

If the UM cannot find a type or a matching Email address it will forward the Email to a postmaster address defined in the global UM configuration.

Automatically unsubscribe users with too many bounces

The Universal Messenger can automatically unsubscribe users from all lists if their Email address has too many bounces. It is also possible to give a CSE callback function if the threshold is reached.

  • cmsbs.bounce.hardbounce.max = <number>

  • cmsbs.bounce.softbounce.max = <number>

  • cmsbs.bounce.autorespond.max = <number>