Actually, all people who use google MX will have google.com or gmail.com in their domains.

They can use other email servers on their devices. However, those servers will not be google.com or gmail.com email addresses. They can publish their google.com or gmail.com addresses as their return address. But if they are actually using a different email provider, they the actually email provider will provide their own domain.com smtp servers and configurations for those clients.

-- L. James

--
L. D.  James
lja...@apollo3.com
www.apollo3.com/~ljames

On 11/21/2014 10:25 PM, Peter wrote:
On 11/21/2014 07:02 AM, Wietse Venema wrote:
/etc/postfix/master.cf:
     forced-ipv4 unix  -       -       n       -       -       smtp
        -o inet_protocols=ipv4

/etc/postfix/transport:
     google.com forced-ipv4:
     gmail.com  forced-ipv4:

/etc/postfix/main.cf:
     transport_maps = hash:/etc/postfix/transport
Unfortunately the above solution assumes that all recipients that use
the google MX servers will have email addresses with google.com or
gmail.com domains.  Unfortunately there is literally an endless number
of domains that use the google MXes (google apps anyone?) so a solution
that looks up the MX of the recipient domain and picks a transport based
on that would be better.  I'm not aware of a postfix setting that
directly allows this and the best thing I can think of is a policy
daemon that will look up the recipient MX and direct mail accordingly.


Peter

Reply via email to