I had to use fetchmail because of wanting to retrieve mail from IMAP accounts, and fond it very well designed. However I don't know if that solve your problems.
Cheers,
Carl
Fox Sterling wrote:
Not sure if feature requests should be sent to this list or development list. I started using the FetchPOP in order to filter mail from my ISP account, which does not seem to have any form of SPAM protection system. I noticed that the FetchPOP does not have a way to specify the recipients. Right now I have to enable the FetchPOP, then do a FetchedFrom in the transport and add my ISP's domain name. There are 2 problems I have with this. I do not want to declare the ISP domain name, and the excess configuration in the transport seems very error prone. What I would like to see is a single child element added to the <fetch> element, <recipients>. This would be a comma seperated list of recipients to use as the recipient list as if it came from the RCPT TO SMTP command. This would allow me to control where it goes before it enters the root stream, and would not requre the domain name to be specified. If the <recipients> is not provided, it gets the list as it does now.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
