<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: jeyk333</title>
    <description>The latest articles on DEV Community by jeyk333 (@jeyk333).</description>
    <link>https://dev.to/jeyk333</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F211592%2F92a46af2-b097-4229-80ed-48e214b8345e.png</url>
      <title>DEV Community: jeyk333</title>
      <link>https://dev.to/jeyk333</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jeyk333"/>
    <language>en</language>
    <item>
      <title>Why Your Contact Form Emails Go to Spam (and How to Fix It)</title>
      <dc:creator>jeyk333</dc:creator>
      <pubDate>Fri, 13 Nov 2026 12:14:54 +0000</pubDate>
      <link>https://dev.to/jeyk333/why-your-contact-form-emails-go-to-spam-and-how-to-fix-it-53b6</link>
      <guid>https://dev.to/jeyk333/why-your-contact-form-emails-go-to-spam-and-how-to-fix-it-53b6</guid>
      <description>&lt;p&gt;Your contact form works. The submission goes through, the visitor sees "thanks", and the email lands in spam, or nowhere. Most guides on this assume WordPress. This one is for any site: static pages, custom code, or a form service. It explains why it happens and how to fix it properly, starting with the most common cause.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Need it fixed in your own inbox today?&lt;/strong&gt; In Gmail, open one of the form emails in Spam, click &lt;em&gt;Not spam&lt;/em&gt;, then create a filter for the sender's address with &lt;em&gt;Never send it to Spam&lt;/em&gt;. In Outlook, add the sender to &lt;em&gt;Safe senders&lt;/em&gt;. That helps you, but not anyone else on your team, and it doesn't fix the cause. Read on for that.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Why form emails end up in spam
&lt;/h2&gt;

&lt;p&gt;Mailbox providers like Gmail, Outlook and Yahoo decide where an email goes based mostly on two things: whether it is &lt;strong&gt;authenticated&lt;/strong&gt; (provably sent by someone allowed to send for that domain) and whether its &lt;strong&gt;sender has a good reputation&lt;/strong&gt;. Contact forms break the first rule in a few classic ways.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. The email is "from" the visitor
&lt;/h3&gt;

&lt;p&gt;This is the big one. It feels natural to set the From address to the person who filled in the form, so you can just hit Reply. But your server is not allowed to send email as &lt;code&gt;priya@yahoo.com&lt;/code&gt;. To Yahoo, Gmail or Outlook, that email is indistinguishable from a forgery.&lt;/p&gt;

&lt;p&gt;Many large providers publish a strict DMARC policy that tells everyone else to reject mail pretending to come from their domain. Yahoo and AOL have done this since 2014. So a form email with &lt;code&gt;From: someone@yahoo.com&lt;/code&gt;, sent from your server, gets rejected or quarantined before you ever see it. The visitor did nothing wrong; the form did.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The fix:&lt;/strong&gt; send from an address on a domain you control, and put the visitor's address in &lt;code&gt;Reply-To&lt;/code&gt;. Your Reply button still goes to them.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight email"&gt;&lt;code&gt;&lt;span class="nc"&gt;From&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;     &lt;span class="nc"&gt;Website&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;forms&lt;/span&gt;@&lt;span class="n"&gt;mail&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;yourdomain&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="nc"&gt;Reply&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;To&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Priya&lt;/span&gt; &lt;span class="nc"&gt;Nair&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;priya&lt;/span&gt;@&lt;span class="n"&gt;yahoo&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="nc"&gt;To&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;       &lt;span class="n"&gt;you&lt;/span&gt;@&lt;span class="n"&gt;yourdomain&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt;
&lt;span class="nc"&gt;Subject&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;  &lt;span class="nc"&gt;New&lt;/span&gt; &lt;span class="n"&gt;message&lt;/span&gt; &lt;span class="n"&gt;from&lt;/span&gt; &lt;span class="nc"&gt;Priya&lt;/span&gt; &lt;span class="nc"&gt;Nair&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  2. The server isn't allowed to send for your domain
&lt;/h3&gt;

