re: (Pegasus 4.41)
(SMTP).. ISP msg says.. 550 - not authenticated .....OK fair enough,
but *why* is there *no* indication from Pegasus that this has occurred ?
!!! So how do you know it had an error. and the email was not, in fact, sent !!!
Initially, this occurred because I sent an email not realising my new ISP needed SMTP authorisation... (Mea culpa!)
But since Pegasus said the mail was "sent" .. it resulted in a lot of heartache & accusations,
trying to detemine who was right in the chain of events.
...With each party asserting their version of events was right - thus the other must be at fault !
Fortunately, "fisticuffs" was avoided !!! ...but it was heading that way! :-)))
I have since proven that Pegasus does *not* issue a warning message -
By first opening an a/c at Gmail and then sending an email via Pegasus - to myself at Gmail,
... *** with the SMTP authorisation deliberately turned off (temporarily) ***
I watched the whole process very carefully ...
Pegasus did not barf at all and did indeed say the email was "sent".
I then scratched around in the various files, hoping to find a proper system or error log of the "550 error"...
I found a file "6TM4EKU5.CNM" which did indeed, contain the 550 error issued by the ISP's mail program.
But how would I know I should look there? (And this one looks like a work file of some sort anyway).
More to the point... How can I ensure that serious errors such as this are notified to me in some way, please?
And it would be a very good idea, too, for Pegasus to *not* report it was sent, when it clearly wasn't.
NB: Suggesting that it *was* sent (as far as the ISP) ... is not amusing!
BTW, is there a "proper" log file which records this sort of thing? I couldn't find one .. but that might be me.
Possibly I have some combination of settings which precludes me from seeing such messages.
If so, **please** advise what I need to change.
This "failure" worries me . I have no idea, now, of how many other mails did not get sent as intended.
BTW.. My ISP's view is that if Pegasus does not report such an error to the user,
it is in violation of some RFC - tho' I've forgotten which number was specifed.
It is a difficult point to refute!
Please help. I do like Pegasus but I see this as a major failure and it bothers me!.
I cannot see any sense in not ensuring the user is immediately aware that such a
serious error has occurred.
At this pont, I can easily imagine someone suggesting that if I emailed say 5000 people,
with each email resulting in an error, would I then want to be notified, individually,
of every one? A valid point and clearly one would not like that.
But in such an extreme case, the sane thing to do is to log all the errors to a file
and after the last one was dealt with, advise the user (instead of saying message sent)
that... "At least 1 serious error has occurred. Please review error(s) in file xxxxxxxx"
Surely that would be the smart way to handle such things?