This is not strictly a DBMail question, but it is close. Lately I noticed that any time the SQL server needs to be restarted for some reason, DBMail starts having problems with inserting messages. Since the error message was changed to 450 from 503, this is not a big issue, as mail is not lost. Nevertheless I want to know if someone else had such problems and what steps if any were taken to solve them.
What about having an option to fallback to a temp-deliver-to-filesystem mode when the DB is temporarily unavailable (and then move messages from the filesystem to the DB when DB connectivity is restored)?
You could then have an option that if the DB is unavailable for longer than x minutes, *then* start temp failing delivery.
Just a thought... -- Best regards, Charles _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
