>> I can send emails via this system just fine using mutt or >> whatever command line mail I like, BUT I also use fetchmail to >> get email from our IMAP server. I then use a .forward file to >> keep a local copy AND send a copy to gmail as a backup. > > Ugly and complex, but, oh well.
Until they moved over to this new TLS/Auth system I'd been using this for years - so I guess I've gotten used to its ugliness and complexity :-) > 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... cheers mike
