Incoming emails trigger specific operations in PageSeeder.
Incoming email domain
By default, PageSeeder processes incoming emails from the domain defined by the
emailDomain property in the global properties. If the
emailDomain property is set to
pshosts, PageSeeder processes any incoming email from hosts.
For information for the sender email domain, see From address.
Valid PageSeeder recipients must match the incoming email domain defined above and their local part (the part before the ‘@’) must match one of these values:
A number of switches can be used to change how incoming emails are processed. Switches are appended to the normal recipient and all start with ‘--’.
--announce– causes the email to be sent to all members regardless of their notification settings. Only available to group contributors and higher.
--silent– prevents the email from being sent to anyone in the group, but it is still recorded as a comment in the group. Only available to group contributors and higher.
--preserve– prevents PageSeeder from using the new-comment template and forwards the email verbatim to group members. Only available to group managers and higher.
--announce--preserve– combines the announce and preserve switches. Only available to group managers and higher.
--noreply– ignore the email regardless of prefix.
If a user sends an email with a switch not available to them, the email is rejected.
All groups have a group email address defined as:
When incoming emails arrive at this address, the email is considered to be a general comment for that group. It is sent to all members of the group who have elected to receive emails and is processed by PageSeeder using the new-comment email template.
If the group name specified in the email address does not match a valid group name, a delivery error is sent back to the sender.
Summary of group email recipients
|Announce & preserve|
Comments on a specific document instead of a general comment on the group have the following format:
The URI ID must be a number corresponding to a valid document.
Replies to comments, workflow and edit notes have the following format:
The comment ID must be a number corresponding to a valid comment, workflow and edit note. Otherwise, a delivery error is sent back to the sender.
If a comment belongs on multiple groups, replies to that comment are automatically posted on all these groups.
Group returned address
Any incoming email arriving at:
is automatically forwarded to the
mailReturnedAddress defined in the group properties of that group.
Sender for emails sent by PageSeeder is:
The following recipients are always ignored:
As well as any recipient ending with
Any incoming email that is not a valid PageSeeder email recipient returns an email to the sender coming from