Version-Release number of selected component: evolution-3.6.2-3.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: camel_internet_address_encode_address executable: /usr/bin/evolution kernel: 3.6.9-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #4 camel_internet_address_encode_address at camel-internet-address.c:447 #5 internet_address_encode at camel-internet-address.c:87 #6 camel_mime_message_set_from at camel-mime-message.c:671 #7 spamcop_report at rspam.c:608 #8 rspam_command at rspam.c:315 #9 rspam_action_do at rspam.c:827 #10 g_simple_async_result_complete at gsimpleasyncresult.c:775 #11 complete_in_idle_cb_for_thread at gsimpleasyncresult.c:843 #15 g_main_context_iteration at gmain.c:3351 #16 gtk_main_iteration at gtkmain.c:1264
Created attachment 662942 [details] File: backtrace
Created attachment 662943 [details] File: build_ids
Created attachment 662944 [details] File: cgroup
Created attachment 662945 [details] File: core_backtrace
Created attachment 662946 [details] File: dso_list
Created attachment 662947 [details] File: environ
Created attachment 662948 [details] File: limits
Created attachment 662949 [details] File: maps
Created attachment 662950 [details] File: open_fds
Created attachment 662951 [details] File: proc_pid_status
Created attachment 662952 [details] File: var_log_messages
Thanks for a bug report it seems like evolution-rspam passing incorrect address when creating a message, and camel aborts on it. I'd start in evolution-rspam, thus I'm moving it there.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.