History

Versions 74

Version Author Diff Last updated
v74 Antoine Beaupré
mention TPA-RFC-45 (tpo/tpa/team#41009)
v73 Roger Dingledine
make clearer that smtp_sender_dependent_authentication and relay_host conflict
v72 Antoine Beaupré
finish filling up the email service template
v71 Antoine Beaupré
lint
v70 Antoine Beaupré
merge the howto/submission docs into service/email
v69 Antoine Beaupré
restore the manual opendkim procedure (tpo/tpa/team#40989) I don't believe the duplication will bring much confusion but, more importantly, some parts of the manual configuration (e.g. RemoveOldSignatures) are not present in the new documentation...
v68 Jérôme Charaoui
service/email: rewrite dkim procedure for puppet setup (tpo/tpa/team#40989)
v67 Antoine Beaupré
moar docs
v66 Antoine Beaupré
document our DMARC policy
v65 Antoine Beaupré
document the SPF setup
v64 Antoine Beaupré
note rate limiting on mail-tester.com (tpo/tpa/team#40990)
v63 Antoine Beaupré
more hacks for eugeni (tpo/tpa/team#40988)
v62 Antoine Beaupré
add OpenDKIM setup procedure used on submit-01 (tpo/tpa/team#40988)
v61 Antoine Beaupré
start jotting down notes about email services Currently only the base template, unchanged, but i want to brain dump stuff i find along the way in tpo/tpa/team#40986
v60 Antoine Beaupré
service template: describe the Reference section a bit more broadly
v59 Antoine Beaupré
service template: add a section about upgrades
v58 Antoine Beaupré
service template: reorganise monitoring/metrics/tests/logs Logs and metrics don't really go together, metrics are part of monitoring. And testing doesn't go with monitoring, at least not directly: we're talking about unit tests and things like that here, basically "how do you tell this still works", which *may* be "just look at monitoring", but is usually not.
v57 Antoine Beaupré
service template: split maintainers/users/upstreams section Those are really three completely different sections, and worth detailing properly. That way, there's also a tiny little chance the "maintainers" can be reused in some other table.
v56 Antoine Beaupré
service template: split the "Design" section Every time I document a service, I end up splitting it up mostly like this, based on the comments that were present there. By making specific headings for each of those sections, we'll ensure this is filled up properly for next services. Previous services will need to catch up, of course...
v55 Antoine Beaupré
add an example issue label to the service template