On Wed, Sep 08, 2010 at 11:12:45AM +0800, Richard Chapman wrote:
>>> AFAIK smtp.google.com requires an authenticated TLS connection.
>> If you have a Google Apps hosted domain, you use fixed MTA credentials,
>> (possibly just an IP whitelist) negotiated with Google and send to
>> alternate servers (not smtp.gmail.com 587). No per-user credentials
>> required.
>
> Not sure I fully understand this...
> I AM using a google apps hosted domain - and I think I need to use per user
> credentials because that is what would happen if the users connected direct
> to smtp.google.com as described in the google apps setup instructions. If I
> don't use per user credientials - I think google apps will change the
> sender address to a "fixed" sender address. It seems that you don't agree
> with me here? Also - part of the rationale of sending via smtp.google.com
> with user credentials - is to ensure that the google apps users "sent email
> folders" are maintained correctly.
>
> Perhaps you are describing an alternative method for google apps smtp which
> I am unaware of. If so - can you point me to a description of this
> alternative option?
The implementation I am familiar with has users submitting mail directly
via Gmail (Webmail or SMTP, their choice). Mail from Google hosted users,
even to other Google hosted users, flows through a corporate (non-Google)
relay and only then to its destination. Mail to Google hosted users is
only accepted from the corporate relay, and the MX records are not handled
by Google. In other words Gmail is just a large alternative mailstore,
but is not the edge SMTP service.
It is not clear what your use-case is, perhaps you should describe it in
more detail. I probably misunderstood what you are trying to achieve in
my initial reply.
--
Viktor.