&lt;p&gt;Even with the right From address, the email has to prove it really came from you. A plain PHP &lt;code&gt;mail()&lt;/code&gt; call on shared hosting, or a script on a cloud server sending directly, usually proves nothing. Your domain has no record saying that server may send for it, so the email arrives "unauthenticated" and is treated with suspicion.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. No DMARC, or nothing lines up
&lt;/h3&gt;

&lt;p&gt;Passing SPF or DKIM isn't quite enough on its own. DMARC checks that the domain which passed matches the domain in the visible From address. If your email service signs with its own domain while your From says &lt;code&gt;yourdomain.com&lt;/code&gt;, the checks can pass and still fail DMARC's "alignment" test.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. The form is carrying spam
&lt;/h3&gt;

&lt;p&gt;If bots fill your form with links and SEO pitches, every notification you send is, in effect, spam. Filters learn from that, and your real messages start sharing the same fate. Filtering junk before it is emailed protects your sending reputation as well as your inbox.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get the headers right
&lt;/h2&gt;

&lt;p&gt;Whatever sends the email, use these rules:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;From&lt;/strong&gt; is always your domain, ideally a dedicated address like &lt;code&gt;forms@&lt;/code&gt; or &lt;code&gt;notifications@&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reply-To&lt;/strong&gt; is the visitor, so replying works as before.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Subject&lt;/strong&gt; is plain and predictable, such as "New message from Priya Nair". Avoid copying the visitor's text into the subject.&lt;/li&gt;
&lt;li&gt;Send &lt;strong&gt;plain text&lt;/strong&gt;, or simple HTML with a plain-text part.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here's what that looks like with Node.js and Nodemailer. Any email API (Resend, Postmark, Amazon SES, SendGrid) takes the same three fields.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;nodemailer&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'nodemailer'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;transport&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;nodemailer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createTransport&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="cm"&gt;/* your provider's SMTP settings */&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="c1"&gt;// Never let newlines from the form reach an email header.&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;oneLine&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;replace&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;\&lt;span class="n"&gt;r&lt;/span&gt;\&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="o"&gt;+/&lt;/span&gt;&lt;span class="n"&gt;g&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;' '&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;trim&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;slice&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;200&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;notify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;email&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;message&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;safeName&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;oneLine&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;'Website visitor'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;safeEmail&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="o"&gt;/^&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="o"&gt;^&lt;/span&gt;\&lt;span class="n"&gt;s&lt;/span&gt;@&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;@&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="o"&gt;^&lt;/span&gt;\&lt;span class="n"&gt;s&lt;/span&gt;@&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;\&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="o"&gt;^&lt;/span&gt;\&lt;span class="n"&gt;s&lt;/span&gt;@&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;$&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;test&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;email&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="nf"&gt;oneLine&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;email&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;transport&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sendMail&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;from&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'Website form &amp;lt;forms@mail.yourdomain.com&amp;gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;to&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'you@yourdomain.com'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;replyTo&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;safeEmail&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="sb"&gt;`${safeName} &amp;lt;${safeEmail}&amp;gt;`&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;subject&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`New message from ${safeName}`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;text&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;String&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;message&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="s1"&gt;''&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;slice&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;10000&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;oneLine&lt;/code&gt; step matters for security too: if a name containing a line break reaches a header, an attacker can add their own headers, including extra recipients. That's called header injection, and it's how contact forms get turned into spam relays.&lt;/p&gt;

&lt;h2&gt;
  
  
  Set up SPF, DKIM and DMARC
&lt;/h2&gt;

&lt;p&gt;These are three DNS records that tell the world which servers may send email for your domain. Your email provider gives you the exact values; here's what each one does.&lt;/p&gt;

&lt;h3&gt;
  
  
  SPF: which servers may send
&lt;/h3&gt;

