[1003.1(2016/18)/Issue7+TC2 0001408]: mailx: add mta-bcc-ok internal variable
The following issue has been SUBMITTED. == https://www.austingroupbugs.net/view.php?id=1408 == Reported By:steffen Assigned To: == Project:1003.1(2016/18)/Issue7+TC2 Issue ID: 1408 Category: Shell and Utilities Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: steffen Organization: User Reference: Section:Vol. 3: Shell and Utilities, mailx Page Number:2952 Line Number:97836 Interp Status: --- Final Accepted Text: == Date Submitted: 2020-09-30 20:48 UTC Last Modified: 2020-09-30 20:48 UTC == Summary:mailx: add mta-bcc-ok internal variable Description: My mailx clone (will) document(s) it like this: mta-bcc-ok (Boolean) In violation of RFC 5322 some MTAs do not remove ‘Bcc:’ header lines from transported messages after having noted the respective receivers for addressing purposes. (The MTAs Exim and Courier for example require the command line option -t to enforce removal.) Setting this variable asserts that the MTA performs stripping. Desired Action: Adapt an internal variable mta-bcc-ok, default unset. == Issue History Date ModifiedUsername FieldChange == 2020-09-30 20:48 steffenNew Issue 2020-09-30 20:48 steffenName => steffen 2020-09-30 20:48 steffenSection => Vol. 3: Shell and Utilities, mailx 2020-09-30 20:48 steffenPage Number => 2952 2020-09-30 20:48 steffenLine Number => 97836 ==
[Issue 8 drafts 0001369]: COLUMNS and LINES rationale
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1369 == Reported By:geoffclare Assigned To: == Project:Issue 8 drafts Issue ID: 1369 Category: Rationale Type: Error Severity: Comment Priority: normal Status: Applied Name: Geoff Clare Organization: The Open Group User Reference: Section:A.8.3 Page Number:3407 Line Number:116496 Final Accepted Text: Resolution: Accepted Fixed in Version: == Date Submitted: 2020-07-09 11:11 UTC Last Modified: 2020-09-30 14:25 UTC == Summary:COLUMNS and LINES rationale == Relationships ID Summary -- related to 0001185 Additional 3rd option for getting line ... == Issue History Date ModifiedUsername FieldChange == 2020-07-09 11:11 geoffclare New Issue 2020-07-09 11:11 geoffclare Name => Geoff Clare 2020-07-09 11:11 geoffclare Organization => The Open Group 2020-07-09 11:11 geoffclare Section => A.8.3 2020-07-09 11:11 geoffclare Page Number => 3407 2020-07-09 11:11 geoffclare Line Number => 116496 2020-07-09 11:12 geoffclare Relationship added related to 0001185 2020-09-14 15:43 Don Cragun Status New => Resolved 2020-09-14 15:43 Don Cragun Resolution Open => Accepted 2020-09-14 15:43 Don Cragun Tag Attached: issue8 2020-09-30 14:25 geoffclare Status Resolved => Applied ==
[Issue 8 drafts 0001370]: Where change history starts
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1370 == Reported By:geoffclare Assigned To: == Project:Issue 8 drafts Issue ID: 1370 Category: Rationale Type: Error Severity: Editorial Priority: normal Status: Applied Name: Geoff Clare Organization: The Open Group User Reference: Section:B.1.1, C.1.1 Page Number:3433, 3555 Line Number:117421, 122714 Final Accepted Text:See https://austingroupbugs.net/view.php?id=1370#c4992. Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2020-07-10 09:21 UTC Last Modified: 2020-09-30 14:27 UTC == Summary:Where change history starts == Issue History Date ModifiedUsername FieldChange == 2020-07-10 09:21 geoffclare New Issue 2020-07-10 09:21 geoffclare Name => Geoff Clare 2020-07-10 09:21 geoffclare Organization => The Open Group 2020-07-10 09:21 geoffclare Section => B.1.1, C.1.1 2020-07-10 09:21 geoffclare Page Number => 3433, 3555 2020-07-10 09:21 geoffclare Line Number => 117421, 122714 2020-09-14 15:57 rhansenNote Added: 0004992 2020-09-17 15:10 Don Cragun Final Accepted Text => See https://austingroupbugs.net/view.php?id=1370#c4992. 2020-09-17 15:10 Don Cragun Status New => Resolved 2020-09-17 15:10 Don Cragun Resolution Open => Accepted As Marked 2020-09-17 15:11 Don Cragun Tag Attached: issue8 2020-09-30 14:27 geoffclare Status Resolved => Applied ==
[Issue 8 drafts 0001366]: Out of date rationale for XSI definition
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1366 == Reported By:geoffclare Assigned To: == Project:Issue 8 drafts Issue ID: 1366 Category: Rationale Type: Error Severity: Comment Priority: normal Status: Applied Name: Geoff Clare Organization: The Open Group User Reference: Section:A.3 Definitions (XSI) Page Number:3379 Line Number:115320 Final Accepted Text: Resolution: Accepted Fixed in Version: == Date Submitted: 2020-07-08 15:20 UTC Last Modified: 2020-09-30 14:24 UTC == Summary:Out of date rationale for XSI definition == Issue History Date ModifiedUsername FieldChange == 2020-07-08 15:20 geoffclare New Issue 2020-07-08 15:20 geoffclare Name => Geoff Clare 2020-07-08 15:20 geoffclare Organization => The Open Group 2020-07-08 15:20 geoffclare Section => A.3 Definitions (XSI) 2020-07-08 15:20 geoffclare Page Number => 3379 2020-07-08 15:20 geoffclare Line Number => 115320 2020-09-14 15:41 Don Cragun Status New => Resolved 2020-09-14 15:41 Don Cragun Resolution Open => Accepted 2020-09-14 15:41 Don Cragun Tag Attached: issue8 2020-09-30 14:24 geoffclare Status Resolved => Applied ==
[Issue 8 drafts 0001365]: rm -v description implies only operands are reported
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1365 == Reported By:geoffclare Assigned To: == Project:Issue 8 drafts Issue ID: 1365 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: Applied Name: Geoff Clare Organization: The Open Group User Reference: Section:rm Page Number:3066 Line Number:103824 Final Accepted Text: Resolution: Accepted Fixed in Version: == Date Submitted: 2020-07-07 09:36 UTC Last Modified: 2020-09-30 14:22 UTC == Summary:rm -v description implies only operands are reported == Relationships ID Summary -- related to 0001154 Add 'rm -v' == Issue History Date ModifiedUsername FieldChange == 2020-07-07 09:36 geoffclare New Issue 2020-07-07 09:36 geoffclare Name => Geoff Clare 2020-07-07 09:36 geoffclare Organization => The Open Group 2020-07-07 09:36 geoffclare Section => rm 2020-07-07 09:36 geoffclare Page Number => 3066 2020-07-07 09:36 geoffclare Line Number => 103824 2020-07-07 09:37 geoffclare Relationship added related to 0001154 2020-09-14 15:39 Don Cragun Status New => Resolved 2020-09-14 15:39 Don Cragun Resolution Open => Accepted 2020-09-14 15:40 Don Cragun Tag Attached: issue8 2020-09-30 14:22 geoffclare Status Resolved => Applied ==
[Issue 8 drafts 0001364]: use of noclobber with files in /tmp
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=1364 == Reported By:geoffclare Assigned To: == Project:Issue 8 drafts Issue ID: 1364 Category: Shell and Utilities Type: Clarification Requested Severity: Comment Priority: normal Status: Applied Name: Geoff Clare Organization: The Open Group User Reference: Section:2.7.2 Redirecting Output Page Number:2287 Line Number:73909 Final Accepted Text:https://austingroupbugs.net/view.php?id=1364#c4991 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2020-07-06 10:45 UTC Last Modified: 2020-09-30 14:20 UTC == Summary:use of noclobber with files in /tmp == Relationships ID Summary -- related to 0001016 race condition with set -C == Issue History Date ModifiedUsername FieldChange == 2020-07-06 10:45 geoffclare New Issue 2020-07-06 10:45 geoffclare Name => Geoff Clare 2020-07-06 10:45 geoffclare Organization => The Open Group 2020-07-06 10:45 geoffclare Section => 2.7.2 Redirecting Output 2020-07-06 10:45 geoffclare Page Number => 2287 2020-07-06 10:45 geoffclare Line Number => 73909 2020-07-06 10:46 geoffclare Relationship added related to 0001016 2020-09-14 15:35 rhansenNote Added: 0004991 2020-09-14 15:35 rhansenNote Edited: 0004991 2020-09-14 15:36 rhansenNote Edited: 0004991 2020-09-14 15:36 rhansenNote Edited: 0004991 2020-09-14 15:36 rhansenNote Edited: 0004991 2020-09-14 15:37 rhansenTag Attached: issue8 2020-09-14 15:37 rhansenFinal Accepted Text => https://austingroupbugs.net/view.php?id=1364#c4991 2020-09-14 15:37 rhansenStatus New => Resolved 2020-09-14 15:37 rhansenResolution Open => Accepted As Marked 2020-09-30 14:20 geoffclare Status Resolved => Applied ==
Re: [1003.1(2016/18)/Issue7+TC2 0001401]: reply command uses obsolete wording
Geoff Clare wrote in <20200930090055.GA19622@localhost>: |Steffen Nurpmeso wrote, on 29 Sep 2020: |> The vaporisation of address lists happens after the compose-mode is left: | |> P.S.: and this is because alias expansion, hooks |> (*on-compose-leave* plus, which can use `digmsg' to edit the |> message), automatic receivers (*autocc*, *autobcc*) as well as MTA |> alias expansion (*mta-aliases*, optional) are all performed after |> the user agrees in sending the message. That is, the actual list |> of receivers is still subject to change, in sofar performing |> cleanup is possible but at least questionable. |> |> The question whether the message is ok to be sent as such only |> happens with *asksend* set and in interactive mode. Maybe it |> should state that the shown header has not undergone cleanup. | |It's certainly dubious behaviour to show header field content that is |not the same as the fields in the sent message are going to contain, |without at least alerting the user that they may change. I had already committed exactly this last night, it is just not pushed yet. Though "before refinement", i am still thinking to refine that.. It really is meant as an assertion only, as in "have i really addressed everyone?". You know, creating the real, final version and allowing re-edit thereafter aka supporting "rollback" is hard, all the objects and the temporary message draft had to be duplicated for this to happen, which is very expensive. And hook macros etc. need to be made aware that they may be called multiple times for a message. The manual states (in "On sending mail, and non-interactive mode") that "some introductional [.] dry-run tests will prove correctness". Maybe i revert *asksend* as a default setting. It likely is something for more chaotic people. |In any case that's a quality-of-implementation issue. As far as |bug 1401 is concerned, the proposed changes should be updated to make |it optional whether cross-field de-duplication is also performed. Well it better be default to avoid sending multiple copies to the same receiver. Some MTAs send to each and every address, or did so in the past. POSIX mailx could see quite some changes, the question is whether it would be accepted by implementors to spend expensive developer time for such a tool, which i doubt. Important would be an equivalence to or some words about the *mta-bcc-ok* setting of my one, since POSIX mailx supports Bcc: via ~b, ~h and *askbcc*: mta-bcc-ok (Boolean) By default "Bcc:" header lines are not passed through since some MTAs do not remove them before sending them over the wire, in violation of RFC 5322. (For example Exim and Courier would need to be started with the -t command line option to force stripping.) Setting this enables pass-through, therefore avoids generation of mutilated message versions, and [v15 behaviour may differ] improves performance. That performance note is also about the BSD Mail / Research Unix and still my codebase, which create a temporary message file, and for this Bcc: modification we (unfortunately, still) need to create a specific version without Bcc:. --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
Re: [1003.1(2016/18)/Issue7+TC2 0001401]: reply command uses obsolete wording
Steffen Nurpmeso wrote, on 29 Sep 2020: > > The vaporisation of address lists happens after the compose-mode is left: > P.S.: and this is because alias expansion, hooks > (*on-compose-leave* plus, which can use `digmsg' to edit the > message), automatic receivers (*autocc*, *autobcc*) as well as MTA > alias expansion (*mta-aliases*, optional) are all performed after > the user agrees in sending the message. That is, the actual list > of receivers is still subject to change, in sofar performing > cleanup is possible but at least questionable. > > The question whether the message is ok to be sent as such only > happens with *asksend* set and in interactive mode. Maybe it > should state that the shown header has not undergone cleanup. It's certainly dubious behaviour to show header field content that is not the same as the fields in the sent message are going to contain, without at least alerting the user that they may change. In any case that's a quality-of-implementation issue. As far as bug 1401 is concerned, the proposed changes should be updated to make it optional whether cross-field de-duplication is also performed. -- Geoff Clare The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
Minutes of the 28th September 2020 Teleconference
All Enclosed are the minutes of the Monday meeting regards Andrew Minutes of the 28th September 2020 Teleconference Austin-1067 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 30th September 2020 Attendees: Don Cragun, IEEE PASC OR Mark Ziegast, SHware Systems Dev. Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann, HPI, University of Potsdam Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Richard Hansen Apologies: Andrew Josey * General news None. * Outstanding actions (Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 13th June 2019 and earlier) Bug 1254: "asynchronous list" description uses "command" instead of "AND-OR list" OPEN https://austingroupbugs.net/view.php?id=1254 Action: Joerg to investigate how his shell behaves. Bug 700 - Nick to raise this issue with the C committee Bug 713 - Nick to raise with the C committee. Bug 739 - Nick to raise with the C committee. * Current Business Bug 697: Adding of a getdirentries() function OPEN https://www.austingroupbugs.net/view.php?id=697 This has a separate etherpad page. https://posix.rhansen.org/p/bug697 This item was discussed and will be continued on the next call. Gettext draft. We will return to this on a future call. The gettext draft in the etherpad is at https://posix.rhansen.org/p/gettext_draft https://posix.rhansen.org/p/gettext_split Next Steps -- The next calls are on: October 1st 2020 (Thursday) This call will be for 90 minutes. October 5th 2020 (Monday) This call will be for 60 minutes. Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Bugs are at: https://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/20xx-mm-dd (For write access this uses The Open Group single sign on, for those individuals with gitlab.opengroup.org accounts. Please contact Andrew if you need to be setup) Andrew JoseyThe Open Group Austin Group Chair Email: a.jo...@opengroup.org Apex Plaza, Forbury Road,Reading,Berks.RG1 1AX,England To learn how we maintain your privacy, please review The Open Group Privacy Statement at http://www.opengroup.org/privacy. To unsubscribe/opt-out from this mailing list login to The Open Group collaboration portal at https://collaboration.opengroup.org/operational/portal.php?action=unsub=2481
Austin Group teleconference +1 888 974 9888 PIN 618 156 403
BEGIN:VCALENDAR VERSION:2.0 PRODID:-//opengroup.org//NONSGML kigkonsult.se iCalcreator 2.22.1// CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/New_York X-LIC-LOCATION:America/New_York BEGIN:DAYLIGHT TZOFFSETFROM:-0500 TZOFFSETTO:-0400 TZNAME:EDT DTSTART:20120311T02 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:-0400 TZOFFSETTO:-0500 TZNAME:EST DTSTART:20121104T02 RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT UID:5f74320e5a...@opengroup.org DTSTAMP:20200930T072150Z ATTENDEE;ROLE=CHAIR:MAILTO:a.jo...@opengroup.org CREATED:20200930T00Z DESCRIPTION:Web/Project: Single UNIX Specification\nTitle: Austin Group tel econference +1 888 974 9888 PIN 618 156 403\nDate/Time: 05-Oct-2020 at 11: 00 America/New_York\nDuration: 1.00 hours\nURL: https://collaboration.open group.org/platform/single_unix_specification/events.php\n\n* All calls are anchored on US time **\n\nTopic: Austin Group teleconference\n--- \nAudio conference information \n---\n\nYou are invit ed to a Zoom meeting.\n\nMeeting ID: 618 156 403\n\nJoin from PC\, Mac\, i OS or Android: https://logitech.zoom.us/j/618156403\n \nor join by phone: \nUS: 888 974 9888\nUK: 800 031 5717\nDE: 800 724 3138\nFR: 805 082 588\n \nOther international numbers available here:\nhttps://zoom.us/u/adlvrb8IL j\n \nMeeting ID: 618 156 403\n\nor join from a H.323/SIP Device:\n Dial: 162.255.37.11 (US West) or 162.255.36.11 (US East)\nMeeting ID: 618 156 403\n\nShare from a PC or MAC: https://zoom.us/share/618156403\n \nOr iPhone one-tap (US Toll): +16699006833\,618156403# or +16465588656\, 618156403#\n\nPassword for zoom call ends with x\n\nAll Austin Group part icipants are most welcome to join the call.\nThe call will last for 60 min utes.\n\n\nAn etherpad is usually up for a meeting\, with a URL using the date format as below:\n\nhttps://posix.rhansen.org/p/202x-mm-dd\n\n(Note t hat this uses The Open Group single sign on\,\nfor those individuals with gitlab.opengroup.org accounts.\nPlease contact Andrew if you need to be se tup)\n\nBug reports are available at:\nhttps://www.austingroupbugs.net\n DTSTART;TZID=America/New_York:20201005T11 DURATION:PT1H0M0S LAST-MODIFIED:20200930T032150Z ORGANIZER;CN=Single UNIX Specification:MAILTO:do-not-re...@opengroup.org SEQUENCE:0 STATUS:CONFIRMED SUMMARY:Austin Group teleconference +1 888 974 9888 PIN 618 156 403 TRANSP:OPAQUE URL:https://collaboration.opengroup.org/platform/single_unix_specification/ events.php X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-VISIBILITY:40 X-JOINBEFORE:5 X-CATEGORY:Teleconference X-PLATO-SITE:Single UNIX Specification X-PLATO-SITEID:136 END:VEVENT END:VCALENDAR meeting.ics Description: application/ics
