I would say working great, when compared to the pop3 connector for
exchange which is a complete PITA.
It also allows me to forward the mail via SMTP into the exchange
server so the exchange will respect the spam headers from Spam
Assassin. I have the exchange box firewalled off and only accepting
traffic from the internal linux box running fetchmail
I guess the Microsoft pop connector does not let you filter the mail
in exchange because the "Intelligent Message Filter" in exchange only
works on SMTP traffic not pop connector traffic.
Over all using fetchmail is a huge improvement and I can have it
check my mail box once every 5 minutes instead of every 15 minutes
which is the min for exchange. I probably will end up creating a
mail box for each user on the mail server and dropping the catch all.
I would eliminate exchange completely if our CRM would work with
IMAP. Don't get started on the CRM though. :)
A couple more questions:
if I want to check 20 pop accounts, should I run fetchmail in daemon
mode or via a cron. Is there a way to get it to pause for a time
between each poll?
Thanks for all the help with everything,
Andrew
On Feb 9, 2007, at 9:27 PM, Matthias Andree wrote:
> "Andrew N. Gray" <an...@gr...> writes:
>
>> I have fetchmail configured and working great. It fetches the mail
>> from a pop catch all and sends it out via SMTP to our exchange server
>>
>> The issue I have is with a couple of mailing lists that are delivered
>> via BCC
>
> So you call that "working great"? I wouldn't.
>
> fetchmail can only handle this if the catchall account conforms to
> http://home.pages.de/~mandree/mail/multidrop - else you need to
> take any
> "mailbox fetching" (thus, fetchmail) out of the loop and do direct
> SMTP. That's beyond this list's scope, pointers are Postfix and
> perhaps
> Exim.
>
> --
> Matthias Andree
|
