Ok, smk has come to the rescue. Recently he made some firewall changes for the topp office filters and changed things so that our computers couldn't make outgoing port 25 connections unless it was to our mailserver. Since those who are using mutt use their local postfix to send out mail, they use their Internet connection instead of our mail server and so their messages were being blocked.
To fix this he is modifying the rules to be less restrictive. This still leaves the question of why were we getting that unicode error from listen. I guess this was a result of some other problem that we should keep an eye out for. But for now, things are back to normal :) Chris Chris Abraham wrote: > Sometime during the last 48 hours, something has changed on theman such > that listen is no longer successfully receiving mail sent from mutt. As > far as I know, this has only affected rmarianski and jhammel, who use > mutt. By looking at the headers of a mutt message compared with my > Thunderbird client, the only notable difference I can see is the lack of > this from the mutt headers: > Content-Transfer-Encoding: 7bit > > The error trace produced at the time these messages are sent seems to be > something like: > > 2007-05-04T14:18:08 ERROR Zope.SiteErrorLog > http://www.openplans.org/send_listen_mail > Traceback (innermost last): > Module ZPublisher.Publish, line 115, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 41, in call_object > Module Products.listen.utilities.list_lookup, line 374, in __call__ > Module Products.listen.utilities.list_lookup, line 238, in deliverMessage > Module Products.listen.content.mailboxer_list, line 193, in > manage_mailboxer > Module Products.listen.content.mailboxer_list, line 212, in adaptMail > Module plone.mail, line 19, in decode_header > Module email.Header, line 205, in __unicode__ > UnicodeDecodeError: 'iso2022_jp' codec can't decode byte 0x8d in > position 0: illegal multibyte sequence > > > This behavior can't be reproduced upon a local installation. So questions: > > Why did this just start happening? > I might speculate that it may have something to do with the recent > tasktracker rollout on theman. > > Why just mutt? > Maybe because of the absence of that header, though I haven't looked > into it. > > How do we fix it? > > > Chris > > > -- > Archive: > http://www.openplans.org/projects/listen/lists/listen-dev/archive/2007/05/1178305009928 > To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED] > Please contact [EMAIL PROTECTED] for questions. > -- Archive: http://www.openplans.org/projects/listen/lists/listen-dev/archive/2007/05/1178308997830 To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED] Please contact [EMAIL PROTECTED] for questions. X-pstn-neptune: 992/375/0.38/24 X-pstn-levels: (S:99.90000/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 4 (1.5000:1.5000) s gt3 gt2 gt1 r p m c X-pstn-addresses: from <[EMAIL PROTECTED]> [294/10]
