Re: [courier-users] sendmail removes bcc header unconditionally
Just tested my sentfolder filter, and the new Bcc: support works nicely. Thanks for your help, Sam. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] sendmail removes bcc header unconditionally
On 07/06/2017 05:09 PM, Sam Varshavchik wrote: Yeah, github was a couple of commits behind. Just pushed everything out, and it's up to date now. Thanks, again. Is this an accurate update to the sendmail document? diff --git a/courier/courier/doc/sendmail.sgml b/courier/courier/doc/sendmail.sgml index 634b262..6f956c3 100644 --- a/courier/courier/doc/sendmail.sgml +++ b/courier/courier/doc/sendmail.sgml @@ -74,8 +74,8 @@ message and builds the recipient list from the To: Cc: and moreinfo="none">Bcc: headers. -sendmail always removes all moreinfo="none">Bcc: -headers before sending the message. +sendmail removes moreinfo="none">Bcc: +headers before sending the message if recipients are not specified on the command line. Some of the functionality described below is actually implemented by other @@ -194,7 +194,7 @@ information. Read Bcc: headers only. Normally, if no recipients are specified, sendmail obtains the list of recipients by reading the To:, Cc: and -Bcc: headers (moreinfo="none">Bcc: headers are always +Bcc: headers (moreinfo="none">Bcc: headers are then removed). The -bcc option ignores moreinfo="none">To: and Cc: -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] sendmail removes bcc header unconditionally
Gordon Messmer writes: On 07/06/2017 01:58 PM, Sam Varshavchik wrote: This is a reasonable position to make, so I'll change this. Thanks very much, Sam. If you push a patch into git (github looks a bit out of date?) I'll test it. Or, if you'd rather, I can modify sendmail and send a patch. Yeah, github was a couple of commits behind. Just pushed everything out, and it's up to date now. pgpJGQYoFfPpX.pgp Description: PGP signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] sendmail removes bcc header unconditionally
On 07/06/2017 01:58 PM, Sam Varshavchik wrote: This is a reasonable position to make, so I'll change this. Thanks very much, Sam. If you push a patch into git (github looks a bit out of date?) I'll test it. Or, if you'd rather, I can modify sendmail and send a patch. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] sendmail removes bcc header unconditionally
Gordon Messmer writes: On 07/06/2017 03:54 AM, Sam Varshavchik wrote: Would it work to simply use a custom header name instead of "Bcc:". Most email clients won't show it by default, but it's going to be there and can be looked at, in some way; and the email clients will also ignore it if the message is replied to. That's the other option I'm looking at, and I'm more likely to go that route than introduce another message delivery code path in the framework. Some record is better than no record, but I feel like that path would still be very slightly inferior to the solutions that Gmail and Courier IMAP provide. Is there a logical reason why sendmail should remove the Bcc: header when headers aren't used to indicate recipients? My recollection is hazy, but I thought that this was sendmail-sendmail's behavior, which was to simply strip off the Bcc: header from the mail. The current version of sendmail's man page suggests β with some ambiguity β that only the -t option does that; so I don't know whether this was changed some time, or it was always like that. I was curious as to the historical origin of this, and poking around the Intertubes all the references were to RFC 733 which only states that βthe contents of this field are not included in copies of the message sent to the primary and secondary recipients. Some systems may choose to include the text of the "Bcc" field only in the author(s)'s copy, while others may also include it in the text sent to all those indicated in the "Bcc" list.β without going into much detail of how the recipient list is established; but the "may" part's only logical intepretation is that the whole thing is always optional. Still, from a certain point of view, sendmail-sendmail's behavior is quite reasonable, too. You can say that by explicitly specifying the recipient list this places the onus on the sender to identify the so-called "primary and secondary" recipients; with the presumption that the sender is responsible for formatting the message, and the sender is wholly responsible for including or omitting the contents of the Bcc. This is a reasonable position to make, so I'll change this. pgpU3zvzSFowB.pgp Description: PGP signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] sendmail removes bcc header unconditionally
On 07/06/2017 03:54 AM, Sam Varshavchik wrote: Would it work to simply use a custom header name instead of "Bcc:". Most email clients won't show it by default, but it's going to be there and can be looked at, in some way; and the email clients will also ignore it if the message is replied to. That's the other option I'm looking at, and I'm more likely to go that route than introduce another message delivery code path in the framework. Some record is better than no record, but I feel like that path would still be very slightly inferior to the solutions that Gmail and Courier IMAP provide. Is there a logical reason why sendmail should remove the Bcc: header when headers aren't used to indicate recipients? -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] setuid/setgid problem, mail from website not sent
On 07/06/2017 12:13 PM, Matus UHLAR - fantomas wrote: > On 06.07.17 12:43, Bernd Plagge wrote: >> thank you VERY much! >> This was the answer. >> >> Just for the record: >> I had to downgrade my Debian system due to issues with the new Debian >> packages. >> Seems that the permissions on the sendmail wrapper were not set correctly by >> the installation program. > > I believe debian developer either knows what permissions to set up, or > should be informed if that causes troubles... Yes, please file a bug and I'll take a look at it. Thanks Racke > >> On Thu, 06 Jul 2017 03:03:37 + >> courier-users-requ...@lists.sourceforge.net wrote: >> >>> From: Sam Varshavchik >>> To: courier-users@lists.sourceforge.net >>> Subject: Re: [courier-users] setuid/setgid problem, mail from website not >>>sent >>> Date: Wed, 05 Jul 2017 17:55:26 -0400 >>> >>> Bernd Plagge writes: >>> >>> > Hi >>> > >>> > I'm trying to send mail from website mail, or webmail. >>> > However, sending doesn't work, >>> > >>> > Log entries: >>> > >>> > Jul 06 00:25:45 linde lighttpd[1182]: setuid/setgid: Operation not >>> > permitted >>> > Jul 06 00:25:45 linde lighttpd[1182]: /cgi-bin/FormMail.pl: close sendmail >>> > pipe failed, mailprog=[/usr/lib/sendmail -oi -t] at (eval 9) line 108. >>> > >>> > The courier sendmail program: >>> > s -l /usr/sbin/sendmail >>> > -rwxr-sr-x 1 root courier 59120 Jan 26 2015 /usr/sbin/sendmail >>> > >>> > >>> > What can I do to solve this problem? >>> >>> Permissions on the sendmail wrapper should be setuid root, not setgid. > -- Ecommerce and Linux consulting + Perl and web application programming. Debian and Sympa administration. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] sendmail removes bcc header unconditionally
Gordon Messmer writes: I'm working on improving my "sentfolder" mail filter. This filter works like GMail's SMTP system, copying messages that a user sends into their sent folder, so that messages only need to traverse the network once. Courier IMAP has a better option, but no client support to speak of. I've updated the sendfolder filter to examine the recipients in the control files and the message file headers, and add a Bcc: header for any addresses that don't appear in the message headers. It then uses sendmail to send a copy to the user, along with a header that marks it for delivery to their sent folder. The problem here is that sendmail unconditionally removes the bcc: header. I think it might be better if sendmail removed the bcc header only if it uses headers for the destination addresses, and left the bcc header if it uses destinations given as command line arguments. Would that be an acceptable change? I could work around the problem by using SMTP rather than sendmail, but I prefer to use sendmail to avoid passing through the courier filters (at least, in the default configuration). Would it work to simply use a custom header name instead of "Bcc:". Most email clients won't show it by default, but it's going to be there and can be looked at, in some way; and the email clients will also ignore it if the message is replied to. pgpRHc4p8PIVR.pgp Description: PGP signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] setuid/setgid problem, mail from website not sent
On 06.07.17 12:43, Bernd Plagge wrote: thank you VERY much! This was the answer. Just for the record: I had to downgrade my Debian system due to issues with the new Debian packages. Seems that the permissions on the sendmail wrapper were not set correctly by the installation program. I believe debian developer either knows what permissions to set up, or should be informed if that causes troubles... On Thu, 06 Jul 2017 03:03:37 + courier-users-requ...@lists.sourceforge.net wrote: From: Sam Varshavchik To: courier-users@lists.sourceforge.net Subject: Re: [courier-users] setuid/setgid problem, mail from website not sent Date: Wed, 05 Jul 2017 17:55:26 -0400 Bernd Plagge writes: > Hi > > I'm trying to send mail from website mail, or webmail. > However, sending doesn't work, > > Log entries: > > Jul 06 00:25:45 linde lighttpd[1182]: setuid/setgid: Operation not permitted > Jul 06 00:25:45 linde lighttpd[1182]: /cgi-bin/FormMail.pl: close sendmail > pipe failed, mailprog=[/usr/lib/sendmail -oi -t] at (eval 9) line 108. > > The courier sendmail program: > s -l /usr/sbin/sendmail > -rwxr-sr-x 1 root courier 59120 Jan 26 2015 /usr/sbin/sendmail > > > What can I do to solve this problem? Permissions on the sendmail wrapper should be setuid root, not setgid. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Windows 2000: 640 MB ought to be enough for anybody -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users