qmail Digest 31 Jul 1999 10:00:00 -0000 Issue 714
Topics (messages 28366 through 28397):
How to debug "soft error" on qmail-pop3d?
28366 by: Steen Suder <[EMAIL PROTECTED]>
28377 by: "Tim Hunter" <[EMAIL PROTECTED]>
28381 by: Steen Suder <[EMAIL PROTECTED]>
Internet draft for VERP
28367 by: Dave Sill <[EMAIL PROTECTED]>
28368 by: Dave Sill <[EMAIL PROTECTED]>
28370 by: "Sam" <[EMAIL PROTECTED]>
28372 by: Dave Sill <[EMAIL PROTECTED]>
28373 by: Russell Nelson <[EMAIL PROTECTED]>
28387 by: Scott Schwartz <[EMAIL PROTECTED]>
28388 by: Mark Delany <[EMAIL PROTECTED]>
28389 by: "Chris Garrigues" <[EMAIL PROTECTED]>
28390 by: Mark Delany <[EMAIL PROTECTED]>
28391 by: "Chris Garrigues" <[EMAIL PROTECTED]>
28392 by: "Sam" <[EMAIL PROTECTED]>
28393 by: [EMAIL PROTECTED] ()
28394 by: Scott Schwartz <[EMAIL PROTECTED]>
28397 by: "D. J. Bernstein" <[EMAIL PROTECTED]>
How to do AOL patch?
28369 by: Dave Sill <[EMAIL PROTECTED]>
Problems with user aliases
28371 by: Dave Sill <[EMAIL PROTECTED]>
unable to exec qq
28374 by: Dave Sill <[EMAIL PROTECTED]>
28382 by: "Rob Baham" <[EMAIL PROTECTED]>
28383 by: Dave Sill <[EMAIL PROTECTED]>
28384 by: "Rob Baham" <[EMAIL PROTECTED]>
Setting up Qmail as a mail gateway
28375 by: Dave Sill <[EMAIL PROTECTED]>
vanishing messages
28376 by: Dave Sill <[EMAIL PROTECTED]>
Sendmail equivalent of Qmail
28378 by: Amit Vadehra <[EMAIL PROTECTED]>
28379 by: Anand Buddhdev <[EMAIL PROTECTED]>
just a quick one...how do I have a user's mail go to /dev/null
28380 by: Mate Wierdl <[EMAIL PROTECTED]>
Off Topic: Netscape 3.0
28385 by: David Villeger <[EMAIL PROTECTED]>
IMAP and Maildir
28386 by: [EMAIL PROTECTED]
Qmail and database to route mail
28395 by: "Brian McKinney" <[EMAIL PROTECTED]>
Eliding quotes in envelope?
28396 by: "D. J. Bernstein" <[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]
----------------------------------------------------------------------
When I run /etc/rc.d/init.d/qmail-pop3d.init start on my freshly
installed qmail 1.03 system, it gives me a "soft error" before the
"starting qmail-pop3d... done" message.
Furthermore, I can't login through pop3.
It gives me the "this user has no $HOME/Maildir" and breaks connection.
Maildir is there:
[root@ns sfs]# ls -al Maildir/
total 5
drwx------ 5 sfs wheel 1024 Jul 30 11:42 ./
drwxr-xr-x 5 sfs wheel 1024 Jul 30 13:06 ../
drwx------ 2 sfs wheel 1024 Jul 30 11:42 cur/
drwx------ 2 sfs wheel 1024 Jul 30 11:42 new/
drwx------ 2 sfs wheel 1024 Jul 30 11:42 tmp/
All other users has the same problem.
Mail is delivered OK in all Maildirs (all users).
How can I debug this?
I don't know how to interpret "soft error" (I don't read much code), so
I'm looking for directions.
--
Best regards / Mvh.,
Steen Suder
sysadm kollegie6400.dk
GNU - makes me feel better! Ehhh, Linux is GNU, right...?
I think we will be needing more information. What is the content of the
script that is in /etc/rc.d/init.d/qmail-pop3d.init ?
Most errors I have seen with the error "this user has no $HOME/Maildir" has
to do with a minor mistype. Especially since you say that all mail gets
delivered properly.
-----Original Message-----
From: Steen Suder [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 30, 1999 7:23 AM
To: [EMAIL PROTECTED]
Subject: How to debug "soft error" on qmail-pop3d?
When I run /etc/rc.d/init.d/qmail-pop3d.init start on my freshly
installed qmail 1.03 system, it gives me a "soft error" before the
"starting qmail-pop3d... done" message.
Furthermore, I can't login through pop3.
It gives me the "this user has no $HOME/Maildir" and breaks connection.
Maildir is there:
[root@ns sfs]# ls -al Maildir/
total 5
drwx------ 5 sfs wheel 1024 Jul 30 11:42 ./
drwxr-xr-x 5 sfs wheel 1024 Jul 30 13:06 ../
drwx------ 2 sfs wheel 1024 Jul 30 11:42 cur/
drwx------ 2 sfs wheel 1024 Jul 30 11:42 new/
drwx------ 2 sfs wheel 1024 Jul 30 11:42 tmp/
All other users has the same problem.
Mail is delivered OK in all Maildirs (all users).
How can I debug this?
I don't know how to interpret "soft error" (I don't read much code), so
I'm looking for directions.
--
Best regards / Mvh.,
Steen Suder
sysadm kollegie6400.dk
GNU - makes me feel better! Ehhh, Linux is GNU, right...?
Tim Hunter wrote:
>
> I think we will be needing more information. What is the content of the
> script that is in /etc/rc.d/init.d/qmail-pop3d.init ?
> Most errors I have seen with the error "this user has no $HOME/Maildir" has
> to do with a minor mistype. Especially since you say that all mail gets
> delivered properly.
Well, I got bit further.
There was a error in the name of the reverse zone in the DNS (on the
same machine) in named.conf.
The 4th octet was in name of the reverse zone. It's a Class C zone.
After dealing with this pop3d starts right away with no errors as
opposed to a slight delay and an error before.
Now it gives me the "-ERR Authorization failed" message.
Back to the compiler!
Thanks for your time.
<SNIP old message>
--
Best regards / Mvh.,
Steen Suder
sysadm kollegie6400.dk
GNU - makes me feel better! Ehhh, Linux is GNU, right...?
"Sam" <[EMAIL PROTECTED]> wrote:
>
>[1] Implementing PIPELINING in Qmail would be a rather dumb thing to do, of
>course, this is theoretical.
Why do you say that? qmail-smtpd supports it, and qmail-remote support
multiple recipients.
-Dave
"Sam" <[EMAIL PROTECTED]> wrote:
>
>> John R. Levine ([EMAIL PROTECTED]) wrote:
>>
>> My point is that it is the senders responsibility to generate a
>> return path. Passing that responsibility to the server isn't a good
>
>You are passing the responsibility of delivering the entire message to the
>same exact server. If you think that the server is good enough to accept
>responsibility for delivering the message in the first place, chances that
>it's also good enough to properly bounce it.
No. You don't give a message to remote server because you think it'll
treat it right; you do it because you have to. Considering the
suprisingly large number of MTA's that don't even send bounces to the
return path, it seems likely that trusting random remote systems to do
the right thing will fail pretty often.
-Dave
Dave Sill writes:
> "Sam" <[EMAIL PROTECTED]> wrote:
> >
> >[1] Implementing PIPELINING in Qmail would be a rather dumb thing to do, of
> >course, this is theoretical.
>
> Why do you say that? qmail-smtpd supports it, and qmail-remote support
> multiple recipients.
Except that qmail-remote is always called to deliver one recipient only.
--
Sam
"Sam" <[EMAIL PROTECTED]> wrote:
>
>Except that qmail-remote is always called to deliver one recipient only.
qmail-rspawn only calls it with one recipient, but qmail-remote is
also a documented command that could be used in a home grown bulk
mailer, where pipelining would be a big win.
-Dave
Dave Sill writes:
> No. You don't give a message to remote server because you think it'll
> treat it right; you do it because you have to. Considering the
> suprisingly large number of MTA's that don't even send bounces to the
> return path, it seems likely that trusting random remote systems to do
> the right thing will fail pretty often.
Or like email.com, which does this: s/.*=// on an envelope sender
before generating a bounce. However, I'm working on getting them to
fix that.
--
-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 think it's strange that qmail-inject uses '-' to seperate the mailbox
from the verp part, even when some other conf-break character is in
effect for that user. This surely violates the principle of least
surprise, and it requires some users (but not others) to manually
include their break character in their return address, and to adjust
their dot-qmail scripts to match.
Sam writes:
| 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.
If the sender is to be required to put their conf-break at the end of
their slocal, do you still need the leading '-' in the verp part?
Perhaps giving the VERP extension an argument
(i.e. MAIL FROM:<...> VERP=+) would resolve that issue, albeit at the
cost of added complexity in the MTA.
At 05:18 PM Friday 7/30/99, Scott Schwartz wrote:
>I think it's strange that qmail-inject uses '-' to seperate the mailbox
>from the verp part, even when some other conf-break character is in
>effect for that user. This surely violates the principle of least
>surprise, and it requires some users (but not others) to manually
>include their break character in their return address, and to adjust
>their dot-qmail scripts to match.
I agree with you about "least surprise" but I would be concerned that an
installation is vulnerable to not detecting outstanding VERP mail because an
admin changed the conf-break character.
Likewise, if the bounce-to system (for want of a better term) is not the
same as the sending system, is it reasonable to insist that they have the
same conf-break characters before they can interoperate?
Mark.
> From: Mark Delany <[EMAIL PROTECTED]>
> Date: Fri, 30 Jul 1999 14:39:15 -0700
>
> At 05:18 PM Friday 7/30/99, Scott Schwartz wrote:
> >I think it's strange that qmail-inject uses '-' to seperate the mailbox
> >from the verp part, even when some other conf-break character is in
> >effect for that user. This surely violates the principle of least
> >surprise, and it requires some users (but not others) to manually
> >include their break character in their return address, and to adjust
> >their dot-qmail scripts to match.
>
>
> I agree with you about "least surprise" but I would be concerned that an
> installation is vulnerable to not detecting outstanding VERP mail because an
> admin changed the conf-break character.
>
> Likewise, if the bounce-to system (for want of a better term) is not the
> same as the sending system, is it reasonable to insist that they have the
> same conf-break characters before they can interoperate?
One way to think about it is as defining a "network standard conf-break
character" which systems are expected to convert to and from in order to
interoperate. This is much like FTP URLs using '/' characters no matter what
the underlying OS uses, or requiring bytes to be transmitted little-endian
over the network (or is it big-endian?...whatever...it's the motorola
ordering, not the intel ordering), or requiring that end-of-line be
transmitted as CRLF for text files.
Chris
--
Chris Garrigues virCIO
http://www.DeepEddy.Com/~cwg/ http://www.virCIO.Com
+1 512 432 4046 +1 512 374 0500
4314 Avenue C
O- Austin, TX 78751-3709
My email address is an experiment in SPAM elimination. For an
explanation of what we're doing, see http://www.DeepEddy.Com/tms.html
Nobody ever got fired for buying Microsoft,
but they could get fired for relying on Microsoft.
PGP signature
At 05:54 PM Friday 7/30/99, Chris Garrigues wrote:
> > From: Mark Delany <[EMAIL PROTECTED]>
> > Date: Fri, 30 Jul 1999 14:39:15 -0700
> >
> > At 05:18 PM Friday 7/30/99, Scott Schwartz wrote:
> > >I think it's strange that qmail-inject uses '-' to seperate the mailbox
> > >from the verp part, even when some other conf-break character is in
> > I agree with you about "least surprise" but I would be concerned that an
> > installation is vulnerable to not detecting outstanding VERP mail
> because an
> > admin changed the conf-break character.
> >
> > Likewise, if the bounce-to system (for want of a better term) is not the
> > same as the sending system, is it reasonable to insist that they have the
> > same conf-break characters before they can interoperate?
>
>One way to think about it is as defining a "network standard conf-break
>character" which systems are expected to convert to and from in order to
Yep. A standard conf-break may not be a bad idea, but it doesn't avoid the
confusion that Scott raised that people will confuse or assume that the qmail
conf-break is the same as the VERP conf-break.
Mark.
> From: Mark Delany <[EMAIL PROTECTED]>
> Date: Fri, 30 Jul 1999 16:52:17 -0700
>
> At 05:54 PM Friday 7/30/99, Chris Garrigues wrote:
> >One way to think about it is as defining a "network standard conf-break
> >character" which systems are expected to convert to and from in order to
>
>
> Yep. A standard conf-break may not be a bad idea, but it doesn't avoid the
> confusion that Scott raised that people will confuse or assume that the qmail
> conf-break is the same as the VERP conf-break.
Note that exactly this problem comes up when people write programs to talk to the
SMTP port and assume that \n will work as an end-of-line.
I wonder if it might actuall be better to make the network standard conf-break be
different than qmail's to make it clear that a conversion needs to occur.
Chris
P.S. Mark, I got an bounce saying that you no longer work at mira.net after
my last mail.
--
Chris Garrigues virCIO
http://www.DeepEddy.Com/~cwg/ http://www.virCIO.Com
+1 512 432 4046 +1 512 374 0500
4314 Avenue C
O- Austin, TX 78751-3709
My email address is an experiment in SPAM elimination. For an
explanation of what we're doing, see http://www.DeepEddy.Com/tms.html
Nobody ever got fired for buying Microsoft,
but they could get fired for relying on Microsoft.
PGP signature
On Fri, 30 Jul 1999, Mark Delany wrote:
> Yep. A standard conf-break may not be a bad idea, but it doesn't avoid the
> confusion that Scott raised that people will confuse or assume that the qmail
> conf-break is the same as the VERP conf-break.
This confusion is probably confined to people who use Qmail. I note that
sendmail, by default, uses the + character.
Chris Garrigues ([EMAIL PROTECTED]) wrote:
: > From: Mark Delany <[EMAIL PROTECTED]>
: > At 05:54 PM Friday 7/30/99, Chris Garrigues wrote:
: > >One way to think about it is as defining a "network standard conf-break
: > >character" which systems are expected to convert to and from in order to
: > Yep. A standard conf-break may not be a bad idea, but it doesn't avoid the
: I wonder if it might actuall be better to make the network standard conf-break be
: different than qmail's to make it clear that a conversion needs to occur.
Doesn't this sound very qmail-centric for an internet standard?
The partitioning issue was raised, now conf-break. It's not a
huge leap to letting the sender specify whatever arbitrary string
he wants for a return path.
-harold
"Chris Garrigues" <[EMAIL PROTECTED]> writes:
| One way to think about it is as defining a "network standard conf-break
| character" which systems are expected to convert to and from in order to
| interoperate.
My intuition is that it would be difficult to get people to go along
with that, especially since the break character is in the uninterpreted
local mailbox part of the address.
| This is much like FTP URLs using '/' characters no matter what
So, we invent a new kind of URL:
verp://cse.psu.edu/schwartz/qmail/....
In fact, to save typing you could write it as:
cse.psu.edu!schwartz!qmail!...
(grin.)
Scott Schwartz writes:
> I think it's strange that qmail-inject uses '-' to seperate the mailbox
> from the verp part, even when some other conf-break character is in
> effect for that user. This surely violates the principle of least
> surprise,
Certainly not. If a mailing list is named
Jim+Joe-Bob#3
then people expect the service addresses for that list to be
Jim+Joe-Bob#3-request
Jim+Joe-Bob#3-owner
Jim+Joe-Bob#3-subscribe
and so on. What follows Jim+Joe-Bob#3 is _always_ a dash. It doesn't
matter whether these addresses are controlled by Jim, or Jim+Joe, or
Jim+Joe-Bob, or Fred.
---Dan
"Peter Janett" <[EMAIL PROTECTED]> wrote:
>I've looke all over the qmail pages, and searched through the post I have
>from this list, but can't figure out how to do the AOL patch.
>
>I got the file for the qmail.org site, and uploaded it to /var/qmail/bin
Wrong.
>Then I entered this command. (Found it from a post on this list)
>patch -p0 < patchfile
>
>I figured out that I was supposed to replace "patchfile" with
>"qmail-103.patch"
>
>That gets me a response from patch, that says:
>"Can't find file to patch at input line 3 ..."
>
>So, yup, I'm a newbie, but I need some help. Once I figure this out, I
>would be willing to detail it for posting on the qmail.org site, so others
>like me will be able to add the patch.
See:
http://Web.InfoAve.Net/~dsill/lwq.html#patches
-Dave
Tero Niemi <[EMAIL PROTECTED]> wrote:
>
> Ok then... User that works is [EMAIL PROTECTED], he
>has .qmail-info in his home directory
> and in virtualdomains he is seen like this :
>lannenkonepalvelu.fi:jarkko.turvanen
>
> .qmail-info file has one line which is jarkko.turvanen(tried also with
>jarkko:turvanen). However when I send mail
> to [EMAIL PROTECTED] qmail says that we don't have a mailbox
>by that name here.
You have a user whose username is "jarkko.turvanen"? I wonder if the
length or the "." are messing you up. Try setting up a virtual domain
with a user whose username is alphanumeric and <= 8 characters long.
-Dave
[EMAIL PROTECTED] wrote:
>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
Truss runs a specified program and shows all the system calls it
makes, their arguments, and what they return. It's handy for
debugging.
It's pretty platform-variant, so it might also be known as trace,
strace, or par.
>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?
What does /var/qmail/bin/qmail-queue (AKA qq) look like? Should be
close to:
-rws--x--x 1 qmailq qmail 36480 Sep 11 1998 /var/qmail/bin/qmail-queue
Have you run "make check" from the build directory?
-Dave
Dave,
Here is the info you asked about...
> [EMAIL PROTECTED] wrote:
> >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?
-snip-
> It's pretty platform-variant, so it might also be known as trace,
> strace, or par.
Found it. It was strace. Thanks :) Long output file though...
I'm not sure what I'm looking for in it. I'll post the file at:
http://www.scitechsoft.com/strace.txt
Some points of interest:
1. It's hacking off parts of my file, maybe?
chdir("/var/qmail") = 0
open("control/me", O_RDONLY|O_NONBLOCK) = 5
read(5, "\0\0\0\0scitechsoft.com\n", 64) = 20
This is www.scitechsoft.com
close(5) = 0
open("control/defaultdomain", O_RDONLY|O_NONBLOCK) = 5
read(5, "www.echsoft.com\n", 64) = 16
This is scitechsoft.com
2. What are these files? I've mainly been using "Life with qmail" as my
refernce and didn't find any mention of them...
open("control/defaulthost", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No
such file or directory)
open("control/idhost", O_RDONLY|O_NONBLOCK) = -1 ENOENT (No such
file or directory)
> What does /var/qmail/bin/qmail-queue (AKA qq) look like? Should be
> close to:
>
>-rws--x--x 1 qmailq qmail 36480 Sep 11 1998 /var/qmail/bin/qmail-queue
-rws--x--x 1 qmailq qmail 22136 Jul 20 15:00 /var/qmail/bin/qmail-queue
I'd say that's fairly close, eh?
So, that's what qq is. I am starting to see the light. Well, at least a grey
fuzzy glow.
> Have you run "make check" from the build directory?
>
Just did. It reported:
instcheck: warning: /var/qmail/bin has wrong permissions
So I ran:
ls -al /var/qmail/
and trimmed out the other stuff to keep down on size....
drwxr-xr-x 12 root qmail 1024 Jul 26 09:50 .
drwxr-xr-x 20 root root 1024 Jul 20 16:20 ..
drwxrwxrwx 2 root qmail 1024 Jul 20 16:13 bin
Ok, it's probably too permisive, but the stuff should still run, right?
Thanks again.
Rob
[EMAIL PROTECTED] wrote:
>
>Found it. It was strace. Thanks :) Long output file though...
>I'm not sure what I'm looking for in it. I'll post the file at:
>http://www.scitechsoft.com/strace.txt
Got it.
>Some points of interest:
>1. It's hacking off parts of my file, maybe?
>chdir("/var/qmail") = 0
>open("control/me", O_RDONLY|O_NONBLOCK) = 5
>read(5, "\0\0\0\0scitechsoft.com\n", 64) = 20
>This is www.scitechsoft.com
Examine /var/qmail/control/me carefully, e.g., with "cat -v" or "od
-c". It should contain your FQDN and a newline. The leading nulls are
wrong.
>close(5) = 0
>open("control/defaultdomain", O_RDONLY|O_NONBLOCK) = 5
>read(5, "www.echsoft.com\n", 64) = 16
>This is scitechsoft.com
Same here. Maybe it should be scitechsoft.com, but it's actually
www.echsoft.com. Run qmail-showctl and see if you agree with the
output.
>2. What are these files? I've mainly been using "Life with qmail" as my
>refernce and didn't find any mention of them...
See:
http://Web.InfoAve.Net/~dsill/lwq.html#me
http://Web.InfoAve.Net/~dsill/lwq.html#defaultdomain
>> What does /var/qmail/bin/qmail-queue (AKA qq) look like? Should be
>> close to:
>>
>>-rws--x--x 1 qmailq qmail 36480 Sep 11 1998 /var/qmail/bin/qmail-queue
>-rws--x--x 1 qmailq qmail 22136 Jul 20 15:00 /var/qmail/bin/qmail-queue
>I'd say that's fairly close, eh?
>So, that's what qq is. I am starting to see the light. Well, at
>least a grey fuzzy glow.
What does "file /var/qmail/bin/qmail-queue" say? What happens if you
run qmail-queue as a normal user with no parameters or input? (Be
careful, you might have a hard time killing it off.)
>> Have you run "make check" from the build directory?
>>
>Just did. It reported:
>instcheck: warning: /var/qmail/bin has wrong permissions
>So I ran:
>ls -al /var/qmail/
>and trimmed out the other stuff to keep down on size....
>drwxr-xr-x 12 root qmail 1024 Jul 26 09:50 .
>drwxr-xr-x 20 root root 1024 Jul 20 16:20 ..
>drwxrwxrwx 2 root qmail 1024 Jul 20 16:13 bin
>
>Ok, it's probably too permisive, but the stuff should still run, right?
Yeah, but remove the group & world write bits just to be sure. Any
idea how they got that way?
-Dave
(strace output...)
> >Some points of interest:
> >1. It's hacking off parts of my file, maybe?
> >chdir("/var/qmail") = 0
> >open("control/me", O_RDONLY|O_NONBLOCK) = 5
> >read(5, "\0\0\0\0scitechsoft.com\n", 64) = 20
> >This is www.scitechsoft.com
>
> Examine /var/qmail/control/me carefully, e.g., with "cat -v" or "od
> -c". It should contain your FQDN and a newline. The leading nulls are
> wrong.
That is what is there... see below
>
> >close(5) = 0
> >open("control/defaultdomain", O_RDONLY|O_NONBLOCK) = 5
> >read(5, "www.echsoft.com\n", 64) = 16
> >This is scitechsoft.com
>
> Same here. Maybe it should be scitechsoft.com, but it's actually
> www.echsoft.com. Run qmail-showctl and see if you agree with the
> output.
Ok. This is strange.
od -c defaultdomain
0000000 s c i t e c h s o f t . c o m \n
0000020
me had a similar, correct output.
I ran qmail-showctl:
me: My name is www.scitechsoft.com.
defaultdomain: Default domain name is scitechsoft.com.
Which is exactly what the files say. I'm not sure where the nulls and trashed
name are coming from...
> >2. What are these files? I've mainly been using "Life with qmail" as my
> >refernce and didn't find any mention of them...
I'm sorry, I didn't mean the files above, I meant the files below (they were
missing):
control/defaulthost
control/idhost
> What does "file /var/qmail/bin/qmail-queue" say? What happens if you
> run qmail-queue as a normal user with no parameters or input? (Be
> careful, you might have a hard time killing it off.)
Boy, you were right on that one ;-) Ok, when I ran qq as root, it said nothing.
I guess it just started running until I telneted in on another session and killed
it. If I ran it as admin (default login) it told me:
bash: ./qmail-queue: Operation not permitted
-rws--x--x 1 qmailq qmail 22136 Jul 20 15:00 qmail-queue
It is the *only* file in the /var/qmail/bin directory that has those
owners/permissions.
The other are all root/qmail and either 755, 711 or 700
To me that seems kind of strange. I would think that they should be owned
by one of the qmail users or the qmail group.
> >> Have you run "make check" from the build directory?
-snip-
> >drwxrwxrwx 2 root qmail 1024 Jul 20 16:13 bin
> >Ok, it's probably too permisive, but the stuff should still run, right?
> Yeah, but remove the group & world write bits just to be sure. Any
> idea how they got that way?
No. I *think* that is just the way in installed. I don't think I changed them,
but I could have...
Rob
Ben Kosse <[EMAIL PROTECTED]> wrote:
>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.
Why do you publicly advertise a private address? If you need an
internal MX that points to the exchange box, you probably should set
up a split name service that advertises different addresses to
insiders and outsiders.
>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).
Assuming that <someone>@thecreek.com should go to foo.example.com and
<someone>@pkb.thecreek.com should go to a system whose IP address is
10.10.10.10, add the following to control/smtproutes:
thecreek.com:foo.example.com
pkb.thecreek.com:[10.10.10.10]
-Dave
"Maria Zevenhoven" <[EMAIL PROTECTED]> wrote:
>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....
Search the list archives at:
http://www-archive.ornl.gov:8000/
>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?
What do your logs say?
>earlier it all worked, and then suddenly not anymore. I haven't made
>any changes since, except run qmail-newu for a few times...
The tech support engineer's most commonly heard phrase: "I haven't
changed anything." :-)
If it worked before, but it doesn't work now, *something* has changed.
E.g., what do you have in users/assign?
-Dave
HI,
I am trying to make a sendmail and a qmail server talk to each other
.
What i need to do is that i need all the mail from a sendmail server for
a certian domain to be forwarded to my qmail server. Both servers sit on
the net. This does not have to happen generically for all domains in the
send mail server but for specific domains in that server so i cant point
all mails in this sendmail server to this qmail server.
I would essentially like the MX record to be pointed to the sendmail
server so that, that is the main server that receives all the mail and
the thereafter all the mail is forwarded to my qmail server.
In simple terms we need an eqiuvalent of the SMTPROUTES file entry in
Sendmail.
SMTPROUTES has this functionality and a similar entry in sendmail would
solve the purpose.
Thanks in advance
Amit vadehra
On Fri, Jul 30, 1999 at 07:29:00PM +0530, Amit Vadehra wrote:
> In simple terms we need an eqiuvalent of the SMTPROUTES file entry in
> Sendmail.
> SMTPROUTES has this functionality and a similar entry in sendmail would
> solve the purpose.
> Thanks in advance
See the "mailertable" option in sendmail. BTW, this question belongs to
the sendmail list, in case you need more help with setting up the
mailertable.
--
See complete headers for more info
You mean mail *from* somebody, or mail *for* a local user?
For the first, either put the fellow's address in the badmailfrom
control file, or, if you do not want to produce any bounce, put
| if [ "$SENDER" = "[EMAIL PROTECTED]" ]; then exit 99; else exit 0; fi
./Mailbox
in your .qmail file (or `./Maildir, if you are using maildir).
Now if you want to reject mail for a certain local user (who exists!),
then you need to set up qmail-users, and then you can control the
user's mail via aliases (.qmail file).
Once qmail-users is set up, you can just set up an empty .qmail file
for the user in ~alias.
Mate
Hi,
Test email messages sent by us to Netscape Mail 3.0x users can't be read.
When they click on the message, it opens, flickers, and closes.
This is not a qmail question. Although we use qmail to receive email, we
don't use it to send (too slow). But I am getting desperate, I've looked at
all standards/faqs/... again and I didn't find anything, so I thought I'd
try the email experts on the list.
The body headers are as follow:
Date: Fri, 30 Jul 1999 04:59:25 -0000
Message-Id: <19990730045925.0850.cheetahmail@mta1>
From: "Bat Girl" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Free tonight?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
I looked and looked again and can't find anything outside the standard
(even the order of the fields). This is obviously a Netscape 3.0x bug as it
works perfectly on all other MUAs.
Has anybody ever seen this problem before?
Thanks again.
David.
______________________________________
David Villeger
(212) 972 2030 x34
http://www.CheetahMail.com
The Internet Email Publishing Solution
I am running a server with Qmail installed using vchkpw's virtual domain
addon. This method uses Maildirs only and DOES NOT store the Maildir
within a user's home directory. Instead it stores all mail within a single
directory structure such as:
/home/popusers/domains/domain.com/user/Maildir
And it is owned/grouped for vchkpw.
I am wanting to configure an IMAP server so to allow programs such as Pine
to be used. I have found to references to use IMAP via Qmail's homepage.
But it doesn't seem to work with this method (haven't tried yet).
Is anyone using IMAP and Qmail's Maildirs? If so, could you please supply
some advice on this upgrade? Can I use my own checkpoppassword file
because I am not using system accounts? Does these permissions of vchkpw
make a difference in this IMAP server?
Also if Pine can be used another way with Maildirs, please let me know. But
seeing as the Maildir's are owned by someone else but the user, I see that
an outsource is needed to access these files.
Thanks in advance!
Eric Duncan
President.and.CEO
The.Public.Network
http://www.thepublic.net
[EMAIL PROTECTED]
I am attempting to setup a system where mail is
stored on multiple machines and is sent to the various machines via an
in-bound relay. I need to integrate qmail and our database
so that when I message for our domain comes in, the relay looks up the
server the users mail is stored on and then forward the mail to the
appropiate machine. After looking around the qmail source for
awhile, the closest thing I could come to was making all the
traffic local on the relay and having the lookup done in qmail-local and
having qmail-local forward the mail.
However, this tends to be a
little slow and redundant because every message must travel the relay
twice.
Does anyone have any ideas on
where (ie what qmail module) I should put the lookup in? My best
guess in qmail-send but trying to find where in that module is quite the
task.
Any help would be greatly
appreciated.
Brian
McKinney
|
Here's an example of correct quoting behavior. An SMTP client that wants
to send mail to the address
Joe,[EMAIL PROTECTED]
generates the SMTP command
RCPT TO:<Joe\,[EMAIL PROTECTED]>
which the SMTP server then decodes into
Joe,[EMAIL PROTECTED]
There are many other possibilities for the SMTP command in the middle.
For example:
RCPT TO:<"Joe,Smith"@cr.yp.to>
Rcpt To:<\J\o\e\,\S\m\i\t\[EMAIL PROTECTED]>
rCpT tO:<"\Jo\e,\S\mi\t\h"@cr.yp.to>
The SMTP client may use any of these address encodings. The SMTP server
decodes all of them into the same address.
(The idea that the SMTP server is required to preserve the quotes and
backslashes when it relays messages to other hosts is as ludicrous as
the idea that the SMTP server is required to preserve the case of RCPT.
RFC 821 says nothing of the sort.)
Similar comments apply to RFC 822. A message generator might encode the
address Joe,[EMAIL PROTECTED] as
From: "J\oe\,S\mi\th" (Joey) @ cr.yp.to
A message reader decodes this address into Joe,[EMAIL PROTECTED] and sends
a reply to that address. The address might be encoded in the reply as
To: "Joe,Smith"@cr.yp.to
and in a subsequent SMTP conversation as
RCPT TO:<"Joe\,Smith"@cr.yp.to>
which, as above, specifies the address Joe,[EMAIL PROTECTED] This address
has, as RFC 821 says, ``a single nine character user field with comma
being the fourth character of the field.''
Scott Schwartz writes:
> qmail-smtpd wrongly transforms <"A B"@ARPA> into <A B@ARPA>
No. You are confusing two different objects:
* the address, eight characters long in this example: A B@ARPA
* an SMTP command specifying that address: RCPT TO:<"A B"@ARPA>
Surely you understand the concepts of ASCII-encoded IP addresses, and
zone-file-encoded domain names, and sh-encoded command-line arguments.
So why are you having so much trouble with SMTP-encoded email addresses?
---Dan
