qmail Digest 30 Jul 1999 10:00:01 -0000 Issue 713
Topics (messages 28317 through 28365):
Host masquerading
28317 by: [EMAIL PROTECTED]
Internet draft for VERP
28318 by: "Sam" <[EMAIL PROTECTED]>
28321 by: "Fred Lindberg" <[EMAIL PROTECTED]>
28325 by: "Fred Lindberg" <[EMAIL PROTECTED]>
28328 by: [EMAIL PROTECTED] ()
28339 by: "Sam" <[EMAIL PROTECTED]>
just a quick one...how do I have a user's mail go to /dev/null
28319 by: <[EMAIL PROTECTED]>
28323 by: Russell Nelson <[EMAIL PROTECTED]>
28324 by: <[EMAIL PROTECTED]>
28327 by: Dave Sill <[EMAIL PROTECTED]>
28330 by: "Jay D. Dyson" <[EMAIL PROTECTED]>
28331 by: Doug Lumpkin <[EMAIL PROTECTED]>
*sigh* performance issues again. Please help!
28320 by: "Fred Lindberg" <[EMAIL PROTECTED]>
28326 by: Dave Sill <[EMAIL PROTECTED]>
baboo.smtp does not work by using qmail.
28322 by: "Fred Lindberg" <[EMAIL PROTECTED]>
Stress Test and Mailbox Loss Problem
28329 by: Chris Porreca <[EMAIL PROTECTED]>
Unable to open message
28332 by: "Henrik Johansen" <[EMAIL PROTECTED]>
28333 by: Michael Wand <[EMAIL PROTECTED]>
28335 by: "Henrik Johansen" <[EMAIL PROTECTED]>
28336 by: Chris Johnson <[EMAIL PROTECTED]>
28338 by: "Timothy L. Mayo" <[EMAIL PROTECTED]>
Starting supervise from Digital Unix's rc3 files at bootup.
28334 by: Jim Arnott <[EMAIL PROTECTED]>
28337 by: "Timothy L. Mayo" <[EMAIL PROTECTED]>
security
28340 by: Gustavo Rios <[EMAIL PROTECTED]>
28341 by: "Scott D. Yelich" <[EMAIL PROTECTED]>
28343 by: Gustavo Rios <[EMAIL PROTECTED]>
28345 by: "Scott D. Yelich" <[EMAIL PROTECTED]>
28346 by: Vince Vielhaber <[EMAIL PROTECTED]>
28348 by: Russell Nelson <[EMAIL PROTECTED]>
28349 by: Gustavo Rios <[EMAIL PROTECTED]>
28353 by: Dave Sill <[EMAIL PROTECTED]>
28354 by: "Soffen, Matthew" <[EMAIL PROTECTED]>
28355 by: Jeff Hayward <[EMAIL PROTECTED]>
28357 by: Gustavo Rios <[EMAIL PROTECTED]>
28359 by: Gustavo Rios <[EMAIL PROTECTED]>
Error message
28342 by: Frank Greven <[EMAIL PROTECTED]>
28344 by: Gustavo Rios <[EMAIL PROTECTED]>
Sender address rewriting
28347 by: David ROBERT <[EMAIL PROTECTED]>
Other People's Bounces
28350 by: "Monte Mitzelfelt" <[EMAIL PROTECTED]>
Can qmail feed multiple users from one POP3 Mailbox
28351 by: Marco Leeflang <[EMAIL PROTECTED]>
Who can tell me how to speed up my qmail system?
28352 by: <[EMAIL PROTECTED]>
unable to exec qq
28356 by: "Rob Baham" <[EMAIL PROTECTED]>
28358 by: Mark Delany <[EMAIL PROTECTED]>
28360 by: "Rob Baham" <[EMAIL PROTECTED]>
Setting up Qmail as a mail gateway
28361 by: Ben Kosse <[EMAIL PROTECTED]>
28362 by: "Sam" <[EMAIL PROTECTED]>
/var/spool/mail/* to qmail Maildir?
28363 by: Steen Suder <[EMAIL PROTECTED]>
28364 by: Anand Buddhdev <[EMAIL PROTECTED]>
vanishing messages
28365 by: "Maria Zevenhoven" <[EMAIL PROTECTED]>
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
On Wed, 28 Jul 1999 [EMAIL PROTECTED] wrote:
> So I am about to modify my "ip-up" script to do the following: do
> an nslookup on the IP # I get sent, in order to get the name of the
> "machine" that I've been given, and then insert this machine name into
> /var/qmail/control/defaulthost. I have tested this "by hand" e.g.
> getting the machine-name and doing a "telnet freebsd.org smtp" with
> EHLO etc, and it works.
I use this snippet on my ip-up. I'm sure it's not the cleanest or elegant
solution but it works. :-)
It runs on linux but since you seem to use freebsd your mileage may vary,
if ifconfig has a different output.
LOCAL_ADDR=`/sbin/ifconfig | /usr/bin/grep P-t-P | /bin/cut -f 2 -d ':' |
/usr/bin/awk '{print $1}'`
/usr/bin/nslookup $LOCAL_ADDR | /usr/bin/awk '/^Name:/ { print $2}' >
/var/qmail/control/helohost
# this is necessary because my provider is not a very reliable and
# sometimes, their DNS is down. On these occasions there is nothing one
# can do.
# Acctually i could, i could finger a machine which holds the people that
# is connected through PPP, but that is just too much trouble.
if [ -s /var/qmail/control/helohost ]; then
chmod 644 /var/qmail/control/helohost
else
rm -f /var/qmail/control/helohost
fi
Hope this helps.
--
Tiago Pascoal ([EMAIL PROTECTED]) FAX : +351-1-7273394
Politicamente incorrecto, e membro (nao muito) proeminente da geracao rasca.
Recem empossado (engajado) cidadao da republica das bananas.
The Unspeakable Law:
As soon as you mention something;
if it is good, it goes away.
if it is bad, it happens.
writes:
> I'd really like to get back to the main thing, which is how the
> client smtp can get to decide the form of the VERP, rather than
The client can get to decide right now. There's nothing to stop the client
from doing that.
> As a matter of principle, if the server smtp dictates the VERP
> form and screws up, the sender loses through no fault of his own
> (doesn't get bounce).
The server can also screw up the return address the client gives it, so,
what exactly are you trying to argue?
> The only hop that matters is the one to the target mx. Hops before
Why?
There's nothing particularly special about that particular hop that is not
present at any other time.
> and after are unimportant:
> Before the Hop, the message is in the senders domain, and if the
Not necessarily.
> admin has his wits about him, he will not let the recip list be
> exploded before the Hop. He wants to keep that option open.
> After the Hop, the message is in the recips domain, where it will
> need to be exploded anyway for individual recips.
Not necessarily. Ever seen headers on mail that's delivered to AOL? At
least one or two hops, before it's delivered to mailboxes.
> : > Main problem here is error handling, that your boolean-flag approach
> : > doesn't have.
>
> : Specifically what in regards to error handling are you referring to?
>
> It's a consequence of having multiple copies. The last 250 ok after
> DATA is meant to confirm ALL recips before, but what if I run out of
> disk halfway through.
This is not a new problem, and has been solved a long time ago.
> I have to reject all, and recovery is messy.
> But if the message preceded the recip list, then the 250 is for the
What are you talking about?
--
Sam
On Wed, 28 Jul 1999 22:44:56 GMT, Sam wrote:
>There's no question that there's a big difference between sending an 8K
>message to 10,000 AOL recipients - bigger lists certainly do that - as
>10,000 individual messages, or 500 batchess. Someone will pipe in and
Who does still allow batches of 200? I was under the impression that
most large services have cut that limit way down (20) due to SPAM.
-Sincerely, Fred
(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)
On Thu, 29 Jul 1999 09:41:15 -0400 (EDT), Russell Nelson wrote:
>Let me be the first of many who point out that 10,000 / 500 = 20. :)
... going for coffee.
I most humbly apologize for wasted bandwidth and cc the list only to
save keyboards and fingertips.
-Sincerely, Fred
(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)
: > I'd really like to get back to the main thing, which is how the
: > client smtp can get to decide the form of the VERP, rather than
: The client can get to decide right now. There's nothing to stop the client
: from doing that.
The client is not allowed to use any other separator other than '-',
or any prefix other than his own local, or to include a cookie in
or a suffix to the VERP expansion. To me this is overly restrictive.
It should not be necessary to require that compliant MTAs implement
qmail-style extension addresses.
Your other points are well taken. I shan't be arguing them.
-harold
writes:
> The client is not allowed to use any other separator other than '-',
You are mistaken. If I felt like it, I can easily code a mailing list
manager, using Qmail, that uses the ^ character instead.
Oh, you mean in the draft? Simply include any other valid separator as the
last character in the local part of the address, and simply expect that
every address that you decode from the VERPed return path will start off
with a -, which you will simply ignore.
--
Sam
Basically I just want all mail for a particular user to go to /dev/null.
I put /dev/null in .qmail, but this causes errors on logs. I figured
there should be a clean way of doing this.
Thanks
-jeremy
http://www.xxedgexx.com | [EMAIL PROTECTED]
---------------------------------------------
Y2K. We're all gonna die.
[EMAIL PROTECTED] writes:
>
> Basically I just want all mail for a particular user to go to /dev/null.
> I put /dev/null in .qmail, but this causes errors on logs. I figured
> there should be a clean way of doing this.
Do it the same way we told someone else how to do it on Monday.
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr sells support for free software | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
I've looked through FAQ and I don't save every message posted to the list
and I'm also unaware of an archive, so perhaps either pointing me to a
searchable archive, or an FAQ containing this information would be more
helpful then your line below.
Thanks
-jeremy
> [EMAIL PROTECTED] writes:
> >
> > Basically I just want all mail for a particular user to go to /dev/null.
> > I put /dev/null in .qmail, but this causes errors on logs. I figured
> > there should be a clean way of doing this.
>
> Do it the same way we told someone else how to do it on Monday.
>
> --
> -russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
> Crynwr sells support for free software | PGPok | Government schools are so
> 521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
> Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
>
http://www.xxedgexx.com | [EMAIL PROTECTED]
---------------------------------------------
Y2K. We're all gonna die.
<[EMAIL PROTECTED]> wrote:
>
>I've looked through FAQ and I don't save every message posted to the list
>and I'm also unaware of an archive, so perhaps either pointing me to a
>searchable archive, or an FAQ containing this information would be more
>helpful then your line below.
Do yourself a favor and scan through "Life with qmail". It contains
the URL of the search engine for the list archives, along with other
useful information:
http://Web.InfoAve.Net/~dsill/lwq.html
-Dave
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 29 Jul 1999 [EMAIL PROTECTED] wrote:
> I've looked through FAQ and I don't save every message posted to the
> list and I'm also unaware of an archive, so perhaps either pointing me
> to a searchable archive, or an FAQ containing this information would be
> more helpful then your line below.
Well, you can't do it via /etc/aliases. Not with Qmail.
I suppose ln -s /dev/null /var/mail/username will do.
- -Jay
( ______
)) .--- "There's always time for a good cup of coffee" ---. >===<--.
C|~~| (>--- Jay D. Dyson - [EMAIL PROTECTED] ---<) | = |-'
`--' `- Superman had Kryptonite, I have NT. Life is real. -' `-----'
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBN6BoS82OVDpaKXD9AQE2pwQAl/VkxBZCxhW3ie54KFQQkGCbUsf7h9el
SjjOtP8ndpJxrP1bwk0wG1yv8G7/r8a9whbwuDj+tsAbPwQ/kZoQfjBLf8YSvEvB
nXbTbw8EmdMQl8xGKzbM5gtAVA/lBQHST88gaUGf18AkJQPbtcN2k/Or4KWp7viR
SLYQu3WVQ7s=
=93Xw
-----END PGP SIGNATURE-----
Create a .qmail file in their home directory with a # in it... Also you can get
to any archives from Qmail's home page at www.qmail.org
--
Doug
~username/.qmail
#
"Jay D. Dyson" wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> On Thu, 29 Jul 1999 [EMAIL PROTECTED] wrote:
>
> > I've looked through FAQ and I don't save every message posted to the
> > list and I'm also unaware of an archive, so perhaps either pointing me
> > to a searchable archive, or an FAQ containing this information would be
> > more helpful then your line below.
>
> Well, you can't do it via /etc/aliases. Not with Qmail.
>
> I suppose ln -s /dev/null /var/mail/username will do.
>
> - -Jay
>
> ( ______
> )) .--- "There's always time for a good cup of coffee" ---. >===<--.
> C|~~| (>--- Jay D. Dyson - [EMAIL PROTECTED] ---<) | = |-'
> `--' `- Superman had Kryptonite, I have NT. Life is real. -' `-----'
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.2
>
> iQCVAwUBN6BoS82OVDpaKXD9AQE2pwQAl/VkxBZCxhW3ie54KFQQkGCbUsf7h9el
> SjjOtP8ndpJxrP1bwk0wG1yv8G7/r8a9whbwuDj+tsAbPwQ/kZoQfjBLf8YSvEvB
> nXbTbw8EmdMQl8xGKzbM5gtAVA/lBQHST88gaUGf18AkJQPbtcN2k/Or4KWp7viR
> SLYQu3WVQ7s=
> =93Xw
> -----END PGP SIGNATURE-----
On Wed, 28 Jul 1999 15:42:34 +0100, Alex at Star wrote:
>> Syslog is crap. Pure junk
>We also saw a lot of our performance problems disappear when we moved from syslog to
>cyclog
As has been pointed out before, a simple '-' before the maillog file
name in syslog.conf (see man page) will prevent sync() after each
entry. This realizes most of the performance gains seen with cyclog.
I obviously still prefer cyclog, but the syslog.conf change followed by
a syslogd HUP is a very fast and simple fix when seeing a system in
trouble.
-Sincerely, Fred
(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)
"Fred Lindberg" <[EMAIL PROTECTED]> wrote:
>
>As has been pointed out before, a simple '-' before the maillog file
>name in syslog.conf (see man page) will prevent sync() after each
>entry. This realizes most of the performance gains seen with cyclog.
Not all syslogs support that.
-Dave
On Wed, 28 Jul 1999 14:37:29 +0300, Ferhat Doruk wrote:
>which sends mail by using smtp.dll (bamboo.smtp). These ASP pages does not
A guess would be that this _is_ a Microsoft bug and that it is the bare
LF one. A problem in the SMTP dialog from "bamboo" would give you the
differential symptoms you describe. Log tcpserver output. There are
also notes in the mailing list archives on how to log qmail-smtpd info.
Personally, I'd just try the bare-LF patch and see if it helps.
-Sincerely, Fred
(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)
Folks,
I have been stress testing a new machine here (That I have compiled qmail
v 1.3 on w/ etrn support, using Mailbox format).
Machine:
- BSDI (V 4.0.1)
- i686 w/ 256 mb ram, 9.5 gb hd for testing
- qmail v1.3 (with etrn support)
- tcpserver and qpopper installed
(Not that big of a deal.)
I had decided to send 250 million messages to my mailbox. The message
arrive quickly and my mailbox soon filled to over 1gb large! This was
great.. but their was one major problem: When the user home partitian
filled up completely.. my mailbox was immediately whiped! Is this a known
qmail problem (I haven't found anything on it in the archives) or a BSDI
thing? Thank you!
PS-> I hate BSDI, but I'm forced to use it due to upper level management..
you know how it works.
- Chris
[zorak]:6:19am:~chrisp:(root)-> ls -al
total 1142555
drwxr-xr-x 6 chrisp staff 1024 Jul 29 04:11 .
drwxr-xr-x 3 root wheel 512 Jul 19 07:39 ..
-rw-r--r-- 1 chrisp staff 1835 Jul 28 09:43 .cshrc
-rw------- 1 chrisp staff 7280 Jul 29 04:11 .pine-debug1
-rw------- 1 chrisp staff 6936 Jul 29 04:09 .pine-debug2
-rw------- 1 chrisp staff 7276 Jul 29 04:08 .pine-debug3
-rw-r--r-- 1 chrisp staff 11436 Jul 29 04:09 .pinerc
-rw------- 1 chrisp staff 1169269760 Jul 29 06:19 Mailbox
drwxr-xr-x 3 chrisp staff 512 Jul 28 14:01 SETI
drwxr-xr-x 3 chrisp staff 512 Jul 21 08:50 Software
drwx------ 2 chrisp staff 512 Jul 29 04:08 mail
[zorak]:6:19am:~chrisp:(root)-> ls -al
total 140
drwxr-xr-x 6 chrisp staff 1024 Jul 29 04:11 .
drwxr-xr-x 3 root wheel 512 Jul 19 07:39 ..
-rw-r--r-- 1 chrisp staff 1835 Jul 28 09:43 .cshrc
-rw------- 1 chrisp staff 7280 Jul 29 04:11 .pine-debug1
-rw------- 1 chrisp staff 6936 Jul 29 04:09 .pine-debug2
-rw------- 1 chrisp staff 7276 Jul 29 04:08 .pine-debug3
-rw-r--r-- 1 chrisp staff 11436 Jul 29 04:09 .pinerc
-rw------- 1 chrisp staff 24618 Jul 29 06:20 Mailbox
drwxr-xr-x 3 chrisp staff 512 Jul 28 14:01 SETI
drwxr-xr-x 3 chrisp staff 512 Jul 21 08:50 Software
drwx------ 2 chrisp staff 512 Jul 29 04:08 mail
[zorak]:6:20am:~chrisp:(root)-> df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/sd0a 148703 8480 132787 6% /
/dev/sd0h 1487854 256287 1157174 18% /usr
/dev/sd0g 1487854 142450 1271011 10% /var
/dev/sd0f 991727 1402 940738 0% /tmp
/dev/sd0e 4193771 2177815 1806267 55% /var/qmail
Christopher Porreca
Phone: (716) 756-5596
Systems Administration
N e t A c c e s s, I n c.
Instigrametritron. Grumster Woodland Elf, Bark Pants
Hi all.
I have posted this before, but recieved no responses what so ever.
When a mail is succesfully delivered, and I want to read it from pop3 the
following happens:
telnet mail.domain.com 110
Trying w.x.y.z
Connected to domain.com.
Escape is...
+OK ...
user johndoe
+OK
pass pop3password
+OK
list
1 265
.
> retr 1
-ERR unable to open that message
> quit
the messages in domain-com/johndoe/Maildir/new/ is created with these permissions
-rw------- 1 popuser popuser 265 jul 27 12:00 xxxxxx.domain.com
"popuser" is a user with shell=/bin/false
It seems that mails are created with wrong permission? OR??
If I manually change permission to -rw-r----- I can "retr" the mail though.
Anyone knows how to setup the correct permissions?
And what ARE the default permission-settings on a newly arrived mail?
Im thinking om reinstalling it all to make sure it is 'clean', any way to avoid that?
Henrik Johansen
[EMAIL PROTECTED]
I believe the Maildir, its directories, and its file, permissions should be set
to that of the user.
Try this: chown johndoe.johndoe Maildir -R
(the recursive option will change everything in there to johnjoe.johndoe)
Michael Wand
On Thu, 29 Jul 1999, Henrik Johansen wrote:
> Hi all.
>
> I have posted this before, but recieved no responses what so ever.
>
> When a mail is succesfully delivered, and I want to read it from pop3 the
> following happens:
>
> telnet mail.domain.com 110
> Trying w.x.y.z
> Connected to domain.com.
> Escape is...
> +OK ...
> user johndoe
> +OK
> pass pop3password
> +OK
> list
> 1 265
> .
> >> retr 1
> -ERR unable to open that message
> > quit
>
> the messages in domain-com/johndoe/Maildir/new/ is created with these permissions
> -rw------- 1 popuser popuser 265 jul 27 12:00 xxxxxx.domain.com
>
> "popuser" is a user with shell=/bin/false
>
> It seems that mails are created with wrong permission? OR??
> If I manually change permission to -rw-r----- I can "retr" the mail though.
> Anyone knows how to setup the correct permissions?
>
> And what ARE the default permission-settings on a newly arrived mail?
>
> Im thinking om reinstalling it all to make sure it is 'clean', any way to avoid that?
>
> Henrik Johansen
> [EMAIL PROTECTED]
I have just tried that (chown johndoe.johndoe Maildir -R)
Now the logs says : deferral: temporary error on maildir delivery????
I guess im gonna play a little longer with the permission settings....
----- Original Message -----
From: Michael Wand <[EMAIL PROTECTED]>
To: Henrik Johansen <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, July 29, 1999 5:39 PM
Subject: Re: Unable to open message
> I believe the Maildir, its directories, and its file, permissions should be set
> to that of the user.
>
> Try this: chown johndoe.johndoe Maildir -R
> (the recursive option will change everything in there to johnjoe.johndoe)
>
>
> Michael Wand
> On Thu, 29 Jul 1999, Henrik Johansen wrote:
> > Hi all.
> >
> > I have posted this before, but recieved no responses what so ever.
> >
> > When a mail is succesfully delivered, and I want to read it from pop3 the
> > following happens:
> >
> > telnet mail.domain.com 110
> > Trying w.x.y.z
> > Connected to domain.com.
> > Escape is...
> > +OK ...
> > user johndoe
> > +OK
> > pass pop3password
> > +OK
> > list
> > 1 265
> > .
> > >> retr 1
> > -ERR unable to open that message
> > > quit
> >
> > the messages in domain-com/johndoe/Maildir/new/ is created with these permissions
> > -rw------- 1 popuser popuser 265 jul 27 12:00 xxxxxx.domain.com
> >
> > "popuser" is a user with shell=/bin/false
> >
> > It seems that mails are created with wrong permission? OR??
> > If I manually change permission to -rw-r----- I can "retr" the mail though.
> > Anyone knows how to setup the correct permissions?
> >
> > And what ARE the default permission-settings on a newly arrived mail?
> >
> > Im thinking om reinstalling it all to make sure it is 'clean', any way to avoid
>that?
> >
> > Henrik Johansen
> > [EMAIL PROTECTED]
>
On Thu, Jul 29, 1999 at 05:29:29PM +0200, Henrik Johansen wrote:
> Hi all.
>
> I have posted this before, but recieved no responses what so ever.
That's probably because you've left out too much important information, and
nobody felt like coaxing it out of you.
How is this message delivered? From a users/assign assignment? If so, what does
the pertinent line in users/assign say?
What version of checkpassword are you using? If it's not the standard one and
you're using some kind of pop user database, what does it say in your pop user
database? What user do you expect qmail-pop3d to be running as when it tries to
collect the mail?
Here's what I'm getting at here: delivered mail is owned by popuser, but at
retrieval time, qmail-pop3d isn't running as popuser and doesn't have
permission to read the message.
Chris
> When a mail is succesfully delivered, and I want to read it from pop3 the
> following happens:
>
> telnet mail.domain.com 110
> Trying w.x.y.z
> Connected to domain.com.
> Escape is...
> +OK ...
> user johndoe
> +OK
> pass pop3password
> +OK
> list
> 1 265
> .
> > retr 1
> -ERR unable to open that message
> > quit
>
> the messages in domain-com/johndoe/Maildir/new/ is created with these permissions
> -rw------- 1 popuser popuser 265 jul 27 12:00 xxxxxx.domain.com
>
> "popuser" is a user with shell=/bin/false
>
> It seems that mails are created with wrong permission? OR??
> If I manually change permission to -rw-r----- I can "retr" the mail though.
> Anyone knows how to setup the correct permissions?
>
> And what ARE the default permission-settings on a newly arrived mail?
>
> Im thinking om reinstalling it all to make sure it is 'clean', any way to avoid that?
>
> Henrik Johansen
> [EMAIL PROTECTED]
>
The message must be delivered and read by the same user. Sounds like you
deliver it as one user and then try to read it as another. This will
NEVER work. Please check out the single uid instructions or get the
vchkpw package or equivalent.
On Thu, 29 Jul 1999, Henrik Johansen wrote:
> I have just tried that (chown johndoe.johndoe Maildir -R)
> Now the logs says : deferral: temporary error on maildir delivery????
>
> I guess im gonna play a little longer with the permission settings....
>
>
> ----- Original Message -----
> From: Michael Wand <[EMAIL PROTECTED]>
> To: Henrik Johansen <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Thursday, July 29, 1999 5:39 PM
> Subject: Re: Unable to open message
>
>
> > I believe the Maildir, its directories, and its file, permissions should be set
> > to that of the user.
> >
> > Try this: chown johndoe.johndoe Maildir -R
> > (the recursive option will change everything in there to johnjoe.johndoe)
> >
> >
> > Michael Wand
> > On Thu, 29 Jul 1999, Henrik Johansen wrote:
> > > Hi all.
> > >
> > > I have posted this before, but recieved no responses what so ever.
> > >
> > > When a mail is succesfully delivered, and I want to read it from pop3 the
> > > following happens:
> > >
> > > telnet mail.domain.com 110
> > > Trying w.x.y.z
> > > Connected to domain.com.
> > > Escape is...
> > > +OK ...
> > > user johndoe
> > > +OK
> > > pass pop3password
> > > +OK
> > > list
> > > 1 265
> > > .
> > > >> retr 1
> > > -ERR unable to open that message
> > > > quit
> > >
> > > the messages in domain-com/johndoe/Maildir/new/ is created with these permissions
> > > -rw------- 1 popuser popuser 265 jul 27 12:00 xxxxxx.domain.com
> > >
> > > "popuser" is a user with shell=/bin/false
> > >
> > > It seems that mails are created with wrong permission? OR??
> > > If I manually change permission to -rw-r----- I can "retr" the mail though.
> > > Anyone knows how to setup the correct permissions?
> > >
> > > And what ARE the default permission-settings on a newly arrived mail?
> > >
> > > Im thinking om reinstalling it all to make sure it is 'clean', any way to avoid
>that?
> > >
> > > Henrik Johansen
> > > [EMAIL PROTECTED]
> >
>
>
>
---------------------------------
Timothy L. Mayo mailto:[EMAIL PROTECTED]
Senior Systems Administrator
localconnect(sm)
http://www.localconnect.net/
The National Business Network Inc. http://www.nb.net/
One Monroeville Center, Suite 850
Monroeville, PA 15146
(412) 810-8888 Phone
(412) 810-8886 Fax
Hi,
I'm new to qmail and all its utilities.
I'm using the latest qmail (1.03) and Digital Unix 4.0
Has anyone run into a problem where supervise does not start or stay
running
(nor start any sw that it should start) when a system is coming up
during boot. See the script below.
I also had the same problem with starting tclserver from an rc3.d
script. Qmail-send would start fine, but
only if I start it without supervise.
After I boot and do a ps -aef, no qmail or supervisor processes have
started. When I start this script by
hand (as root) it works fine.
Also, I get the correct comments from the echos on the monitor upon
bootup, so I know the script is running and
executing the supervise programs.
I do not get any error messages.
Any ideas ?
Thanks for any help.
Jim Arnott
Bridge Info Sys
#cd /sbin/rc3.d
#ls -lg S99qmailstart
lrwxrwxrwx 1 root bin 20 Jul 6 07:29 S99qmailstart ->
../init.d/qmailstart
#ls -lg ../init.d/qmailstart
-rwxr-xr-x 1 root system 1710 Jul 7 01:45
../init.d/qmailstart
#cat ../init.d/qmailstart
#!/sbin/sh
NAME=qmail
SUPERVISE=/usr/local/bin/supervise
ACCUSTAMP=/usr/local/bin/accustamp
CYCLOG=/usr/local/bin/cyclog
SETUSER=/usr/local/bin/setuser
SVC=/usr/local/bin/svc
ECHO=/bin/echo
QMAILDIR=/var/qmail
PATH=/bin:/usr/bin:/usr/local/bin:$QMAILDIR/bin
CMD_ENV=bsd
export CMD_ENV PATH
QMAILDUID=606
NOFILESGID=600
set -e
case "$1" in
start)
set `who -r`
if [ $9 = "S" ]; then
$ECHO -n "Starting qmail: "
$ECHO -n "(qmail persistent daemons) "
$SUPERVISE $QMAILDIR/supervise/qmail-send env -
\
PATH="$QMAILDIR/bin:$PATH" qmail-start ./Mailbox
$ACCUSTAMP | $SETUSER qmaill $CYCLOG /var/log/qmail &
$ECHO -n "(qmail-smtpd via tcpserver) "
$SUPERVISE $QMAILDIR/supervise/tcpserver-qmail \
/usr/local/bin/tcpserver -u $QMAILDUID -g
$NOFILESGID 0 smtp \
$QMAILDIR/bin/qmail-smtpd &
$ECHO .
fi
;;
stop)
$ECHO -n "Stopping qmail: "
$ECHO -n "(qmail-smtpd via tcpserver) "
$SVC -dx $QMAILDIR/supervise/tcpserver-qmail
$ECHO -n "(qmail persistent daemons) "
$SVC -dx $QMAILDIR/supervise/qmail-send
$ECHO .
;;
alrm)
$ECHO "Sending ALRM signal to qmail-send."
$SVC -a $QMAILDIR/supervise/qmail-send
;;
hup)
$ECHO "Sending HUP signal to qmail-send."
$SVC -h $QMAILDIR/supervise/qmail-send
;;
restart)
$ECHO "Restarting qmail:"
$ECHO "* Stopping qmail-smtpd via tcpserver."
$SVC -d $QMAILDIR/supervise/tcpserver-qmail
$ECHO "* Sending qmail-send SIGTERM and
restarting."
$SVC -t $QMAILDIR/supervise/qmail-send
$ECHO "* Restarting qmail-smtpd via
tcpserver."
$SVC -u $QMAILDIR/supervise/tcpserver-qmail
;;
*)
$ECHO "Usage: /etc/init.d/$NAME
{start|stop|restart|alrm|hup}"
exit 1
;;
esac
exit 0
You will need to use 'nohup' to start these services. They are being
terminated when the shell they are started from closes.
Here is the line I use to start qmail under the same OS:
/usr/bin/nohup /var/qmail/rc >> /var/adm/qmail/nohup.out &
On Thu, 29 Jul 1999, Jim Arnott wrote:
> Hi,
>
> I'm new to qmail and all its utilities.
> I'm using the latest qmail (1.03) and Digital Unix 4.0
>
> Has anyone run into a problem where supervise does not start or stay
> running
> (nor start any sw that it should start) when a system is coming up
> during boot. See the script below.
>
> I also had the same problem with starting tclserver from an rc3.d
> script. Qmail-send would start fine, but
> only if I start it without supervise.
>
> After I boot and do a ps -aef, no qmail or supervisor processes have
> started. When I start this script by
> hand (as root) it works fine.
>
> Also, I get the correct comments from the echos on the monitor upon
> bootup, so I know the script is running and
> executing the supervise programs.
>
> I do not get any error messages.
>
> Any ideas ?
>
> Thanks for any help.
>
> Jim Arnott
> Bridge Info Sys
>
> #cd /sbin/rc3.d
> #ls -lg S99qmailstart
> lrwxrwxrwx 1 root bin 20 Jul 6 07:29 S99qmailstart ->
> ../init.d/qmailstart
> #ls -lg ../init.d/qmailstart
> -rwxr-xr-x 1 root system 1710 Jul 7 01:45
> ../init.d/qmailstart
> #cat ../init.d/qmailstart
> #!/sbin/sh
>
> NAME=qmail
> SUPERVISE=/usr/local/bin/supervise
> ACCUSTAMP=/usr/local/bin/accustamp
> CYCLOG=/usr/local/bin/cyclog
> SETUSER=/usr/local/bin/setuser
> SVC=/usr/local/bin/svc
>
> ECHO=/bin/echo
> QMAILDIR=/var/qmail
> PATH=/bin:/usr/bin:/usr/local/bin:$QMAILDIR/bin
> CMD_ENV=bsd
> export CMD_ENV PATH
>
> QMAILDUID=606
> NOFILESGID=600
>
> set -e
>
> case "$1" in
> start)
> set `who -r`
> if [ $9 = "S" ]; then
> $ECHO -n "Starting qmail: "
> $ECHO -n "(qmail persistent daemons) "
> $SUPERVISE $QMAILDIR/supervise/qmail-send env -
> \
> PATH="$QMAILDIR/bin:$PATH" qmail-start ./Mailbox
> $ACCUSTAMP | $SETUSER qmaill $CYCLOG /var/log/qmail &
> $ECHO -n "(qmail-smtpd via tcpserver) "
> $SUPERVISE $QMAILDIR/supervise/tcpserver-qmail \
>
> /usr/local/bin/tcpserver -u $QMAILDUID -g
> $NOFILESGID 0 smtp \
> $QMAILDIR/bin/qmail-smtpd &
> $ECHO .
> fi
> ;;
> stop)
> $ECHO -n "Stopping qmail: "
> $ECHO -n "(qmail-smtpd via tcpserver) "
> $SVC -dx $QMAILDIR/supervise/tcpserver-qmail
> $ECHO -n "(qmail persistent daemons) "
> $SVC -dx $QMAILDIR/supervise/qmail-send
> $ECHO .
> ;;
> alrm)
> $ECHO "Sending ALRM signal to qmail-send."
> $SVC -a $QMAILDIR/supervise/qmail-send
> ;;
> hup)
> $ECHO "Sending HUP signal to qmail-send."
> $SVC -h $QMAILDIR/supervise/qmail-send
> ;;
> restart)
> $ECHO "Restarting qmail:"
> $ECHO "* Stopping qmail-smtpd via tcpserver."
> $SVC -d $QMAILDIR/supervise/tcpserver-qmail
> $ECHO "* Sending qmail-send SIGTERM and
> restarting."
> $SVC -t $QMAILDIR/supervise/qmail-send
> $ECHO "* Restarting qmail-smtpd via
> tcpserver."
> $SVC -u $QMAILDIR/supervise/tcpserver-qmail
> ;;
> *)
> $ECHO "Usage: /etc/init.d/$NAME
> {start|stop|restart|alrm|hup}"
> exit 1
> ;;
> esac
>
> exit 0
>
>
---------------------------------
Timothy L. Mayo mailto:[EMAIL PROTECTED]
Senior Systems Administrator
localconnect(sm)
http://www.localconnect.net/
The National Business Network Inc. http://www.nb.net/
One Monroeville Center, Suite 850
Monroeville, PA 15146
(412) 810-8888 Phone
(412) 810-8886 Fax
Does any body here knows something about rootshell attack?
According some people at bos-br, they were hacked through qmail, which has
some bug! (Nothing sure).
Is there really buggy versions of qmail ?
Thanks in advance!
PS: i am a beginner with qmail, so i would like to know what's really
going on!
--
What's the similarity between an air
conditioner and a computer? They both
stop working when you open windows.
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 29 Jul 1999, Gustavo Rios wrote:
> Does any body here knows something about rootshell attack?
> According some people at bos-br, they were hacked through qmail, which has
> some bug! (Nothing sure).
A recent attack? Or the one that took them down months ago? The
"official" word of the last attack was that it was a sniffed (root?)
password and/or some ssh+kerberos issue.
Of course, it's easy to use qmail to run commands if you have ftp access
and write permissions to the .qmail* files. Of course, this isn't
considered a bug.
Scott
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBN6CEUR4PLs9vCOqdAQHTWAP/TcuTQys/bZnvAxEVCXEnM8RQSBCkA2So
pafozclj70GXUvOkiIc/YOZjbNtMRdk4slWAprR4Srfr64rhi9l9uQjALp4Hd5Ix
MklXXXluhkcNsFEy2gCBAufhPDnT6b9Fp/8Jku0ABHQFqNDZtf1TSwUiuboctQEx
tVxEdpncP5M=
=UUql
-----END PGP SIGNATURE-----
> A recent attack? Or the one that took them down months ago? The
the one that took them down mounths ago.
> "official" word of the last attack was that it was a sniffed (root?)
> password and/or some ssh+kerberos issue.
IBM and SSH Corp. assured that there was no bug in ssh package!
> Of course, it's easy to use qmail to run commands if you have ftp access
> and write permissions to the .qmail* files. Of course, this isn't
> considered a bug.
.qmail* (Are you referring to /var/qmail/alias/.qmail* ?)
> Scott
>
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.2
>
> iQCVAwUBN6CEUR4PLs9vCOqdAQHTWAP/TcuTQys/bZnvAxEVCXEnM8RQSBCkA2So
> pafozclj70GXUvOkiIc/YOZjbNtMRdk4slWAprR4Srfr64rhi9l9uQjALp4Hd5Ix
> MklXXXluhkcNsFEy2gCBAufhPDnT6b9Fp/8Jku0ABHQFqNDZtf1TSwUiuboctQEx
> tVxEdpncP5M=
> =UUql
> -----END PGP SIGNATURE-----
>
>
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 29 Jul 1999, Gustavo Rios wrote:
> .qmail* (Are you referring to /var/qmail/alias/.qmail* ?)
I'm really not able to say what happened to rootshell -- but since I'm
underconstant attack -- I can tell you what I have seen and what I have
done (with respect to ssh/qmail, etc.)
no.... follow this secenerio:
A host "A" has qmail/ftp/apache and is an ISP type machine. Users need
to be able to ftp to it to update their html files for the web server
and pop (or apop?) to it to get mail and to use it as an outgoing smtp
gateway.
Well, if someone can sniff even a single incoming password (ie: pop or
ftp) .. they can then use this access to write files (or read files)
from the machine. If the incoming FTP can put in a ~user/.qmail* file,
then one can send commands to a program/shell. If one can FTP in a
cgi-bin program, then they can run commands that way.
So far, I have user home dirs owned by root with files like .qmail
pointing to ./Maildir, a "public_html", and any dir with a domain like
"www.mysite.com" and a "word" dir.. where the users can write -- but
they can't write to the top level of their home (sure, I could probably
do this with wuftpd upload as well, but I'm doing it with that *and*
unix perms). cgi is controlled by a suser / wrap where files have to be
"blessed" and once blessed, they can't be modified -- so even through a
file can be put into the cgi-bin directory, it won't execute until
blessed. Finally, adding ipfilter to this machine seems to keep off the
standard wave of things (this is a sun) like rpc.cmsd, rpc.statd, etc.
I've also modified ssh not to allow scp and use "uselogin" to is will
ask for a primary password and then run opie.
Scott
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBN6CIeh4PLs9vCOqdAQHUhQP8CTgB4QV3BgXTw8X6EsZLUGwonaIuBJff
sE+CubwUb2L9vy6EbmIcf5Q0fyHwX+hloQg0Kr085aTM8vIiUQWdK8dzJrgLrIwJ
L1owsktjsTEdh9V81+WbSrAuhuiJ2wqo6tt7BFxLNY0oalJTJwOyxqVivr3wSIEa
wXi5yaMVBUQ=
=J5FG
-----END PGP SIGNATURE-----
On Thu, 29 Jul 1999, Gustavo Rios wrote:
> > A recent attack? Or the one that took them down months ago? The
> the one that took them down mounths ago.
>
> > "official" word of the last attack was that it was a sniffed (root?)
> > password and/or some ssh+kerberos issue.
>
> IBM and SSH Corp. assured that there was no bug in ssh package!
So they gave up and just blamed qmail? Doubtful. I tend to think it
was a sniffed password.
>
> > Of course, it's easy to use qmail to run commands if you have ftp access
> > and write permissions to the .qmail* files. Of course, this isn't
> > considered a bug.
>
> .qmail* (Are you referring to /var/qmail/alias/.qmail* ?)
Or one in the user's $HOME dir.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
Gustavo Rios writes:
> Does any body here knows something about rootshell attack?
> According some people at bos-br, they were hacked through qmail, which has
> some bug! (Nothing sure).
If they can't supply details, they're just guessing.
> Is there really buggy versions of qmail ?
No, unless you count AOL's adoption of DNS records >512 bytes (which
breaks many Unix packages anyway) a bug.
--
-russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson
Crynwr sells support for free software | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
On Thu, 29 Jul 1999, Vince Vielhaber wrote:
> On Thu, 29 Jul 1999, Gustavo Rios wrote:
>
> > > A recent attack? Or the one that took them down months ago? The
> > the one that took them down mounths ago.
> >
> > > "official" word of the last attack was that it was a sniffed (root?)
> > > password and/or some ssh+kerberos issue.
> >
> > IBM and SSH Corp. assured that there was no bug in ssh package!
>
> So they gave up and just blamed qmail? Doubtful. I tend to think it
> was a sniffed password.
I did not say they blamed qmail, they only assured SSH was bugfree!
NOTHING were said about qmail.
> > > and write permissions to the .qmail* files. Of course, this isn't
> > > considered a bug.
> >
> > .qmail* (Are you referring to /var/qmail/alias/.qmail* ?)
>
> Or one in the user's $HOME dir.
>
> Vince.
> --
> ==========================================================================
> Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null
> # include <std/disclaimers.h> TEAM-OS2
> Online Campground Directory http://www.camping-usa.com
> Online Giftshop Superstore http://www.cloudninegifts.com
> ==========================================================================
>
>
>
>
Gustavo Rios <[EMAIL PROTECTED]> wrote:
>
>I did not say they blamed qmail, they only assured SSH was bugfree!
Anyone who says 'X' is bugfree, when 'X' is something as baroque as
ssh, is a fool. My confidence in ssh would only be lowered by hearing
such a claim--unless it was made a marketing type.
>NOTHING were said about qmail.
So why are we talking about it?
-Dave
I just found this in my delete folder.. It looks like Gustavo DID say
they claimed qmail was the point of entry.
On Thu, 29 Jul 1999, Gustavo Rios wrote:
> Does any body here knows something about rootshell attack?
> According some people at bos-br, they were hacked through qmail, which
has
> some bug! (Nothing sure).
> -----Original Message-----
> From: Dave Sill [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, July 29, 1999 2:19 PM
> To: [EMAIL PROTECTED]
> Subject: Re: security
>
> Gustavo Rios <[EMAIL PROTECTED]> wrote:
> >
> >I did not say they blamed qmail, they only assured SSH was bugfree!
>
> Anyone who says 'X' is bugfree, when 'X' is something as baroque as
> ssh, is a fool. My confidence in ssh would only be lowered by hearing
> such a claim--unless it was made a marketing type.
>
> >NOTHING were said about qmail.
>
> So why are we talking about it?
>
> -Dave
On Thu, 29 Jul 1999, Gustavo Rios wrote:
Does any body here knows something about rootshell attack?
According some people at bos-br, they were hacked through qmail, which has
some bug! (Nothing sure).
No, they (rootshell) never implicated qmail. Take a look at their
web page, scroll down to Oct/Nov 1998 and read the notice "rootshell
defaced". In it they implicate SSH 1.2.26.
-- Jeff Hayward
> Anyone who says 'X' is bugfree, when 'X' is something as baroque as
> ssh, is a fool. My confidence in ssh would only be lowered by hearing
> such a claim--unless it was made a marketing type.
>
> >NOTHING were said about qmail.
>
> So why are we talking about it?
Cause, nobody said nothing about qmail!
It was my doubt!
> -Dave
>
On Thu, 29 Jul 1999, Soffen, Matthew wrote:
> I just found this in my delete folder.. It looks like Gustavo DID say
> they claimed qmail was the point of entry.
Ups, some people at bos-br said that! IBM/SSH Corp, said nothing about
qmail!
> On Thu, 29 Jul 1999, Gustavo Rios wrote:
> > Does any body here knows something about rootshell attack?
> > According some people at bos-br, they were hacked through qmail, which
> has
> > some bug! (Nothing sure).
>
>
>
> > -----Original Message-----
> > From: Dave Sill [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, July 29, 1999 2:19 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: security
> >
> > Gustavo Rios <[EMAIL PROTECTED]> wrote:
> > >
> > >I did not say they blamed qmail, they only assured SSH was bugfree!
> >
> > Anyone who says 'X' is bugfree, when 'X' is something as baroque as
> > ssh, is a fool. My confidence in ssh would only be lowered by hearing
> > such a claim--unless it was made a marketing type.
> >
> > >NOTHING were said about qmail.
> >
> > So why are we talking about it?
> >
> > -Dave
>
I'm running qmail 1.03 on a RH 6.0 box.
Does anyone know what this message means:
458 Couldn't exec qmail-etrn
Thank you
Frank Greven
/---------------------------------------------------------\
| RIMNet GmbH Tel. : (02102) 420 760 |
| Kaiserswerther Str. 115 Fax : (02102) 420 62 |
| D-40880 Ratingen WWW : www.rimnet.de |
| Germany Email: [EMAIL PROTECTED] |
It'a RH problem, try switching it to slack/*BSD!
--
What's the similarity between an air
conditioner and a computer? They both
stop working when you open windows.
On Thu, 29 Jul 1999, Frank Greven wrote:
> I'm running qmail 1.03 on a RH 6.0 box.
> Does anyone know what this message means:
>
> 458 Couldn't exec qmail-etrn
>
>
>
> Thank you
> Frank Greven
>
> /---------------------------------------------------------\
> | RIMNet GmbH Tel. : (02102) 420 760 |
> | Kaiserswerther Str. 115 Fax : (02102) 420 62 |
> | D-40880 Ratingen WWW : www.rimnet.de |
> | Germany Email: [EMAIL PROTECTED] |
>
> However messages coming from smtp, qmqp and qmtp input _do_not_ go
> through qmail-inject.
>
> What you can do, is capture all outgoing mail from your domain in a
> directory, and have a program deliver them through qmail-inject. This
> program must set the QMAILUSER, QMAILNAME and QMAILHOST environment
> variables according to the mail headers, so it should parse the message.
>
I have tried this :
I capture all emails :
/var/qmail/control/virtualdomains
:alias-fai
In inject all the messages in a script called inject-filter :
/var/qmail/alias/.qmail-fai-default :
| /var/qmail/bin/inject-filter
Contents of inject-filter :
#!/bin/sh
QMAILINJECT=f
QMAILUSER="Nord.Bassin"
QMAILHOST="netsante.fr"
QMAILNAME="SEL Nord Bassin"
SENDER="[EMAIL PROTECTED]"
export QMAILINJECT QMAILUSER QMAILHOST QMAILNAME
qmail-inject
The problem is when a mail is received, It generate
a loop witch never stop :
mail received by smtp -> (virtual domain )inject-filter -> mail
re-injected via qmail-queue
| |
------------------<------------------
David ROBERT.
I'm having some problems today with people getting a bounce message for
mail that they did not send. I'm looking in /var/qmail/queue, and finding
LatnGrnQQs as a string in files in the bounce/ directory, and nowhere
else. I'm assuming that the number in the filename must map to the other
parts of the queue. If I can find no other references to that number, is
it acceptable to delete those things in bounce/ ?
Thanks,
Monte Mitzelfelt
yes, this is possible.
I setup a host with the holdremotepatch. after calling ISP, automaticly all
mail is dumped by SMTP to my mailserver ( one mailbox with all messages for the
domain ).
Qmail redirect these messages to the right local mailbox
The holdremote patch is used to hold the remote delivery to my ISP and each 20
min. cron triggers qmail to send and automaticly receives his mail to from the
ISP.
setting this up is very easy and without, until now, errors for several months.
Marco Leeflang
Cal Page wrote:
> My ISP puts any mail for my machine into one POP3 mailbox. For example,
> mail sent to either
>
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> would end up in the same mailbox at the ISP-. The only difference noted, is
> in the mail header, where the 'to:' field reflects the difference.
>
> I need some task that will connect to this mailbox, (say driven by cron),
> read the messages, and then post them to the various mailboxes on my
> system. Is there such a task in qmail?
>
> I read the qmail FAQ before posting, but it only mentioned setting up a POP
> server, and did not specifically talk to my case.
>
> Thank You,
> Cal Page
On Thu, 29 Jul 1999, Xiaoxia Zhao wrote:
> Dear friends:
> Now, I am developing freemail system based on qmail. I test the qmail's
> efficiency as following step.
a) use maildirs
b) use a logging file system (eg veritas, xfs, Sun's online disksuite)
c) what is the round-trip latency of the remote addresses?
d) Are you using syslogd? if so, turn off fsync() of the logfiles, or
switch to cyclog
Richard
Greetings again oh qmail guru's
I posted a question last week about getting an "unable to exec qq" error
message.
I got one response that suggested that it was a permissions problem and
that I run Eric Huss' queue-fix. Well, I did that and it reported that everything
was fine.
So, to reiterate, whenever I need to send a bounce message or use our
online forms, which use a 'sendmail -t' command, I get the error message. I
temporarily went back to running sendmail for the forms and also have qmail
running to do our mail relaying, but obviously this kludge isn't something that
I want to have running forever.
Using qmail-inject works fine, as does the mail relaying, so I know that qmail
at least partially works.
If someone could give me some more ideas, or point me towards the
resources to look at, I would appreciate it.
Thanks,
Rob Baham
*********************************
Rob Baham, Network Administrator
Email: [EMAIL PROTECTED]
SciTech Software, Inc.
505 Wall Street
Chico, CA 95928, USA
Voice: (530) 894-8400
Fax : (530) 894-9069
www : http://www.scitechsoft.com
*********************************
Can you truss -f (or the moral equivalent) the invocation of sendmail -t?
Is it a problem regardless of which user invokes sendmail -t?
(I know you don't have users as such, but I'm wondering whether there are
different outcomes for different uids).
What uid do you forms run as?
Mark.
At 11:58 AM Thursday 7/29/99, Rob Baham wrote:
>Greetings again oh qmail guru's
>
>I posted a question last week about getting an "unable to exec qq" error
>message.
>
>I got one response that suggested that it was a permissions problem and
>that I run Eric Huss' queue-fix. Well, I did that and it reported that
>everything
>was fine.
>
>So, to reiterate, whenever I need to send a bounce message or use our
>online forms, which use a 'sendmail -t' command, I get the error message. I
>temporarily went back to running sendmail for the forms and also have qmail
>running to do our mail relaying, but obviously this kludge isn't something
>that
>I want to have running forever.
>
>Using qmail-inject works fine, as does the mail relaying, so I know that
>qmail
>at least partially works.
>
>If someone could give me some more ideas, or point me towards the
>resources to look at, I would appreciate it.
>
>Thanks,
>Rob Baham
>*********************************
>Rob Baham, Network Administrator
>Email: [EMAIL PROTECTED]
>SciTech Software, Inc.
>505 Wall Street
>Chico, CA 95928, USA
>Voice: (530) 894-8400
>Fax : (530) 894-9069
>www : http://www.scitechsoft.com
>*********************************
I should have added the default "I am a newbie at this" :-)
> Can you truss -f (or the moral equivalent) the invocation of sendmail -t?
Um, I don't have truss and the other knowledgeable people looked at me and
asked if I wanted to build a building. What does truss do, so I can try to find
a similar command...
FYI I'm running: Cobalt Linux release 4.0 (Fargo) Kernel 2.0.34
>
> Is it a problem regardless of which user invokes sendmail -t?
I'll check that out - it'll take me a bit though... But, why would I be getting
the same error message for bounces, since they would be run from one of
the qmail users, right?
> (I know you don't have users as such, but I'm wondering whether there are
> different outcomes for different uids).
>
> What uid do you forms run as?
httpd user, home group
Could this be part of the problem? Do I need to add one of the qmail users
to the home group, or httpd to the qmail group?
Rob
>
>
> Mark.
>
> At 11:58 AM Thursday 7/29/99, Rob Baham wrote:
> >Greetings again oh qmail guru's
> >
> >I posted a question last week about getting an "unable to exec qq" error
> >message.
> >
> >I got one response that suggested that it was a permissions problem and
> >that I run Eric Huss' queue-fix. Well, I did that and it reported that
> >everything was fine.
> >
> >So, to reiterate, whenever I need to send a bounce message or use our
> >online forms, which use a 'sendmail -t' command, I get the error message.
> > I temporarily went back to running sendmail for the forms and also have
> >qmail running to do our mail relaying, but obviously this kludge isn't
> >something that I want to have running forever.
> >
> >Using qmail-inject works fine, as does the mail relaying, so I know that
> >qmail at least partially works.
> >
> >If someone could give me some more ideas, or point me towards the
> >resources to look at, I would appreciate it.
> >
> >Thanks,
> >Rob Baham
> >*********************************
> >Rob Baham, Network Administrator
> >Email: [EMAIL PROTECTED]
> >SciTech Software, Inc.
> >505 Wall Street
> >Chico, CA 95928, USA
> >Voice: (530) 894-8400
> >Fax : (530) 894-9069
> >www : http://www.scitechsoft.com
> >*********************************
I'm working on infiltrating qmail into our company's mail gateway (OK, I
have permission to do so, so it's not quite a covert operation :).
This isn't strictly about qmail proper, but I think close enough.
Our system is an Exchange system (please, no comments) and is set on a
private IP range. Currently, we have the NS records set to point to that box
with an MX value of 10. Now, since that's an invalid box in the real world,
it falls back to the Solaris box currently running sendmail. The Solaris box
then forwards the message inside the firewall to the Exchange box because
that box understands where the Exchange system is (the NS record isn't
invalid for the Solaris box).
There has *GOT* to be a better way to do this. What I need to do is forward
mail through the qmail system to users on the Exchange system. If it's
addressed to <someone>@thecreek.com it needs to go to one box. If it's
addressed to <someone>@pkb.thecreek.com it needs to go to another box (also
internal and also configured to receive mail as above).
Any suggestions.
--
Ben Kosse <[EMAIL PROTECTED]>
PC Technician -- Coldwater Creek, Inc.
(208) 265-7114
Ben Kosse writes:
> Our system is an Exchange system (please, no comments) and is set on a
> private IP range. Currently, we have the NS records set to point to that box
> with an MX value of 10. Now, since that's an invalid box in the real world,
> it falls back to the Solaris box currently running sendmail.
That's a rather dumb way to go.
> The Solaris box
> then forwards the message inside the firewall to the Exchange box because
> that box understands where the Exchange system is (the NS record isn't
> invalid for the Solaris box).
>
> There has *GOT* to be a better way to do this. What I need to do is forward
> mail through the qmail system to users on the Exchange system. If it's
> addressed to <someone>@thecreek.com it needs to go to one box. If it's
> addressed to <someone>@pkb.thecreek.com it needs to go to another box (also
> internal and also configured to receive mail as above).
>
> Any suggestions.
Yes.
$ man qmail-remote
And scroll down to the part about control/smtproutes.
--
Sam
After a crash reinstallation of a Linux server (vicious blackout and no
UPS) I migrated the system from Sendmail to qmail 1.03. As always it's
setup using Maildirs, but that has left me with a pile of old mailboxes
in /var/spool/mail.
My question:
How can I "reinstate" these mailboxes into the new system?
My first idea was to pipe them into the queue via port 25 on the system,
using telnet.
Can this be done?
How is it done?
--
Best regards / Mvh.,
Steen Suder
sysadm kollegie6400.dk
GNU - makes me feel better! Ehhh, Linux is GNU, right...?
On Fri, Jul 30, 1999 at 08:49:21AM +0000, Steen Suder wrote:
> My question:
>
> How can I "reinstate" these mailboxes into the new system?
> My first idea was to pipe them into the queue via port 25 on the system,
> using telnet.
Use Russell Nelson's
http://www.qmail.org/convert-and-create
--
See complete headers for more info
|
a while ago here was a thread about messages
that vanished... now I have the same problem, but I can't find the old messages
anywhere... anyone that still has those, could you please send the thread
messages to me (on private, not to the list) or if you have any reasons for the
folowing, please give advice....
all my normal mail adresses are working, but
those adresses, which are redirected from root via .qmail-root are vanished
somewhere...
.qmail-root has 4 recipients listed, and no one
of them gets the mail, but it doesn't go to /var/qmail/alias/Mailbox either...
so where, and why, does it go, and how can I stop this from happening?
earlier it all worked, and then suddenly not
anymore. I haven't made any changes since, except run qmail-newu for a few
times...
-Maria
|
