-Each email contains an X-Envelope-From adress constructed as
+Each email contains an X-Envelope-From address constructed as
follows:
-The adress starts with "bounce" (can be changed by a parameter)
+The address starts with "bounce" (can be changed by a parameter)
followed by the user_id, a hashkey and the package_id of the
package instance that sent the email, separated by "-". The
-domain name of this adress can be changed with a parameter.
+domain name of this address can be changed with a parameter.
The system checks every 2 minutes (configurable) in a certain maildirectory (configurable) for newly bounced emails, so the @@ -32,7 +32,7 @@ strips out the message_id and verifies the hashkey in the bounce-address. After that the package-key of the package sending the original mail is found out by using the package_id provided in the bounce -adress. With that, the system then tries to invoke a callback +address. With that, the system then tries to invoke a callback procedure via a service contract if one is registered for that particular package-key. This enables each package to deal with bouncing mails on their own - probably logging this in special tables. @@ -70,5 +70,9 @@ In case of multiple services on one system, create a bounce email for each of them (e.g. changeing "bounce" to "bounce_service1") and create a new user that runs the aolserver process for each of them. You do not want to have service1 deal with bounces for service2. +
Please file bugs in the Bug Tracker.
+