On Thursday, January 16, 2020 at 7:34:27 PM UTC-5, Walter Lee Davis wrote:
>
>
>
> > On Jan 16, 2020, at 6:19 PM, fugee ohu <fuge...@gmail.com <javascript:>> 
> wrote: 
> > 
> > 
> > 
> > On Monday, December 30, 2019 at 2:48:06 PM UTC-5, Walter Lee Davis 
> wrote: 
> > 
> > 
> > > On Dec 29, 2019, at 11:44 PM, fugee ohu <fuge...@gmail.com> wrote: 
> > > 
> > > I searched my entire tree starting at / for the name of my mail server 
> but didn't find it Everything's working it sends mail in production just 
> fine but I'm trying to figure out how, since it seems I never put the url 
> of my mail server anywhere? 
> > 
> > Your production server may be set up with postfix or sendmail, and thus 
> the default (SMTP to localhost) will Just Work™. When your application 
> sends mail, it just sends a raw SMTP message to port 25 on the localhost, 
> and the mail server running there accepts it and forwards it. That's the 
> default, baked into Rails, in case you don't configure anything more 
> specific. 
> > 
> > This is almost never what you actually want, because unless your 
> production Web server is also set up as an authoritative (DNS-verified) 
> SMTP server, your mail delivery will be spotty at best to large (think 
> Gmail) recipients. Those services take spam very seriously, and you have to 
> climb over some tall fences (configured in DNS, mainly, through TEXT and MX 
> records) in order to please them enough to accept your messages. 
> > 
> > This is doubly-true if your application is designed to send mail that is 
> "apparently-from" someone who is not at your server's domain. Services like 
> SendGrid exist to take this pain away from you, making sending 
> transactional e-mail as pain-free as possible, because they work to ensure 
> that their servers don't end up on banned lists, or get off them quickly. 
> > 
> > My recommendation if you want to send mail out to one user that appears 
> to be from another user, such that they can just hit "reply" in their mail 
> application and respond to it, send the message with the headers From: 
> a-real-...@your-server.com, and Reply-to: us...@example.com. That way the 
> message is deliverable (since it came from you, and you authenticate that 
> in your DNS settings), but the recipient can simply press Reply and not 
> have to manually correct the To: address in that message. 
> > 
> > Walter 
> > 
> > I found google was rejecting mail from my server because I didn't DKIM 
> and DMARC signatures setup After adding the services how do I ask google to 
> re-review my mail server if I'm not using gsuite? 
> > 
>
> I'm pretty sure it's done on a message-by-message basis. I doubt they 
> maintain a ban-list that you're on, and have to remove you from. Each 
> message purportedly "from" some other address is a new and special thing, 
> since headers are so very easy to forge. 
>
> Walter 
>
>
They keep adding things you have to do to not be rejected Now they want 
DKIM and DMARC setup  

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-talk+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/ef547849-d093-44a0-a3ea-38ec0f253764%40googlegroups.com.

Reply via email to