Extensions to run
The Extensions to Run tab determines how extensions are handled for the mailings. The table below explains the settings:
Field Name | Description |
---|---|
Before Posting |
This setting allows you extend the Aurea List Manager posting processing with your own program. When a message comes in for distribution on this mailing list, your program is going to first be run and your program can do any processing it wishes on the message. If your program wants to stop processing of the message or stop the message from being posted, it can delete it. |
After Posting |
This setting allows you extend the list posting processing with your own program. When a message comes in for distribution on this mailing list, your program runs at the very end after the message has been distributed. |
Before Subscribing |
This setting allows you to extend the subscribe process by running your own program before the subscription is accepted by the server. Whenever a subscribe request comes into this list, this program id going to run. For example, your program may have a database of acceptable users and you may want to look up each subscribe request to make sure they are in the database. |
After Subscribing |
This setting allows you to extend the subscribe process by running your own program after a subscribe request has been processed by the server. For example, your script may want to update your external database, so it can keep your Aurea List Manager db and your external db in sync. |
Before Unsubscribing |
This setting allows you to extend the unsubscribe process by running your own program before an unsubscribe request has been processed by the server. |
After Unsubscribing |
This setting allows you to extend the unsubscribe process by running your own program after an unsubscribe request has been processed by the server. For example, your script may then update your external database so that your ListManager db and your external db are in sync. |