Hi, This is my ~/.fetchmailrc config, works with Office365 and should(TM) work with every exchange, PS: I use another fetchmail command on cron that replace some options, but are only to use procmail instead to mailgate directly.
poll pod51028.outlook.com proto pop3 user "[email protected]" pass "secret123" options ssl mda "/usr/bin/rt-mailgate --queue General --action correspond --url http://127.0.0.1/rt/"; Your error point to MDA, verify path of rt-mailgate binary and --url option. De: [email protected] [mailto:[email protected]] Em nome de Shane Vedvik Enviada em: quarta-feira, 17 de abril de 2013 15:35 Para: [email protected] Assunto: [rt-users] Fetchmail Exchange RT4 Configuration questions I was wondering if anyone had any insight into how to configure the RT MDA to accept a self-signed certificate, or if I have to go ahead and get a dv cert for this server. Email sent to support@ is taken off the exchange 2010 server using fetchmail to collect it via pop3, then forwarded to the RT MDA as below: #--- fetchmail Config #set daemon 120 #set syslog poll exch1.mk.local proto pop3 user"support" pass"********" to root sslproto "TLS1" mda "/opt/rt4/bin/rt-mailgate --url https://rt.markentsolutions.com/rt --queue support --action correspond" When it runs, I get the following error: 500 Can't connect to rt.markentsolutions.com:443 (certificate verify failed) fetchmail: MDA returned nonzero status 75 not flushed fetchmail: POP3> LIST 8 fetchmail: POP3< +OK 8 406 fetchmail: POP3> TOP 8 99999999 fetchmail: POP3< +OK reading message [email protected]:8 of 8 (406 octets) #**An Error Occurred Any help would be appreciated. Thanks, Shane
