Fetchmailrc

Using fetchmail for 1st time to collect mail from an Exchange server.
Exchange 2010
RT 4.0.1
Centos 5.7
fetchmail release 6.3.21+HESIOD+NLS.

Here’s my /opt/rt4/etc/fetchmailrc:

poll mail.domain.com proto pop3:
user trackrequests there with password ‘cleverly removed’ is kiss here mda “/opt/rt4/bin/rt-mailgate --url http://xtracker.domain.com. --queue General --action correspond”

When I invoke fetchmail -f /opt/rt4/etc/fetchmailrc, it appends “@mail.domain.com” to the username, whereas the correct user is trackrequests@domain.commailto:trackrequests@domain.com.

If I specify user trackrequests@domain.commailto:trackrequests@domain.com in the fetchmailrc file, then fetchmail turns it into trackrequests@domain.com@mail.domain.commailto:trackrequests@domain.com@mail.domain.com. For example:

[root@xtracker ~]# fetchmail -f /opt/rt4/etc/fetchmailrc
fetchmail: WARNING: Running as root is discouraged.
fetchmail: Authorization failure on trackrequests@domain.com@mail.domain.com
fetchmail: Query status=3 (AUTHFAIL)

I’ve googled for an answer, but haven’t stumbled across it yet. Thanks for any help,
Mike

When I invoke fetchmail –f /opt/rt4/etc/fetchmailrc, it appends
@mail.domain.com” to the username, whereas the correct user is
trackrequests@domain.com.
<—SNIP—>
[root@xtracker ~]# fetchmail -f /opt/rt4/etc/fetchmailrc

fetchmail: WARNING: Running as root is discouraged.

fetchmail: Authorization failure on trackrequests@domain.com@mail.domain.com

That’s just the logging, it doesn’t actually pass the
@mail.example.com as part of the username. It is there so you can
differentiate problems logging in to multiple accounts on different
mail servers.

             Please keep list traffic on the list.

Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn’t become a monster. Friedrich Nietzsche

Thanks for the quick reply, now to figure out why I get the AUTHFAIL.From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Rob MacGregor
Sent: Wednesday, November 16, 2011 4:00 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] fetchmailrc

When I invoke fetchmail –f /opt/rt4/etc/fetchmailrc, it appends
@mail.domain.com” to the username, whereas the correct user is
trackrequests@domain.com.
<—SNIP—>
[root@xtracker ~]# fetchmail -f /opt/rt4/etc/fetchmailrc

fetchmail: WARNING: Running as root is discouraged.

fetchmail: Authorization failure on
trackrequests@domain.com@mail.domain.com

