| 1 |
Ahhh yes, screen! |
| 2 |
|
| 3 |
Good idea. ;) I'll have to think about how to implement this because |
| 4 |
I'm not certain I'll have access to one single server from all the |
| 5 |
different locations I know I'm going to be using mutt as a mail |
| 6 |
client. |
| 7 |
|
| 8 |
:) |
| 9 |
|
| 10 |
Definitely geeky to boot! Good idea indeed! |
| 11 |
|
| 12 |
-j |
| 13 |
|
| 14 |
On Sun, May 3, 2009 at 5:10 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 15 |
> On Sunday 03 May 2009 06:06:54 James wrote: |
| 16 |
>> Alan, |
| 17 |
>> |
| 18 |
>> Thanks for the response. :) |
| 19 |
>> |
| 20 |
>> I've thought about doing something similar to this, but it's a last |
| 21 |
>> resort. I end up using mutt on various different workstations and it'd |
| 22 |
>> be nice to run everything "locally". Obviously a solution where I'm |
| 23 |
>> fetching mail on every machine where I'm using mutt doesn't scale very |
| 24 |
>> well. |
| 25 |
> |
| 26 |
> I've got several hard-core network engineer users with the same problem. They |
| 27 |
> solved it in a neat way, by running mutt in a permanent screen session on a |
| 28 |
> server I provided for the purpose. Getmail is now not necessary as I deliver |
| 29 |
> their mail to that machine. Working on the LAN and from home over vpn it just |
| 30 |
> works, connecting from home without vpn is a simple matter of ssh port |
| 31 |
> forwarding. Their shell profiles on every workstation runs screen and |
| 32 |
> .screenrc is set up to automatically connect to that server. |
| 33 |
> |
| 34 |
> It works for them and is just geeky enough to appeal :-) |
| 35 |
> |
| 36 |
> -- |
| 37 |
> alan dot mckinnon at gmail dot com |
| 38 |
> |
Archives