LucidServerMoreMailIntegration

Revision 2 as of 2009-11-20 16:40:08

Clear message

Summary

This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Rationale

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

User stories

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Ubuntu mail filtering

Upstream

Postfix recommends amavisd-new as a filtering option and then stack other tools with it.

Goals

Provide API to /etc/postfix/master.cf Amavisd-new already covered Separate mail stacks for use in different environments (someone wants mail filtering, someone doesn't, same goes for SASL, etc...)

Stack

* MTA * Antispam

  • RBL

  • RulesDuJour

  • Bayesian
  • Greylisting (postgrey in Main)
  • SPF/DKIM
  • Other possible rules:
    • reject_invalid_hostname
    • reject_non_fqdn_hostname
    • reject_non_fqdn_sender
    • reject_unknown_sender_domain
    • etc

* AntiVirus

  • ClamAV

* Spam/Ham training by the user * What do to with:

  • Spam mails
  • Virus mails
    • Special case for .exe files (very annoying for users)

* Mail delivery

Decision tree

Decision for mail task

  • Single server?

    • Y: -> everything is installed N: Filter or MTA ?

      • Filter: Postfix + Amavisd + ... MTA: Postfix + Dovecot + ...

Discoverabilty

  • --> talk about it in the server-tips session and ask Ivanka Big Grin :) --> add url for additional info in each debconf question --> Tasksel option(s)

Documentation

  • Update Server Guide with new additions, but leave old instructions.
    • Advertise the Server Guide in the conf files
    • Explain the general policy: why it's this way by default, and what steps to do to improve filtering
  • Update help.u.c mail sections for current postfix, dovecot, etc.

CategorySpec