hi, Regarding the upgrade path, I'm in favor of requiring an empty mailQueue. > To achieve that, downtime on the SMTP service + MailQueue flush. > > Would it be resonable to people around here? >
I don't claim to understand the breadth of the issue here and I know enough of java serialization to understand the concern. With that said, If I were operating a james server in production and was told that starting with the next version I will have to choose between "downtime on the SMTP service + MailQueue flush." or bug fixes, I would not be happy. What are the risks of losing production emails with such a migration path ? If there are risks, shouldn't we ask the james-user list and overall community to know if people actually use the affected components in production deployments and confirm with them that downtime would be acceptable for improved security ? -- Jean
