legacy code has no transactional integrity

[cprima]

Description

The diagram of the legacy process shows clearly: If an error happens during FTP upload, the mail is handed over to a human, while already having been entered into the webapplication.

Acceptance Criteria

• Common error situation up to and including FTP upload must be anticipated and handled
• minimum unit of work shall be a QueueItem, not a MailMessage

Subtasks

• use Orchestrator Queue and Dispatcher or a in-process queue
• sanitize subject to be fit for use as filename (at minimum remove forbidden characters)
• Prior to any output implement validation as part of data processing

Related Issues / Dependencies

• Related to: Refactoring monolithic legacy code #1
• Depends on: Implement In-Process Queue Management for Email-Based ReFramework Workflow #13

Priority

• Priority: High

Attachments / Additional Resources

• Attachments: none