On Wed, Jul 13, 2022 at 10:15:47PM +0100, Sabahattin Gucukoglu wrote:
(Minor quibble, but I get a spurious warning about passwords being sent
in clear text where AuthMechs=LOGIN even across a tunnel, that doesn’t
apply to AUTH=PLAIN.)
that's another reason why you should try master. ;)
(thou
On 13 Jul 2022, at 21:13, Oswald Buddenhagen wrote:
> On Wed, Jul 13, 2022 at 08:27:36PM +0100, Sabahattin Gucukoglu wrote:
>> * OK [CAPABILITY XAPPLEPUSHSERVICE IMAP4 IMAP4rev1 SASL-IR AUTH=ATOKEN
>> AUTH=PLAIN] (2218B35-28881d7dd77f) ms11p00im-qufv17101001.me.com
>> Logging in...
>> Authenticat
On Wed, Jul 13, 2022 at 08:27:36PM +0100, Sabahattin Gucukoglu wrote:
* OK [CAPABILITY XAPPLEPUSHSERVICE IMAP4 IMAP4rev1 SASL-IR AUTH=ATOKEN
AUTH=PLAIN] (2218B35-28881d7dd77f) ms11p00im-qufv17101001.me.com
Logging in...
Authenticating with SASL mechanism PLAIN...
1 AUTHENTICATE PLAIN
1 OK use
On 5 Jul 2022, at 12:51, Oswald Buddenhagen wrote:
> On Tue, Jul 05, 2022 at 12:21:19PM +0100, Sabahattin Gucukoglu wrote:
>> Sadly the banner of imap.mail.me.com:993 changed.
>
> damn. mind posting the current -Dn output of the auth sequence?
sgucukoglu@Onyx:~$ mbsync -DN -a -l
Reading configur
On Tue, Jul 05, 2022 at 12:21:19PM +0100, Sabahattin Gucukoglu wrote:
Sadly the banner of imap.mail.me.com:993 changed.
damn. mind posting the current -Dn output of the auth sequence?
You could just target all IPv4 addresses in 17.0.0.0/8.
that seems suboptimal, as there are certainly other
On 20 May 2022, at 13:16, Oswald Buddenhagen wrote:
> On Thu, May 19, 2022 at 11:16:45PM +0100, Sabahattin Gucukoglu wrote:
>> On 17 May 2022, at 09:56, Oswald Buddenhagen
>> wrote:
>>> does the weirdness persist?
>>
>> Yes. Sending a single CAPABILITY request immediately after login to iCloud
On Thu, May 19, 2022 at 11:16:45PM +0100, Sabahattin Gucukoglu wrote:
On 17 May 2022, at 09:56, Oswald Buddenhagen
wrote:
does the weirdness persist?
Yes. Sending a single CAPABILITY request immediately after login to iCloud IMAP
is all that’s required to make their proxy transparent again.
On Thu, May 19, 2022 at 11:16:45PM +0100, Sabahattin Gucukoglu wrote:
On 17 May 2022, at 09:56, Oswald Buddenhagen
wrote:
does the weirdness persist?
Yes. Sending a single CAPABILITY request immediately after login to iCloud IMAP
is all that’s required to make their proxy transparent again.
Apologies for sluggishness.
On 17 May 2022, at 09:56, Oswald Buddenhagen wrote:
> does the weirdness persist?
Yes. Sending a single CAPABILITY request immediately after login to iCloud IMAP
is all that’s required to make their proxy transparent again.
Cheers,
Sabahattin
moin,
sorry for dropping the ball.
does the weirdness persist?
On Sat, Jul 24, 2021 at 04:00:25PM +0100, Sabahattin Gucukoglu via isync-devel
wrote:
On 22 Jul 2021, at 21:55, Oswald Buddenhagen wrote:
On Thu, Jul 22, 2021 at 08:20:04PM +0100, Sabahattin Gucukoglu via isync-devel
wrote:
Wit
On 22 Jul 2021, at 21:55, Oswald Buddenhagen wrote:
> On Thu, Jul 22, 2021 at 08:20:04PM +0100, Sabahattin Gucukoglu via
> isync-devel wrote:
>> Without the workaround script below, CAPABILITY is never issued by mbsync,
>> therefore the bodging is still in effect and I got bogus response [...]
>
On Thu, Jul 22, 2021 at 08:20:04PM +0100, Sabahattin Gucukoglu via isync-devel
wrote:
Without the workaround script below, CAPABILITY is never issued by
mbsync, therefore the bodging is still in effect and I got bogus
response [...]
ok, from what i gather the short version is that that proxy
On 18 Jul 2021, at 00:03, Oswald Buddenhagen wrote:
> On Sat, Jul 17, 2021 at 09:56:55PM +0100, Sabahattin Gucukoglu via
> isync-devel wrote:
>> Anyway the problem goes away and literal payloads all have the right sizes,
>> and sync completes successfully, if I write a little wrapper script that
On Sat, Jul 17, 2021 at 09:56:55PM +0100, Sabahattin Gucukoglu via isync-devel
wrote:
Anyway the problem goes away and literal payloads all have the right
sizes, and sync completes successfully, if I write a little wrapper
script that just adds a CAPABILITY request immediately after login.
wo
God knows why, but iCloud IMAP (imaps://imap.mail.me.com:993) bodges responses
(even lines within literals) so that every occurrence of CAPABILITY is
immediately followed by XAPPLEPUSHSERVICE, and STARTTLS preceded by a space
character is discarded. I can only assume it’s some side-effect of try
15 matches
Mail list logo
