Hi,
I use cpio to backup nfs server:
find . -depth | cpio -o -v --format=newc | ssh [EMAIL PROTECTED] "
/bin/cat > /PathBackup/file.cpio "
The backup directory on backup server has xfs file system
When I check the integrity of cpio file:
cat file.cpio |cpio -itv
, I've error messages:
Hi
I have a mail server with some domains (about 200). I'm taking them from a
sendmail and putting them on a postfix-ldap + courier-ldap + amavisd +
spamassassin + clamav (thanks to perdition, the pop/imap proxy, I am doing
this and nobody notices). Everything goes well, but I have a doubt.
On
Hi
I was just thinking... Courier-ldap authentication needs some user/pass on the
config file to validate on the LDAP server and then, once validated, it looks
for the user and pass of the pop-ing user. That is "2 auth" on one action.
Just a thought... wouldn't be a better solution to use the us
On Tue, May 25, 2004 at 11:57:36AM +0200, Tom?s N??ez wrote:
> Hi
> I have a mail server with some domains (about 200). I'm taking them from a
> sendmail and putting them on a postfix-ldap + courier-ldap + amavisd +
> spamassassin + clamav (thanks to perdition, the pop/imap proxy, I am doing
> t
El Martes, 25 de Mayo de 2004 12:06, Brett Parker escribió:
>
> How about option 3...
>
> Add a wildcard to the bottom of the domain name to catch all the other
> rubbish...
>
> @domain.name[EMAIL PROTECTED]
>
> This will catch anything that's not already caught by the addresses
> befo
Hi,
I use cpio to backup nfs server:
find . -depth | cpio -o -v --format=newc | ssh [EMAIL PROTECTED] "
/bin/cat > /PathBackup/file.cpio "
The backup directory on backup server has xfs file system
When I check the integrity of cpio file:
cat file.cpio |cpio -itv
, I've error messages:
Hi
I have a mail server with some domains (about 200). I'm taking them from a
sendmail and putting them on a postfix-ldap + courier-ldap + amavisd +
spamassassin + clamav (thanks to perdition, the pop/imap proxy, I am doing
this and nobody notices). Everything goes well, but I have a doubt.
On
Hi
I was just thinking... Courier-ldap authentication needs some user/pass on the
config file to validate on the LDAP server and then, once validated, it looks
for the user and pass of the pop-ing user. That is "2 auth" on one action.
Just a thought... wouldn't be a better solution to use the us
On Tue, May 25, 2004 at 11:57:36AM +0200, Tom?s N??ez wrote:
> Hi
> I have a mail server with some domains (about 200). I'm taking them from a
> sendmail and putting them on a postfix-ldap + courier-ldap + amavisd +
> spamassassin + clamav (thanks to perdition, the pop/imap proxy, I am doing
> t
El Martes, 25 de Mayo de 2004 12:06, Brett Parker escribió:
>
> How about option 3...
>
> Add a wildcard to the bottom of the domain name to catch all the other
> rubbish...
>
> @domain.name[EMAIL PROTECTED]
>
> This will catch anything that's not already caught by the addresses
> befo
10 matches
Mail list logo
