From: Patrick B. K. <p...@st...> - 2011-01-19 21:06:40
|
Mark, * Mark Martinec <Mar...@ij...>: > > have you ever considered adding a failover or fallback mechanism for > > $archive_quarantine_method? > > > > I use amavis with Postfix smtpd_proxy_filter and my Postfix instance comes > > to an instant halt, if the smtp target defined in > > $archive_quarantine_method becomes unavailable. > > It may need some cleaning, but with 2.7.0-pre12 you may provide a > failover server for any *_method which uses an smtp or lmtp protocol. that's good news! > A limitation is that all alternatives must use the same protocol > (e.g. you can't mix a 'local:' with 'smtp:' in the same list). That's also fine in my case. > For example: > > $archive_quarantine_method = > [ 'smtp:[::1]:20025', 'smtp:[10.0.0.10]:10025' ]; > > @archive_quarantine_to_maps = ( 'qua...@ex...' ); > > > Could amavis have a configurable option to "reject", "tempfail" or "pass" a > > connect if a smtp target for $archive_quarantine_method becomes > > unavailable? > > I'm not inclined to such solution. Either you need an archive, in which case > it is best for the mail flow to halt during times when a service can't be > ensured. If you don't need an archive, then don't request one. You say best. My customer disagrees. From their point of view mail service availabilty has a higher priority than mail archiving. > An alternative may be to use always_bcc or its brothers at the MTA level. We've used $archive_quarantine_method and a load balancer as target. A smtp-sink serves as last resort if all other servers are gone. In such a scenario mail ultimately will be lost if the sink gets into the game, but the mail service itself will remain available. p@rick -- All technical questions asked privately will be automatically answered on the list and archived for public access unless privacy is explicitely required and justified. saslfinger (debugging SMTP AUTH): <http://postfix.state-of-mind.de/patrick.koetter/saslfinger/> |