
Aug. 2, 2019
6:50 p.m.
So it has taken me a couple of days regarding the right implementation.
According to me, I think a new command which takes all the Address
instances and in each instances checks which tuple of bounce_info
have disabled
attribute true ( more regarding these attribute in this pr ). If it sees the disabled
attribute of a tuple to be true it will roughly:
- Send a warning
- Increase warning counter
- Check with the threshold
- Updates last_warning_sent timestamp value
The newly updated tuple ( with the updated counter and timestamp ) will be stored again. I will add it to a cron job. Is the above implementation thought correct? Am I missing