[quote user="bday"]Thanks for the reply, however in answer to the points you raised ...
What did not happen was.... that you said I *should* be notified - but I was *not* notified.
Nor was there a bounce message in my inbox (or anywhere I would normally find one).
Does not mean that was was not one sent, it just means that for some reason it did not get to or stay in your inbox. There are all sort of reasons way a new mail message may go astray through filtering or improper setup where the MAIL FROM address is incorrect.
Yes the .CNM file exists ... I found it by pure chance/diligence ... I did *not* say I saw a new message. I clearly said I located the .CNM file whilst scratching around afterwards.
A CNM file is a new mail message. If it was not located in your new mail directory there are any number of ways that can happen.
You said that "message sent" (which appears in the status bar, and is the *only* information about the operation which is returned to the user) .. just refers to placing the email in the send queue... and has no bearing on the SMTP aspect. I have to say, what on earth is the use of that information to the user? In any event, it is thereby an improper message. It should clearly say "message placed in queue for sending" or something very similar.
Clearly the user is (mis)led to believe that the mail was sent (to the ISPs mailer, of course) always bearing in mind that it could still bounce for other reasons such as an undeliverable address & whatnot.
The point here, **beyond question** - is that Pegasus is informed *immediately* by the ISP that the mail is going nowhere and Pegasus does *not* ensure that the user is made aware of that serious fact. How much clearer can I be?
I have no idea why you have a problem. Pegasus Mail is a mail system with a mail client to read and create mail and a separate mail system based on queues. There are all sorts of ways the the mail can be actually sent to the SMTP system; the Mercury Netware queue, the Mercury/32 User Defined Gateway or the built-in mail user agent. In all cases the when you hit send in the editor you are sending the mail message to one of these queues. With the mail gets to the queue the Pegasus Mail lets you know is was successfully sent to the queue.
When using the built in mailer you will see the mail being actualy sent to the SMTP host on the bottom of the screen and it shows the progress of the sending. When you have set Pegasus Mail to send immediately all that means is the mail is sent to the built-in mailer queue (HOME mail directory) and the sending system is immediately triggered.
Surely you can see how serious/important this is?
No I do not.
And - tho' I thought it was plainly obvious - that is the "hole" I've been referring to.
I summarise:
- there is *no* advice of any kind from Pegasus, that this has occurred. Yet Pegasus was aware *immediately* that the email would not be sent anywhere.
Correct, there was a email address that was bad but the form was correct.
- there is *no* bounce message
That one I disagree. You may not have seen it but when the SMTP hosrt bounces a message is sends it back the the sendere. Now if you are using a bad address for sending (i.e.the SMTP MAIL FROM: address) then the sending server may send it back to the wrong address but there will be a bopunce message.
- The user is left believing (incorrectly) that the mail has been sent - meaning of course, to the ISP and beyond.
I'm not so sure about that. The sender must have seen the message going to the SMTP host and they know it got that far at least.
Finally. This cannot be palmed-off to the ISP ... Pegasus has been properly informed by the ISP that the email is unacceptable for sending. It is clearly the duty of Pegasus - and no-one else - to correctly inform the user that the email was faulty & will not proceed further. Together with the reason (that the ISP correctly gave), for that.
No, the SMTP host bounced the mail back to the sender. If you are using a normal POP3 system that means it goes to your POP3 mailbox. This assumes it does not fail when sending to the SMTP host. In this case there will be an error messge with the connection to the SMTP host.
Why are you "fighting" this so??? Surely it is glaringly obvious the user is left misinformed ... Is that the state you want him/her to be left in?
I disagree. There are thousands of Pegasus Mail users that do not find this to be a problem at all. In the past 15 or so years I belive you are the second one to even bring this up.
I have to say I am very disappointed in the way this is progressing. No reasonably sane person would consider this as not being... (a) serious & (b) a bug.
It's neither serious or a bug. Pegasus Mail is operating IAW the RFCs in the sending of the mail. If it fails there will either be an immediate error message at the time of sending or a bounce message from the SMTP host. Obviously we are not communication so I'll leave this for others to handle.
Barry Day[/quote]