On December 28, 2022 1:49:16 PM EST, "Mario Župan" <mzu...@ftrr.hr> wrote: >Negative. > >I also had a need to download all my mails from office365 domain with >zero help of an admin. We moved to another office365 domain which I >wanted to read with aerc. > >So, I will try just to give you an overview: > >#1 GPG > >gpg --full-generate-key > >gpg --sign-key "mzupan mzu...@vup.hr<mailto:mzu...@vup.hr>" > >gpg --output ./Documents/manual/email-terminal/vup-token --armor >--export "mzupan <mzu...@vup.hr<mailto:mzu...@vup.hr>" > > >#2 use mutt_ouath2.py script > >python ./Documents/manual/email-terminal/mutt_oauth2.py >./Documents/manual/email-terminal/vup-token --verbose --authorize > >#3 in mutt_ouath2.py you need just to change the next row: > >ENCRYPTION_PIPE = ['gpg', '--encrypt', '--recipient', 'mario ><mzu...@vup.hr<mailto:mzu...@vup.hr>>' > > > ># then in .mbsyncrc you need todo this: > > >#### >... > >IMAPAccount vup >Host outlook.office365.com<http://outlook.office365.com/> >User mzu...@vup.hr<mailto:mzu...@vup.hr> >AuthMechs XOAUTH2 >PassCmd "python ~/Documents/manual/email-terminal/mutt_oauth2.py >~/Documents/manual/email-terminal/vup-token" >CertificateFile /etc/ssl/certs/ca-certificates.crt >TLSType IMAPS > >... > >#### > >Other lines are the same for every account. I hope I make the process >understandable. > >Best, > >Mario Zupan >________________________________ >Šalje: H <age...@meddatainc.com> >Poslano: 26. prosinca 2022. 16:52 >Kopija: Isync Mailing List <isync-devel@lists.sourceforge.net> >Predmet: Re: Logging in to O365 account > >On December 26, 2022 2:39:56 AM EST, Bence Ferdinandy ><be...@ferdinandy.com> wrote: >>2022. dec. 26. 3:08:32 H <age...@meddatainc.com>: >> >>> The TENANT_ID is available on the portal.azure.com page when logged >>in, >>> registering an app to get the CLIENT_ID is locked down. I don't see >>any >>> upside for the organization to provide a CLIENT_ID, only a potential >>> security risk, so I do not see that happening. >> >>For the client id, I suggest you use this: >>https://github.com/ferdinandyb/dotfiles/blob/master/.config/emailconfiguration/mutt_oauth2.py#L77 >> >>you will find that it's a rather well known application and thus will >>likely be already authorized. >> >>Besr, >>Bence > >Thank you. Does this require someone has already gotten mutt registered >as an application on my organization's O365 site? > > >_______________________________________________ >isync-devel mailing list >isync-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/isync-devel
Thank you, will try this! What is the reason for generating the gpg key? I have not seen this in other write-ups? _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
