Re: outgoing smtpd: Too many recipients
On Dec 17 09:21:58, gil...@poolp.org wrote: On Tue, Dec 17, 2013 at 09:17:27AM +0100, Jan Stary wrote: On Dec 17 08:35:28, gil...@poolp.org wrote: On Mon, Dec 16, 2013 at 07:08:17PM +0100, Jan Stary wrote: I am using smtpd as my mail server on a network where the relay server often replies with 4.5.3 Too many recipients Indeed, I was sending messages with a lot of recipients (a group of students). Is there a way in the smtpd configuration to specify that a message with N recipients should be broken into N individual messages? Why so ? Because if not, the message is rejected with 4.5.3. Messages with certain number of recipients just cannot be sent through this relay. Oh, the entire message is rejected ? That's kind of violent... There's a tweak to limit the number of recipients but if we could avoid it, it would benefit everyone. Does it prevent OpenSMTPD from sending to the recipients it has submitted already ? The relay disables my mailserver for some fixed time. No messages from me will be accepted during that time. The relay disabling code has been removed, this should no longer happen to you with last snapshot. We will release 5.4.2 in a few days to fix the first shortcomings we experienced from 5.4.1 and this will be part of it. With the lates snapshot (i386) this is still happening. After a relay rejects me because of too many recipients, my OpenSMTPd disables that route. Here is the messages for ~120 recipients, accpeted my my OpenSMTPd: Jan 8 09:19:32 biblio smtpd[6960]: smtp-in: New session 1908b342ff9f6ed5 from host localhost [127.0.0.1] Jan 8 09:19:32 biblio smtpd[6960]: smtp-in: Accepted message 045d1768 on session 1908b342ff9f6ed5: from=jan.st...@fit.cvut.cz, to=bartu...@fit.cvut.cz, size=5543, ndest=1, proto=ESMTP Jan 8 09:19:32 biblio smtpd[6960]: smtp-in: Accepted message 045d1768 on session 1908b342ff9f6ed5: from=jan.st...@fit.cvut.cz, to=brkam...@fit.cvut.cz, size=5543, ndest=1, proto=ESMTP [...] Jan 8 09:19:32 biblio smtpd[6960]: smtp-in: Accepted message 045d1768 on session 1908b342ff9f6ed5: from=jan.st...@fit.cvut.cz, to=daniel.vas...@fit.cvut.cz, size=5543, ndest=1, proto=ESMTP Jan 8 09:19:32 biblio smtpd[6960]: smtp-in: Closing session 1908b342ff9f6ed5 Here we try to deliver through the relay, and get rejected ... Jan 8 09:19:32 biblio smtpd[28003]: smtp-out: Connecting to smtp://147.32.232.237:25 (relay.fit.cvut.cz) on session 62fe24cfe25a335f... Jan 8 09:19:32 biblio smtpd[28003]: smtp-out: Connected on session 62fe24cfe25a335f Jan 8 09:19:32 biblio smtpd[28003]: relay: TempFail for 045d176837eedf25: session=62fe24cfe25a335f, from=jan.st...@fit.cvut.cz, to=matys...@fit.cvut.cz, rcpt=-, source=147.32.233.137, relay=147.32.232.237 (relay.fit.cvut.cz), delay=0s, stat=452 4.5.3 Too many recipients Jan 8 09:19:33 biblio smtpd[28003]: relay: TempFail for 045d17683ba5d943: session=62fe24cfe25a335f, from=jan.st...@fit.cvut.cz, to=gorne...@fit.cvut.cz, rcpt=-, source=147.32.233.137, relay=147.32.232.237 (relay.fit.cvut.cz), delay=1s, stat=452 4.5.3 Too many recipients [...] Jan 8 09:19:45 biblio smtpd[28003]: relay: TempFail for 045d17685d71de97: session=62fe24cfe25a335f, from=jan.st...@fit.cvut.cz, to=urban...@fit.cvut.cz, rcpt=-, source=147.32.233.137, relay=147.32.232.237 (relay.fit.cvut.cz), delay=13s, stat=452 4.5.3 Too many recipients Jan 8 09:19:46 biblio smtpd[28003]: relay: TempFail for 045d17685da6a160: session=62fe24cfe25a335f, from=jan.st...@fit.cvut.cz, to=plyus...@fit.cvut.cz, rcpt=-, source=147.32.233.137, relay=147.32.232.237 (relay.fit.cvut.cz), delay=14s, stat=452 4.5.3 Too many recipients ... resulting in the host being Temporarily disabled (to be sure, is that my OpenSMTP disabling this relay, or the relay temporarily disabling me?): Jan 8 09:19:46 biblio smtpd[28003]: relay: TempFail for 045d17680388e458: session=62fe24cfe25a335f, from=jan.st...@fit.cvut.cz, to=vondr...@fit.cvut.cz, rcpt=-, source=147.32.233.137, relay=147.32.232.237 (relay.fit.cvut.cz), delay=14s, stat=Host temporarily disabled Jan 8 09:19:46 biblio smtpd[28003]: relay: TempFail for 045d17680c1c0e65: session=62fe24cfe25a335f, from=jan.st...@fit.cvut.cz, to=zahra...@fit.cvut.cz, rcpt=-, source=147.32.233.137, relay=147.32.232.237 (relay.fit.cvut.cz), delay=14s, stat=Host temporarily disabled [...] Jan 8 09:19:46 biblio smtpd[28003]: relay: TempFail for 045d1768fb82541f: session=62fe24cfe25a335f, from=jan.st...@fit.cvut.cz, to=dudas...@fit.cvut.cz, rcpt=-, source=147.32.233.137, relay=147.32.232.237 (relay.fit.cvut.cz), delay=14s, stat=Host temporarily disabled Jan 8 09:19:46 biblio smtpd[28003]: relay: TempFail for 045d1768fcf95048: session=62fe24cfe25a335f, from=jan.st...@fit.cvut.cz, to=tumov...@fit.cvut.cz, rcpt=-, source=147.32.233.137, relay=147.32.232.237 (relay.fit.cvut.cz), delay=14s, stat=Host temporarily
Re: outgoing smtpd: Too many recipients
On Dec 17 07:32:00, uni...@idempot.net wrote: On 12/17/2013 5:37 AM, Jan Stary wrote: That's the relay which is rejecting my messages if there are too many recipients in them. I deleted all the failed ones from my queue and after some time, resent to the individual recipients (~120) one by one with a bit of grepawkery; that went fine. http://www.sendmail.com/sm/open_source/docs/m4/tweaking_config.html (look for MaxRecipientsPerMessage) It seems that in this case sendmail really does just want the sending mailer to retry those addresses later. You might want to do a test run and just let deferred recipients sit for a while, to see if they do eventually get delivered. Yes, this time I will just let them sit there and see.
Re: outgoing smtpd: Too many recipients
Eventually, OpenSMTP gives up on that route completely for 800s: Jan 8 09:19:46 biblio smtpd[28003]: smtp-out: Disabling route [] - 147.32.232.237 (relay.fit.cvut.cz) for 800s Jan 8 09:19:46 biblio smtpd[28003]: smtp-out: Closing session 62fe24cfe25a335f: 0 message sent. BTW, where does the 800 come from? Is that a constant of ours, or is it something the (non)relaying sendmail told us? Jan
Re: outgoing smtpd: Too many recipients
Eventually, OpenSMTP gives up on that route completely for 800s: Jan 8 09:19:46 biblio smtpd[28003]: smtp-out: Disabling route [] - 147.32.232.237 (relay.fit.cvut.cz) for 800s Jan 8 09:19:46 biblio smtpd[28003]: smtp-out: Closing session 62fe24cfe25a335f: 0 message sent. As that was my only route, now I cannot send anything, right? At least it looks like it: Jan 8 09:56:20 biblio smtpd[26669]: smtp-in: New session 0f714bf625d2e0ce from host localhost [127.0.0.1] Jan 8 09:56:20 biblio smtpd[26669]: smtp-in: Accepted message 90b6747a on session 0f714bf625d2e0ce: from=jan.st...@fit.cvut.cz, to=tomas.kalv...@fit.cvut.cz, size=2905, ndest=1, proto=ESMTP Jan 8 09:56:20 biblio smtpd[26669]: smtp-in: Accepted message 90b6747a on session 0f714bf625d2e0ce: from=jan.st...@fit.cvut.cz, to=rozvrha...@fit.cvut.cz, size=2905, ndest=1, proto=ESMTP Jan 8 09:56:20 biblio smtpd[26669]: smtp-in: Closing session 0f714bf625d2e0ce Jan 8 09:56:20 biblio smtpd[10684]: smtp-out: Connecting to smtp://IPv6:2001:718:2:2901::237:25 (relay.fit.cvut.cz) on session 81041eb294d182c0... Ah, does this mean now that the IP4 route to relay.fit.cvut.cz is disabled, we try the IP6 route ... Jan 8 09:56:20 biblio smtpd[10684]: smtp-out: Error on session 81041eb294d182c0: Connection failed: No route to host Jan 8 09:56:20 biblio smtpd[10684]: smtp-out: Disabling route [] - IPv6:2001:718:2:2901::237 (relay.fit.cvut.cz) for 800s ... and after error, disable it too? BTW, the 800s is our constant, right, because now the relay haven't told us anything. Jan 8 09:56:22 biblio smtpd[10684]: smtp-out: No valid route for [connector:[]-[relay:relay.fit.cvut.cz,mx],0x0] Jan 8 09:56:31 biblio smtpd[10684]: relay: TempFail for 90b6747a238b0f03: session=, from=jan.st...@fit.cvut.cz, to=rozvrha...@fit.cvut.cz, rcpt=-, source=-, relay=relay.fit.cvut.cz, delay=11s, stat=Destination seem to reject all mails Jan 8 09:56:31 biblio smtpd[10684]: relay: TempFail for 90b6747a74f68a99: session=, from=jan.st...@fit.cvut.cz, to=tomas.kalv...@fit.cvut.cz, rcpt=-, source=-, relay=relay.fit.cvut.cz, delay=11s, stat=Destination seem to reject all mails
Re: outgoing smtpd: Too many recipients
On Jan 08 09:50:15, h...@stare.cz wrote: On Dec 17 07:32:00, uni...@idempot.net wrote: On 12/17/2013 5:37 AM, Jan Stary wrote: That's the relay which is rejecting my messages if there are too many recipients in them. I deleted all the failed ones from my queue and after some time, resent to the individual recipients (~120) one by one with a bit of grepawkery; that went fine. http://www.sendmail.com/sm/open_source/docs/m4/tweaking_config.html (look for MaxRecipientsPerMessage) It seems that in this case sendmail really does just want the sending mailer to retry those addresses later. You might want to do a test run and just let deferred recipients sit for a while, to see if they do eventually get delivered. Yes, this time I will just let them sit there and see. Well, after a couple of hours, they got through by pieces. Every now and then (that is, following some strategy, surely) OpenSMTPD tries to resend. The relay accepts a few (respectively: 15, 17, 50, 20, 25, 14) and rejects the rest with 'too many recipients' again, which leads to 'host temporarily disabled', and a disabled route. After a timeout, it enables the route again, tries again, some more get through, etc. They are all sent now. Jan
Re: outgoing smtpd: Too many recipients
On Dec 17 08:35:28, gil...@poolp.org wrote: On Mon, Dec 16, 2013 at 07:08:17PM +0100, Jan Stary wrote: I am using smtpd as my mail server on a network where the relay server often replies with 4.5.3 Too many recipients Indeed, I was sending messages with a lot of recipients (a group of students). Is there a way in the smtpd configuration to specify that a message with N recipients should be broken into N individual messages? Why so ? Because if not, the message is rejected with 4.5.3. Messages with certain number of recipients just cannot be sent through this relay. Does it prevent OpenSMTPD from sending to the recipients it has submitted already ? The relay disables my mailserver for some fixed time. No messages from me will be accepted during that time. It should fail the ones after 4.5.3 and mark them as tempfail which will cause them to be retried a few seconds later while the ones before the error will be submitted. Isn't that what is happening ? smtpd tries to resend the failed ones, only to be told again that there are too many recipients. If so, will smtpd create a new smtp connection for each of the messages? That could also be a problem. No, smtpd will always try to group and reuse connections, Thanks you. Jan
Re: outgoing smtpd: Too many recipients
On Tue, Dec 17, 2013 at 09:17:27AM +0100, Jan Stary wrote: On Dec 17 08:35:28, gil...@poolp.org wrote: On Mon, Dec 16, 2013 at 07:08:17PM +0100, Jan Stary wrote: I am using smtpd as my mail server on a network where the relay server often replies with 4.5.3 Too many recipients Indeed, I was sending messages with a lot of recipients (a group of students). Is there a way in the smtpd configuration to specify that a message with N recipients should be broken into N individual messages? Why so ? Because if not, the message is rejected with 4.5.3. Messages with certain number of recipients just cannot be sent through this relay. Oh, the entire message is rejected ? That's kind of violent... There's a tweak to limit the number of recipients but if we could avoid it, it would benefit everyone. Does it prevent OpenSMTPD from sending to the recipients it has submitted already ? The relay disables my mailserver for some fixed time. No messages from me will be accepted during that time. The relay disabling code has been removed, this should no longer happen to you with last snapshot. We will release 5.4.2 in a few days to fix the first shortcomings we experienced from 5.4.1 and this will be part of it. It should fail the ones after 4.5.3 and mark them as tempfail which will cause them to be retried a few seconds later while the ones before the error will be submitted. Isn't that what is happening ? smtpd tries to resend the failed ones, only to be told again that there are too many recipients. So not a single recipient is ever accepted ? If that's the case, I'll tell you in private how to fix this and we will have to find a way that works for everyone... If so, will smtpd create a new smtp connection for each of the messages? That could also be a problem. No, smtpd will always try to group and reuse connections, -- Gilles Chehade https://www.poolp.org @poolpOrg
Re: outgoing smtpd: Too many recipients
On Dec 17 09:21:58, gil...@poolp.org wrote: On Tue, Dec 17, 2013 at 09:17:27AM +0100, Jan Stary wrote: On Dec 17 08:35:28, gil...@poolp.org wrote: On Mon, Dec 16, 2013 at 07:08:17PM +0100, Jan Stary wrote: I am using smtpd as my mail server on a network where the relay server often replies with 4.5.3 Too many recipients Indeed, I was sending messages with a lot of recipients (a group of students). Is there a way in the smtpd configuration to specify that a message with N recipients should be broken into N individual messages? Why so ? Because if not, the message is rejected with 4.5.3. Messages with certain number of recipients just cannot be sent through this relay. Oh, the entire message is rejected ? That's kind of violent... There's a tweak to limit the number of recipients but if we could avoid it, it would benefit everyone. Does it prevent OpenSMTPD from sending to the recipients it has submitted already ? The relay disables my mailserver for some fixed time. No messages from me will be accepted during that time. The relay disabling code has been removed, this should no longer happen to you with last snapshot. Now I am not sure if I described my problem well. On my machine, OpenSMTP is running as my mailserver. The relay I am sending through, which is another machine (this network's outgoing smtp server) is not OpenSMTP: It's geeting me as ESMTP Sendmail 8.14.5/8.14.5. That's the relay which is rejecting my messages if there are too many recipients in them. I deleted all the failed ones from my queue and after some time, resent to the individual recipients (~120) one by one with a bit of grepawkery; that went fine. Occasionaly though, I just need to send an email to ~120 people, and it would be nice if OpenSMTP could cut that to smaller pieces which the realy would accept. (It would also be nice if the relay just accepted the messages as they are, of course.) We will release 5.4.2 in a few days to fix the first shortcomings we experienced from 5.4.1 and this will be part of it. OK, I will try again then. Thank you Jan
Re: outgoing smtpd: Too many recipients
The relay disabling code has been removed, Disabling the relay which does not accept me seems pretty neat actually - if I do have another route through another relay :-)
Re: outgoing smtpd: Too many recipients
Jan, Sorry, but I do not see what your problem is? If you need to send an email to a group of people that's significantly bigger allowed on your relay, why don't you just try to implement a very simple script, that will send your mail to one recipient at a time. -- With best regards, Gregory Edigarov
Re: outgoing smtpd: Too many recipients
On 12/17/2013 5:37 AM, Jan Stary wrote: That's the relay which is rejecting my messages if there are too many recipients in them. I deleted all the failed ones from my queue and after some time, resent to the individual recipients (~120) one by one with a bit of grepawkery; that went fine. http://www.sendmail.com/sm/open_source/docs/m4/tweaking_config.html (look for MaxRecipientsPerMessage) It seems that in this case sendmail really does just want the sending mailer to retry those addresses later. You might want to do a test run and just let deferred recipients sit for a while, to see if they do eventually get delivered. -- Matthew Weigel hacker unique idempot . ent
Re: outgoing smtpd: Too many recipients
On 12/17/2013 03:32 PM, Matthew Weigel wrote: On 12/17/2013 5:37 AM, Jan Stary wrote: That's the relay which is rejecting my messages if there are too many recipients in them. I deleted all the failed ones from my queue and after some time, resent to the individual recipients (~120) one by one with a bit of grepawkery; that went fine. http://www.sendmail.com/sm/open_source/docs/m4/tweaking_config.html (look for MaxRecipientsPerMessage) It seems that in this case sendmail really does just want the sending mailer to retry those addresses later. You might want to do a test run and just let deferred recipients sit for a while, to see if they do eventually get delivered. But I do not think sendmail(or whatever) server is under TS control. -- With best regards, Gregory Edigarov
Re: outgoing smtpd: Too many recipients
On Dec 17 14:53:59, ediga...@qarea.com wrote: Jan, Sorry, but I do not see what your problem is? If you need to send an email to a group of people that's significantly bigger allowed on your relay, why don't you just try to implement a very simple script, that will send your mail to one recipient at a time. That's exactly what I eventually did, as described in previous email. My question was whether OpenSMTP can do it for me.
Re: outgoing smtpd: Too many recipients
On Mon, Dec 16, 2013 at 07:08:17PM +0100, Jan Stary wrote: I am using smtpd as my mail server on a network where the relay server often replies with 4.5.3 Too many recipients Indeed, I was sending messages with a lot of recipients (a group of students). Is there a way in the smtpd configuration to specify that a message with N recipients should be broken into N individual messages? Why so ? Does it prevent OpenSMTPD from sending to the recipients it has submitted already ? It should fail the ones after 4.5.3 and mark them as tempfail which will cause them to be retried a few seconds later while the ones before the error will be submitted. Isn't that what is happening ? If so, will smtpd create a new smtp connection for each of the messages? That could also be a problem. No, smtpd will always try to group and reuse connections, -- Gilles Chehade https://www.poolp.org @poolpOrg