&lt;p&gt;A TXT record on your domain listing the services allowed to send for it:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mail.yourdomain.com.  TXT  "v=spf1 include:spf.your-email-provider.com ~all"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;A domain can have &lt;strong&gt;only one&lt;/strong&gt; SPF record. If you send through several services, put all their &lt;code&gt;include:&lt;/code&gt; parts in the same record.&lt;/li&gt;
&lt;li&gt;SPF allows at most 10 DNS lookups. Long chains of includes quietly break it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  DKIM: a signature on every email
&lt;/h3&gt;

&lt;p&gt;Your provider signs each message with a private key, and you publish the public key in DNS, usually as a CNAME or TXT record at something like &lt;code&gt;selector._domainkey.mail.yourdomain.com&lt;/code&gt;. Unlike SPF, a DKIM signature survives forwarding, which makes it the more reliable of the two.&lt;/p&gt;

&lt;h3&gt;
  
  
  DMARC: what to do when checks fail
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;_dmarc.yourdomain.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Start with &lt;code&gt;p=none&lt;/code&gt;, which only collects reports, so you can see what's sending as you. Once everything legitimate passes, move to &lt;code&gt;p=quarantine&lt;/code&gt; and later &lt;code&gt;p=reject&lt;/code&gt;. That also stops others from forging your domain.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Use a subdomain for sending.&lt;/strong&gt; Sending form notifications from &lt;code&gt;mail.yourdomain.com&lt;/code&gt; keeps their reputation separate from your main domain, where your team's day-to-day email lives. If something goes wrong with one, the other isn't dragged down.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What Gmail, Yahoo and Outlook now require
&lt;/h2&gt;

&lt;p&gt;Since 2024, Google and Yahoo have required &lt;strong&gt;every&lt;/strong&gt; sender to pass at least SPF or DKIM. Senders of more than about 5,000 messages a day to their users must have SPF, DKIM and DMARC, keep their spam-complaint rate low, and offer one-click unsubscribe on marketing mail. Microsoft applied similar rules to high-volume senders to Outlook.com in 2025.&lt;/p&gt;

&lt;p&gt;A contact form will rarely reach those volumes, but the baseline applies to everyone: unauthenticated email is increasingly likely to be filtered or refused outright.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check it's fixed
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Read the headers.&lt;/strong&gt; In Gmail, open a form email, click the three dots, then &lt;em&gt;Show original&lt;/em&gt;. You want &lt;code&gt;SPF: PASS&lt;/code&gt;, &lt;code&gt;DKIM: PASS&lt;/code&gt; and &lt;code&gt;DMARC: PASS&lt;/code&gt;. Outlook shows the same information under &lt;em&gt;View message source&lt;/em&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Send a test to a scoring tool.&lt;/strong&gt; Services like mail-tester.com give you a temporary address and a score with specific problems listed. Submit your form with that address as the recipient.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test several providers.&lt;/strong&gt; Send to a Gmail, an Outlook and a Yahoo address. They filter differently.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Watch over time.&lt;/strong&gt; If you send a lot of mail from the domain, Google Postmaster Tools shows your reputation and spam rate.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Stop junk before it's emailed
&lt;/h2&gt;

&lt;p&gt;The less spam your form forwards, the better your notifications are treated. A hidden honeypot field, a minimum fill time, link limits and per-IP rate limits catch most of it without bothering real visitors. There's a full walkthrough with code in &lt;a href="https://formpit.com/blog/stop-contact-form-spam-without-captcha" rel="noopener noreferrer"&gt;how to stop contact form spam without a CAPTCHA&lt;/a&gt;. Keep flagged messages in a spam folder instead of emailing them.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you use a form service
&lt;/h2&gt;

