Re: Django email | Gmail | Outlook

[Abdul Qoyyuum]

There are other alternatives if you use Django-Anymail package. Go 
to https://anymail.dev/en/stable/ to see a list of supported 3rd party 
email services. Some have free limits for you to use. Good luck!

On Monday, May 30, 2022 at 7:22:38 PM UTC+8 devfem...@gmail.com wrote:

> *Google* no longer support less seureappswhat 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/7f261021-456f-49df-8d35-b1b4885c2a25n%40googlegroups.com.

Re: Django email | Gmail | Outlook

[Paul Kudla (SCOM.CA Internet Services Inc.)]

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 
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 > wrote:


Wow  thanks  so much Paul

On Mon, May 30, 2022, 13:40 Paul Kudla (SCOM.CA 
Internet Services Inc.) 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 >
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/30/2022 7:22 AM, Dev femibadmus wrote:
 > *Google* no longer support less seureappswhat 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

 > >.
 > To view this discussion on the web visit
 >

https://groups.google.com/d/msgid/django-users/5318be25-e226-489d-8586-155d9161dad5n%40googlegroups.com



 >

Re: Django email | Gmail | Outlook

[Dev femibadmus]

i have solved my issue using the gmailapi anyone having same issue??


On Mon, May 30, 2022 at 2:57 PM Dev femibadmus 
wrote:

> Wow  thanks  so much Paul
>
> On Mon, May 30, 2022, 13:40 Paul Kudla (SCOM.CA Internet Services Inc.) <
> 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 
>> 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/30/2022 7:22 AM, Dev femibadmus wrote:
>> > *Google* no longer support less seureappswhat 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
>> > .
>> > 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?utm_medium=email_source=footer
>> >.
>> >
>> > --
>> > This message has been scanned for viruses and
>> > dangerous content by *MailScanner* , 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/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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAD9bWYxd1HjeR_sX8Nn0D4RhBkSDt3BXO47RQJaMSTOg7JiHjg%40mail.gmail.com.

Re: Django email | Gmail | Outlook

[Dev femibadmus]

Wow  thanks  so much Paul

On Mon, May 30, 2022, 13:40 Paul Kudla (SCOM.CA Internet Services Inc.) <
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 
> 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/30/2022 7:22 AM, Dev femibadmus wrote:
> > *Google* no longer support less seureappswhat 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
> > .
> > 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?utm_medium=email_source=footer
> >.
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by *MailScanner* , 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/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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAD9bWYx4UXjMC2j-rH6QdOXUry7vxedeGsZW2s%3DJy7rUaE%3DHsw%40mail.gmail.com.

Re: Django email | Gmail | Outlook

[Paul Kudla (SCOM.CA Internet Services Inc.)]

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 
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/30/2022 7:22 AM, Dev femibadmus wrote:

*Google* no longer support less seureappswhat 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 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/5318be25-e226-489d-8586-155d9161dad5n%40googlegroups.com 
.


--
This message has been scanned for viruses and
dangerous content by *MailScanner* , 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/d3029493-4b38-903f-11f5-e5709cac9666%40scom.ca.

Re: Django Email Model

[ludovic coues]

https://docs.djangoproject.com/en/1.9/topics/db/examples/many_to_many/

Each student can subscribe to more than one newsletter
Each newsletter have many of students.




2016-07-21 15:20 GMT+02:00 Ant :
> Being a Django "newcomer" I am hoping someone can help us with this simple
> problem.
>
> We have a model for students containing names and email addresses. We want
> them to subscribe to various newsletters.
>
> Is it better to have a separate model for newsletters and how would we
> produce the list for these subscribers.
>
> I have read other posts on this subject but am still somewhat confused!
>
> Any help would be greatly appreciated.
>
> Thanks
>
> --
> 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 post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/6c79fe60-559b-47cd-9613-168262edf517%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 

Cordialement, Coues Ludovic
+336 148 743 42

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAEuG%2BTZC_sbG%2BmyXyx581K43SQPDfnsz0vWutu4p2HQLDCK3zA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: django email client (reusable app) kickstarter

[Internet Profil Filip Kowalski]

