Hi Support - can we get a better method of dealing with emails when they fail to send?
The situation is that when emails fail to send they just sit in a folder called UNSENT on the Aware dir and you get an Error in system.log... these items are not monitored or easily monitored, would be way better to have an instance created that we can fire rules off, then they can be easily checked by a user just logging in and checking a log with a query etc. Or we can send a notification to the user trying to send, etc.
Is there a better way we can configure some solution here (failure rules perhaps)? Has anyone done anything good around this?
(just discovered a client system not sending email for past 3 weeks - ouch)
When emails don't send
When emails don't send
Rod. Aware 8.6 (latest build), Developer Edition, on OS Linux (Ubuntu) using GUI hosted on AWS EC2, MYSQL on AWS RDS
-
- Posts: 7532
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Re: When emails don't send
What do you mean "instance created"? Could you please elaborate?
Aware IM Support Team
Re: When emails don't send
I considered this but never implemented it:Is there a better way we can configure some solution here (failure rules perhaps)? Has anyone done anything good around this?
- Having a process that runs on a schedule to look for files in the directory you mentioned
- Count those records and store them in system settings.
- Upon login of certain users, display a message if there are unsent emails that were counted and stored in System Settings.
Tom - V8.8 build 3137 - MySql / PostGres
Re: When emails don't send
Create an instance in the database in a preset table/BO that we can write rules on.
For example, let's say there is a default BO called "EmailLog" (similar to SystemSettings and RegularUser it exists by default or you can create it) then when an email fails an instance is created in this Object. It can be as simple as Timestamp, LoginName, From, To, Subject so when a fail happens it gets logged in that BO.
This way we can write rules to deal with failures in an automated fashion, for example we could write rule IS NEW THEN send an email to login name "Your email to xxx on zzz with the Subject aaa has failed to send, please check all details and send again"
It would be even better if we got an error code for why it didn't send:
100 = no To address
101 = no From address
102 = could not authenticate with mail server
103 = time out (attachment too large)
etc
For example, let's say there is a default BO called "EmailLog" (similar to SystemSettings and RegularUser it exists by default or you can create it) then when an email fails an instance is created in this Object. It can be as simple as Timestamp, LoginName, From, To, Subject so when a fail happens it gets logged in that BO.
This way we can write rules to deal with failures in an automated fashion, for example we could write rule IS NEW THEN send an email to login name "Your email to xxx on zzz with the Subject aaa has failed to send, please check all details and send again"
It would be even better if we got an error code for why it didn't send:
100 = no To address
101 = no From address
102 = could not authenticate with mail server
103 = time out (attachment too large)
etc
Rod. Aware 8.6 (latest build), Developer Edition, on OS Linux (Ubuntu) using GUI hosted on AWS EC2, MYSQL on AWS RDS
-
- Posts: 7532
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Re: When emails don't send
Yes, please. I have the exact same challenges with emails.
Thanks.
Thanks.