

when I started v2 with fresh account it worked right away but I didn't verified via cli if sync was done I'm only saying if it was it was very quick why sync is required in v3 but not in v2, i.e.



Sync (vkuznet): 91.9% (Elapsed: 4035.4s, ETA: 358.0s)ĮRRO Failed to parse address error="mismatched input ':' expecting " Sync (vkuznet): 91.5% (Elapsed: 3989.5s, ETA: 369.8s)ĮRRO Get "": net/http: timeout awaiting response headers, Attempt 1ĮRRO Failed to parse address error="no viable alternative at input 'ariza '" Sync (vkuznet): 91.4% (Elapsed: 3983.7s, ETA: 377.2s)ĮRRO Failed to parse address error="no viable alternative at input 'todor '" So far I'm downgrading the proton bridge to previous version to avoid this issue. For instance, if email is fetch by one client and is fetched by another later its flag are not properly reset. I think either cache or concurrency fetching is an issue here. V3.0.20 Context (Environment) Detailed Description Please note, that in previous version of bridge this issue was never pop-up. mutt, and fetch your email, then delete your recently fetched email, repeat step 3 and your email will be fetched again.