You are right, we will provide support for all db backends. Extra 
functionality that is fully possible only with Postgres (e.g. use of 
GeoDjango) will require that backend. Core features mentioned in 
kickstarter description will work everywhere.


Filip Kowalski
Internet Profil
www.internetprofil.pl 
mob. 506 385 326
tel. 58 661 11 62
skype: easy-r1der
ul. Śląska 53
81-304 Gdynia
VAT EU: PL586-203-45-48
W dniu 2014-10-13 o 18:13, Scot Hacker pisze:



On Monday, October 13, 2014 4:18:52 AM UTC-7, biuro wrote:



perhaps I run out too far in the future and this should be put on
a different database.
what do you think guys?


I think that database independence is a core feature of Django and of 
virtually every reusable app. Your project is designed (I assume) to 
be integrated into existing Django projects. By tying yourself to one 
database, your app is not being a good Django community citizen, and 
will be unusable by hundreds of thousands of existing Django projects 
that don't use postgres.


If you find down the line that your app absolutely must have some 
pg-specific features, I recommend making those into *optional* 
features that can be enabled for qualifying users.


./s

--
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 post to this group, send email to django-users@googlegroups.com 
.

Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1f8d0f7f-9e61-4fb4-ad7b-c5684cfab833%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/543D9E8A.8060009%40internetprofil.pl.
For more options, visit https://groups.google.com/d/optout.

Re: django email client (reusable app) kickstarter

[Scot Hacker]

On Monday, October 13, 2014 4:18:52 AM UTC-7, biuro wrote:
>
>  
>
> perhaps I run out too far in the future and this should be put on a 
> different database. 
> what do you think guys?
>

I think that database independence is a core feature of Django and of 
virtually every reusable app. Your project is designed (I assume) to be 
integrated into existing Django projects. By tying yourself to one 
database, your app is not being a good Django community citizen, and will 
be unusable by hundreds of thousands of existing Django projects that don't 
use postgres. 

If you find down the line that your app absolutely must have some 
pg-specific features, I recommend making those into *optional* features 
that can be enabled for qualifying users.

./s

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/1f8d0f7f-9e61-4fb4-ad7b-c5684cfab833%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django email client (reusable app) kickstarter

[Internet Profil Filip Kowalski]

This project is a reusable app and license MIT

I do not know and I'm not sure to which projects will be used in the future

but

I assume that the imagination of people is very large so even to this 
reason we prefer to give a database that gives you a lot more possibilities


and the first example of what comes to my mind is that if someone wanted 
to combine email client with a calendar of events, and events associated 
with places around the world, the very useful geolocation, and there is 
no better solution for geolocation as PostgreSQL.


perhaps I run out too far in the future and this should be put on a 
different database.

what do you think guys?

Filip Kowalski
Internet Profil
www.internetprofil.pl 
mob. 506 385 326
tel. 58 661 11 62
skype: easy-r1der
ul. Śląska 53
81-304 Gdynia
VAT EU: PL586-203-45-48
W dniu 2014-10-08 o 22:16, Subodh Nijsure pisze:


Why does it need to have dependence  on specific database postgres?

Subodh

On Oct 8, 2014 5:43 AM, "Internet Profil Filip Kowalski" 
> wrote:


Hi,

I have started kickstarter campaign:

https://www.kickstarter.com/projects/112336300/open-source-email-client-based-on-python-and-djang

The aim is to create an email client based on Python/Django which
would be shared as open source.
It would be easy to implement in projects and simple to develop
(re-usable app).

It would also:

Be supported by Django>=1.6 and Python 2>=2.6 and Python 3>=3.3.

Use PostgreSQL and Elasticsearch.

Only support IMAP and use Imapclient (created by developers of
Mozilla) which is currently the most stable library available.

Use SSE (Server-sent events) for all notifications from the server.

Have good documentation and clean, understandable code for easy
implementation and further development.

Be provided with templates that are based on bootstrap 3.0.

The amount we are trying to raise - $7000- will go towards at
least 320 hours of work on the project.

10% of all funds raised over the target will be donated to the DSF
(Django Software Foundation).

More information, mockups, production and fulfillment plan you can
find at kickstarter project page.



Thank you for your help, both in helping to publish information
via fb / twitter accounts and for direct support.
-- 
Filip Kowalski

