Roughly a week ago, about the time I upgraded to Evolution v1.4.5 via Dropline, my attempts to send Email result in the following message: "Error while performing operation: RSET response error: Interrupted system call"

Logically it seems reasonable to conclude that the new version has a bug, so I've reverted to v1.4.4, which had been working just fine all along, but unfortunately the situation is no better. Interesting, the Email actually does seem to be delivered to the recipient, however, the message gets stuck in the Outbox folder, never goes into the Sent folder, and the only way to clear it is to move it into Trash and then Empty Trash.

This is becoming a nuisance. If anyone knows what the real underlying problem is, I'd definitely be interested in hearing about it. I suspect that it isn't Evolution itself because I had been using v1.4.4 for months without incident, but now even if I am using v1.4.4 I'm getting problems. In theory maybe my ISP's mail server (PacBell DSL) is clamping down hard on all Emails in response to MyDoom, but that's a long shot.

I'm running Slack v.9.1 on my rig, along with Dropline v2.4.2. Your feedback is welcome. Thanks -- J.W.

hmm i think its evolution as every install of evolution is an adventure for its own thats why i moved over to sylpheed-claws :=)
had a lot of such problems with evolution too but maybe you need to update another lib or program for use with evolution 1.4.5 ? did you check it during dropline upgrade?

Well, as part of the Dropline 2.4.2 installation, I downloaded the entire set of all packages relevant to that release. I'll check it again tonight though, perhaps there may have been some subsequent updates that have been released. Thanks for the suggestion -- J.W.

I have been using Evolution 1.2.2 for a very long time (like probably more than a couple of years), and have been very happy with it.

However I have also been getting the "RSET response error: Interrupted system call" error recently.

Interestingly enough I am also on pacbell DSL. More interestingly, is the problem has come and gone for a couple weeks now, and I normally use a mail server for my domain (fej.org) to send email, and it also has had the same error popping up, but even when I switch to use pacbell's email server I get the error.

BLAME IT ON SBC/PACBELL!!!

Here is why I think that -

I've played around and found this to be the case....

It does not matter which email server I send through (pacbell.net or fej.org), the result is the same - if I use my @pacbell.net as the from address, I get the error. I use any @fej.org as the from address, no error.

I don't know how or why anything would care about the from address, but it is definitely related to that.

I'm curious if J.W. has also not done the DSL "upgrade". I have not because I use Linux, and they want to install programs under windows. And I am afraid that I would be forced to switch to using PPPoE (what a mess that would be! and loose my constent net connection, etc.).

Hi jeffgarrett - thanks for your note. I'm inclined to agree with your analysis that Pacbell may be doing something unexpected. Regarding your question about the "upgrade" -- NO, I have not upgraded, mainly because everything was OK the way it was before, and I want to keep things the way they were. I don't have my own domain to play with, but your idea may be a really good clue as to why this may be happening.

FYI - it appears that the RSET error actually may only be a red herring. From what I can tell, the RSET error is thrown after the Email is sent - at least when I sent an Email to my work address, I got the error, but I also got the Email at work the next day. Similarly, my sister reported that my recent Emails have been received multiple times, which corresponds to the multiple Send attempts I made when I saw that error. So, overall, although this error is annoying, I now believe that it does not actually prevent your Emails from being Sent. What you do need to do though is to move them from the Outbox to your Sent folder manually (assuming you want to keep a copy of them). At least for me, the Email just sits in the Outbox indefinitely, until I etiher move it to Trash or Sent. -- J.W.

I too am a Pacbell DSL subscriber and am experiencing this EXACT same problem. At forst I thought it was my Kmail so I tried Evolution...no resolution. Has any of you folks brought this up w/ PacBell and if so, have they offered up any "fix"? I may try contacting them myself this upcoming week but it won't surprise me if the response I get is: "We don't know of any problems at the moment..."...hmm.

I am not pursuing the matter, and I am just using my domain addresses.

I've been planning on abandoning my pacbell account for a very long time, and now I am not only going to give up my email account, but the DSL line. I've had too many problems with them ignoring disputed charges, mis-handling the account in general, and on.... (And I have not gotten credits from the lawsuit either like I should have).

So you're on your own. But as J.W. pointed out (and I had found out before) - the emails do send through, you get the error after it sends. (And apparently in evolution, it only does the first email in the outbox, and you have to clear it to get the next one through).

I just am so surprised though that I get the error when I send through a completely different mail server, and just have the from address as @pacbell.net.... Don't know how that works, but my solution is just to not use @pacbell.net.

The question Tahoe, is if you have done the "upgrade" (which is really a downgrade). If you have not done that, they will not help you until you do. And if you have a true DSL line (static IP and no PPPoE), be aware that I believe that the "upgrade" will force you to use PPPoE, and you will no longer have a static IP. They say there will be no changes in the DSL, but I think they are lying.

Good luck.

I have ameritech (sbc) and have the same problem. try using smtpauth.sbcglobal.net for out going server fixed the problem. It is sbc but they don't admit it. you also might want to check out dslreports.com pacbell forum.

That did my friend. Mucho gracias!..

I want to thank inhaler for the tip in post #9. There was some interesting info on the DSLReports Site, and by changing the Host name to smtpauth.sbcglobal.net in the Outgoing Mail settings, the RSET error disappeared. Thanks for the pointer, inhaler.

However, and this may be either a non-issue or a separate discussion, but I sent a quick "test", nonsense Email to my Yahoo account, and it got screened out as Spam and ended up in the Bulk folder. I tried again by sending myself a realistic, non-spam Email, and it still got filtered out, so now I wonder if the major Email carriers are treating Email originating from this Host as spam. I'll explore this some more this evening, and if I discover anything interesting, I'll report back.

I'll tell you, this is really starting to aggravate me -- I don't want to have to wonder whether my Email is going to work or not, but it seems my ISP has made some changes to their Email servers to transform what should be a simple, basic service into something that's flakey and undependable. I really hate changing ISP's but might be forced to. -- J.W.