After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 226884 - Not sending mail - least not consistently,
Not sending mail - least not consistently,
Status: RESOLVED DUPLICATE of bug 226112
Product: evolution
Classification: Applications
Component: Mailer
pre-1.5 (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 226885 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-06-24 14:44 UTC by Mike Gifford
Modified: 2002-06-24 19:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mike Gifford 2002-06-24 14:44:57 UTC
Not Zed - Thanks again for your assistance on this issue..

As per your request:

gdb evolution-mail
(gdb) r
 (and wait a while while it starts up)

Then when it gets into that state, go back to gdb and type ctrl-c and
then
(gdb) thread apply all bt

And send me the output of that.  Actually it would be better to create a
bug on bugzilla.ximian.com and assign it to notzed@ximian.com and attach
the info there.

The results are:

[New Thread 11276 (LWP 32082)]
EBook-Message: Use score for "pgsadmin@web.ca" is now 13.222455
sending : EHLO [192.168.1.21]
received: 250-tomts19-srv.bellnexxia.net
received: 250-HELP
received: 250-PIPELINING
received: 250-DSN
received: 250-8BITMIME
This server supports 8bit MIME
received: 250 SIZE 10485760
sending : MAIL FROM: <mike@openconcept.ca>
received: 250 Sender <mike@openconcept.ca> Ok
sending : RCPT TO: <pgsadmin@web.ca>
received: 250 Recipient <pgsadmin@web.ca> Ok
sending : DATA
received: 354 Ok Send data ending with <CRLF>.<CRLF>
sending : \r\n.\r\n
[New Thread 12301 (LWP 32219)]
received: +OK POP3 calcutta2.flora.ca v2000.70rh server ready
sending : CAPA
received: +OK Capability list follows:
received: TOP
received: LOGIN-DELAY 180
received: UIDL
received: STLS
received: USER
received: SASL LOGIN
received: .
sending : USER mike-pop
received: +OK User name accepted, password please
sending : PASS xxxx
received: +OK Mailbox open, 0 messages
sending : STAT
received: +OK 0 0
sending : QUIT
received: +OK Sayonara
setting as body text:
-----
<PRE>http://ca.news.yahoo.com/020622/6/n86j.html</PRE>
-----
impl_event = delete
impl_event = command_after
impl_event = delete
EBook-Message: Use score for "carol@flora.org" is now 147.000000
received: 421 tomts19-srv.bellnexxia.net Lost connection to [64.230.112.225]
sending : MAIL FROM: <mike@openconcept.ca>
sending : RCPT TO: <carol@flora.org>


Program received signal SIGINT, Interrupt.
[Switching to Thread 8201 (LWP 30590)]
0x40fc3b3e in __select ()
   from /lib/libc.so.6
(gdb) thread apply all bt

Thread 5 (Thread 3076 (LWP 21187))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 pthread_cond_wait
    at restart.h line 34
  • #3 e_msgport_wait
    at e-msgport.c line 198
  • #4 thread_dispatch
    at e-msgport.c line 517
  • #5 pthread_start_thread
    at manager.c line 284

Thread 4 (Thread 2051 (LWP 21057))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 pthread_cond_wait
    at restart.h line 34
  • #3 e_msgport_wait
    at e-msgport.c line 198
  • #4 thread_dispatch
    at e-msgport.c line 517
  • #5 pthread_start_thread
    at manager.c line 284

Thread 3 (Thread 1026 (LWP 21056))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 pthread_cond_wait
    at restart.h line 34
  • #3 e_msgport_wait
    at e-msgport.c line 198
  • #4 thread_dispatch
    at e-msgport.c line 517
  • #5 pthread_start_thread
    at manager.c line 284

Comment 1 Jeffrey Stedfast 2002-06-24 18:24:28 UTC
it looks like your SMTP server (or tcp connection?) is pretty flaky
from the looks of this bug report and your other bug report about the
same thing (which seemed to get disconnected at a different point).
Comment 2 Jeffrey Stedfast 2002-06-24 18:24:46 UTC
*** bug 226885 has been marked as a duplicate of this bug. ***
Comment 3 Mike Gifford 2002-06-24 19:56:21 UTC
I hear you that it is likely something messed up with their SMTP server.

However, there are 60,000+ users using this SMTP server and I've
talked to lots of their techies in the last two weeks.  No similar
reports of problems have been reported.  They have no known problems
that they know of or that interrupt the use of all of the users
sending out in a windows platform...

Also, there needs to be a better way to deal with smtp errors than
evolution presently manages.  If it doesn't succeed sending it should
at some point time out and try again..  

Finally a related point - evolution should save messages that are
being edited every minute (like you do) AND also when it is sent (in
case the sent fails and bugs up evolution)..  this way I wouldn't be
loosing the last minute of my email every time this happens.

Mike

ps.  Really like evolution & Ximian..  This is the first major problem
I've had since I started using it..  Wanted to support it and thus
became a Red Carpet Express member..  I'm thinking of dropping my ISP,
but don't think this should be required to use evolution.
Comment 4 Jeffrey Stedfast 2002-06-24 19:58:46 UTC

*** This bug has been marked as a duplicate of 226112 ***