Internet Profil
www.internetprofil.pl 
mob. 506 385 326
tel. 58 661 11 62
skype: easy-r1der
ul. Śląska 53
81-304 Gdynia
VAT EU: PL586-203-45-48
-- 
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 post to this group, send email to django-users@googlegroups.com
.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit

https://groups.google.com/d/msgid/django-users/54352F68.6020500%40internetprofil.pl

.
For more options, visit https://groups.google.com/d/optout.

--
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 post to this group, send email to django-users@googlegroups.com 
.

Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CALr9Q3Z-GKTTOUMLU5QPUrt0k3CTyhhExEZ3A147-8%2BDXBB%2Bxg%40mail.gmail.com 
.

For more options, visit https://groups.google.com/d/optout.


--
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/543BA49F.60205%40internetprofil.pl.
For more options, visit https://groups.google.com/d/optout.

Re: django email client (reusable app) kickstarter

[Subodh Nijsure]

Why does it need to have dependence  on specific database postgres?

Subodh
On Oct 8, 2014 5:43 AM, "Internet Profil Filip Kowalski" <
bi...@internetprofil.pl> wrote:

>  Hi,
>
> I have started kickstarter campaign:
> https://www.kickstarter.com/projects/112336300/open-source-email-client-based-on-python-and-djang
>
> The aim is to create an email client based on Python/Django which would be
> shared as open source.
> It would be easy to implement in projects and simple to develop (re-usable
> app).
>
> It would also:
>
> Be supported by Django>=1.6 and Python 2>=2.6 and Python 3>=3.3.
>
> Use PostgreSQL and Elasticsearch.
>
> Only support IMAP and use Imapclient (created by developers of Mozilla)
> which is currently the most stable library available.
>
> Use SSE (Server-sent events) for all notifications from the server.
>
> Have good documentation and clean, understandable code for easy
> implementation and further development.
>
> Be provided with templates that are based on bootstrap 3.0.
>
> The amount we are trying to raise - $7000- will go towards at least 320
> hours of work on the project.
>
> 10% of all funds raised over the target will be donated to the DSF (Django
> Software Foundation).
>
> More information, mockups, production and fulfillment plan you can find at
> kickstarter project page.
>
>
>
> Thank you for your help, both in helping to publish information via fb /
> twitter accounts and for direct support.
> --
> Filip Kowalski
> Internet Profil
> www.internetprofil.pl
> mob. 506 385 326
> tel. 58 661 11 62
> skype: easy-r1der
> ul. Śląska 53
> 81-304 Gdynia
> VAT EU: PL586-203-45-48
>
> --
> 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 post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/54352F68.6020500%40internetprofil.pl
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CALr9Q3Z-GKTTOUMLU5QPUrt0k3CTyhhExEZ3A147-8%2BDXBB%2Bxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django Email

[Shawn Milochik]

http://docs.djangoproject.com/en/dev/topics/email/#the-emailmessage-class

http://docs.djangoproject.com/en/dev/topics/email/#sending-multiple-e-mails


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Email

[Tom Evans]

On Fri, Jan 21, 2011 at 3:28 PM, hank23  wrote:
> OK what exactly is django-mailer?
>

http://lmgtfy.com/?q=django-mailer

HTH

Tom

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Email

[Anurag Chourasia]

Googling for django-mailer gets me to this page

http://code.google.com/p/django-mailer/

Regards,
Anurag

On Fri, Jan 21, 2011 at 8:58 PM, hank23  wrote:

