On Saturday 1 December 2018 16:19,
Kevin J. McCarthy put forth the proposition:
> On Sat, Dec 01, 2018 at 11:31:38PM +, Dave Woodfall wrote:
> > Is there a way to make sure that all mail sent via CLI saves a copy in
> > =Sent? The only way I can see at the moment is by using a separate
> > st
On Sat, Dec 01, 2018 at 11:31:38PM +, Dave Woodfall wrote:
Is there a way to make sure that all mail sent via CLI saves a copy in
=Sent? The only way I can see at the moment is by using a separate
startup file.
Does adding -e 'set record="=Sent"' to the command line help?
--
Kevin J. McC
On Tue, May 21, 2013 at 06:56:56AM +0100, David Woodfall wrote:
> On (20/05/13 20:33), Patrick Shanahan put forth the
> proposition:
> >* David Woodfall [05-20-13 20:01]:
> >>I've found that sending mail as root saves a copy in /root/mail/Sent/,
> >>whereas sending as my user doesn't seem to kee
On (20/05/13 20:33), Patrick Shanahan put forth the
proposition:
* David Woodfall [05-20-13 20:01]:
I've found that sending mail as root saves a copy in /root/mail/Sent/,
whereas sending as my user doesn't seem to keep a record at all.
The only difference between root and user is that root i
On (20/05/13 20:33), Patrick Shanahan put forth the
proposition:
* David Woodfall [05-20-13 20:01]:
I've found that sending mail as root saves a copy in /root/mail/Sent/,
whereas sending as my user doesn't seem to keep a record at all.
The only difference between root and user is that root i
* David Woodfall [05-20-13 20:01]:
> I've found that sending mail as root saves a copy in /root/mail/Sent/,
> whereas sending as my user doesn't seem to keep a record at all.
>
> The only difference between root and user is that root is using mbox
> and user is maildir.
>
> Is there some way aro
