How can I fix this code? Not Sending the Email when triggered - if-statement

I am struggling to get this code to Send my Email. I have the loop established so the 6th column is read the 2nd and 3rd rows, identify if they are true and false, then goes through the steps to send an email. Please comment if you figure out why the flow is not working. Thanks! code with a while and if loop
I want the Email to be sent to only the last recipient filled in the list. Here is a screenshot of the sheet to read from. sheet to be pulled from

Related

Request Read Receipt with Python/Exchangelib?

My first post so please excuse any ignorance on my part. I have had great success with email automation using Exchangelib. I am curious to know if there is a configuration option to request a read or delivery receipt?
I have spent the last few days researching options but not having any luck.
You should be able to set the Message.is_read_receipt_requested boolean field. When set to True, you will get a read receipt when the is_read field of the received message is set to True, unless the receiver explicitly disabled sending read receipts.

How can I know whether user clicked on notification or not?

my tried wayI am trying to know when i am sending push notification to users they will open the notification or not. i am able to get the number of sent notification or number of successful and failed notification but i am unable to get the user response record.I am using aws sns push notification with fcm
it's easy!
Just put a little code in notification code, when user clicked the notification it gets the value from the database which is 0 when you start sending the notification, and add +1 in it and again store that value in the database.
This is the simple way you can check how many people open your notification.
Regards,
Sameer Rehman

Receiving complaints for SES transactional emails - are TiS notifications generated by filters?

We're doing everything we can think of to limit the number of complaints we receive and will immediately remove anyone who marks us as junk that does not need to receive our emails. However, the last handful of complaints we've received have come from transactional emails of people who are receiving our company's services and NEED to receive everything we send transactionally as a critical part of our service. (e.g. We are booking their travel on their behalf and we need to send them verification emails to confirm their booking details.)
We're assuming that most of these complaints are somehow either false positives or are being done on accident. One customer confirmed that they did not click the junk mail button but it ended up in their junk folder and they moved it to their inbox. Some questions:
Can a TiS complaint be triggered by any means other than the user manually marking an email as junk in their email client? (Can automatic spam filters trigger this complaint? AWS documentation specifies only clicking the junk button.)
Besides contacting each individual personally, what would you suggest we do? Our complaint rate is continuing to rise even though we are taking action on every one.

I receive the email notificaction instantly(VTiger doesn't wait for the date to arrive to send it)

When I create a ToDo(or an event), and activate the "Send Notification" box, and set a future date for it to begin(for example in two days), I receive the email notification instantly(VTiger doesn't wait for the date to arrive to send it).
I've tried to find answers by myself and online, but I haven't been able to solve it. Mi cron is working OK, and I have my correct timezone configured in config.inc.php.
I'm using Vtiger CRM 6.2.0.
Do you have any idea of why this is happening, or what can I do to find out or solve it?
Thanks for your time!
It seems that this is the correct way in which VTiger works. Send notification tells the user that a ToDo was created and assigned to him.
Im not sure how can I email a user when a task is due.

Subscribing to updates via Faye/websockets results in duplicate records

Update
Demo: http://jsbin.com/ogorab/311/edit
I'm trying to build a simple chat room that updates in realtime using Faye/Websockets. Messages are posted using regular REST, but there is also a subscription via Faye to /messages/created, which uses store.pushPayload to push the new messages.
Now the following scenario happens and I can see where it goes wrong but I have no clue how to solve it:
User submits chat message
ChatController handles the submit, calls createRecord with the chat message, and subsequently #save
The chat messages is instantly shown in the chat (triggered by createRecord). Note that no id has been assigned yet.
A REST request is send to the server
The server first publishes the message to Faye
The server responds to the REST request
Before the ajax call is resolved, a message has arrived at /messages/created
The message is again inserted in the view (it should be merged with the original message of course, but that one still hasn't been assigned an id)
The ajax call is resolved, and the id of the original message is assigned.
This results in duplicate messages, in the following order:
[message via createRecord, will resolve via ajax response]
[message inserted via pushPayload/Faye]
I hope you can understand so far. A solution would be to have Faye wait for the save call to resolve before pushing the payload. Unfortunately I don't have a reference to the record that is being saved (happens in a controller, faye subscription is set up in ApplicationRouter).
Also I would like this to work in a generic way:)
Finally found a solution for this, but other suggestions are still welcome.
Turns out that Store#didSaveRecord updates the id after the record is saved. By overriding this method (and then calling super, in that order), we can first check if a record for that id already exists:
App.Store = DS.Store.extend
didSaveRecord: (record, data) ->
# This will remove any existing records with the same id
#getById(record.constructor, data.id)?.unloadRecord()
#_super(record, data)