Dilemma -- to re-release 3.2.2 or release 3.2.3?

Last night, I posted the files for version 3.2.2 to fix some issues reported by Thomas in Germany.  The tests I ran worked just fine.

Today, however, I looked more closely at log files and found that AT&T SMTP software violates RFC 6152.  Specifically, it responds with “250-8 BITMIME” instead of “250-8BITMIME”.  Note that the server’s response has a space character between ‘8’ and “BITMIME”, contrary to RFC 6152.

What I did today was to change the source to accept “250-8 BITMIME” as if it were “250-8BITMIME”.  I also made a small change to output UTF-7 codes instead of UTF-8 if the server does not indicate “250-BINARYMIME” or “250-8BITMIME”.

So, here’s the question to the group – do I re-release version 3.2.2 with this small change, or do I release version 3.2.3?

-- 
Chip