Tickets :: [#2574] message sending fails with a error, if all the recipients are in the Bcc:

6.0.0-beta1

7/29/25

Summary	message sending fails with a error, if all the recipients are in the Bcc:
Queue	IMP
Queue Version	FRAMEWORK_3
Type	Bug
State	Resolved
Priority	1. Low
Owners	Horde Developers (at)
Requester	leena.heino (at) uta (dot) fi
Created	09/08/2005 (7264 days ago)
Due
Updated	09/08/2005 (7264 days ago)
Assigned	09/08/2005 (7264 days ago)
Resolved	09/08/2005 (7264 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

09/08/2005 06:49:35 PM	Chuck Hagenbuch	State ⇒ Resolved

09/08/2005 06:45:42 PM	leena (dot) heino (at) uta (dot) fi	Comment #6	Reply to this comment
Ahhh... I see where chuck is coming from. The only place we would put in 'undisclosed-recipients' is in the To: line, not the recipients list we pass onto the mail backend. So if sendmail is somehow trying to extract recipient addresses from the To: header, you have your sendmail configured incorrectly. Make sure '-t' does not appear in $conf['mailer']['params']['sendmail_args'] in horde/config/conf.php. You guys are fantastic. That was it. I'm not sure why that '-t' was added to the sendmail's parameters, but it must have happened a long time ago. I must have had some sort of mixup with php's sendmail defaults at that time.

09/08/2005 06:21:23 PM	Michael Slusarz	Comment #5	Reply to this comment
Ahhh... I see where chuck is coming from. The only place we would put in 'undisclosed-recipients' is in the To: line, not the recipients list we pass onto the mail backend. So if sendmail is somehow trying to extract recipient addresses from the To: header, you have your sendmail configured incorrectly. Make sure '-t' does not appear in $conf['mailer']['params']['sendmail_args'] in horde/config/conf.php.

09/08/2005 06:10:10 PM	leena (dot) heino (at) uta (dot) fi	Comment #4	Reply to this comment
My first reaction to this is that this is something that should be handled in the sendmail driver rather than in Horde/IMP (especially since undisclosed-recipients; is perfectly valid - and desired - when sending via SMTP). It is not a valid recipient address even when using smtp: mail from:<> 250 2.1.0 <>... Sender ok rcpt to:<undisclosed-recipients:;> 553 5.1.3 <undisclosed-recipients:;>... List:; syntax illegal for recipient addresses

09/08/2005 02:12:59 PM	Chuck Hagenbuch	Comment #3 State ⇒ Feedback Assigned to Horde Developers	Reply to this comment
Any sense where the undisclosed-recipients in the actual $recipients value is coming from?

09/08/2005 02:12:29 PM	Michael Slusarz	Comment #2	Reply to this comment
My first reaction to this is that this is something that should be handled in the sendmail driver rather than in Horde/IMP (especially since undisclosed-recipients; is perfectly valid - and desired - when sending via SMTP).

09/08/2005 09:58:39 AM	leena (dot) heino (at) uta (dot) fi	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ message sending fails with a error, if all the recipients are in the Bcc: Queue ⇒ IMP State ⇒ Unconfirmed	Reply to this comment
If the message's all recipients are in Bcc: then compose puts To: address as undisclosed-recipients:;. This is a valid construct in message's To: header, but invalid as a sendmail's command line recipient address. This invalid command line address causes a error message in compose window "sendmail returned error code 64" and mail is not sent. To testi this bug just type in command line: sendmail undisclosed-recipients:; Proposed fix would be that you drop the undisclosed-recipients:; from the list of addresses that are sent to the sendmail program.