 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
8 messages in net.sourceforge.lists.courier-users[courier-users] Re: various bugs| From | Sent On | Attachments |
|---|---|---|
| Alan Curry | Aug 7, 2001 2:02 am | |
| Sam Varshavchik | Aug 7, 2001 4:38 am | |
| ves...@tana.it | Aug 7, 2001 7:23 am | |
| Lars Christensen | Aug 7, 2001 10:08 am | |
| Aly S.P Dharshi | Aug 7, 2001 11:47 am | |
| Sam Varshavchik | Aug 7, 2001 3:03 pm | |
| ves...@tana.it | Aug 7, 2001 6:47 pm | |
| Sam Varshavchik | Aug 7, 2001 7:05 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [courier-users] Re: various bugs | Actions... |
|---|---|---|
| From: | ves...@tana.it (ves...@tana.it) | |
| Date: | Aug 7, 2001 7:23:39 am | |
| List: | net.sourceforge.lists.courier-users | |
Sam Varshavchik writes:
Alan Curry writes: [...]
2. People who go running around with umask 022 all the time...
Some people always log in as root: they obviously don't like umask 022. For building Courier they must add "su" and "umask" to their scripts. (People use scripts for their configure options anyway, don't they?)
ipv6-style addresses into the Received headers...
So, people who do not fully understand mail headers will find the mail headers confusing. Yup.
I thought it was a mean for advertising ipv6 worldwide :)
Solution: install Courier correctly.
That's not easy. In fact it's rated "medium" in http://www.geocities.com/mailsoftware42/
Yes: that's always a problem - incorrectly set permissions mean that you have problems reading the file.
That's a good point. Even scripts like makehosteddomains need that permissions be corrected after running them. Courier has an open permissions model (which is why the lack of properly formatted error messages is felt so hardly.) Hence, it doesn't do any chown/chgrp/chmod.
System administrators obviously want to set their own rules for grouping users and the like. For real users, with telnet access, Courier doesn't break the existing security model, still letting users run their own scripts.
For virtual users one has to work out a suitable set of uids and gids. A rather obvious choice is courierusers:courierusers, which may or may not coincide with courier:courier (or whatever was given to configure). With MySQL one has the choice of assigning a different uid:gid to each virtual user.
Carefully planning permissions will be a relief when virtual users will be able to run their own scripts. Currently, webmail doesn't allow to edit .courier files and I guess a somewhat deeper understanding of security implications is needed before that happens.
I never understood why qmail didn't automatically create ./Maildir/ if it wasn't already there.
Well, try a bit harder to understand then, ok?
Admittedly, reporting that Maildir doesn't exist would be cleaner. But then, if that happened in real life, one would be happier to recover the mail message from a however formatted legacy mbox file. Again, the problem gets solved by proper scripts that invoke maildirmake and adjust permissions behind it. Since maildirmake doesn't know how to adjust permissions, it wouldn't make sense to invoke it automatically on the first message. (I'm not sure this is the only reason, nor that it applies to Qmail as well.)
I hope this helps. However, as I'm quite new to Courier myself, the above guesses may be either corrected by more experienced people or validated by silent=assent.
Ciao Ale