Bugzilla

This fixes the append problem.  If utf8=accept is enabled, it adds the parenthesis and the tilde in the same manner as the python patch pointed to in comment 58. Append to Sent folder now works OK with no alerts with Alessandro's and gmail server.
 
It also fixes another problem revealed after some email exchanges with Arnt Gulbrandsen (co-author of imap enable RFC and others too I think). He recommended that I go ahead and attempt the enable of utf8=accept if ENABLE capability is detected. If the server doesn't support utf8=accept you still get an OK response from the ENABLE command but you don't get the untagged
```
* ENABLED UTF8=ACCEPT
```
response. Before I wasn't even looking for this but just assumed that it worked if the ENABLE and UTF8=ACCEPT capabilities are both present and if OK tagged response occurs (which it always does unless you, for example, misspell ENABLE).

I also now set a flag accessible with m_imapServerSink-> and imapServer-> since there are several other places that utf8=accept needs to be known. Before I was just looking at capabilities and not whether it was really enabled at the server.

The .diff still contains some debug and printfs that need to be cleaned up. It also contain the changes for SMTPUTF8 from bug #1563891 that need to be taken out for this bug.

This fixes the append problem.  If utf8=accept is enabled, it adds the UTF8, parenthesis and the tilde in the same manner as the python patch pointed to in comment 58. Append to Sent folder now works OK with no alerts with Alessandro's and gmail server.
 
It also fixes another problem revealed after some email exchanges with Arnt Gulbrandsen (co-author of imap enable RFC and others too I think). He recommended that I go ahead and attempt the enable of utf8=accept if ENABLE capability is detected. If the server doesn't support utf8=accept you still get an OK response from the ENABLE command but you don't get the untagged
```
* ENABLED UTF8=ACCEPT
```
response. Before I wasn't even looking for this but just assumed that it worked if the ENABLE and UTF8=ACCEPT capabilities are both present and if OK tagged response occurs (which it always does unless you, for example, misspell ENABLE).

I also now set a flag accessible with m_imapServerSink-> and imapServer-> since there are several other places that utf8=accept needs to be known. Before I was just looking at capabilities and not whether it was really enabled at the server.

The .diff still contains some debug and printfs that need to be cleaned up. It also contain the changes for SMTPUTF8 from bug #1563891 that need to be taken out for this bug.