thanks for the hint on gmailapi
i figure they had something outlook has an azure server plugin (same idea)
just an fyi i was taking a more generalized approach to the issue
as an isp i have customers spanning several different providers needing
a more generalized solution.
gmail, office, rogers, aol, yahoo etc etc etc
i generally use fetchmail to handle this but there is no oauth2
avaliable yet and you still need a device key - aka manual setup
I am putting together a python program to handle this the main issue is
getting prompted backwards in html on a new device / connection and
busilding some sort of connect library per provider.
Afterwhich i save the device key in a local database for future use?
Happy Thursday !!!
Thanks - paul
Paul Kudla
Scom.ca Internet Services <http://www.scom.ca>
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3
Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca
On 5/31/2022 4:31 PM, Dev femibadmus wrote:
i have solved my issue using the gmailapi anyone having same issue??
On Mon, May 30, 2022 at 2:57 PM Dev femibadmus <devfemibad...@gmail.com
<mailto:devfemibad...@gmail.com>> wrote:
Wow 😲 thanks 🙏 so much Paul
On Mon, May 30, 2022, 13:40 Paul Kudla (SCOM.CA <http://SCOM.CA>
Internet Services Inc.) <p...@scom.ca <mailto:p...@scom.ca>> wrote:
Unfortunately gmail / outlook although on different time tables
will
force oauth2 shortly without end users being able to avoid this.
Thus outlook protocol will not really be an option.
I have researched this with python and alike.
right now there does not seem to be any turn key soultions in
python or
fetchmail (i use fetchmail for my older customers)
there seems to be lib's around to handle to oauth2 protocols but
not
much doc's on how to use them?
simply put from my research to date is oauth2 does the following
1. you try to connect to the mail server
2. it stops (unless you already have a device id key) and
redirects to a
website link for a key
3. once on the website you need to say yes to some kind of auth
(trying
to accomodate with http libs)
4. the website returns the key (which you probably should save)
5. from there (thus far research to date) normal python libs
will handle
emails thereafter as before.
other option is like with google where you need to signup for a
developer account (or something) that will generate a key for your
account & device at which point other emails to that, only good
for 15
devices ??
after that you have to pay?
just a heads up, other non-main stream providers (like myself) have
other devices in place for security and will not force customers to
migrate, maybe look for a local provider?
I will eventually handle oauth2 etc but only when forced to
(government
contracts etc)
My suggestion (if you are in unix) is to start up a postfix /
dovecot
email server instance where you are in control of the protocol's
used?
this way your in complete control of your emails in both
directions. Its
a bit of work but leaving things to the main stream providers isn't
Happy Monday !!!
Thanks - paul
Paul Kudla
Scom.ca Internet Services <http://www.scom.ca <http://www.scom.ca>>
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3
Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca <mailto:p...@scom.ca>
On 5/30/2022 7:22 AM, Dev femibadmus wrote:
> *Google* no longer support less seureapps............what next?
> is there anyway we can use gmail for Django email?
>
>
> if no way please send the best lesson for *Outlook*
configuration :)
>
> --
> You received this message because you are subscribed to the
Google
> Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from
it, send
> an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users%2bunsubscr...@googlegroups.com>
> <mailto:django-users+unsubscr...@googlegroups.com
<mailto:django-users%2bunsubscr...@googlegroups.com>>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/django-users/5318be25-e226-489d-8586-155d9161dad5n%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/5318be25-e226-489d-8586-155d9161dad5n%40googlegroups.com>
>
<https://groups.google.com/d/msgid/django-users/5318be25-e226-489d-8586-155d9161dad5n%40googlegroups.com?utm_medium=email&utm_source=footer
<https://groups.google.com/d/msgid/django-users/5318be25-e226-489d-8586-155d9161dad5n%40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner*
<http://www.mailscanner.info/ <http://www.mailscanner.info/>>,
and is
> believed to be clean.
--
You received this message because you are subscribed to the
Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users%2bunsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/d3029493-4b38-903f-11f5-e5709cac9666%40scom.ca
<https://groups.google.com/d/msgid/django-users/d3029493-4b38-903f-11f5-e5709cac9666%40scom.ca>.
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to django-users+unsubscr...@googlegroups.com
<mailto:django-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/CAD9bWYxd1HjeR_sX8Nn0D4RhBkSDt3BXO47RQJaMSTOg7JiHjg%40mail.gmail.com
<https://groups.google.com/d/msgid/django-users/CAD9bWYxd1HjeR_sX8Nn0D4RhBkSDt3BXO47RQJaMSTOg7JiHjg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/42575a71-d344-d095-fc9d-4678ec96177e%40scom.ca.
