Re: Exim on slink - frozen messages

2000-09-16 Thread Gregory Wood
I found no directory under /var/cache/exim. I do have exim with potato running, so I looked at it and it does mention 'auto-thaw' in the config file. Mostly, it tells you to go look it up in the documentation, which I already did. *** REPLY SEPARATOR *** On 9/16/00 at 3:41 PM

Re: Exim on slink - frozen messages

2000-09-16 Thread Gregory Wood
I found no directory under /var/cache/exim. I do have exim with potato running, so I looked at it and it does mention 'auto-thaw' in the config file. Mostly, it tells you to go look it up in the documentation, which I already did. *** REPLY SEPARATOR *** On 9/16/00 at 3:41 PM

Re: Exim on potato

2000-09-16 Thread tps
On Sat, Sep 16, 2000 at 08:00:02AM -0500, Gregory Wood wrote: > When the customer trys to send to an account outside the local ISP's control, > it receives an immediate 'look-up' error (i.e. DNS failure). Likewise when an > outside account tries to access the customer, they get an 'account not fo

Re: Exim on slink - frozen messages

2000-09-16 Thread Dariush Pietrzak
> I've been through my exim doc and found 'auto-thaw' (section 3.3) but I am > unsure how to use it or even if it is the right option. there is example of how to use it in examples and in your default /etc/exim.conf. I don't use it, i do sth like this: cd /var/cache/exim/msglog exim -Mt *

Exim on potato

2000-09-16 Thread Gregory Wood
About a month ago, I set up a mail server for a local customer. His ISP provides a wireless service with a firewall at his location. The firewall is set up to allow email (ports 110 and 25) through to a specific local IP address.   The setup of Exim went so smoothly that I didn't even make

Exim on slink - frozen messages

2000-09-16 Thread Gregory Wood
I was going through my exim mainlog file and find that I have 200+ frozen messages. I would like to get rid of them.   I've been through my exim doc and found 'auto-thaw' (section 3.3) but I am unsure how to use it or even if it is the right option.   Likewise, section 32.3, Long-term failu

Re: Exim on potato

2000-09-16 Thread tps
On Sat, Sep 16, 2000 at 08:00:02AM -0500, Gregory Wood wrote: > When the customer trys to send to an account outside the local ISP's control, it >receives an immediate 'look-up' error (i.e. DNS failure). Likewise when an outside >account tries to access the customer, they get an 'account not fou

Re: Exim on slink - frozen messages

2000-09-16 Thread Dariush Pietrzak
> I've been through my exim doc and found 'auto-thaw' (section 3.3) but I am unsure >how to use it or even if it is the right option. there is example of how to use it in examples and in your default /etc/exim.conf. I don't use it, i do sth like this: cd /var/cache/exim/msglog exim -Mt * --

Exim on potato

2000-09-16 Thread Gregory Wood
About a month ago, I set up a mail server for a local customer. His ISP provides a wireless service with a firewall at his location. The firewall is set up to allow email (ports 110 and 25) through to a specific local IP address.   The setup of Exim went so smoothly that I didn't even make

Exim on slink - frozen messages

2000-09-16 Thread Gregory Wood
I was going through my exim mainlog file and find that I have 200+ frozen messages. I would like to get rid of them.   I've been through my exim doc and found 'auto-thaw' (section 3.3) but I am unsure how to use it or even if it is the right option.   Likewise, section 32.3, Long-term failu

SSH and chroot()

2000-09-16 Thread chris
Hi all, I've written a small patch for F-Secure SSH version 1 (1.2.30) which adds a chroot() to home directory option to SSH. Basically this works by specifying GuestUser directives in /etc/sshd_config, listing which users should be chroot()ed to their home. I have informed the SSH mailing list,

SSH and chroot()

2000-09-16 Thread chris
Hi all, I've written a small patch for F-Secure SSH version 1 (1.2.30) which adds a chroot() to home directory option to SSH. Basically this works by specifying GuestUser directives in /etc/sshd_config, listing which users should be chroot()ed to their home. I have informed the SSH mailing list