> OK what exactly is django-mailer?
>
> On Jan 19, 4:32 pm, Eduardo Cereto Carvalho 
> wrote:
> > django-mailer[1] is a nice application to have around if you're planning
> to
> > send too much emails. It queues messages and retry failled attempts.
> >
> > [1]
> >
> >
> >
> >
> >
> > On Wed, Jan 19, 2011 at 8:09 PM, Shawn Milochik 
> wrote:
> > > Whatever method you decide to use to gather the e-mail addresses is up
> to
> > > you, and depends on your needs.
> >
> > > The send_mail function accepts a list of recipients, and it doesn't
> really
> > > matter how you get them.
> >
> > > Two notes on sending e-mail, though:
> >
> > > 1. Ensure that you're sending the e-mail multiple times (once to each
> > > person) to ensure privacy. Unless, for some reason, it's fine that all
> > > recipients get the e-mail addresses of the others.
> >
> > > 2. SMTP communications are expensive, so you may want to go deeper than
> the
> > > send_mail function so you can create an SMTP connection and send
> multiple
> > > messages then include it. Otherwise you'll create a new SMTP connection
> for
> > > each message, which will take longer. Unless that's what you want.
> >
> > > Shawn
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Django users" group.
> > > To post to this group, send email to django-users@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > django-users+unsubscr...@googlegroups.com
> 
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/django-users?hl=en.
> >
> > --
> > Eduardo Cereto Carvalho- Hide quoted text -
> >
> > - Show quoted text -
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Email

[hank23]

OK what exactly is django-mailer?

On Jan 19, 4:32 pm, Eduardo Cereto Carvalho 
wrote:
> django-mailer[1] is a nice application to have around if you're planning to
> send too much emails. It queues messages and retry failled attempts.
>
> [1]
>
>
>
>
>
> On Wed, Jan 19, 2011 at 8:09 PM, Shawn Milochik  wrote:
> > Whatever method you decide to use to gather the e-mail addresses is up to
> > you, and depends on your needs.
>
> > The send_mail function accepts a list of recipients, and it doesn't really
> > matter how you get them.
>
> > Two notes on sending e-mail, though:
>
> > 1. Ensure that you're sending the e-mail multiple times (once to each
> > person) to ensure privacy. Unless, for some reason, it's fine that all
> > recipients get the e-mail addresses of the others.
>
> > 2. SMTP communications are expensive, so you may want to go deeper than the
> > send_mail function so you can create an SMTP connection and send multiple
> > messages then include it. Otherwise you'll create a new SMTP connection for
> > each message, which will take longer. Unless that's what you want.
>
> > Shawn
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django users" group.
> > To post to this group, send email to django-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > django-users+unsubscr...@googlegroups.com
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/django-users?hl=en.
>
> --
> Eduardo Cereto Carvalho- Hide quoted text -
>
> - Show quoted text -

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Email

[hank23]

OK. Any idea if there's a good django coding example somewhere showing
basic settings for sending email, how to setup the smtp connection so
I can use it to send multiple messages if desired, without having to
get a new connection for each message, etc.?

On Jan 19, 4:09 pm, Shawn Milochik  wrote:
> Whatever method you decide to use to gather the e-mail addresses is up
> to you, and depends on your needs.
>
> The send_mail function accepts a list of recipients, and it doesn't
> really matter how you get them.
>
> Two notes on sending e-mail, though:
>
> 1. Ensure that you're sending the e-mail multiple times (once to each
> person) to ensure privacy. Unless, for some reason, it's fine that all
> recipients get the e-mail addresses of the others.
>
> 2. SMTP communications are expensive, so you may want to go deeper than
> the send_mail function so you can create an SMTP connection and send
> multiple messages then include it. Otherwise you'll create a new SMTP
> connection for each message, which will take longer. Unless that's what
> you want.
>
> Shawn

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Email

[Eduardo Cereto Carvalho]

django-mailer[1] is a nice application to have around if you're planning to
send too much emails. It queues messages and retry failled attempts.

[1]

On Wed, Jan 19, 2011 at 8:09 PM, Shawn Milochik  wrote:

> Whatever method you decide to use to gather the e-mail addresses is up to
> you, and depends on your needs.
>
> The send_mail function accepts a list of recipients, and it doesn't really
> matter how you get them.
>
> Two notes on sending e-mail, though:
>
> 1. Ensure that you're sending the e-mail multiple times (once to each
> person) to ensure privacy. Unless, for some reason, it's fine that all
> recipients get the e-mail addresses of the others.
>
> 2. SMTP communications are expensive, so you may want to go deeper than the
> send_mail function so you can create an SMTP connection and send multiple
> messages then include it. Otherwise you'll create a new SMTP connection for
> each message, which will take longer. Unless that's what you want.
>
> Shawn
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>