That’s just the logging, it doesn’t actually pass the @mail.example.com as part of the username. It is there so you can differentiate problems logging in to multiple accounts on different mail servers.

             Please keep list traffic on the list.

Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn’t become a monster. Friedrich Nietzsche
RT Training Sessions (http://bestpractical.com/services/training.html)

  • Barcelona, Spain November 28 & 29, 2011

Shouldnt you have "s around your user name?

the only difference I have in mine is

user “username” pass “password” to user here

tho our mailserver auths with full domain.On 11/16/2011 12:49 PM, mjames@guesswho.com wrote:

Using fetchmail for 1^st time to collect mail from an Exchange server.

Exchange 2010

RT 4.0.1

Centos 5.7

fetchmail release 6.3.21+HESIOD+NLS.

Here’s my /opt/rt4/etc/fetchmailrc:

poll mail.domain.com proto pop3:

user trackrequests there with password ‘cleverly removed’ is kiss
here mda “/opt/rt4/bin/rt-mailgate --url http://xtracker.domain.com.
–queue General --action correspond”

When I invoke fetchmail --f /opt/rt4/etc/fetchmailrc, it appends
@mail.domain.com” to the username, whereas the correct user is
trackrequests@domain.com mailto:trackrequests@domain.com.

If I specify user trackrequests@domain.com
mailto:trackrequests@domain.com in the fetchmailrc file, then
fetchmail turns it into trackrequests@domain.com@mail.domain.com
mailto:trackrequests@domain.com@mail.domain.com. For example:

[root@xtracker ~]# fetchmail -f /opt/rt4/etc/fetchmailrc

fetchmail: WARNING: Running as root is discouraged.

fetchmail: Authorization failure on
trackrequests@domain.com@mail.domain.com

fetchmail: Query status=3 (AUTHFAIL)

I’ve googled for an answer, but haven’t stumbled across it yet. Thanks
for any help,

Mike


RT Training Sessions (http://bestpractical.com/services/training.html)

  • Barcelona, Spain — November 28& 29, 2011

This is what we use (pulling emails from a gmail account, hence the 995 port)
:
~rt/.fetchmailrc:
set postmaster “ronen”
set daemon 600
pool pop.gmail.com with proto pop3 user ‘xx@gmail.com’ there with password ‘XXXXXXX’ is user5 here options ssl

crontab for user rt:
5,15,25,35,45,55 * * * * /usr/bin/fetchmail -d 0 -P 995 -ssl -smtpname xx@gmail.commailto:xx@gmail.com -u xx@gmail.commailto:xx@gmail.com pop.gmail.com -f fetchmail.test 2>&1 > /dev/null

fetchmail.test:

poll pop.gmail.com proto pop3:
username “xx@gmail.com” password “XXXXXXXX” mda “/opt/rt4/bin/rt-mailgate --url http://cm-help --queue CM --action correspond”

RonenFrom: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of 20/20 Lab
Sent: Wednesday, November 16, 2011 23:45
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] fetchmailrc

Shouldnt you have "s around your user name?

the only difference I have in mine is

user “username” pass “password” to user here

tho our mailserver auths with full domain.

Knowledge that I’d like to document for the list. By trial and error, on Centos 5 I’ve found that you should use single quotes if your password contains special characters such as ‘$’. Double-quotes didn’t work. I also found (thx, Google) that in Exchange 2007 plaintext password authentication is disabled by default, but it can be turned on (assuming that POP3 is enabled on Exchange server in the 1st place) MS Exchange Tips: Exchange 2007: POP3 ERR Command is not valid in this state and many others.

Also, I think you can use secure POP3 (port 995) but it seems I would need a version of fetchmail with SSL compiled in. The stock version that comes with Centos 5.7 doesn’t. Nor does it have NTLM compiled in. NTLM can be used with IMAP (secure port 993) if I understand correctly.

[root@tracker ~]# fetchmail -V
fetchmail: WARNING: Running as root is discouraged.
This is fetchmail release 6.3.21+HESIOD+NLS.

Our Exchange server does have OWA (outlook web access), and I’ve found two tools that can access mailboxes via OWA - DavMail and FetchExc.

MikeFrom: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Ronen_Amity@DELL.com
Sent: Thursday, November 17, 2011 3:38 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] fetchmailrc

This is what we use (pulling emails from a gmail account, hence the 995 port)
:
~rt/.fetchmailrc:
set postmaster “ronen”
set daemon 600
pool pop.gmail.com with proto pop3 user ‘xx@gmail.com’ there with password ‘XXXXXXX’ is user5 here options ssl

crontab for user rt:
5,15,25,35,45,55 * * * * /usr/bin/fetchmail -d 0 -P 995 -ssl -smtpname xx@gmail.commailto:xx@gmail.com -u xx@gmail.commailto:xx@gmail.com pop.gmail.com -f fetchmail.test 2>&1 > /dev/null

fetchmail.test:

poll pop.gmail.com proto pop3:
username “xx@gmail.commailto:xx@gmail.com” password “XXXXXXXX” mda “/opt/rt4/bin/rt-mailgate --url http://cm-help --queue CM --action correspond”

Ronen

From: rt-users-bounces@lists.bestpractical.commailto:rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com]mailto:[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of 20/20 Lab
Sent: Wednesday, November 16, 2011 23:45
To: rt-users@lists.bestpractical.commailto:rt-users@lists.bestpractical.com
Subject: Re: [rt-users] fetchmailrc

Shouldnt you have "s around your user name?

the only difference I have in mine is

user “username” pass “password” to user here

tho our mailserver auths with full domain.