RE: [courier-users] Re: Does courier / maildrop unset SENDER if it's empty?
Personally I think "auto-unsetting" empty vars. Is not right. Can I make a
case for my opinion?
A non-existant shell variable equating to "" is not the same as the variable
not existing. From what I have seen (and comments read) many programs rely
on the existance tests - the test is common in most languages (is_set /
is_defined / defined / etc.) as is the specific ability to unset a variable.
In fact iirc, someone was talking before about adding an unset command to
maildrop (requiring parenthesis and made comment that it wouldn't be that
hard.
Was this a recent addition? I've seen people stating that "X" used to work
and now it doesn't... but I don't know first hand so I'm asking - is there
anyone opposed to changing this behaviour?
As maildrop is not persistant (it is launched and terminated for each
delivery) I don't see the benefit to this cleanup process particlarly when I
consider the number of times people have to resort to calling external
programs or altering programs for what appears to be a non-standard
procedure.
Even standard shells avoid this (man bash AND man sh):
"A parameter is set if it has been assigned a value. The
null string is a valid value. Once a variable is set, it
may be unset only by using the unset builtin command (see
SHELL BUILTIN COMMANDS below)."
In SQL, "" is not NULL...
Was there a reason this was done? Does it outweigh the problems it seems to
cause?
Thanks.
m/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Courier
User
Sent: Tuesday, January 13, 2004 5:46 PM
To: [EMAIL PROTECTED]
Subject: [courier-users] Re: Does courier / maildrop unset SENDER if
it's empty?
Sam Varshavchik <[EMAIL PROTECTED]> writes:
> Courier User writes:
>
>
>> Could someone (Sam?) explain why that 'delete' statement exists? Is
>> there part of maildrop or courier that depends on this odd behavior?
>
> Because if variable FOO is not defined, $FOO defaults to an empty string.
>
> Logically, the converse should also be true.
But the converse varies greatly from the way that most software that I
know of functions. It seems contrary to "the principle of least
surprise" ("PoLS") to have A be equivalent to B, instead of C:
A: (in maildrop)
SENDER=""
B: (in an xfilter program)
getenv("SENDER") == NULL /* contrary to PoLS */
C: (in an xfilter program)
getenv("SENDER") != NULL /* adheres to PoLS */
In other words, in most software I know of, A => C. But in maildrop,
A => B.
--
Courier User
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] Does courier / maildrop unset SENDER if it's empty?
In a line like this: >>cc "| env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter" the "" are the only quotes processed by maildrop. As they are double quotes (assuming same interpetation as bash / php / perl etc.) they allow variable interpolation. The '' surrounding sender are ignored by maildrop, and when the line appears to the shell, the value is already in place of the quotes. My reason for including the quotes is the similar to Gordons for escaping (forgot that part - thanks!) - to protect against embedded spaces or empty values getting confusing the end of the intended value... Consider if: SENDER="bob smith" without the quotes, smith would cause a syntax error. m/ --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Backup MX configuration
Ok, I've tried this now and either I'm missing something or the semantics aren't quite as you explained. I'll try to explain my total configuration to give you a better view of what I'm trying to acheive. The machine is called mail.craffe.se. It is a MX for the domain craffe.se. Sending mail to the domain works fine (it is later forwarded to an internal server using esmptroutes). It is also a backup MX for the domain mathias.nu. Being a backup MX I have the machine's name in locals in order for the backup MX semantics to function properly. Sending mail to the domain mathias.nu also works perfectly fine. Now for the problem. Sending mail to, for example, [EMAIL PROTECTED] results in the machine trying to deliver the mail to the local user account 'luser'. I added mail.craffe.se to esmtproutes in an attempt to redirect the mail, but the locals file seems to have priority. What I'd like is that mail would have been redirected to [EMAIL PROTECTED] (i.e. to the domain, not the machine) or have it rejected (with '550 User unknown' or similar). From what I can gather the only system that has priority over locals is the aliases. And I doesn't seem to be a syntax that gives me what I want (except one aliases for each and every user on the machine). So, what are my options? I don't like the current situation where the local users can receive mail but I can't figure out how to stop it. Regards Pierre Patrick O'Reilly wrote: From: "Pierre Ossman" <[EMAIL PROTECTED]> Thanks for the reply, but I'm afraid it doesn't quite answer my questions. The problem was never mail directed to the domain that it was a backup MX for. The problem is mail directed at the mail server itself. So in a more condensed form: * Does it check in 'me' when comparing MX records if 'locals' doesn't exist? * How can I block/redirect mail addressed to the mail server (_not_ the domain it's handling) without having to put up an alias for every user on the machine? Ah. Well, all the hostnames must be in 'locals', both for primary and secondary roles. And all the domain names must be in 'esmtpacceptmailfor'. The server will compare itself with the MX records. * Where the server finds itself to be the MX at the lowest priority, it will keep the email - you need to have a local account, or perhaps forward it to a private internal mail server using 'smtproutes'. Of course, if you relay the mail using smtproutes, then the destination server will do the user account validation. * Where the server finds itself to be a secondary MX, it will queue the mail for the primary MX. I hope this is what you needed... Patrick. --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: Does courier / maildrop unset SENDER if it's empty?
Sam Varshavchik <[EMAIL PROTECTED]> writes:
> Courier User writes:
>
>
>> Could someone (Sam?) explain why that 'delete' statement exists? Is
>> there part of maildrop or courier that depends on this odd behavior?
>
> Because if variable FOO is not defined, $FOO defaults to an empty string.
>
> Logically, the converse should also be true.
But the converse varies greatly from the way that most software that I
know of functions. It seems contrary to "the principle of least
surprise" ("PoLS") to have A be equivalent to B, instead of C:
A: (in maildrop)
SENDER=""
B: (in an xfilter program)
getenv("SENDER") == NULL /* contrary to PoLS */
C: (in an xfilter program)
getenv("SENDER") != NULL /* adheres to PoLS */
In other words, in most software I know of, A => C. But in maildrop,
A => B.
--
Courier User
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Does courier / maildrop unset SENDER if it's empty?
Roland wrote: --On Dienstag, 13. Januar 2004 12:37 -0800 "Mitch \\(WebCob\\)" <[EMAIL PROTECTED]> wrote: cc "| env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter" I referred to the single quote which will prevent any variable expansion under sh. Test for yourself: $ SENDER='$SENDER' env | grep SENDER I am surprised expansion within single-quotes works with env... I don't think "env" has anything to do with it. I'm pretty sure the $SENDER is expanded by maildrop before passing to the shell. ...which reminds me: never pass "$SENDER" to the shell without using escape() to get a safe version: SH_SENDER=escape($SENDER) cc "| env SENDER='$SH_SENDER' /usr/local/tmda/bin/tmda-filter" --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] blocking a user id?
--On Dienstag, 13. Januar 2004 12:07 -0800 "Mitch \\(WebCob\\)" <[EMAIL PROTECTED]> wrote: > I'd like to allow cron jobs to continue to call sendmail... however, I don't > want any chance of "nobody" (i.e. apache) calling sendmail directly. All > other mail is of course traceable as the unique user id will nail any user > spamming etc. Enforce suexec for anything executed by Apache. Whith PHP there are also other ways. Roland --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] Does courier / maildrop unset SENDER if it's empty?
--On Dienstag, 13. Januar 2004 12:37 -0800 "Mitch \\(WebCob\\)"
<[EMAIL PROTECTED]> wrote:
> Hi Roland - thanks - but if you read the followups I got it to work - the
> problem is that courier DELETES empty env's which have to be forced before
> calling programs that depend on their existance - not the value they
> contain.
>
> cc "| env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
was:
>> to "| SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
I referred to the single quote which will prevent any variable
expansion under sh. Test for yourself:
$ SENDER='$SENDER' env | grep SENDER
I am surprised expansion within single-quotes works with env...
But the point is still there: TDMA is supposed to return challenges
to unknown senders which is just not possible with bounces.
And tdma especially trolls for bounces with exactly those challenges.
The line in .mailfilter should be something like:
cc "| test \"$SENDER\" && tdma-filter"
now the exitcodes from this line will be:
0: tdma approved
1: bounce, empty or missing sender
99: tdma nagging (possibly forged) sender
and then simply stop further processing on 99:
if ($EXITCODE == "99")
{
EXITCODE=0
exit
}
...continue .mailfilter processing
If you want to do the same thing from .courier I'd suggest something
like the following. Here we have to take care not to return '1' to
courier because this would be interpreted as temporary failure and
retried forever:
| test "$SENDER" && { tdma || exit 99; } || exit 0
./Maildir/
of course this is all untested since I never would use TDMA or
any other such abusive filtering methods.
And yes, courier should not remove the empty sender imho, but there
is also no reason for tdma to be so picky about...
Roland
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: Courier 20040112 - imapd manpage patch
Stefan Hornburg writes: Patch from me attached. Here it goes with the patch. This patch doesn't do anything: -to the default IMAP mailbox, which is usually -\fI./Maildir\fR. +to the default IMAP mailbox, which is usually \fI./Maildir\fR. The original nroff sources are syntactically correct. I dimly recall a bug in very old versions of nroff that misparsed lines that have an escape sequence followed by a period as a command, as if the escape sequence did not exist and the period lead off the line. This is really an nroff bug. pgp0.pgp Description: PGP signature
[courier-users] Re: Courier 20040112 - imapd manpage patch
Gordon Messmer writes: Stefan Hornburg wrote: The manual page reads: ... The sole argument to imapd is the pathname to the default IMAP mailbox, which is usually Some authentication modules are capable of specifying a ... Obviously there is some text missing. This used to happen with fairly recent docbook utils. I sent a patch to their maintainer probably 6 - 9 months ago, and we got it resolved. Is the text missing from the docbook sources, or just the man pages generated from them? For that matter, where are the sgml sources? The man pages seem to be generated, but I can't find the source. The SGML sources are in CVS. I just checked, and yes indeed docbook now does something different. I'll fix this by rebuilding the man pages. pgp0.pgp Description: PGP signature
[courier-users] Re: alternate method of configuring .courier-default processing?
Mitch (WebCob) writes: Last question I promise (for a while anyways) I'm managing users that are largely virtual - is there an alternative to creating .courier-default files in the home directories? Replace virtual domain aliases with true virtual domains, using hosteddomains, and adjust your authentication database accordingly. pgp0.pgp Description: PGP signature
Re: [courier-users] Re: Courier 20040112 - imapd manpage patch
Sam Varshavchik wrote: There was no patch, and in any case the man pages are generated from Docbook SGML, which you'll need to pull from CVS. Looking at the latest build, the nroff source appears to be correct: The sole argument to \fBimapd\fR is the pathname to the default IMAP mailbox, which is usually \fI./Maildir\fR. It's not. I don't remember exactly what's wrong, but I'm pretty sure the '.' character has a special meaning right after the macro that happens to precede it in this instance. Older releases of docbook didn't translate the '.' to its escaped sequence, so it gets munged. Newer releases should not have this bug. --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: afx compilation issue
Dan Melomedman writes: Trying to compile on FreeBSD 4.9-STABLE. Errors: Making all in afx make all-am g++ -I.. -I./.. -Wall -g -O2 -L/usr/local/lib -o testafxpipe testafxpipe.o l ibafx.a testafxpipe.o: In function `main': /var/tmp/courier-0.44.2/afx/testafxpipe.C:217: undefined reference to `ostream:: You do not have C++ development libraries installed. pgp0.pgp Description: PGP signature
[courier-users] Re: Does courier / maildrop unset SENDER if it's empty?
Courier User writes: Could someone (Sam?) explain why that 'delete' statement exists? Is there part of maildrop or courier that depends on this odd behavior? Because if variable FOO is not defined, $FOO defaults to an empty string. Logically, the converse should also be true. pgp0.pgp Description: PGP signature
Re: [courier-users] is there a --without-fax switch?
Egbert Jan van den Bussche wrote: The list is now down to missing Ghostscript, xpdf and netpbm-progs. I cannot repeat all the other rpm's needed... a lot. Several with other (new?) names. Most of those are now called lib I think that these 3 rpms (with again a lot of underlying dependencies) are only needed to handle faxes. I do not want that. Is there a --without-fax switch??? I couldn't find it in the docs. Pity the getting to a usable development environment (just want to do a rpmbuild) is such a hassle. If you "rpmbuild --without fax courier-.tar.gz", rpm will not ask you for the fax dependencies. However, if you have enough of them that courier builds the fax module anyway, the whole thing will fail. Try with the proper switch and see what results you get. --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: courier-0.44.2.20040112 make check fails
Alexander Gretha writes: all goes well until SMAP test fails: INFO: LOGIN, user=confmdtest, ip=[127.0.0.1], protocol=SMAP1 INFO: LOGOUT, user=confmdtest, ip=[127.0.0.1], headers=0, body=0 make[1]: *** [check-am] Error 1 make[1]: Leaving directory `/home/rlx/courier-0.44.2.20040112/imap' make: *** [check-recursive] Error 1 this is on suse 9.0, suse 8.2 builds ok. strange thing. no ill effects noticeable, though. In the imap directory, run "make testsuite-smap | diff -U 3 smaptestsuite.txt -", and see what comes out. pgp0.pgp Description: PGP signature
Re: [courier-users] Courier 20040112 - imapd manpage patch
On Tue, 13 Jan 2004 15:57:07 -0800 Gordon Messmer <[EMAIL PROTECTED]> wrote: > Stefan Hornburg wrote: > > > > The manual page reads: > ... > > The sole argument to imapd is > > the pathname to the default IMAP mailbox, which is usually > > Some authentication modules are capable of specifying a > ... > > Obviously there is some text missing. > > This used to happen with fairly recent docbook utils. I sent a > patch to their maintainer probably 6 - 9 months ago, and we got > it resolved. Is the text missing from the docbook sources, or > just the man pages generated from them? For that matter, where > are the sgml sources? The man pages seem to be generated, but > I can't find the source. That is probably the reason for the wrong manpage source. Thanks for the hint. Bye Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Courier 20040112 - imapd manpage patch
Stefan Hornburg wrote: The manual page reads: ... The sole argument to imapd is the pathname to the default IMAP mailbox, which is usually Some authentication modules are capable of specifying a ... Obviously there is some text missing. This used to happen with fairly recent docbook utils. I sent a patch to their maintainer probably 6 - 9 months ago, and we got it resolved. Is the text missing from the docbook sources, or just the man pages generated from them? For that matter, where are the sgml sources? The man pages seem to be generated, but I can't find the source. --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Courier 20040112 - imapd manpage patch
On Wed, 14 Jan 2004 00:30:43 +0100 Stefan Hornburg <[EMAIL PROTECTED]> wrote: > On Mon, 12 Jan 2004 22:54:50 -0500 > Sam Varshavchik <[EMAIL PROTECTED]> wrote: > > > Download: http://www.courier-mta.org/download.php > > > > Feedback from the 20040110 build was helpful. This build fixes all reported > > bugs. > > Bug Report (Debian #227551) > > package: courier-imap > severity: minor > > The manual page reads: > > The last daisy-chained command is imapd, which is the > actual IMAP server, which is started from the logged-in > account's home directory. The sole argument to imapd is > the pathname to the default IMAP mailbox, which is usually > Some authentication modules are capable of specifying a > different filename, by setting the MAILDIR environment > variable. > > Obviously there is some text missing. > > Thanks to Auke Jilderda <[EMAIL PROTECTED]> for the original > report. > > Patch from me attached. Here it goes with the patch. Ciao Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team imapd-manpage.patch Description: Binary data
[courier-users] Re: Courier 20040112 - imapd manpage patch
Stefan Hornburg writes: The manual page reads: The last daisy-chained command is imapd, which is the actual IMAP server, which is started from the logged-in account's home directory. The sole argument to imapd is the pathname to the default IMAP mailbox, which is usually Some authentication modules are capable of specifying a different filename, by setting the MAILDIR environment variable. Obviously there is some text missing. Thanks to Auke Jilderda <[EMAIL PROTECTED]> for the original report. Patch from me attached. There was no patch, and in any case the man pages are generated from Docbook SGML, which you'll need to pull from CVS. Looking at the latest build, the nroff source appears to be correct: The sole argument to \fBimapd\fR is the pathname to the default IMAP mailbox, which is usually \fI./Maildir\fR. Some authentication modules are capable of specifying a different filename, by setting the \fBMAILDIR\fR environment variable. pgp0.pgp Description: PGP signature
[courier-users] Courier 20040112 - imapd manpage patch
On Mon, 12 Jan 2004 22:54:50 -0500 Sam Varshavchik <[EMAIL PROTECTED]> wrote: > Download: http://www.courier-mta.org/download.php > > Feedback from the 20040110 build was helpful. This build fixes all reported > bugs. Bug Report (Debian #227551) package: courier-imap severity: minor The manual page reads: The last daisy-chained command is imapd, which is the actual IMAP server, which is started from the logged-in account's home directory. The sole argument to imapd is the pathname to the default IMAP mailbox, which is usually Some authentication modules are capable of specifying a different filename, by setting the MAILDIR environment variable. Obviously there is some text missing. Thanks to Auke Jilderda <[EMAIL PROTECTED]> for the original report. Patch from me attached. Bye Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] is there a --without-fax switch?
H1! Back to the list to give Courier another try. I've spend most of the evening to install the packages needed to do a rpmbuild -ta on my Mandrake 9.2 Linux server. I do not have any X stuff installed (it is a server). I downloaded the last Courier tarball snapshot. The list is now down to missing Ghostscript, xpdf and netpbm-progs. I cannot repeat all the other rpm's needed... a lot. Several with other (new?) names. Most of those are now called lib I think that these 3 rpms (with again a lot of underlying dependencies) are only needed to handle faxes. I do not want that. Is there a --without-fax switch??? I couldn't find it in the docs. Pity the getting to a usable development environment (just want to do a rpmbuild) is such a hassle. Thanks for any advise! Egbert Jan NL --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] deleting messages reviewed...
ok - maybe I misunderstood what I was reading... I saw people writing that "to /dev/null" wasn't working for them - and someone else was talking about permissions issues and how courier wouldn't deliver to a world writable file... Maybe this was an old problem? or maybe I misread. That's much easier then... m/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chris Petersen Sent: Tuesday, January 13, 2004 1:43 PM To: [EMAIL PROTECTED] Subject: Re: [courier-users] deleting messages reviewed... > I'm dumping message by piping to cat and dumping it's output to /dev/null - > we can't deliver directly to it due to ownership issues - right? wouldn't it > make sense to have an exception to the security rule for /dev/null to avoid > having to shell and cat just to dump a message? What ownership issues? /dev/null is world-writable. I use "to /dev/null" in my .mailfilter all the time. Or am I misunderstanding what you're trying to do? -- Chris Petersen Programmer / Web Designer Silicon Mechanics: http://www.siliconmechanics.com/ Blade Servers: http://www.siliconmechanics.com/c292/blade-server.php 1U Servers: http://www.siliconmechanics.com/c272/1u-server.php --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] postfix, courier, ldap and quotas.
Roland wrote: > --On Dienstag, 13. Januar 2004 13:35 +0100 Mauro > <[EMAIL PROTECTED]> wrote: > >> I use linux debian woody with postfix-1.1.11, courier-pop 0.37.3, >> courier-imap 1.4.3 and ldap to autenticate virtual users. >> In my ldap database also I have an attribute in which to put quota >> value. >> I don't have any idea how to configure quotas. > > You missed maildrop, no softquotas possible without. > >> Perhaps the courier version that come with debian woody isn't able to >> use quotas? > > Its completely out of date, and courier's quota managment > had some changes since then. Get the packages from Sarge. > You might also take a look at using the packages from http://www.backports.org/ if you want to keep everything else stock woody > Roland > > > > --- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > ___ > courier-users mailing list > [EMAIL PROTECTED] > Unsubscribe: > https://lists.sourceforge.net/lists/listinfo/courier-users --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] deleting messages reviewed...
> I'm dumping message by piping to cat and dumping it's output to /dev/null - > we can't deliver directly to it due to ownership issues - right? wouldn't it > make sense to have an exception to the security rule for /dev/null to avoid > having to shell and cat just to dump a message? What ownership issues? /dev/null is world-writable. I use "to /dev/null" in my .mailfilter all the time. Or am I misunderstanding what you're trying to do? -- Chris Petersen Programmer / Web Designer Silicon Mechanics: http://www.siliconmechanics.com/ Blade Servers: http://www.siliconmechanics.com/c292/blade-server.php 1U Servers: http://www.siliconmechanics.com/c272/1u-server.php --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] alternate method of configuring .courier-default processing?
Last question I promise (for a while anyways) I'm managing users that are largely virtual - is there an alternative to creating .courier-default files in the home directories? what makes this test? Thanks again m/ --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: Does courier / maildrop unset SENDER if it's empty?
Roland <[EMAIL PROTECTED]> writes:
> --On Dienstag, 13. Januar 2004 09:55 -0800 "Mitch \\(WebCob\\)"
> <[EMAIL PROTECTED]> wrote:
>
>> I'm trying to call TMDA, and I get an error that SENDER is not set during
>> one of it's processes... it IS set during the others... the difference in
>> the messages (from the logs) is that in this case from is showing as <>
>>
>> Someone on the TMDA list says it is maildrop unsetting the RMPTY env vars...
>>
>> I tried changing my code to reset it, but it isn't working (syntax error)
>>
>> to "| SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
>
> This wont ever work, and there is also absolutely no point
> to pipe mails with empty sender into tmda.
This works fine if you use "env" as follows:
to "| /usr/bin/env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
TMDA works fine with a SENDER environment variable set to the empty
string (""). It just fails when the SENDER variable has been completely
removed from the environment, as the following command
(counter-intuitively) does within maildrop:
SENDER=""
Using the above command (with /usr/bin/env) guarantees that TMDA works
from within maildrop. I know, because that's what I had to do on my
host to get it working.
> use |env to see what variables are available, and import
> those you need in maildrop.
>
> Roland
--
Courier User
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] Does courier / maildrop unset SENDER if it's empty?
Hi Roland - thanks - but if you read the followups I got it to work - the problem is that courier DELETES empty env's which have to be forced before calling programs that depend on their existance - not the value they contain. cc "| env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter" does work... regardless of whether sender has a value (3 out of 4 calls) or not. m/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Roland Sent: Tuesday, January 13, 2004 12:21 PM To: [EMAIL PROTECTED] Subject: Re: [courier-users] Does courier / maildrop unset SENDER if it's empty? --On Dienstag, 13. Januar 2004 09:55 -0800 "Mitch \\(WebCob\\)" <[EMAIL PROTECTED]> wrote: > I'm trying to call TMDA, and I get an error that SENDER is not set during > one of it's processes... it IS set during the others... the difference in > the messages (from the logs) is that in this case from is showing as <> > > Someone on the TMDA list says it is maildrop unsetting the RMPTY env vars... > > I tried changing my code to reset it, but it isn't working (syntax error) > > to "| SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter" This wont ever work, and there is also absolutely no point to pipe mails with empty sender into tmda. use |env to see what variables are available, and import those you need in maildrop. Roland --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Does courier / maildrop unset SENDER if it's empty?
--On Dienstag, 13. Januar 2004 09:55 -0800 "Mitch \\(WebCob\\)" <[EMAIL PROTECTED]> wrote: > I'm trying to call TMDA, and I get an error that SENDER is not set during > one of it's processes... it IS set during the others... the difference in > the messages (from the logs) is that in this case from is showing as <> > > Someone on the TMDA list says it is maildrop unsetting the RMPTY env vars... > > I tried changing my code to reset it, but it isn't working (syntax error) > > to "| SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter" This wont ever work, and there is also absolutely no point to pipe mails with empty sender into tmda. use |env to see what variables are available, and import those you need in maildrop. Roland --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] forcing queue run / message flush or shortening retry time for debugging?
--On Dienstag, 13. Januar 2004 09:50 -0800 "Mitch \\(WebCob\\)"
<[EMAIL PROTECTED]> wrote:
> When working on maildrop rules and so on, it would be nice to have the
> equivalent of sendmail -q or something similar - even if on a per message
> basis...
courier does both.
but the best was is still to inject via stdin/pipe
> I think I remember reading about something like that at one point, but I
> can't find it now of course... does it exist already? I think there is
> something...
see courier(5) or the homepage and pick one.
courier { start | stop | restart | flush | flush qid }
Roland
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] blocking a user id?
I'd like to allow cron jobs to continue to call sendmail... however, I don't want any chance of "nobody" (i.e. apache) calling sendmail directly. All other mail is of course traceable as the unique user id will nail any user spamming etc. I belive in layered security, so if there is some way to reject mail from "nobody" I'd like to know how... My concern is with local submission (I already require authentication for smtp (even on 127.0.0.1) thanks m/ --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] Re: Compile problem on BSDi 4.1
Hi At 04:27 PM 1/13/2004, Sam Varshavchik wrote: Huaikun Lin writes: Hi I compiled courier-imap 2.2.1 on BSDi4.1, I used the option: ./configure --without-authldap and ./configure --without-authldap --without-socks When I did make, I encounter the following error: On BSD you must use gmake instead of make. See INSTALL. When I tried gmake, I got lots of errors like the following: Making all in tcpd gmake[1]: Entering directory `/home/staff/lin/imap-bsdi/courier-imap-2.2.1/tcpd' Makefile:349: *** missing separator. Stop. gmake[1]: Leaving directory `/home/staff/lin/imap-bsdi/courier-imap-2.2.1/tcpd' gmake: *** [all-recursive] Error 1 This happened on many directories such as numlib,rfc822,rfc1035,unicode, userdb etc. Eventually fixed them by editing Makefile file under these directories. When I did "gmake check", I got: ... INFO: LOGOUT, user=user, ip=[127.0.0.1], headers=0, body=0 INFO: LOGIN, user=user, ip=[127.0.0.1], protocol=SMAP1 INFO: LOGOUT, user=user, ip=[127.0.0.1], headers=0, body=0 gmake[1]: *** [check-am] Error 1 gmake[1]: Leaving directory `/home/staff/lin/imap-bsdi/courier-imap-2.2.1/imap' gmake: *** [check-recursive] Error 1 Any idea? Lin Content-Type: application/pgp-signature; x-avg-checked=avg-ok-1D5E2767 Content-Transfer-Encoding: 7bit -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQBAA2Wmx9p3GYHlUOIRAmi5AJ41/L9kmMXL7MY3z5mD23KXrolzDgCfc6HK PiH/vXJmXIH4eaznHsKRrM8= =etgg -END PGP SIGNATURE- --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 1/8/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 1/8/2004
RE: [courier-users] Re: Does courier / maildrop unset SENDER if it's empty?
My original goal was making tmda work from maildroprc... got it working
now - if this env hack is going to cause problems can someone let me know?
Sam had mentioned (when I was cc'ing :
cc "|env >log"
that the pipe would overflow and cause problems... if so, how do I resolve?
In the meantime here is my solution:
And success!
In the users home dir:
/usr/local/tmda/bin/tmda-keygen
mkdir /home/mitch/.tmda
echo 596041dcfe0a344ecbfc2478fc4b8ecde169ea9c >/home/mitch/.tmda/crypt_key
chown -R u595 /home/mitch/.tmda
chmod -R u=rwX,g=,o= /home/mitch/.tmda
touch /home/mitch/.courier-default
chown -R u595 /home/mitch/.courier-default
This is from my maildroprc:
LOCKTMDA=$HOME/.tmda.lock
flock $LOCKTMDA {
#to "| env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
# IF EXITCODE is 99, then tmda processed an action
# IF EXITCODE is 0, then tmda has approved the message for further
action
cc "| env SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
if ($EXITCODE != "0")
{
#tmda has done it's job - get rid of the evidense!
to "|cat >/dev/null"
}
}
#IF the message hasn't been dumped at this point, continue processing
Hope that example helps someone!
m/
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] deleting messages reviewed...
I've seen a lot of talk on this, but never a definitive "this is the best way and here's why" maybe I missed it, but here are my current thoguhts: I'm dumping message by piping to cat and dumping it's output to /dev/null - we can't deliver directly to it due to ownership issues - right? wouldn't it make sense to have an exception to the security rule for /dev/null to avoid having to shell and cat just to dump a message? Someone had spoke of exit codes, but then someone else said that just caused the messages to defer until bounced... Am I missing something? Thanks! m/ --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Re: Does courier / maildrop unset SENDER if it's empty?
"Mitch \(WebCob\)" <[EMAIL PROTECTED]> writes:
> Jason on TMDA list mentioned these threads:
>
> See http://thread.gmane.org/gmane.mail.imap.courier.general/13703
> http://thread.gmane.org/gmane.mail.maildrop/1831
>
> they quote this code which deletes empty env vars...:
> and some external programs rely on the existance of those env's even if
> empty!
It's more than just _some_ programs. For one example out of many, any
program built with the standard C libraries in Unix is apt to be
affected by this behavior, as the getenv() function returns different
values for a missing environment variable and one that is set to "".
Many programs behave differently depending on this return value.
> The following snippet of code in the SetVar function in
> maildrop/varlist.C illustrates this behavior:
>
> if (value.Length() == 0)// Delete variable
> {
> Variable **v;
>
> for (v= &varlist[n]; *v; v= &(*v)->next)
> if ( (*v)->name == var )
> {
> Variable *vv= (*v);
>
> (*v)= vv->next;
> delete vv;
> break;
> }
> return;
> }
Could someone (Sam?) explain why that 'delete' statement exists? Is
there part of maildrop or courier that depends on this odd behavior?
> They suggest:
>
> xfilter "env VARIABLE=$VARIABLE /usr/local/bin/your-command"
>
> WHICH SEEMS TO WORK?
>
> BUT, Sam told me a little while ago that env didn't pipe std in (I was
> delivering a cc to it to capture some stuff) so I thought that meant it
> wouldn't work here...
>
> Confused...
Try this on your machine:
% echo foo | /usr/bin/env A=B /bin/cat
foo
As you can see, "foo" was output, which means that at least my "env"
does indeed allow stdin to get piped through (on FreeBSD 4.0).
--
Courier User
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] how to remove messages other than with cancelmsg?
Hi, I'm trying to clean up my system because it is bogged down with about 100,000 junk messages in the mailq. I've already identified all of the message ids that I want to get rid of, and actually I've already issued a cancelmsg command for all of these... However, I'm not sure exactly how cancelmsg works, and I still see the messages in mailq. Isn't there a way to simply delete the messages directly? I'm guessing if I delete the appropriate files from the msgq and msgs directories, that would work? But obviously I'm afraid of screwing something up. If it is "safe" to delete the files (control + data), how can I determine which control and data files belong to a particular message id? I'm not sure how to do the mapping. All I want to do is rid my system of this accumulated junk. Thanks for any help. Ricardo --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
RE: [courier-users] Does courier / maildrop unset SENDER if it's empty?
Jason on TMDA list mentioned these threads:
See http://thread.gmane.org/gmane.mail.imap.courier.general/13703
http://thread.gmane.org/gmane.mail.maildrop/1831
they quote this code which deletes empty env vars...:
and some external programs rely on the existance of those env's even if
empty!
The following snippet of code in the SetVar function in
maildrop/varlist.C illustrates this behavior:
if (value.Length() == 0)// Delete variable
{
Variable **v;
for (v= &varlist[n]; *v; v= &(*v)->next)
if ( (*v)->name == var )
{
Variable *vv= (*v);
(*v)= vv->next;
delete vv;
break;
}
return;
}
They suggest:
xfilter "env VARIABLE=$VARIABLE /usr/local/bin/your-command"
WHICH SEEMS TO WORK?
BUT, Sam told me a little while ago that env didn't pipe std in (I was
delivering a cc to it to capture some stuff) so I thought that meant it
wouldn't work here...
Confused...
m/
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mitch
(WebCob)
Sent: Tuesday, January 13, 2004 9:56 AM
To: [EMAIL PROTECTED]
Subject: [courier-users] Does courier / maildrop unset SENDER if it's
empty?
I'm trying to call TMDA, and I get an error that SENDER is not set during
one of it's processes... it IS set during the others... the difference in
the messages (from the logs) is that in this case from is showing as <>
Someone on the TMDA list says it is maildrop unsetting the RMPTY env vars...
I tried changing my code to reset it, but it isn't working (syntax error)
to "| SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter"
Any ideas?!
Thanks!
m/
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] afx compilation issue
Trying to compile on FreeBSD 4.9-STABLE. Errors: Making all in afx make all-am g++ -I.. -I./.. -Wall -g -O2 -L/usr/local/lib -o testafxpipe testafxpipe.o l ibafx.a testafxpipe.o: In function `main': /var/tmp/courier-0.44.2/afx/testafxpipe.C:217: undefined reference to `ostream:: operator<<(char)' testafxpipe.o: In function `main': /usr/include/g++/iostream.h:174: undefined reference to `ostream::flush(void)' testafxpipe.o: In function `main': /usr/include/g++/streambuf.h:175: undefined reference to `_IO_getc' libafx.a(afxpipe.o): In function `afxipipestream::fd(int)': /var/tmp/courier-0.44.2/afx/afx.h(.text+0x1b): undefined reference to `streambuf and so on. -- "The crowd neither wants nor seeks knowledge, and the leaders of the crowd, in their own interests, try to strengthen its fear and dislike of everything new and unknown. The slavery in which mankind lives is based upon this fear." --George Gurdjieff --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] Does courier / maildrop unset SENDER if it's empty?
I'm trying to call TMDA, and I get an error that SENDER is not set during one of it's processes... it IS set during the others... the difference in the messages (from the logs) is that in this case from is showing as <> Someone on the TMDA list says it is maildrop unsetting the RMPTY env vars... I tried changing my code to reset it, but it isn't working (syntax error) to "| SENDER='$SENDER' /usr/local/tmda/bin/tmda-filter" Any ideas?! Thanks! m/ --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] forcing queue run / message flush or shortening retry time for debugging?
Is there a way to hurry it up? When working on maildrop rules and so on, it would be nice to have the equivalent of sendmail -q or something similar - even if on a per message basis... I think I remember reading about something like that at one point, but I can't find it now of course... does it exist already? I think there is something... Thanks! m/ --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Re: [courier-users] postfix, courier, ldap and quotas.
--On Dienstag, 13. Januar 2004 13:35 +0100 Mauro <[EMAIL PROTECTED]> wrote: > I use linux debian woody with postfix-1.1.11, courier-pop 0.37.3, > courier-imap 1.4.3 and ldap to autenticate virtual users. > In my ldap database also I have an attribute in which to put quota > value. > I don't have any idea how to configure quotas. You missed maildrop, no softquotas possible without. > Perhaps the courier version that come with debian woody isn't able to > use quotas? Its completely out of date, and courier's quota managment had some changes since then. Get the packages from Sarge. Roland --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] postfix, courier, ldap and quotas.
Hello. Can I have a help to use quotas? I use linux debian woody with postfix-1.1.11, courier-pop 0.37.3, courier-imap 1.4.3 and ldap to autenticate virtual users. In my ldap database also I have an attribute in which to put quota value. I don't have any idea how to configure quotas. Perhaps the courier version that come with debian woody isn't able to use quotas? Can you help me? Thank you. --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
[courier-users] courier-0.44.2.20040112 make check fails
all goes well until SMAP test fails: INFO: LOGIN, user=confmdtest, ip=[127.0.0.1], protocol=SMAP1 INFO: LOGOUT, user=confmdtest, ip=[127.0.0.1], headers=0, body=0 make[1]: *** [check-am] Error 1 make[1]: Leaving directory `/home/rlx/courier-0.44.2.20040112/imap' make: *** [check-recursive] Error 1 this is on suse 9.0, suse 8.2 builds ok. strange thing. no ill effects noticeable, though. greets and thanks for your quick fix with the folder thing, alex --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
