Suddenly without apparent cause, I cannot send an email unless I change my “identity email setting” (under account settings) to match my email address from my I
A couple years ago I registered my name as a domain, and I set up an email address for that domain to be forwarded to my POP email account with my ISP. Then in the Thunderbird "account settings" I changed my "identity" email address to my domain email address, instead of my ISP email address. So when I sent emails, it would say that it was coming from my domain email address.
This worked fine for a couple years until today. I keep getting "administrative prohibition" error when trying to send an email. The only way it works is if I go into my identity email setting and change it back to my ISP email address. But I want people to send and reply back to my domain email address. My ISP was no help with this issue. I can't think of anything I changed. This problem seems to have appeared for no reason--that I can see.
Any help would be greatly appreciated...
すべての返信 (3)
I would guess your ISP has changed their email forwarding policies. Unfortunately I can not cure stupid. Or your ISP would have people that answered the phone that were more than script jockeys.
I would guess that your should complete your domain setup including the mail exchanger information and use the SMTP server provided in your hosting account.
Hey, thanks for the reply. Not sure if I explained my problem clearly (I’m not really a tech guy). My incoming and outgoing mail server is my ISP. They don’t do any forwarding. My domain registrar forwards my domain emails to my ISP email, and that works. Incoming mail works fine.
Outgoing mail is the current problem. For the past couple years, I would use my domain email in my Thunderbird identity, so emails sent from my ISP email account would appear to be coming from my domain email (this was not for the intention of spamming of course, I just wanted my email address to be my domain).
But now I can’t send an email unless my outgoing identity email matches my actual ISP email address.
The reason I don’t use my domain registrar as my mail server is because I don’t like the way they filter spam. My ISP does a better job with SPAM filtering, so I prefer emails to be forwarded to my ISP. It’s a somewhat convoluted problem.
My thinking was that my ISP decided to reject outgoing emails unless the identity email matches the actual sending email address, because a mismatch might appear to be a spamming intention. But my ISP claims they haven’t changed anything. And I haven’t changed anything on my end, so I’m baffled.
hey perhaps I did not make myself clear.
Relaying= sending mail from @mydomain.com from the server of myisp.com
Some ISP's, particularly in the USA have gone to extreme lengths over the years to force their subscribers to use their email severs including blocking mail ports on their network edge. I have no idea really why they dd this. But they did.
The result is as you have done. folk sending mail from a mail server that is not the right one for the email address. This causes all sorts of trouble, especially now that most mail receivers do a simple reverse DNS check to see if mail is spam. (Ironically the same ISP's that force their customers to relay also love doing reverse DNS).
The reverse DNS means that they check the originating mail servers domain name against the IP address that the mail came from. no match means it is spam. It also means over time that the ISP gets declared a source of spam and their mail server makes it onto one of the lists mail providers use of sources of spam to not receive mail from.
So what is your domain name? lets have a look and see what is and is not set up. What is your ISP? Despite their denials we might find something useful.