&lt;p&gt;If a form backend sends your notifications, most of the above is its job, but it's worth checking two things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Emails arrive &lt;strong&gt;from the service's own authenticated domain&lt;/strong&gt;, or from yours after you've added its DNS records, and never "from" the visitor. Use &lt;em&gt;Show original&lt;/em&gt; to confirm all three checks pass.&lt;/li&gt;
&lt;li&gt;The visitor's address is in &lt;strong&gt;Reply-To&lt;/strong&gt;, so replying still works.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://formpit.com" rel="noopener noreferrer"&gt;Formpit&lt;/a&gt;, which I build, works this way: notifications come from its own authenticated domain with the visitor in Reply-To, spam is filtered before anything is emailed, and you can also reply from an inbox where their answer comes back into the same conversation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;From is your domain, never the visitor's. The visitor goes in Reply-To.&lt;/li&gt;
&lt;li&gt;Strip line breaks from anything that goes into a header.&lt;/li&gt;
&lt;li&gt;Send through a real email provider, not bare &lt;code&gt;mail()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Publish SPF (one record), DKIM and DMARC for the sending domain, ideally a subdomain.&lt;/li&gt;
&lt;li&gt;Check &lt;em&gt;Show original&lt;/em&gt; for three PASSes, and test Gmail, Outlook and Yahoo.&lt;/li&gt;
&lt;li&gt;Filter spam before it's emailed.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Fix the From address and add the three DNS records, and the large majority of "my form emails go to spam" problems go away.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>email</category>
      <category>tutorial</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Building REST APIs using Node with Express and MongoDB</title>
      <dc:creator>jeyk333</dc:creator>
      <pubDate>Sat, 02 May 2020 14:45:48 +0000</pubDate>
      <link>https://dev.to/jeyk333/building-rest-apis-using-node-with-express-and-mongodb-p4m</link>
      <guid>https://dev.to/jeyk333/building-rest-apis-using-node-with-express-and-mongodb-p4m</guid>
      <description>&lt;p&gt;In the following Medium article, I am gonna show you, how to build REST APIs for CRUD operation with Node using Express and MongoDB. We will be creating a simple posts API, Where user can create, edit, update and retrieve a post. To check the full post, Please click the below article link&lt;/p&gt;


&lt;div class="ltag__link"&gt;
  &lt;a href="https://medium.com/@jeyanthkanagaraju/creating-restful-crud-apis-with-node-js-express-js-and-mongodb-from-scratch-3ef632067928" class="ltag__link__link"&gt;
    &lt;div class="ltag__link__pic"&gt;
      &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--x_5O_QPV--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://miro.medium.com/fit/c/96/96/0%2AHeobTIZWRIqNAaAi" alt="Jeyanth Kanagaraju"&gt;
    &lt;/div&gt;
  &lt;/a&gt;
  &lt;a href="https://medium.com/@jeyanthkanagaraju/creating-restful-crud-apis-with-node-js-express-js-and-mongodb-from-scratch-3ef632067928" class="ltag__link__link"&gt;
    &lt;div class="ltag__link__content"&gt;
      &lt;h2&gt;Creating RESTful CRUD APIs using Node.js, Express and MongoDB from scratch&lt;/h2&gt;
      &lt;h3&gt;Jeyanth Kanagaraju ・ &lt;time&gt;Apr 30, 2020&lt;/time&gt; ・ 12 min read
      &lt;div class="ltag__link__servicename"&gt;
        &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--_EkM13RG--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://practicaldev-herokuapp-com.freetls.fastly.net/assets/medium_icon-2c57b3ec653e92a3d6207e708f1e4987099fc69342e556aaf9f035b1968b3f26.svg" alt="Medium Logo"&gt;
        Medium
      &lt;/div&gt;
    &lt;/h3&gt;
&lt;/div&gt;
  &lt;/a&gt;
&lt;/div&gt;


&lt;p&gt;You can find the complete code of the application explained in this article in below GitHub Repository.&lt;/p&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--vWogaON8--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://practicaldev-herokuapp-com.freetls.fastly.net/assets/github-logo-28d89282e0daa1e2496205e2f218a44c755b0dd6536bbadf5ed5a44a7ca54716.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/jeyk333"&gt;
        jeyk333
      &lt;/a&gt; / &lt;a href="https://github.com/jeyk333/CRUD-REST-APIs"&gt;
        CRUD-REST-APIs
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      RESTful APIs to do CRUD operation using Express, Nodejs and MongoDB
    &lt;/h3&gt;
  &lt;/div&gt;
