Sent from my iPhone

> On Dec 20, 2023, at 2:14 PM, Marco Moock <m...@dorfdsl.de> wrote:
> 
> Am 20.12.2023 um 14:04:41 Uhr schrieb Pocket:
> 
>> I have emails from other lists and personal email from other with the 
>> same time frame
>> 
>> So in this case it was not because the email box/account was not
>> available.
> 
> Are you really that thick as a brick that you don't understand that
> this is specific to the sender IP, in that case the Debian mailinglist
> server?
> 

Ignoring your personal attack,  has it occured that if spectrum blocked bendel 
that i would lose all my subscribed lists .  Which i have not.

As others here received the same bounce ails could it also be yrue that the 
user list rmails look like spam to the ISP?

This issue seems to only be associated with this list only

>> That only leaves the number of sessions that were opened.
>> 
>> How many sessions were opened sending that one email?
> 
> Only one can be opened for that.
> But multiple connections might exist for multiple mails, maybe also for
> different users.
> 
> Your ISP blocks those with a hard error and that is the fault.
> 
> There is no hard limit in the SMTP RFC.
> Your mailbox provider is the fault here.
> 
>> second question does bendel.debian.org handle all the mail for all 
>> debian lists?
> 
> There are other servers too that handle some mailing lists (e.g. for
> bug reports), but bendel handles the "normal" Debian mailing lists that
> end with @lists.debian.org.
> 
> 
>> And could that be the reason to multiple sessions were opened from 
>> debian list servers?
> 
> No, the reason is that SMTP doesn't specify that only a special
> amount of connections can be established, but your provider enforces
> that and give back a hard fail (5xx error).
> If your mailbox provider handled that properly, it gave a 4xx error, so
> bendel tries it again after a certain amount of time.
> 
>> If that is the case then why no bounces occurred for the other lists
> 
> Ask your mailbox provider for the logs to find out, we can't tell you.
> 

Reply via email to