As one can see the program terminates at message 195. I examined this message and found that it was a spam message that contained no "To:"-Field:
Subject: Former EMI Record exec.goes public
Date: 15 Feb 00 7:36:25 PM
From: grundle82@email.com
Could this lead to the crash of the program? After removing this message Althea run successfully through all messages and worked correct as far as I could see.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did find out at least one cause of the infamous Aborted message. If you read past the begining of a string with substring (like stringname.substr(-1,100))
it will do that... So it sounds likely that a missing to command might do that. However, I believe that the SMTP specs say that a message MUST have a to line.... so while it would be nice to fix this, it isn't a top priority...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sorry I thought I put that in the docs... run althea -h to get info in debugging info. (-v for some and -V for a lot.)
let me know if you figgure out what was wrong. I'm gearing up to start working on some bugs again now that I'm back at school....
I used the -V flag to get the following result:
S: * 194 FETCH (UID 4505)
S: a009 OK FETCH completed
S: * 194 FETCH (FLAGS (\Seen))
S: * 194 FETCH (FLAGS (\Seen))
S: a194 OK FETCH completed
S: a194 OK FETCH completed
S: * 195 FETCH (BODY[HEADER] {817}
S: * 195 FETCH (BODY[HEADER] {817}
S:
S:
S: a195 OK FETCH completed
S: a195 OK FETCH completed
C: a009 fetch 195 UID
S: * 195 FETCH (UID 4507)
S: a009 OK FETCH completed
S: * 195 FETCH (FLAGS (\Seen))
S: * 195 FETCH (FLAGS (\Seen))
S: a195 OK FETCH completed
S: a195 OK FETCH completed
Aborted
As one can see the program terminates at message 195. I examined this message and found that it was a spam message that contained no "To:"-Field:
Subject: Former EMI Record exec.goes public
Date: 15 Feb 00 7:36:25 PM
From: grundle82@email.com
Could this lead to the crash of the program? After removing this message Althea run successfully through all messages and worked correct as far as I could see.
I did find out at least one cause of the infamous Aborted message. If you read past the begining of a string with substring (like stringname.substr(-1,100))
it will do that... So it sounds likely that a missing to command might do that. However, I believe that the SMTP specs say that a message MUST have a to line.... so while it would be nice to fix this, it isn't a top priority...
Logged In: YES
user_id=28252
OK, I think this is fixed. It was the result of using a
string.substring (or string[]) where the substring was past
the end of the string...