l as existing attached files, may be confidential and
> privileged. Use or disclosure by anyone other than an intended recipient is
> not authorised.
> If you have received this message by error, you are kindly requested to
> delete it and notify the sender. Thank you for your cooperat
hank you for your cooperation.*
>
> ------
> *From:* Alexander Malysh on behalf of Alexander
> Malysh
> *Sent:* 22 May 2020 15:38
> *To:* Paulo Correia
> *Cc:* users@kannel.org
> *Subject:* Re: Unable to deliver DLRs: "Couldn't fetch..."
>
__
From: Alexander Malysh on behalf of Alexander Malysh
Sent: 22 May 2020 15:38
To: Paulo Correia
Cc: users@kannel.org
Subject: Re: Unable to deliver DLRs: "Couldn't fetch..."
Hi,
do you have any errors except couldn’t fetch? mostly it’s because either kannel
ran
Hi,
do you have any errors except couldn’t fetch? mostly it’s because either kannel
ran out of filedexfriptors or
because receiving server is unable to accept that much connections from kannel
(or both).
Check you kannel log file for other errors.
Thanks,
Alex
> Am 21.05.2020 um 14:35 schrie
Hi fellow kannel users,
We've been using kannel for quite some years and on the latest months we've
seen an issue when processing DLRs on high traffic.
We send the messages to kannel using HTTP with the /cgi-bin/sendsms adding the
dlr-url and dlr-mask values as always have been sending.
When ka
