CiviCRM Community Forums (archive)

I've found that imap2soap.pl dies when presented with international character sets 

Though is sounds like there is going to be a new, better mechanism for the return channel (http://forum.civicrm.org/?topic=5220) in 2.2, I suspect there will remain many users who will need an updated imap2soap.pl that can handle unicode character sets.  I see that amavisd 2.4.2 uses some new Perl libraries to handle proper encoding of the messages, and I suspect pulling in that code will fix things.

I'm a bit swamped right now, but will try to get to this in the next couple weeks.  If anyone out there is interested in working on this and making a patch/contribution, please replay asap - so we're not both working on this at the same time.

Thanks!
=Fen

It turns out that imap2soap.pl was dying when sending an unencoded MIME body to CiviCRM via the SOAP channel.  I've installed and partially tested a fix (maybe a hack?) that fixes the problem on my systems, though I don't use the message body returned via the back-channel for anything, so I'm not sure this will work in all cases, and this is a known problem with some mailers (see e.g., http://issues.civicrm.org/jira/browse/CRM-2959).

Try the new version available from https://svn.civicactions.net/repos/civicrm/scripts/ and please post if you discover any issues.  There's a "Note:" at the top describing the change, which is on line #338.