-- 
Eduardo Cereto Carvalho

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django Email

[Shawn Milochik]

Whatever method you decide to use to gather the e-mail addresses is up 
to you, and depends on your needs.


The send_mail function accepts a list of recipients, and it doesn't 
really matter how you get them.


Two notes on sending e-mail, though:

1. Ensure that you're sending the e-mail multiple times (once to each 
person) to ensure privacy. Unless, for some reason, it's fine that all 
recipients get the e-mail addresses of the others.


2. SMTP communications are expensive, so you may want to go deeper than 
the send_mail function so you can create an SMTP connection and send 
multiple messages then include it. Otherwise you'll create a new SMTP 
connection for each message, which will take longer. Unless that's what 
you want.


Shawn

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django email and BCC recipients

[Adam Fast]

Julien,

Looking at the code you linked confirmed my suspicions - just like an
email in your favorite email client, you must include a 'to' field
when using BCCs.  The example linked is sending their message /to/
somewhere...and my suspicion is that is what is causing your messages
not to send.  Add a recipient of the sender_email and you should be
fine (yes, you will have to delete the messages from that account, but
BCCs will work.  Alternately, send a single message to each recipient,
then you don't need BCCs.

Adam


On Tue, May 13, 2008 at 1:16 AM, Julien <[EMAIL PROTECTED]> wrote:
>
>  Hi,
>
>  Apparently others have had trouble with the BCC attribute of the
>  Django email classes [1]. I also have a problem, but a bit different.
>  The 'to' recipients receive the email, but not the 'bcc' recipients.
>
>  Works:
> msg = EmailMultiAlternatives(subject, plain_body, sender_email,
>  recipients)
> msg.attach_alternative(html_body, "text/html")
> msg.send()
>
>  Doesn't work (executes without problem, but emails are never
>  received):
> msg = EmailMultiAlternatives(subject, plain_body, sender_email,
>  bcc=recipients)
> msg.attach_alternative(html_body, "text/html")
> msg.send()
>
>  I'm using today's version of Django: 0.97-pre-SVN-7523
>
>  Is that a bug or am I missing something?
>
>  Thanks a lot,
>
>  Julien
>
>  [1] 
> http://groups.google.com/group/django-users/browse_thread/thread/7067b4e6686290b4/dff9ff1258105130?lnk=gst=bcc#dff9ff1258105130
>  >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django Email Failure

[kidormb]

Andrey,

Thank you for your reply.  Your suggestion solved my problem along
with
correcting my mistake of not putting the to address in a list.

I don't know how I ever would have figured out that the
EMAIL_HOST_USER
and EMAIL_HOST_PASSWORD were not for sending and needed to be
commented
out.

Everything is working great at this time.

Thanks again for your help,

kidormb


On Oct 2, 4:38 pm, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
>  k> I am trying to use the send_email facility from django.core.mail with
>  k> the following
>  k> in my settings.py
>
>  k> EMAIL_HOST = 'smtp-server.cfl.rr.com'
>  k> EMAIL_PORT = '25'
>  k> EMAIL_HOST_USER = 'username'
>  k> EMAIL_HOST_PASSWORD = 'password'
>
>  k> I get the error message:
>
>  k> SMTP AUTH extension not supported by server.
>
>  k> I am sure the username and password are correct and am using
>  k> RoadRunner in the central Florida area:
>
> Are you sure that this login/password are for *sending*?  Try commenting
> out EMAIL_HOST_USER and EMAIL_HOST_PASSWORD.
>
> --
> Andrey V Khavryuchenko
> Django NewGate -  http://www.kds.com.ua/djiggit/
> Chytach -http://www.chytach.com/


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django Email Failure

[kidormb]

Thejaswi,

Thank you for your reply.  For the record I am using XUbuntu 7.04 and
the
subversion release of django.  My problem has been solved by another
responder.

Thanks again,

kidormb


On Oct 2, 3:46 am, Thejaswi Puthraya <[EMAIL PROTECTED]>
wrote:
> On Oct 2, 8:04 am, kidormb <[EMAIL PROTECTED]> wrote:
>
> > Thanks for the reply, but
>
> > SMTP AUTH extension not supported by server.
>
> > is the exact error message that I receive, which I think is
> > a python error.
>
> Have never come across this problem!!! Which version of Django do you
> use? Django 0.96 or from the subversion repository? Can you also give
> us some information about the OS you use...sometimes Windows XP
> firewall blocks port 25.
>
> Cheers
> Thejaswi Puthraya


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django Email Failure

