On Tue, Jun 07, 2011 at 10:38:44AM -0400, Michael Way wrote:
> > So why not just take MSexChange out of the picture? Set up direct
> > authentication to gmail. SASL_README.html#client_sasl just as you
> > did, setting it up to authenticate to MSexChange.
> >
> > Have your .forward invoke sendmail(1) with your gmail address as
> > the sender. Then maybe a transport_maps entry to force your gmail
> > address to use the gmail submission service.
> >
> > Did I miss something? Does that not achieve the original goal?
>
> Yes, I agree that this would be the obvious way to attack it except
> that our corporate firewall does not allow such outbound smtp
> packets on ports less than 1024: e.g.
> % telnet smtp.gmail.com 587
> Trying 209.85.225.109...
>
> and never connecting... while for my corporate smtp server it does
> connect. You see, I'm trying to get around what *they* think is
> best for me and them...
Need Able System Administrators ;)
I could suggest some sort of tunnelling to a host outside the Great
Firewall, but that would likely be a violation of network use rules.
The best next step that occurs to me would be to go to the IT gang
and ask for support. If the answer is as I suspect, "No, you may not
and cannot do this," I guess you must either obey or resort to
sneakernet solutions.
Another possible approach is to see if there's any software to
automate the gmail webmail interface. I know spammers have done it,
because stuff like that is about the only spam that gets through to
my mailboxes.
Good luck.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
