Looks like MS is requiring oauth2 or similar from next week. Looks
like smtpmail has a potential workaround for this and there seems to
be an enhancement for sasl to deal with it. Has anyone got this to
work with the exchange server remaining as the remote spool file or is
it recommended to switch
Uday Reddy writes on Fri 15 Oct 2021 15:49:
> By the "launchpad version", I mean the trunk or "development version". You
> need to access the latest revision, e.g.,
>
> https://bazaar.launchpad.net/~vm/vm/trunk/revision/1538?start_revid=1538
>
> and you can download the tarball from
By the "launchpad version", I mean the trunk or "development version". You
need to access the latest revision, e.g.,
https://bazaar.launchpad.net/~vm/vm/trunk/revision/1538?start_revid=1538
and you can download the tarball from there.
The only difference between this and a public release is
alain.coch...@unistra.fr writes:
> It seems like VM tries to reintroduce a 2-character-long string. For
> example if I use 4 characters, it becomes like this:
>
> 73 alain.coch...@unistra.fr Mon 11 Oct 2021 18:40 test png
>74 D R AmelieMon 11 Oct 2021 19:11
