Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
There's an error with Sylpheed <= 2.4.3 with Gmail SMTP server that makes Sylpheed bogus when it's default SMTP server is Gmail: The Error Log: [11:30:55] ** LibSylph-WARNING: SSL_read() returned error 1, ret = -1 [11:30:55] ** LibSylph-WARNING: session_read_msg_cb: sock_read: Success [11:30:55] ** LibSylph-WARNING: [11:30:55] Error occurred while sending the message. [11:30:55] ** warning: Error occurred while sending the message. There's a workaround for this error in just released 2.4.4, according to the ChangeLog: ... A workaround for the error which occurs with Gmail SMTP server was made. ... Reproducible: Always Steps to Reproduce: Send email with Sylpheed using GMail SMTP server. Actual Results: "Error occurred while sending the message." Expected Results: Sent
*** Bug 187832 has been marked as a duplicate of this bug. ***
2.4.4 merges fine on x86 stable using the 2.4.3 ebuild and it truly fixes the annoying error with Gmail SMTP. On the other hand, if I enable the spell use flag, I get errors regarding aspell functions: compose.o: In function `compose_create': compose.c:(.text+0xd183): undefined reference to `new_aspell_config' compose.c:(.text+0xd18d): undefined reference to `get_aspell_dict_info_list' <...> Is anyone else getting these errors when renaming sylpheed-2.4.3.ebuild to 2.4.4 and turning the spell use flag on? If not, when why isn't sylpheed-2.4.4 being bumped to the tree?
Fixed in CVS. Thank you for reporting.