Do not respond to everyone with the same question. We see it once you respond
to somebody (mail is delivered to every subscriber of this group).
I already gave you a suggestion. It should be pretty easy to search "what is a
PTR record" and "how to set PTR record on $server_host" on your favorite
On May 16, 2017 11:24 PM, "Ismail Sarenkapic" wrote:
I already fixed the problem tnx.
but i still dont know why are my emails treated like potential fishing
content, can you help me with that?
There are potentially dozens of reasons for this. Some may be
Django-related,
Hi Ismail,
Thank you for your suggestion.
Will get it into consideration for future responds.
Have a nice day to all.
On Wed, May 17, 2017 at 10:55 AM, m712 - Developer <
comeon@getbackinthe.kitchen> wrote:
> That's a pretty rude way to reply for someone who is asking questions.
> Many major
Ok, so how do I solve this problem of fishing content in my mails?
On Wednesday, May 17, 2017 at 9:56:56 AM UTC+2, m712 - Developer wrote:
>
> That's a pretty rude way to reply for someone who is asking questions.
> Many major email providers mark emails from servers without a PTR record to
>
Ok, so how do I solve this problem of fishing content in my mails?
On Wednesday, May 17, 2017 at 9:54:15 AM UTC+2, Andréas Kühne wrote:
>
> Hi,
>
> I think Constantine is probably correct. It's not a specific django
> problem if your emails are being flagged as fishing emails. The problem is
>
That's a pretty rude way to reply for someone who is asking questions. Many major email providers mark emails from servers without a PTR record to their domains as "spam".
On May 17, 2017 9:52 AM, Ismail Sarenkapic wrote:lol, It is Django related question and can be solved
Hi,
I think Constantine is probably correct. It's not a specific django problem
if your emails are being flagged as fishing emails. The problem is more
likely how the emails are being sent AFTER they are sent from django.
Django only creates an email based on the properties you use - sender,
lol, It is Django related question and can be solved with some of third
party libraries like allauth, scoialauth etc.
Please don't replay to the posts when you don't know what it is about.tnx
again
On Wednesday, May 17, 2017 at 8:41:05 AM UTC+2, Constantine Covtushenko
wrote:
>
> It is not a
It is not a Django related question, sorry.
I can just suggest to look in 'SPAM' filters in you mailing agent.
On Wed, May 17, 2017 at 9:24 AM, Ismail Sarenkapic
wrote:
> I already fixed the problem tnx.
> but i still dont know why are my emails treated like potential
I already fixed the problem tnx.
but i still dont know why are my emails treated like potential fishing
content, can you help me with that?
On Wednesday, May 17, 2017 at 8:21:22 AM UTC+2, Constantine Covtushenko
wrote:
>
> Hi, Ismail
>
> Did you try:
>
> *instance.user.email*?
>
> I hope it
Hi, Ismail
Did you try:
*instance.user.email*?
I hope it should be what you need.
Regards,
Constantine C.
On Mon, May 15, 2017 at 3:47 PM, Ismail Sarenkapic
wrote:
> from django.conf import settings
> from django.contrib.auth.models import (
> BaseUserManager,
from django.conf import settings
from django.contrib.auth.models import (
BaseUserManager, AbstractBaseUser
)
from django.contrib import messages
from django.core.mail import send_mail
from django.conf import settings
from django.core.validators import RegexValidator
from django.db import
12 matches
Mail list logo