Re: smtp server problems && error when sending

[Fernan Aguero <fernan iib unsam edu ar>]

Seems that now I found the culprit. 
As suggested in another thread, it was some messages left in the outbox
that have been causing some trouble.

The odd thing was that a day and a half ago I sent an email to a bad email
address and got this 'Error sending message, child exited 67 (User
unknown.)'. I then deleted the message from the outbox, but now the error
message said something like 'Error, cannot relay'. So i assume the problem
had to do with the recent smtp closing in our network.

Apparently the bad message reappeared in my outbox, I deleted it again and
solved it.
Now for the questions:

Why is it that Balsa writes an outgoing message both to the outbox and to
the sentbox, even though the message is not sent? In the case that the
message fails to be sent, it should not be written to the sentbox
An alternative option would be to follow Eudora's behaviour and merge the
outbox and the sentbox into just one mailbox. This alternative will need to
have flags to know which messages are sent/queued/unsent. This would have
the benefit of allowing for 'resend' or 'mark as unsent' and let us resend
messages.

Is this OK or am i missing something?


On 2001.04.10 10:43 Fernan Aguero wrote:
> Hi!
> 
> I started having problems to send mail using Balsa, although I can send
> messages with pine. 
> The problems started when the IT people decided to block smtp access to
> the outside world for all workstations (except for our main smtp
> server). I have always had Balsa configured to use our main smtp server
> and not to use the local sendmail ... thus this intrigues me. Also, as i
> said, pine, which is configured to use the remote smtp server, works
> fine.
> 
> Any ideas what could be going on with Balsa?
> 
> Thanks in advance,
> 
> Fernan

-- 
Fernan Aguero
Bioinformatics
IIB-UNSAM
fernan@iib.unsam.edu.ar
ICQ 100325972