TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0200
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 5e9ee9ce
REPLY: 3:640/1384 5e9ee77a
Hi Paul,

On 2020-04-21 22:26:53, you wrote to me:

 WV>> "bytes": So it could be anything, including "high ascii".

 WV>> When I look at the packets I receive, there are some with lower or
 WV>> even mixed case passwords. (So it's a good thing FMail does a case
 WV>> insensitive compare, otherwise it wouldn't match against the
 WV>> configured uppercase password)

 PQ> This has been unsteady 'ground' for me.  What is FMail doing when it's
 PQ> coding the forced uppercase, after having potential mixedcase entered in
 PQ> the setup?

You can't enter mixed or lowercase into the configuration program, only
uppercase. And when someone updates the packet password through areafix it's
converted to uppercase before storing in the configuration file. So on
outgoing packet files the packet password is always uppercase only.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 18/200 90/1 103/705 120/340 601 154/10 203/0 221/0
SEEN-BY: 226/30 227/114 229/426 1014 240/5832 249/206 317 280/464
SEEN-BY: 280/5003 288/100 292/854 8125 310/31 317/3 322/757 342/200
SEEN-BY: 396/45 423/120 633/280 712/848 770/1
PATH: 280/464 229/426