On Sun, Dec 18, 2022 at 03:50:51PM -0600, Brian Conway wrote:
> On Sun, Dec 18, 2022, at 3:29 PM, Jason McIntyre wrote:
> > On Fri, Dec 16, 2022 at 02:21:41AM +, Tim Chase wrote:
> >> According to the POSIX definitions for mail(1) & mailx(1), the
> >> (s)ave command should save to "mbox" if
On 22-12-18 09:29PM, Jason McIntyre wrote:
> On Fri, Dec 16, 2022 at 02:21:41AM +, Tim Chase wrote:
> > According to the POSIX definitions for mail(1) & mailx(1), the
> > (s)ave command should save to "mbox" if the filename is not specified
> >
> > > Save the specified messages in the file
On Sun, Dec 18, 2022, at 3:29 PM, Jason McIntyre wrote:
> On Fri, Dec 16, 2022 at 02:21:41AM +, Tim Chase wrote:
>> According to the POSIX definitions for mail(1) & mailx(1), the
>> (s)ave command should save to "mbox" if the filename is not specified
>>
>> > Save the specified messages in
On Fri, Dec 16, 2022 at 02:21:41AM +, Tim Chase wrote:
> According to the POSIX definitions for mail(1) & mailx(1), the
> (s)ave command should save to "mbox" if the filename is not specified
>
> > Save the specified messages in the file named by the pathname
> > file, or the mbox if the file
On 22-12-16 02:21AM, Tim Chase wrote:
> According to the POSIX definitions for mail(1) & mailx(1), the
> (s)ave command should save to "mbox" if the filename is not specified
>
> ...
>
> However, when exercising this functionality, mail(1) on OpenBSD
> (also tested on FreeBSD where the same issue
According to the POSIX definitions for mail(1) & mailx(1), the
(s)ave command should save to "mbox" if the filename is not specified
> Save the specified messages in the file named by the pathname
> file, or the mbox if the file argument is omitted
(newer spec)
