Do you see entries in DelayShowDB for this sender/recipient tuple?
You mentioned having DelayMD5 enabled. Try unsetting it/setting it to 0
while you troubleshoot this issue.
I wonder if ASSP's attempts to write to the delaydb for this particular
sender/recipient tuple is failing for some rea
set 'DelayLog' to the highest level and watch the log
Thomas
DISCLAIMER:
***
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to w
DelayEmbargoTime, DelayWaitTime and DelayExpiryTime are all at their
defaults: 5 minutes, 28 hours, 36 days.
It's definitely not retrying within the 5 minute DelayEmbargoTime, and
yes, it seems to be a ~25 minute interval between retries.
On 5/27/2021 5:18 PM, Dossy Shiobara via Assp-user wro
What's your DelayEmbargoTime set to? The default is 5 (minutes).
What's your DelayWaitTime and DelayExpiryTime set to? The defaults are
28 (hours) and is 36 (days), respectively.
It looks like the sender is retrying after ~25 minutes.
On 5/27/21 12:06 PM, Scott MacLean wrote:
May-27-21 00:
Hi Thomas,
That's what I thought as well, and you are correct - it changes for each
email, so every email is unique, and should rightly be delayed. However,
subsequent ATTEMPTS by the sending server to send each email are also
being delayed, over and over again until the sending server finally
The reason is simple. The sender address changes in every mail (SRS0+
080cfd88caf4c8dd.) because the (in this case) sensless SRS extension
is used.
If the sender address changes, the delay hash changes and everytime a mail
is send, it is the first time the sender is seen by assp.
'noDelay' sh
