You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be some race condition going on possibly where a connection gets used by a different send request and I wonder if this explains also knadh/listmonk#300 (although I am not using listmonk, only smtppool).
I only send to only one address, but there are many send requests coming in in parallel sometimes.
The text was updated successfully, but these errors were encountered:
But I see also that there was a commit done - 6f93552
, which I am not using I think. Perhaps that is the fix actually and perhaps I should just upgrade
Sometimes, when there is a lot of sending going on I get a "503 Sender already specified" from pool.Send() when the pool has been instantiated with
There seems to be some race condition going on possibly where a connection gets used by a different send request and I wonder if this explains also knadh/listmonk#300 (although I am not using listmonk, only smtppool).
I only send to only one address, but there are many send requests coming in in parallel sometimes.
The text was updated successfully, but these errors were encountered: