On Sat, 6 Feb 2010, Simon Horman <ho...@verge.net.au> wrote: > POP3 capabilities can include spaces. Or more specifically > the capability may be followed by a space-delimited list of > parameters. So rather than use a space to delimit capabilities, > two spaces is used. > > So ---pop_capability "USER UIDL" works as expected. > But ---pop_capability "USER UIDL" does not. Which seems > to be all-together too subtle.
Are there any characters that can't occur in a POP capability such as a comma that can be used? Another possibility would be to have "\ " for a literal space in a capability. > An idea that I had was to allow multiple ---pop_capability arguments > to be provided. > > e.g. ---pop_capability "USER" ---pop_capability "UIDL" That would be ugly but would work. > Another option, which is simpler from a coding point of view, > would be to use . as the delimiter for POP3 capabilities. As "." > is excluded from being used in capabilities (though perhaps not > parameters). > > e.g. ---pop_capability "USER.UIDL.LOGIN-DELAY 900" That seems good to me. > BTW, are you really using POP3 capabilities? I've got 10,000 users from all around the world. I have no idea what their MUAs do or expect from my servers. So it's best to just have things work according to the specs to avoid corner case bug reports. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