[Andrey Khavryuchenko]

 k> I am trying to use the send_email facility from django.core.mail with
 k> the following
 k> in my settings.py

 k> EMAIL_HOST = 'smtp-server.cfl.rr.com'
 k> EMAIL_PORT = '25'
 k> EMAIL_HOST_USER = 'username'
 k> EMAIL_HOST_PASSWORD = 'password'

 k> I get the error message:

 k> SMTP AUTH extension not supported by server.

 k> I am sure the username and password are correct and am using
 k> RoadRunner in the central Florida area:

Are you sure that this login/password are for *sending*?  Try commenting
out EMAIL_HOST_USER and EMAIL_HOST_PASSWORD.


-- 
Andrey V Khavryuchenko
Django NewGate -  http://www.kds.com.ua/djiggit/
Chytach - http://www.chytach.com/

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django Email Failure

[Thejaswi Puthraya]

On Oct 2, 8:04 am, kidormb <[EMAIL PROTECTED]> wrote:
> Thanks for the reply, but
>
> SMTP AUTH extension not supported by server.
>
> is the exact error message that I receive, which I think is
> a python error.
>

Have never come across this problem!!! Which version of Django do you
use? Django 0.96 or from the subversion repository? Can you also give
us some information about the OS you use...sometimes Windows XP
firewall blocks port 25.

Cheers
Thejaswi Puthraya


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django Email Failure

[kidormb]

Thanks for the reply, but

SMTP AUTH extension not supported by server.

is the exact error message that I receive, which I think is
a python error.

Any ideas,

Thanks again



On Sep 30, 9:49 pm, Thejaswi Puthraya <[EMAIL PROTECTED]>
wrote:
> [snipped]
>
> > I get the error message:
>
> >   SMTP AUTH extension not supported by server.
>
> It would be helpful if you could post the exact error message.
>
> Cheers
> Thejaswi Puthraya


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django Email Failure

[Thejaswi Puthraya]

[snipped]
> I get the error message:
>
>   SMTP AUTH extension not supported by server.

It would be helpful if you could post the exact error message.

Cheers
Thejaswi Puthraya


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django email

[Reinhard Knobelspies]

For your requirements OpenEMM might be a better solution:
http://www.openemm.org/home.html .

Reinhard


--~--~-~--~~~---~--~~
 You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django email

[Jeremy Dunck]

On 12/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> We have been sending bulk mail (error logs) to gmail for the past few
> weeks, but it hasnt been working too well :)


We've run into some delivery problems w/ email, too.

Causes I've found so far:
  x SPF not configured
  x hostname wrong for reverse DNS -- I think this is either a bug in
python's email module or confusion about /etc/mailname :
http://wiki.debian.net/?EtcMailName
  x message id missing (new in django dev trunk)
  x recipient whitelisting (nothing to be done about that)
  x too many links in email.

Any other thoughts on causes?

--~--~-~--~~~---~--~~
 You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django email

[[EMAIL PROTECTED]]

We have been sending bulk mail (error logs) to gmail for the past few
weeks, but it hasnt been working too well :)

On that note though, I don't think the question is whether django can,
or should, handle something like that itself, as its not a CMS. You
will most likely need to build a mail app to distribute the emails in
chunks.

On Dec 12, 8:03 pm, "Ramdas S" <[EMAIL PROTECTED]> wrote:
> I am seriously getting a client to consider Django for a CRM web site of a
> client.
>
> Django templating language is the reason, since each campaign needs to be
> heavily customized from a database.
>
> Problem is they have a customer base of 100,000 registered users, and each
> campaign goes to a subset of these database which means a mailer campaign
> can run between 1000 and 70,000 users.
>
> Question is does Django's built-in mail component scale to handle such
> loads. Can we use it to send such huge volumes of emails in a single day?
> 
> Ramdas


--~--~-~--~~~---~--~~
 You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---