Reuben Thomas wrote:
On Tue, 9 Jan 2007, Josip Rodin wrote:
And then someone files a bug saying they made it setuid but now it's
completely open to the world... what do I do then? :)
This is the way that procmail works, and it's hardly open to the
world, it's just more susceptible to bugs.
On Tue, Jan 09, 2007 at 12:59:35AM +, Reuben Thomas wrote:
And then someone files a bug saying they made it setuid but now it's
completely open to the world... what do I do then? :)
This is the way that procmail works, and it's hardly open to the world,
it's just more susceptible to
On Tue, 9 Jan 2007, Stefan Hornburg wrote:
Just my two cents: sending email to the root account (physically) instead
using an alias is unnecessary and therefore deprecated by
the standard MTA on Debian.
Yes, I guess this is a weakness of esmtp (i.e. presumably you're not saying
that you
On Tue, 9 Jan 2007, Josip Rodin wrote:
It's actually a bit fuzzy to me. Why should any user be able to do deliver
e-mail to another user using only the MDA? A really simple reason against it
is when the other user uses a MTA-side-mechanism to redirect their mail
elsewhere (~user/.forward?),
Reuben Thomas wrote:
On Tue, 9 Jan 2007, Stefan Hornburg wrote:
Just my two cents: sending email to the root account (physically)
instead using an alias is unnecessary and therefore deprecated by
the standard MTA on Debian.
Yes, I guess this is a weakness of esmtp (i.e. presumably you're
On Tue, 9 Jan 2007, Stefan Hornburg (Racke) wrote:
Yes, there is no issue with sending to root, but it should be aliased
to a regular user or an email account outside the host.
I'll file a wishlist bug against esmtp :) ssmtp aliases root in particular,
and other users in general if you want,
On Mon, 8 Jan 2007, Josip Rodin wrote:
[Note to self: always re-read what you wrote originally.]
Sorry, I've confused the issue by mis-restating it. My problem is with
sending mail *to* root, not *from* root.
What exactly happens in your case? What is the exact error message?
This is the
On Mon, Jan 08, 2007 at 06:35:45PM +, Reuben Thomas wrote:
What exactly happens in your case? What is the exact error message?
This is the case that I was hoping should work:
$ sudo chmod u+s /usr/bin/maildrop
$ ls -l /usr/bin/maildrop
-rwsr-sr-x 1 root mail 162132 2006-10-08 23:11
On Mon, 8 Jan 2007, Josip Rodin wrote:
Well, the solution to this is to have esmtp run that command either
as the user root, daemon or mail (the trusted users), or not use -d.
Can you do either of this?
I can't do either of those. I can't make esmtp run the command as root,
because it itself
On Mon, Jan 08, 2007 at 07:43:41PM +, Reuben Thomas wrote:
Well, the solution to this is to have esmtp run that command either
as the user root, daemon or mail (the trusted users), or not use -d.
Can you do either of this?
I can't do either of those. I can't make esmtp run the command as
On Mon, 8 Jan 2007, Josip Rodin wrote:
Restricting -d to trusted users has been the default for as long as I can
remember. Tracking back old versions, I can confirm that it's been done
since at least six years ago. It's a pretty sane default and changing it
would be a mistake IMHO.
I agree
On Tue, Jan 09, 2007 at 12:27:58AM +, Reuben Thomas wrote:
I agree that use with esmtp is a minority case. The one reason I think
changing this default might be reasonable is precisely because maildrop is
not shipped setuid root in Debian, so its behaviour when setuid root could
arguably
On Tue, 9 Jan 2007, Josip Rodin wrote:
And then someone files a bug saying they made it setuid but now it's
completely open to the world... what do I do then? :)
This is the way that procmail works, and it's hardly open to the world,
it's just more susceptible to bugs.
(Any suggestion
On Sun, 7 Jan 2007, Josip Rodin wrote:
There you go. Unless you quote the argument to to, it is evaluated.
!rrt means 'not string', and that means 0. That's why maildrop said that
it delivered to 0.
Thanks. However, this only cures the side note about mail seemingly
disappearing altogether,
On Sun, Jan 07, 2007 at 07:43:17PM +, Reuben Thomas wrote:
There you go. Unless you quote the argument to to, it is evaluated.
!rrt means 'not string', and that means 0. That's why maildrop said that
it delivered to 0.
Thanks. However, this only cures the side note about mail seemingly
On Sun, 7 Jan 2007, Josip Rodin wrote:
Well, it should work if esmtp runs it as one of the so-called trusted users.
The compiled-in default includes: root mail daemon. What does esmtp run it
as?
esmtp runs it as whatever user it is run as. In this case, the problem
occurs when I run esmtp as
On Sun, Jan 07, 2007 at 11:59:29PM +, Reuben Thomas wrote:
Well, it should work if esmtp runs it as one of the so-called trusted
users.
The compiled-in default includes: root mail daemon. What does esmtp run it
as?
esmtp runs it as whatever user it is run as. In this case, the problem
On Sat, Jan 06, 2007 at 01:44:19AM +, Reuben Thomas wrote:
Can you run this trivial test:
echo foo /tmp/foo
su -c 'maildrop -V2 /tmp/foo'
And paste the output?
maildrop: Changing to /root
Message start at 0 bytes, envelope sender=root
maildrop: Attempting .mailfilter
maildrop:
On Sat, 6 Jan 2007, Josip Rodin wrote:
Uhh. cat /root/.mailfilter ?
to !rrt
(rrt is the name of my normal user)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sat, Jan 06, 2007 at 08:04:16PM +, Reuben Thomas wrote:
On Sat, 6 Jan 2007, Josip Rodin wrote:
Uhh. cat /root/.mailfilter ?
to !rrt
(rrt is the name of my normal user)
There you go. Unless you quote the argument to to, it is evaluated.
!rrt means 'not string', and that means 0.
On Fri, Jan 05, 2007 at 12:40:11AM +, Reuben Thomas wrote:
BTW, it should deliver to /var/mail/root, or whatever you used in
/etc/maildroprc as the default $DEFAULT. It doesn't?
I have nothing configured in /etc/maildroprc. Should I? Again, I just left
it alone when I installed it.
No,
On Fri, 5 Jan 2007, Josip Rodin wrote:
Can you run this trivial test:
echo foo /tmp/foo
su -c 'maildrop -V2 /tmp/foo'
And paste the output?
maildrop: Changing to /root
Message start at 0 bytes, envelope sender=root
maildrop: Attempting .mailfilter
maildrop: Delivering to 0
--
To
Package: maildrop
Version: 2.0.2-11
Severity: normal
I was using maildrop as the MDA with esmtp-run. In this configuration
it's set up to run as /usr/bin/maildrop -d %T, and %T is the local
part of the address.
This fails when I try to send mail to root, complaining that it can't
change user,
On Thu, Jan 04, 2007 at 06:45:59PM +, Reuben Thomas wrote:
Package: maildrop
Version: 2.0.2-11
Severity: normal
I was using maildrop as the MDA with esmtp-run. In this configuration
it's set up to run as /usr/bin/maildrop -d %T, and %T is the local
part of the address.
This fails
On Thu, Jan 04, 2007 at 06:45:59PM +, Reuben Thomas wrote:
If I drop the -d %T in esmtp's configuration, then mail from root
(whether to root or another user) goes AWOL with no messages and no record
that I can discover
BTW, it should deliver to /var/mail/root, or whatever you used in
25 matches
Mail list logo
