-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/27/2017 01:08:02 PM Sat, Albrecht Dreß wrote:
Hi Peter:
Am 27.05.17 18:48 schrieb(en) Peter Bloomfield:
With my AT&T/Yahoo server, I more often get errors like "connection lost", or "transient
error" with something about "internal server error". As far as I know, these also require no
action except resending,
This is at least what RFC 5321, Sect. 4.2.1. says...
BTW, now that everything runs in background, I think I should adjust the
timeouts according to RFC 5321, Sect. 4.5.3.2., which may also ease your issues.
but currently I first have to clear the flag.
The attached patch clears the flags with these two types of error. Does that
look reasonable? Is there a better way to use the new error-handling code? All
feedback welcome!
I think this is a *really* useful change! I do not have these issues (my ISP
is bad, but apparently not /that/ bad...), but the use case you describe makes
sense.
OK, I'll commit it.
The next step would now be an automatic re-send of the queue, as requested by
user John Jack Doe, probably with an option to disable it if the user prefers
to control it manually.
That will take a bit of care. We'll need to be able to cancel the timer if the
user queues some mail for sending, b/c that could mean that the user is
preparing messages to be sent out in a single batch--I've used it that way to
reach a number of people who need to be notified as close to simultaneously as
possible. I'm sure there are other nuances, too.
Best,
Peter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlkpuI8ACgkQH1/UtbkqdPWIFACggubFaP3mW34ZVJ1DlyadV7mO
B3kAniBBShshpQrkHXhnxp+mSMPXMW5t
=LI3i
-----END PGP SIGNATURE-----
_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list
