On 4/4/2013 5:42 μμ, Wietse Venema wrote:
How long is your expected downtime? Even it someone receives only
one email per week, they should expire in 24 days.
It will be around 5-6 hours. I would like to avoid the gateway server
bouncing mails due to not being able to verify the recipients.
Ideally, mails should be accepted by the gateway server based on its
verify cache, and then kept in the queue during the main server downtime
period.
One solution would be to delete the verify_cache.db file NOW and thus
force the creation of a new one, so that any positive cached address
will be added and be valid for at least 7 days (provided that the
downtime will occur in the next 7 days); the only drawback - I think -
is that some addresses may not be used until the downtime occurs, so
they will be missing from the verify cache when the downtime occurs.
One way to solve this would be to send one mail to all our users, so
that they will be added to the verify cache. However there are multiple
addresses per user (due to aliases, so this complicates things a bit).
If we use a group alias like all-st...@example.com as a recipient
address, does that cause all of the true recipient addresses (that the
alias resolves to) to be added to the verify cache as well?
Or, can we manually add addresses to the verify cache?
Alternatively, we could switch to ldap-based verification during this
period - but I would like to avoid doing serious changes under pressure.
Thanks,
Nick
