Propper way to deliver email messages to gmail

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Propper way to deliver email messages to gmail

Pau Peris
Hi,

could someone tell, in his opinion, which would be the right way to
deliver remote messages to gmail? Looking at this [1] URL looks like
the only way available is through port 25. If i wanted my Postfix to
communicate through 465 or 587 it would need a user/pass but it looks
weird to me. I mean, should an MTA really need an account for each
other MTA where to deliver email messages? Of course not. Don't know
if i'm missing something here.

This question comes because in my domains table, from the MySQL
database managed by Postfix, there's a domain which used to be virtual
but right now it is not so i changed the transport to
smtp:[aspmx.l.google.com]:25

Thanks,

[1] https://support.google.com/a/answer/176600?hl=en
Reply | Threaded
Open this post in threaded view
|

Re: Propper way to deliver email messages to gmail

Anvar Kuchkartaev
If you want to use gmail servers as relay when sending emails you can simply use [smtp.gmail.com]‎:587 with starttls and authorising with existing gmail account. However you probably need to overwrite from part with your gmail account (I don't think they will allow to use different email in from field than sending account).

If you are not sending a lot of emails it is recommended use mailgun or sendgrid or other mass mailing service as relay.

Anvar Kuchkartaev
[hidden email] 
  Original Message  
From: Pau Peris
Sent: domingo, 5 de noviembre de 2017 07:29 p.m.
To: postfix-users
Subject: Propper way to deliver email messages to gmail


Hi,

could someone tell, in his opinion, which would be the right way to
deliver remote messages to gmail? Looking at this [1] URL looks like
the only way available is through port 25. If i wanted my Postfix to
communicate through 465 or 587 it would need a user/pass but it looks
weird to me. I mean, should an MTA really need an account for each
other MTA where to deliver email messages? Of course not. Don't know
if i'm missing something here.

This question comes because in my domains table, from the MySQL
database managed by Postfix, there's a domain which used to be virtual
but right now it is not so i changed the transport to
smtp:[aspmx.l.google.com]:25

Thanks,

[1] https://support.google.com/a/answer/176600?hl=en


Reply | Threaded
Open this post in threaded view
|

Re: Propper way to deliver email messages to gmail

Viktor Dukhovni
In reply to this post by Pau Peris


> On Nov 5, 2017, at 1:29 PM, Pau Peris <[hidden email]> wrote:
>
> This question comes because in my domains table, from the MySQL
> database managed by Postfix, there's a domain which used to be virtual
> but right now it is not so i changed the transport to
> smtp:[aspmx.l.google.com]:25

Delete the transport entry and let MX records take the traffic to
the right place.

--
        Viktor.

Reply | Threaded
Open this post in threaded view
|

Re: Propper way to deliver email messages to gmail

/dev/rob0
In reply to this post by Pau Peris
On Sun, Nov 05, 2017 at 07:29:16PM +0100, Pau Peris wrote:
> could someone tell, in his opinion, which would be the right way
> to deliver remote messages to gmail? Looking at this [1] URL looks
> like the only way available is through port 25.

See also RFC 5321.  All mail exchange among unconnected sites
exclusively takes place on port 25.

> If i wanted my Postfix to communicate through 465 or 587 it would
> need a user/pass but it looks weird to me. I mean, should an MTA
> really need an account for each other MTA where to deliver email
> messages? Of course not. Don't know if i'm missing something here.

You're missing the above bit about mail exchange being exclusively
done on port 25.  Submission (587) or the deprecated, non-standard
smtps (465) are for AUTHENTICATED USERS to submit mail.  They are
never to be used for server-to-server mail exchange.

> This question comes because in my domains table, from the MySQL
> database managed by Postfix, there's a domain which used to be
> virtual but right now it is not so i changed the transport to
> smtp:[aspmx.l.google.com]:25

If you are no longer hosting the domain, you probably need to remove
it from your domains table.  And likewise, remove it from your
transport table.

BTW if for some reason you did want to deliver "@example.com" to
Google, simply use the MX lookup in your transport entry:

example.com smtp:google.com

> [1] https://support.google.com/a/answer/176600?hl=en
--
  http://rob0.nodns4.us/
  Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Reply | Threaded
Open this post in threaded view
|

Re: Propper way to deliver email messages to gmail

Viktor Dukhovni


> On Nov 5, 2017, at 3:27 PM, /dev/rob0 <[hidden email]> wrote:
>
> BTW if for some reason you did want to deliver "@example.com" to
> Google, simply use the MX lookup in your transport entry:
>
> example.com smtp:google.com
>
>> [1] https://support.google.com/a/answer/176600?hl=en
> --

More likely "gmail.com" than "google.com", just in case they
split the MX hosts for corporate mail from hosted mail, but
even that's fragile.  Just use the MX records for "example.com".

--
        Viktor.

Reply | Threaded
Open this post in threaded view
|

Re: Propper way to deliver email messages to gmail

Pau Peris
Thanks a lot for your answers. They really helped me.  :)

On Sun, Nov 5, 2017 at 11:19 PM, Viktor Dukhovni
<[hidden email]> wrote:

>
>
>> On Nov 5, 2017, at 3:27 PM, /dev/rob0 <[hidden email]> wrote:
>>
>> BTW if for some reason you did want to deliver "@example.com" to
>> Google, simply use the MX lookup in your transport entry:
>>
>> example.com   smtp:google.com
>>
>>> [1] https://support.google.com/a/answer/176600?hl=en
>> --
>
> More likely "gmail.com" than "google.com", just in case they
> split the MX hosts for corporate mail from hosted mail, but
> even that's fragile.  Just use the MX records for "example.com".
>
> --
>         Viktor.
>