On Fri, March 3, 2006 3:32 pm, Derrick MacPherson said:
>> I have nearly 5000 listers on about 110 lists and my initial reaction is
>> that this would be a very bad idea. It seems to me that it would make the
>> list itself seem less involved and less a perceived service. Maybe I'm off
>> the mark, but why would you want to do this?
> It's completely internal lists, they've broken for our exchange users,
> the mail is delivered into local traditional mailboxes, and a 3rd party
> POP connector pulls the mail from the mail server to the exchange
> server, and those messages are not getting delivered as because the To:
> field is not what it's looking for. I *might* just turn the lists over
> to mailman as I know it supports this feature, but I've got a lot of
> lists to convert etc.. Was hoping for something else before that
Ah, that makes sense now. Okay, what about using fetchmail. The syntax is:
poll mail.domain.com and options no dns
user 'username' therre with password 'password' is 'username' here
If you could set it up that way, wouldn't you then be able to have procmail
process it and add a new TO: field to the correct user? Something like:
| formail -tb -I "To: $LOGNAME"
If you put this in the .procmailrc file for each user, the TO: header field
would contain the correct information before Exchange go hold of it... Since
I didn't follow your topology very well and don't have any more time (I
should have left 10 minutes ago)... Senior moments are also involved.
_/ _/ _/ _/_/_/ ____________ __o
_/ _/ _/ _/ _/ ____________ _-\<._
_/_/ _/ _/_/_/ (_)/ (_)
_/ _/ _/ _/ ......................
_/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com
Senior Consulting Sys/DB Analyst
My Thoughts on Terrorism In America right after 9/11/2001:
A right is not what someone gives you; it's what no one can take from you.