Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 215264 - Include a backup MX host in re-designed mail setup
Summary: Include a backup MX host in re-designed mail setup
Status: IN_PROGRESS
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Infrastructure
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-28 22:57 UTC by Alex Howells (RETIRED)
Modified: 2010-08-03 23:12 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Howells (RETIRED) gentoo-dev 2008-03-28 22:57:54 UTC
We've been talking about fixing the mail situation for a little while, and as I recall there was a *big* discussion about making gentoo.org have multiple MXs for vague redundancy purposes; one might be going on lark, one elsewhere?

Just a reminder for robbat2 to get stuff moving on this one, or kick/molest someone else into setting up Postfix or qpsmtpd in the required fashion ;)
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2008-03-29 08:08:50 UTC
I honestly can't remember what the other box was besides lark.
It was going to be in parallel to handle the load of scanning, not simply redundancy.

The postfix side of it was already set up on lark, but the qpsmtpd side is still needed to handle filtering the mail.

It's like this:

1. qpsmtpd on :25, validates and accepts.
2. qpsmtpd delivers to local Postfix, which queues. Per-box redirections happen here, but aliases are not broken out (I think).
3. local Postfix delivers to destination machine (99.99% of this is either lists.g.o or woodpecker.g.o).

Stuff needed:
- Regular push of permissive data from pecker to mailin nodes.
- More granularity in the permissive settings (some devs don't want SAV, but do want spamassassin etc) - this is easy in qpsmtpd luckily :-)

Presently my main holdup is that I want to wait for the final 0.43 release of qpsmtpd.