Author |
|
BKV Newbie
Joined: 18 October 2007 Location: Russian Federation
Online Status: Offline Posts: 9
|
Posted: 07 June 2017 at 3:10pm | IP Logged
|
|
|
Hello,
What is a right way to process failed recipients status(reason) in direct send mode to multiple destinations?
When smtp.send is used in direct mode in several threads, it is possible to get failed recipients, but how to get a reason why certain recipient failded (does not exist, message size to big, etc) or to get last smtp server response?
Thanks.
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 07 June 2017 at 4:03pm | IP Logged
|
|
|
Hi,
You can use Smtp.MessageRecipientSubmitted event, it's raised for all recipients, both failed and successful. Its ServerStatusMessage property returns the reply from the SMTP server.
Regards,
Alex
|
Back to Top |
|
|
BKV Newbie
Joined: 18 October 2007 Location: Russian Federation
Online Status: Offline Posts: 9
|
Posted: 08 June 2017 at 4:57pm | IP Logged
|
|
|
What will be the totall logic for failed\success status processing in case of direct send to multiple destinations in several threads?
Tracking only Smtp.MessageRecipientSubmitted event is not enought, as message sending could be failed after or before recipient submition to smtp server.
What is a rights way to correctly process status with failed reason in direct send mode for each recipient?
Thank you.
|
Back to Top |
|
|
Alex AfterLogic Support
Joined: 19 November 2003
Online Status: Offline Posts: 2206
|
Posted: 13 June 2017 at 2:22am | IP Logged
|
|
|
There is no ideal solution for direct send. Direct send should only be used as a fail-over backup method when SMTP relay is not available.
You can, however, combine Smtp.MessageRecipientSubmitted event with Smtp.MessageNotSent. The latter will be raised when sending failed at any stage.
Regards,
Alex
|
Back to Top |
|
|