&lt;/div&gt;


</description>
      <category>node</category>
      <category>express</category>
      <category>mongodb</category>
      <category>webdev</category>
    </item>
    <item>
      <title>React Chatbot using MERN stack and Dialogflow</title>
      <dc:creator>jeyk333</dc:creator>
      <pubDate>Thu, 05 Mar 2020 18:16:11 +0000</pubDate>
      <link>https://dev.to/jeyk333/react-chatbot-using-mern-stack-and-dialogflow-4lmd</link>
      <guid>https://dev.to/jeyk333/react-chatbot-using-mern-stack-and-dialogflow-4lmd</guid>
      <description>&lt;p&gt;Hi, &lt;/p&gt;

&lt;p&gt;I created an &lt;strong&gt;React Chatbot&lt;/strong&gt; using &lt;strong&gt;Reactjs, Nodejs, MongoDB&lt;/strong&gt; and &lt;strong&gt;Dialogflow(NLP)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It is an interactive web application chatbot to interact with the users, who visiting your application. This chatbot is made with MERN stack using &lt;strong&gt;Google's Machine Learning Dialogflow(NLP)&lt;/strong&gt;. Dialogflow uses &lt;strong&gt;Natural Language Processing(NLP)&lt;/strong&gt; technique to make the bot understand the Human Language and to efficiently interact with users. I am ReactJs as the frontend and NodeJs as backend, which will interact between the Frontend and Dialogflow to get desired results.&lt;/p&gt;

&lt;p&gt;Please check the complete code repository for the chatbot and Give a 🌟 in github, if you like it.&lt;/p&gt;

&lt;p&gt;Github Respository - &lt;a href="https://github.com/jeyk333/React-Chatbot"&gt;https://github.com/jeyk333/React-Chatbot&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;To play with it -&amp;gt; &lt;a href="https://vast-badlands-40215.herokuapp.com/"&gt;https://vast-badlands-40215.herokuapp.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Things you can ask to it&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Hi/Hello&lt;/li&gt;
&lt;li&gt;where is pikachu&lt;/li&gt;
&lt;li&gt;courses (It will list some dummy courses from the mongo db and will ask, if you need any personal training)&lt;/li&gt;
&lt;li&gt;If you give Yes for the personal training, it will ask for your details.&lt;/li&gt;
&lt;li&gt;You can enter the details, which will also stored in the database&lt;/li&gt;
&lt;li&gt;You can also do some random chats&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The UI may look bad, as i didn't put much effort in the ui for now. Its not completed. I am still improving the chatbot.&lt;/p&gt;

</description>
      <category>react</category>
      <category>node</category>
      <category>mongodb</category>
      <category>chatbot</category>
    </item>
    <item>
      <title>Simple React CRUD app using Material Ui</title>
      <dc:creator>jeyk333</dc:creator>
      <pubDate>Tue, 13 Aug 2019 12:58:30 +0000</pubDate>
      <link>https://dev.to/jeyk333/simple-react-crud-app-using-material-ui-1lep</link>
      <guid>https://dev.to/jeyk333/simple-react-crud-app-using-material-ui-1lep</guid>
      <description>&lt;p&gt;App Link : &lt;a href="https://rm-crud.herokuapp.com/"&gt;https://rm-crud.herokuapp.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Github Repository Link: &lt;a href="https://github.com/jeyk333/React-CRUD-using-Material-Ui"&gt;https://github.com/jeyk333/React-CRUD-using-Material-Ui&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;My First Commit in Github. I made an Simple CRUD app using Reactjs and Material UI. Please Check and give feedbacks about Code or Ui etc.&lt;/p&gt;

</description>
      <category>react</category>
      <category>material</category>
    </item>
  </channel>
</rss>
