Feat request: redeliver with suppression list ignore

[arthurzenika]

We have something that happens quite often on our postal instances : something is wrong on the recipient side (over quota, smtp migration, ssl wrongly configured, etc) so postal rightfully goes into soft fail/hard fail and the email ends up on the suppression list. So far so good. That's a great feature.

But... when the recipient side fixes the problem and we are still in the 30 days "pause" period, we want to redeliver a message or even a test message, but that will be intercepted by the suppression list. What we do is we go and do an SQL query delete from suppressions where address = '[email protected]'; and then go and click "Redeliver message". That seems to fix the problem and we can then (if the older messages are still in the database) go back and redeliver a bunch of failed messages.

The feature could look like : having an "advanced" button (hidden somewhere) that enables a "Redeliver message while ignoring suppression list".

[willpower232]

I think the way to remove someone from the suppression list is to release a held message to them. A message that was held because they were on the suppression list.

It may in fact be a bug if you cannot click on redeliver on an already failed message in order to take them off the list.

[adamcooke]

Yes. Upgrading should resolve the issue.

[arthurzenika]

Can you point me to some code so that I understand the issue and how it was fixed ? (thanks a lot for taking the time answer my questions)

[arthurzenika]

We're looking into the impacts of upgrading. Would upgrading to 2.3.2 be enough ? or do we have to upgrade 3.x ?

[sandrovenezuela]

Hi @arthurzenika

Did you manage to update Postal from version 2.1.4 to 2.3.2?

[arthurzenika]

hi @sandrovenezuela we haven't decided yet if we were to upgrade to 2.3.2 for now or if we have to upgrade to v3 to see a fix to the problem described here. Without further news or info, we will probably upgrade to 2.3.2 in the following days.

[sandrovenezuela]

Hi @arthurzenika,

Thank you for the return.

I tried to update my Postal server from version 2.1.4 to 2.3.2 and I couldn't. When executing the command "postal upgrade 2.3.2" the Docker images were not updated.

Postal continued to work, but in version 2.1.4.

If you could share how the update went, if everything went as expected, that would be great.

Thanks!

[abhilashtekiestech]

@arthurzenika I had the same issue, I resolved it by updating the config parameter default_suppression_list_automatic_removal_days to 0, I don't know if this is present in older version but maybe this will help you