#31758 closed task (fixed)

upgrade postfix configurations to stretch/buster

Reported by: anarcat Owned by: anarcat
Priority: High Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Major Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


our postfix configuration as delivered by puppet is pretty old, probably pre-stretch. it's generally not a problem until some upgrade breaks certain assertions. buster seems to have at least broken one, as described in #31743, so it seems it would be a good idea to upgrade our configs everywhere.

first I'll look on all hosts to see if we have this problem elsewhere and then I'll cleanup the configs to port to the brave new world...

Child Tickets

Change History (2)

comment:1 Changed 15 months ago by anarcat

Owner: changed from tpa to anarcat
Status: newassigned

Looking for the magic string (bad command startup -- throttling) in logs:

cumin  -p 0 -b 10 -o txt  '*' 'grep "bad command startup -- throttling" /var/log/mail.log'

also yields a match on rouyi and perdulce, so i'll head there next for a hotfix.

comment:2 Changed 15 months ago by anarcat

Resolution: fixed
Status: assignedclosed

fix on rouyi, perdulce and carinatum. i deployed the changes to postfix everywhere with puppet after a test with eugeni.

i think this is mostly fixed now, although we still need to enabled postlogd in buster, but that's incompatible with stretch, unfortunately. this can be fixed when we add a postfix_version fact or when we upgrade all to buster. since things seem to be working fine without it, i prefer the latter.

Note: See TracTickets for help on using tickets.