Thanks a lot for your answers. They really helped me. :)
On Sun, Nov 5, 2017 at 11:19 PM, Viktor Dukhovni
wrote:
>
>
>> On Nov 5, 2017, at 3:27 PM, /dev/rob0 wrote:
>>
>> BTW if for some reason you did want to deliver "@example.com" to
>> Google, simply use the MX lookup in your transport entry
> On Nov 5, 2017, at 3:27 PM, /dev/rob0 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 "gmai
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 unconnec
> On Nov 5, 2017, at 1:29 PM, Pau Peris 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 transpor
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
