[xmail] Re: MAIL FROM: Syntax

2005-02-18 Thread Francesco Vertova
At 17.06 17/02/05 +0100, you wrote: What's a clear response ;-) Thanks Chris ;-) What is the new crypto algo used here ? Didn't pass any crack here ... = ;-) Francis -Message d'origine- De : Chris L. Franklin [mailto:[EMAIL PROTECTED] Envoy=E9 : jeudi 17 f=E9vrier 2005 14:30 =C0 :

[xmail] Default permissions, umask

2005-02-18 Thread Darren
Hi all, I've noticed on my FreeBSD 5.3 box that all normal files (logs, maildir emails, dnscache files, tabindexes etc) are all created by xmail with a chmod value of 666, aka world readable/writeable by everyone. I'm sure this cannot be the desired behavior since pop3 passwords are for some

[xmail] Re: Default permissions, umask

2005-02-18 Thread Sönke Ruempler
[EMAIL PROTECTED] wrote on Friday, February 18, 2005 12:14 PM: Hi all, =20 I've noticed on my FreeBSD 5.3 box that all normal files (logs, maildir emails, dnscache files, tabindexes etc) are all created by xmail with a chmod value of 666, aka world readable/writeable by everyone. I'm sure

[xmail] Re: Default permissions, umask

2005-02-18 Thread decker
Thanks for the reply S=F6nke ! Make your MailRoot folder chmod 700. It does not matter what modes the files in you MailRoot have then. I saw that in the install notes, I was just hoping for a more thorough=20 solution. Having one directory's permissions be the line between fairly=20 secure

[xmail] Re: Default permissions, umask

2005-02-18 Thread Sönke Ruempler
On Friday, February 18, 2005 8:52 PM [GMT+1=CET], decker [EMAIL PROTECTED] wrote: I saw that in the install notes, I was just hoping for a more thorough=20 solution. Having one directory's permissions be the line between fairly=20 secure email and wide open email makes me a little uneasy. An

[xmail] Re: Default permissions, umask -- Mail Rejection Warning

2005-02-18 Thread Sönke Ruempler
On Friday, February 18, 2005 9:23 PM [GMT+1=CET], [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Your Message got filtered out because it was not possible to validate it. No mail exchange could be identified as belonging to your organization. This is why it has been identified as spam. This is

[xmail] Re: Default permissions, umask

2005-02-18 Thread decker
Hi As I said, there is no extra security if the files are 600 or something similar (since your MailRoot is 700). XMail does not handle real system accounts for storing mail (and that is imho one of it's biggest advantages). I'm gonna have to disagree. I know what you are saying, but security

[xmail] R: Re: Default permissions, umask

2005-02-18 Thread Dario
Why not installing xmail in a sandbox? Dario - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]

[xmail] Re: R: Re: Default permissions, umask

2005-02-18 Thread decker
Hello, Why not installing xmail in a sandbox? Good call :) I am planning on using a freebsd jail for it eventually, just testing the waters right now. Allthough if the jail/sandbox is broken into, the problems with the current permissions still apply and the cracker can still read the emails

[xmail] R: Re: R: Re: Default permissions, umask

2005-02-18 Thread Dario
I understand what you mean, the sandbox cannot make it 99.9% safe. Don't really know why files are saved with those permissions, might be something to do with how filters are processed, as you pointed... I've tested this against qmail and postfix; files are 600. Although a brake through it's

[xmail] Only authenticated user can send mail

2005-02-18 Thread Michal Altair Valasek
Hello, I need to configure Xmail to accept messages via SMTP only after authentication or from specified IP. The server is not an MX, MX is dedicated server for incoming mail only. I want to prohibit any SMTP communication, with exception of authenticated users and the frontend servers. I

[xmail] Re: R: Re: R: Re: Default permissions, umask

2005-02-18 Thread decker
Me again 8=] After work tonight I spent a few moments and put together a patch for xmail 1.21 that: 1)substitutes the POP3 user's pass word in the pop-* log with (password) 2)Sets the umask to 0077 (for BSD, Linux and Solaris) so all files created are done so with the permissions 0600: : ll