| 199 | |
| 200 | == Apple Attachments options == |
| 201 | |
| 202 | === binhex === |
| 203 | |
| 204 | The !BinHex encoding format is deprecated (in favor of !AppleDouble MIME, see RFC 1740), but some older clients might still be using it. A file encoded with !BinHex is annoying to decode unless you are on a Mac. |
| 205 | |
| 206 | The binhex option can be set to one of: |
| 207 | * 'keep', in which case attachments encoded with !BinHex will be included in the ticket |
| 208 | * 'warn', in which case attachments encoded with !BinHex will be ignored, but a warning message to that effect will be included in the ticket description |
| 209 | * 'drop', in which case attachments encoded with !BinHex will be silently ignored |
| 210 | |
| 211 | The default is 'warn'. |
| 212 | |
| 213 | === applesingle === |
| 214 | |
| 215 | Same options and meaning as for binhex option above. |
| 216 | |
| 217 | === appledouble === |
| 218 | |
| 219 | The !AppleDouble encoding format is the recommended way to include Mac-specific data in a MIME message, as per RFC 1740. A file encoded with !AppleDouble can easily be presented usefully on all platforms. |
| 220 | |
| 221 | The applesingle option can be set to one of: |
| 222 | * 'keep', in which case both the platform-neutral data and the Mac-specific data will be included in the ticket (as two separate attachments) |
| 223 | * 'warn', in which case only the platform-neutral file data will be included in the ticket. Mac-specific data will be left out, but a warning message will be included in the ticket description. |
| 224 | * 'strip', in which case only the platform-neutral file data will be included in the ticket. Mac-specific data will be left out with no warning. |
| 225 | |
| 226 | The default is 'warn'. |