You are currently working in version

Hack: If there is only one POP3 Account we might as well show all about it all the time.

Do you want to be able to reply to email notifications?
For that to work you need to make the "Sitemaster email" property be the same email address as one accepting email defined below. It is also highly recommended that your new-issue-notifications contain the full description of the issue and not just the title.

This is how it works:
You create one or more POP3 accounts.
For each account you define one or more email address which is dedicated to accepting emails into the IssueTracker.
For each email address you define what Sections, Type and Urgency the issue should take if it's not obvious from the subject line of the email.
The email sender can override these by mentioning certain words in the subject line in a special format.
It is your responsibility to periodically trigger the search for new emails.

Read more about periodically checking for email and for a list of examples of how the email sender can compose the subject of the email see the bottom of this page.

POP3 Account

POP3 Account details

-1">

If you want to you can test the account. To see if we can connect and get the POP3 servers welcome message.

Create new accepting email on this account

Existing accepting emails

" /> style="background-color:#E5E5E5;">

Email address

Default sections

Default type

Default urgency

checked="checked" /> Send confirmation message
checked="checked" /> Reveal issue URL
&blackwhitelist=#ae" >Manage white- and blacklists

" />

Blacklist	Whitelist
<dtml-var "'\n'.join(getBlacklistEmails())">	<dtml-var "'\n'.join(getWhitelistEmails())">

'"/>

Enter one email address per line. You can use * as a wildcard (eg. *@issuetrackerproduct.com). Default is to accept all emails.

Whitelist:
Blacklist:

POP3 Mangement

Existing POP3 Accounts

Create New POP3 Account

None

Examples of subject lines

Example	Yield	Condition
Office: There is a bug...	Issue title: There is a bug... Sections: "Office" Type: <whatever is default> Urgency: <whatever is default>	Section called "Office" defined
Office: There is a bug...	Issue title: Office: There is a bug... Sections: <whatever is default> Type: <whatever is default> Urgency: <whatever is default>	No section called "Office"
Office, stationary: There is a bug...	Issue title: There is a bug... Sections: [Office, Stationary] Type: <whatever is default> Urgency: <whatever is default>	Sections called "Office" and "Stationary" defined
Office, stationary: There is a bug...	Issue title: stationary: There is a bug... Sections: "Office" Type: <whatever is default> Urgency: <whatever is default>	Section called "Office" defined but not "Stationary"
General: There is a bug...	Issue title: There is a bug... Sections: "General" Type: <whatever is default> Urgency: <whatever is default>	Section called "General" and type called "general"
Bug report, Office: There is a bug...	Issue title: There is a bug... Sections: "Office" Type: "bug report" Urgency: <whatever is default>	Section called "Office" and a type called "bug report"
Bug Report, Office: There is a bug...	Issue title: There is a bug... Sections: <whatever is default> Type: "bug report" Urgency: <whatever is default>	A type called "bug report" but no section called "Office"
Urgent: There is a bug...	Issue title: There is a bug... Sections: <whatever is default> Type: <whatever is default> Urgency: "urgent"	An urgency called "urgent"
Bug report, Feature request: There is a bug...	Issue title: Feature request: There is a bug... Sections: <whatever is default> Type: "bug report" Urgency: <whatever is default>	At least a type called "bug report" nomatter if a you have type called "feature request"
Feature request, Bug report: There is a bug...	Issue title: Bug report: There is a bug... Sections: <whatever is default> Type: "feature request" Urgency: <whatever is default>	At least a type called "feature request" nomatter if a you have type called "bug report"

Note:

Case does not matter.
A : sign (or [square brackets]) must be present for any interesting extraction
Office, Urgent: There is a bug... and [Office, Urgent] There is a bug... yields exactly the same result
Data is extracted in the order: sections -> type -> urgency. So if there are words that belong to more than one, this order is respected.

Periodically checking for email

The URL you must periodically invoke to check for new emails is:
/check4MailIssues (or same but more verbose)

If you're uncertain about how to set up a cron job, then try this mini-howto for how to setup crontab on Linux.

Hostname:Port	:
SSL	checked="checked" />
Username
Password
Delete emails after	checked="checked" />