How can i make my email as verified like PayPal, even though my URL and exchange server is having SSL certificate its still going to spam folder.
From https://support.google.com/mail/answer/3070163?hl=en
...who match the following criteria:
Send a high volume of messages over time that most Gmail users think are not spam.
Publish a DMARC reject policy, which means that the domain only sends authenticated mail and any unauthenticated mail sent by the domain should be rejected.
Which means in effect that
You have to be important for lots of users, so that they need to be protected from phishing mails claiming to be you.
And you have to properly controlled the delivery of your email, that is have published DKIM, SPF policies to control who should be able to send email with your domain and how to proof that these emails where delivered by your domain. See http://en.wikipedia.org/wiki/DMARC.
Related
I have Postfix setup on my VPS to relay all outgoing mail through AmazonSES and deal with all my incoming mail myself. I have recently setup DMARC and when analyzing my dmarc reports I find that everything passes except for my SPF Alignment. I'm a bit concerned that if I follow Amazons instructions to setup a MAIL_FROM domain that I will lose the ability to deal with my own incoming mail through Postfix, is that correct?
To answer my own question, no, I don't lose the ability to deal with my own incoming email just by setting up a MAIL_FROM (sub) domain.
Assume you have a Gmail account and want to send an E-mail to an account on yahoo mail server from Gmail account, here are the steps:
Client mail manager (say outlook) connects to gmail server and authenticates your account(using username/password that you have already)
after the authentication is done, your mail is sent to gmail server
so here is the question: how gmail proves itself to yahoo? has
gmail any username/password or some sort of things? is authentication needed for this?
In general there is no authentication from one SMTP server to another. The only authentication is from you to gmail.
This is one reason why spam is such a problem. The basic SMTP protocol just assumes there is no spam. You open a connection to a mail server and just send the headers like
from: mehrdad#gmail.com
to: gman#yahoo.com
Hello
And yahoo.com (the receiver) will happy except the email regardless of what computer it came from.
Because of those issues things have been added but they are optional.
One is DKIM. It works by signing your email with a digital signature. The signed email can be verified by the receiver (in your case by yahoo). Yahoo can check for gmail's public key in gmail's DNS records and check that the mail's signature cryptographically matches. It's up to the receiver (yahoo) to decide if it wants to check that or not. If the sender (Google or a spammer) does not add the signature then again, it's up to the receiver to decide what to do with the message. It could assume it's okay and pass it on. It could check if there is a public key available and if it is and the email has no signature then may not pass it on? Or mark it as "possibly spam"
There's also SPF. SPF is designed so that the receiver (yahoo) can verify that only the sender (Google) is allowed to send mail from gmail.com.
Then there is DMARC. DMARC lets Google (the sender) tell Yahoo (the receiver) what to do when when the stuff above fails. For example wither or not to forward messages who's signatures don't match the key. It's up to the receiver to decide to use this info.
Along with the linked wikipedia articles here's a pretty good overview of what happens and the problems involved.
Best regards
I have an instance configured in Google Cloud, where I installed cPanel to manage more easily my web project. Everything runs fine, but as much a problem to use email accounts.
I set all MX records in the Network section of the console Google, and have also done the same in cPanel. Then I created email accounts in cPanel, and I can access the accounts (I use RoundCube as an email client), but when sending an email, this is going, but does not arrive to destination, or conversely, sent from another account (such as a Gmail) email, and this is sent but not up to my new personal email account.
I realized that what happens is that Google does not allow use ports 25 and 587, so must perform other configuration.
Someone could help me to know how I can create and use email accounts, from a "normal" way, without using Google Apps (because it is paid) or services like Mailgun.
Thanks so much for any help.
You will have to use any third party email service for mail. Please check following URL,
https://cloud.google.com/compute/docs/tutorials/sending-mail/
You cannot use ports 25 and 587 since GCP block all outbound traffic from those ports, I suggest you use port 2525 since that's the only smtp port that GCP does not block and most major vendors use.
I am trying to send authentication requests from several spoofed mac addresses to the AP. When I ran wireshark, I was able to see authentication responses from the AP. But how is this possible as no probe requests packets have been sent from these spoofed mac addresses.
This looks like this is stateless. But from what I have read, I have understand, there are three states -
Unauthenticated, Unassociated
Authenticated, Unassociated
Authenticated, Associated
Simply, the answer is "Yes, it is possible to send authentication request packets without sending probe requests".
As far as I know, Probe Requests are only necessary to allow mobile devices to obtain information from the APs at will (i.e. instead of waiting for beacons).
Im trying to send an html email with attachment to list of users. Our client also requires the track of undelivered email ids, so we thought of using sp_send_dbmail feature available in SQL server, which has logs for email sent using it. Our client also mandate to DKIM sign the emails. Im not able to find how to DKIM sign the emails sent through sp_send_dbmail.
Please help!..
Normally DKIM signing is a SMTP server business, not SQL. You want to talk to postmaster. There are several steps involved in enabling DKIM signing outgoing email:
Generation of RSA crypto key pair
Publication of public key in DNS (so receiving server is able to verify the signature)
Setting up signing service
Modifying your SMTP server configuration to use this signing service for all or specific outgoing emails
There are third party controls that enable signing from within SQL, but not using sp_send_dbmail. See here for example: http://www.example-code.com/sql/dkim_sendDkimSigned.asp
However they don't eliminate the 1 and 2 above.