qmail Digest 21 Sep 1999 10:00:00 -0000 Issue 766
Topics (messages 30513 through 30591):
Pop Server
30513 by: Qmail-User
30518 by: Anand Buddhdev
Re: qmail-smtpd-wrapper error.
30514 by: Chris Johnson
30515 by: Lorens Kockum
30517 by: Mark Thomas
30520 by: Lorens Kockum
30521 by: Dave Sill
30526 by: Mark Thomas
30543 by: Dave Sill
30585 by: Mark Thomas
Re: When will qmail back off to the next MX?
30516 by: David Dyer-Bennet
30551 by: phil.ipal.net
Can't find message after received
30519 by: Eric Davis
30535 by: Dave Sill
Re: Having trouble with pop
30522 by: Tim Hunter
30524 by: Mikko H�nninen
30532 by: Aaron L. Meehan
30533 by: Rick Erlandson
30537 by: Tim Hunter
30539 by: Gregory J. Forkiin (Rhawn)
30546 by: Rick Erlandson
30555 by: Racer X
30558 by: Gregory J. Forkiin (Rhawn)
Re: qmail-smtp fails on RedHat 6.0
30523 by: mw.wierdlmpc.msci.memphis.edu
30534 by: Richard George
30540 by: Dave Sill
30553 by: Mate Wierdl
big Messages with POP3
30525 by: martin.sintesoft.net
Re: Main server = qmail, destination = ms exchange
30527 by: Dave Sill
30548 by: Olivier M.
Re: (Clarification) Installation Quesiton on Qmail.
30528 by: Serban Udrea
30545 by: Dave Sill
30552 by: Mark Thomas
Re: How to remove a (botched) qmail installation to start over?
30529 by: Dave Sill
Re: <> question
30530 by: Aaron L. Meehan
Qmail and HP Openmail
30531 by: Stephan Hadan (E-Mail)
Re: maildir structure
30536 by: qmail.col7.metta.lk
imapd with tcpserver?
30538 by: Piotr Wanat
30541 by: Dave Sill
30542 by: Piotr Wanat
30544 by: Dave Sill
30549 by: Piotr Wanat
30550 by: Dave Sill
30554 by: Piotr Wanat
30565 by: Dave Sill
Re: auto-forward email and hierarchical email account
30547 by: Dave Sill
Weird Message...
30556 by: Andy Walden
How good is RBL at filtering spam?
30557 by: David Harris
30559 by: James J. Lippard
30560 by: schinder.leprss.gsfc.nasa.gov
30562 by: David Harris
30569 by: Nathan J. Mehl
30570 by: David Harris
30571 by: James Smallacombe
30573 by: Fabrice Scemama
30574 by: Vern Hart
30576 by: James Smallacombe
30580 by: schinder.leprss.gsfc.nasa.gov
"550 rejected: cannot route to sender" problem
30561 by: Graham Higgins
Re: Sqwebmail and IMAP
30563 by: Randy Harmon
30566 by: Racer X
30567 by: Randy Harmon
30568 by: Asmodeus
30572 by: Racer X
30575 by: Sam
30584 by: Randy Harmon
usage of qmail-local
30564 by: Joe Chan
Virtual email for non virtual host
30577 by: James
How to Rewrite Message-ID using ofmipd
30578 by: x
how to using maildrop
30579 by: x
HOw to send more with qmail-inject?
30581 by: Hawke
30583 by: Peter Samuel
qmail-start (qmail 1.03) under RedHat 6.0
30582 by: Vladimir Berezniker
Re: race condition in qmail-popbull
30586 by: Michael Boyiazis
Re: ANNOUNCE: /var/qmail/control/locals and regex
30587 by: Robert Sander
ETRN
30588 by: Dimitri SZAJMAN
30591 by: Anand Buddhdev
qmail-smtpd on tcpserver again :(
30589 by: Piotr Wanat
30590 by: Anand Buddhdev
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]
----------------------------------------------------------------------
I am having some difficulty starting my pop server. Could someone give me
an example of what type of syntax they use to start the qmail pop service?
Regards
Vivian Lal
On Mon, Sep 20, 1999 at 09:09:04PM +1000, Qmail-User wrote:
tcpserver -RHlmy.host.name 0 110 /usr/local/qmail/bin/qmail-popup \
my.host.name /usr/local/bin/checkpassword \
/usr/local/qmail/bin/qmail-pop3d Maildir &
Replace my.host.name with your host's name, and change the path to the
programs to /var/qmail. That's where you most likely installed qmail.
> I am having some difficulty starting my pop server. Could someone give me
> an example of what type of syntax they use to start the qmail pop service?
>
> Regards
>
> Vivian Lal
>
--
See complete headers for more info
On Sun, Sep 19, 1999 at 10:46:11PM -0500, Mark Thomas wrote:
> 937728523.256241 tcpserver: warning: dropping connection, unable to run
> /var/qmail/bin/qmail-smtpd-wrapper: access denied
> 937728523.256449 tcpserver: end 16854 status 28416
> 937728523.256503 tcpserver: status: 0/40
>
> This is the /var/qmail/bin/qmail-smtpd-wrapper
> #/bin/bash
The line above needs to be:
#!/bin/bash
And make sure that qmail-smtpd-wrapper is executable.
> # remmed the next line out due to errors.
> ***********************MCT**********************
What's the above line? It needs to be commented out.
> ulimit -d 1024
> exec /var/qmail/bin/qmail-smtpd $ {1+"$@"}
Chris
On the qmail list [EMAIL PROTECTED] wrote:
>937728523.256241 tcpserver: warning: dropping connection, unable to run
>/var/qmail/bin/qmail-smtpd-wrapper: access denied
Apart from the script syntax errors pointed out by Chris
Johnson, did you try reading the error message? It often gives
quite useful help in diagnosing the problem.
Make sure you do have execute access to the script.
Thanks Chris, I did a cut and paste from the Living with Qmail document,
the "Bang" wasn't there.
To prevent certain denial-of-service attacks against qmail-smtpd, you should
create a simple wrapper in /var/qmail/bin/qmail-smtpd-wrapper that looks
like:
#/bin/bash
ulimit -d 1024
exec /var/qmail/bin/qmail-smtpd ${1+"$@"}
To Reply to Lorens Kockum:
This appears to be on inbound mail, rights problems would have to be with
the daemon running the inbound mail process? Can you assign rights to a
daemon? Just for my curiosity, what is he a part of "user,group,other".
Anyway, There are execute rights on the file. Thanks for your comment also.
darkstar:~# cd /var/qmail/bin
darkstar:/var/qmail/bin# ls -Falc qmail-smtpd-wrapper
-rwxr-xr-x 1 root root 163 Sep 19 22:15 qmail-smtpd-wrapper*
Thanks,
MarkT.
-----Original Message-----
From: Chris Johnson [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 20, 1999 6:37 AM
To: Mark Thomas
Cc: Qmail List
Subject: Re: qmail-smtpd-wrapper error.
On Sun, Sep 19, 1999 at 10:46:11PM -0500, Mark Thomas wrote:
> 937728523.256241 tcpserver: warning: dropping connection, unable to run
> /var/qmail/bin/qmail-smtpd-wrapper: access denied
> 937728523.256449 tcpserver: end 16854 status 28416
> 937728523.256503 tcpserver: status: 0/40
>
> This is the /var/qmail/bin/qmail-smtpd-wrapper
> #/bin/bash
The line above needs to be:
#!/bin/bash
And make sure that qmail-smtpd-wrapper is executable.
> # remmed the next line out due to errors.
> ***********************MCT**********************
What's the above line? It needs to be commented out.
> ulimit -d 1024
> exec /var/qmail/bin/qmail-smtpd $ {1+"$@"}
Chris
On the qmail list [EMAIL PROTECTED] wrote:
>This appears to be on inbound mail, rights problems would have to be with
>the daemon running the inbound mail process? Can you assign rights to a
>daemon? Just for my curiosity, what is he a part of "user,group,other".
The daemon has a UID and a GID like other processes. I believe
those of the daemon running the inbound mail process should be
qmaild and qmail, respectively.
>Anyway, There are execute rights on the file. Thanks for your comment also.
>darkstar:~# cd /var/qmail/bin
>darkstar:/var/qmail/bin# ls -Falc qmail-smtpd-wrapper
>-rwxr-xr-x 1 root root 163 Sep 19 22:15 qmail-smtpd-wrapper*
If the problem persists after correcting the errors noted by
Chris Johnson, check that the above-lying directories also have
the necessary permissions.
Hava A Nice Day (and don't loose the machine on the world
without changing the hostname and checking that it doesn't
relay, right? ;-))
"Mark Thomas" <[EMAIL PROTECTED]> wrote:
>Thanks Chris, I did a cut and paste from the Living with Qmail document,
>the "Bang" wasn't there.
That's a typo. I'll fix it ASAP. In the meantime, add the bang.
>This appears to be on inbound mail, rights problems would have to be with
>the daemon running the inbound mail process? Can you assign rights to a
>daemon? Just for my curiosity, what is he a part of "user,group,other".
I'm not sure what you're asking here.
>darkstar:/var/qmail/bin# ls -Falc qmail-smtpd-wrapper
>-rwxr-xr-x 1 root root 163 Sep 19 22:15 qmail-smtpd-wrapper*
That's fine.
So, after adding the bang to qmail-smtpd-wrapper, what's your status?
-Dave
I;m sorry, I failed to answer one of your questions.
The remmed line. Nothing was remmed out at that point. I should have
removed the line before posting. I had remmed the line about ulimit,
because I was getting "502 unimplemented (#5.5.1)" when performing a
telnet to 127.0.0.1 25 to test the mail server on port 25. It was a long
shot, but I thought I would take it out temporarily and try it to see if it was
causing the problem. It was added to the file per the document
instructions also, and the errors were related to this file.
Well, I found out late last night/early this morning, that I did have inbound
mail working also, it was just that I was using 'mail' that evidently was
looking in a different subdir (I think "/home/mcthomas/mbox) and the new
inbound mail was sitting in (/home/mcthomas/Mailbox). Of course I found
this out after I had quit using the LWQ document and went back to the
INSTALL document, and then nothing worked. I found the
/var/adm/messages file with all of the previous mail that was inbound
also. Oh well, I'm going to "Reload again and Retry" damn, that sounds like
NT.
Sendmail came on my system by default (Slackware 3.6). The INSTALL
document said to use some other mail system rather than 'mail' like 'mailx'
but the symlink pointed to the same file. I was doomed anyway.
Qmail must not have its own mail client.?
I know this is not that complicated of an install, I just have to compile my
own instructions/fixes from both of the documents to get it to work.
How did you guys get it installed?
MarkT.
>>> Chris Johnson <[EMAIL PROTECTED]> 09/20/99 06:37am >>>
On Sun, Sep 19, 1999 at 10:46:11PM -0500, Mark Thomas wrote:
> 937728523.256241 tcpserver: warning: dropping connection, unable to
run
> /var/qmail/bin/qmail-smtpd-wrapper: access denied
> 937728523.256449 tcpserver: end 16854 status 28416
> 937728523.256503 tcpserver: status: 0/40
>
> This is the /var/qmail/bin/qmail-smtpd-wrapper
> #/bin/bash
The line above needs to be:
#!/bin/bash
And make sure that qmail-smtpd-wrapper is executable.
> # remmed the next line out due to errors.
> ***********************MCT**********************
What's the above line? It needs to be commented out.
> ulimit -d 1024
> exec /var/qmail/bin/qmail-smtpd $ {1+"$@"}
Chris
Mark Thomas <[EMAIL PROTECTED]> wrote:
>I;m sorry, I failed to answer one of your questions.
>The remmed line. Nothing was remmed out at that point. I should have
>removed the line before posting. I had remmed the line about ulimit,
>because I was getting "502 unimplemented (#5.5.1)" when performing a
>telnet to 127.0.0.1 25 to test the mail server on port 25.
Hmm, that "502 unimplemented (#5.5.1)" message came from qmail-smtpd
when you entered and unrecognized command. So your SMTP service was
working fine.
>Well, I found out late last night/early this morning, that I did have inbound
>mail working also, it was just that I was using 'mail' that evidently was
>looking in a different subdir (I think "/home/mcthomas/mbox) and the new
>inbound mail was sitting in (/home/mcthomas/Mailbox).
Did you look at /home/mcthomas/Mailbox with ls and more and see
the messages there? Or did you expect the mail command to find your
mailbox? As you've learned the hard way, the mail command has to be
told where to look.
>Of course I found
>this out after I had quit using the LWQ document and went back to the
>INSTALL document, and then nothing worked. I found the
>/var/adm/messages file with all of the previous mail that was inbound
>also. Oh well, I'm going to "Reload again and Retry" damn, that sounds like
>NT.
So everything you set up using LWQ worked? Your only problem was not
telling your mail reader where your mailbox was?
>Sendmail came on my system by default (Slackware 3.6). The INSTALL
>document said to use some other mail system rather than 'mail' like 'mailx'
>but the symlink pointed to the same file. I was doomed anyway.
>Qmail must not have its own mail client.?
No, qmail doesn't have its own mail client. It's an MTA, not an
MUA. The standard MUA's work fine with qmail.
>I know this is not that complicated of an install, I just have to compile my
>own instructions/fixes from both of the documents to get it to work.
>How did you guys get it installed?
I used the INSTALL directions, but, then, I'm an experienced system
administrator.
You say you need to compile your own instructions/fixes to get it to
work. I'd be happy to work with you to incorporate any changes
necessary into LWQ.
-Dave
Well, dad, I hate it when your right! You sound like a man who has much
patience.
Ok, we got to tarball a greenhorn today ! I have to admit, I earned this
one!
You guys have to understand, I'm very new to Linux, but not to the game. I
feel like a hungry fella standing at a McDonalds in another country with
both hands behind my back and I can't speak the language. I'm hungry, but
I'm still having Funnnnnnn!
---)))A couple of comments below:
-----Original Message-----
From: Dave Sill [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 20, 1999 11:37 AM
To: [EMAIL PROTECTED]
Subject: Re: qmail-smtpd-wrapper error. -Reply
Mark Thomas <[EMAIL PROTECTED]> wrote:
>I;m sorry, I failed to answer one of your questions.
>The remmed line. Nothing was remmed out at that point. I should have
>removed the line before posting. I had remmed the line about ulimit,
>because I was getting "502 unimplemented (#5.5.1)" when performing a
>telnet to 127.0.0.1 25 to test the mail server on port 25.
Hmm, that "502 unimplemented (#5.5.1)" message came from qmail-smtpd
when you entered and unrecognized command. So your SMTP service was
working fine.
----))) I thought it was going to tell me "helo dude"! I usually try to
refrain from ----))) getting too friendly with a computer. Until,it makes
me a cup of coffee, ----))) I'll just have to command /parameter it to
death.
>Well, I found out late last night/early this morning, that I did have
inbound
>mail working also, it was just that I was using 'mail' that evidently was
>looking in a different subdir (I think "/home/mcthomas/mbox) and the new
>inbound mail was sitting in (/home/mcthomas/Mailbox).
Did you look at /home/mcthomas/Mailbox with ls and more and see
the messages there? Or did you expect the mail command to find your
mailbox? As you've learned the hard way, the mail command has to be
told where to look.
----))))) I have to admit, I was a bit confused with the Qmail being of
Mbox
----)))))format, with Mailbox name and ./Mailbox default delivery shown as
----))))) ~user/Mailbox. It must be a Unix/Linux thing ~user/Mailbox to
mean
----))))) wherever your home user directory is/Mailbox. I'll have to admit,
I did
----))))) look for it, I did see it, but I expected it to be like a
queue/subdir ----))))) insead of a file full of messages. But, now, I dream
about it! <g>
>Of course I found
>this out after I had quit using the LWQ document and went back to the
>INSTALL document, and then nothing worked. I found the
>/var/adm/messages file with all of the previous mail that was inbound
>also. Oh well, I'm going to "Reload again and Retry" damn, that sounds like
>NT.
So everything you set up using LWQ worked? Your only problem was not
telling your mail reader where your mailbox was?
----))) Yep, and the bad thing about it (as I wipe the puppy prints from my
----))) forehead), I did do a "set", and saw where "mail" was pointing. I
couldn't ----))) find an Autoexec.bat to fix, and I forgot to go back and
find/fix it later.
>Sendmail came on my system by default (Slackware 3.6). The INSTALL
>document said to use some other mail system rather than 'mail' like 'mailx'
>but the symlink pointed to the same file. I was doomed anyway.
>Qmail must not have its own mail client.?
No, qmail doesn't have its own mail client. It's an MTA, not an
MUA. The standard MUA's work fine with qmail.
---))) Figured this out after I broke everything!
>I know this is not that complicated of an install, I just have to compile
my
>own instructions/fixes from both of the documents to get it to work.
>How did you guys get it installed?
I used the INSTALL directions, but, then, I'm an experienced system
administrator.
-----)))) Ouch!, Well, the INSTALL document looked alot different after
going
-----)))) through your LWQ. I felt like I could give it a run for the money.
You say you need to compile your own instructions/fixes to get it to
work. I'd be happy to work with you to incorporate any changes
necessary into LWQ.
-----)))) Thanks, I'll be happy to add comments that I would feel would
make LWQ -----)))) more newbie proof.
-----)))) I'll take another shot at it in a nite or two, Until then, stay
tuned for -----)))) part deux.. I think I'll have a beer!
Thanks to everyone for the support! I dare not say "Uncle"!! <G>
MarkT.
Greg Owen <[EMAIL PROTECTED]> writes on 19 September 1999 at 09:18:55 -0400
> But before I go, in response to Racer X:
>
> >> the more i think about this, the more i think that
> >> fallback MX records aren't really necessary anymore.
>
> There are several reasons I think they are still useful:
>
> 1) Redundancy. All machines die at some time or other. I'd rather
> not have the added pressure of knowing that mail will start bouncing if it
> isn't fixed in X amount of time while I'm trying to fix it.
>
> 2) Maintenance. You can take your mail server down for maintenance
> and not worry about where the mail sits in the meantime - I'd rather it sit
> and wait on my server than on someone elses!
>
> 3) Upgrades. You can test upgrades on a fallback MX before moving
> them on up.
This is amusing to me; you're both essentially saying that you trust
your *own* servers more than you trust other people's servers, so it's
better for the mail to do its waiting on *your* servers.
If all sysadmins were like that (and good enough to make it a
*reasonable* preference), we wouldn't have a lot of these discussions
about misconfigured systems :-) .
--
David Dyer-Bennet ***NOTE ADDRESS CHANGES*** [EMAIL PROTECTED]
http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon
http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms
Join the 20th century before it's too late!
David Dyer-Bennet wrote:
> Greg Owen <[EMAIL PROTECTED]> writes on 19 September 1999 at 09:18:55 -0400
>
> > But before I go, in response to Racer X:
> >
> > >> the more i think about this, the more i think that
> > >> fallback MX records aren't really necessary anymore.
> >
> > There are several reasons I think they are still useful:
> >
> > 1) Redundancy. All machines die at some time or other. I'd rather
> > not have the added pressure of knowing that mail will start bouncing if it
> > isn't fixed in X amount of time while I'm trying to fix it.
> >
> > 2) Maintenance. You can take your mail server down for maintenance
> > and not worry about where the mail sits in the meantime - I'd rather it sit
> > and wait on my server than on someone elses!
> >
> > 3) Upgrades. You can test upgrades on a fallback MX before moving
> > them on up.
>
> This is amusing to me; you're both essentially saying that you trust
> your *own* servers more than you trust other people's servers, so it's
> better for the mail to do its waiting on *your* servers.
Yes we do, but, the reason I (I cannot speak for others) prefer the mail to
be queued to my secondary is that I know it will come over to the primary a
whole lot faster. The secondary can do retries every minute and is connected
to the primary at 100 mbps ethernet. And that's only my top reason. There
are also lesser reasons (including that, yes, I do trust my server more than
some arbitrary server I have no idea about). I can also up the expiration
time on my secondary so I give myself more time to correct the primary.
And how do you know that the secondary works from the same MX list as the
sender has? I may well have the real primary unlisted at all. There may
be a perfectly good reason to do that. It could be on a private LAN, for
one example. Or it might be on a slow link where I want to serialize the
mail delivery. The apparent primary would then be in the public MX list as
primary because it is the faster machine, and the apparent secondary being
slower, gets listed next, even though it can deliver to the real primary
without the apparent primary being functional for SMTP.
Sure, I could list the public MX machines as equals in the list. If they
were indeed equal, that might be a good idea. Or I could list one machine
with multiple A records for each separate real machine (some people do have
a problem with this in their talk, but it has worked for me before). But
if the machines are unequal, I would list them unequally.
--
Phil Howard | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
phil | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
at | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
ipal | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
dot | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
net | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
I have someone trying to send an email message to someone on my
mail server. The server smtpd logs show the message coming in,
but I'm getting an error at the end of the message. The message
from the mail server in question does not end with a "." which I
know it needs according to the RFC's...
What I get is the following:
37605376.514440 1048 < Benedict J. Waters
37605376.514577 1048 <
937605376.514695 1048 < -----Original+
37605376.515336 1048 < Message-----
937605376.515481 1048 < From: Joe Albanese [SMTP:joea@ohioonli+
937605376.516434 tcpserver: end 1048 status 256
937605376.516602 tcpserver: status: 0/40
The mail server in question is a Netware Border Manager Firewall.
I am still waiting to hear back from the person who runs the
firewall in question about the specifics of what it is. Does
anyone know of any way though to get qmail to ignore the error
code and still send the mail through? I know that Sendmail does
handles this okay, so I have to find some kind of solution.
Thank you for any help in solving this problem.
-Eric Davis
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
>I have someone trying to send an email message to someone on my
>mail server. The server smtpd logs show the message coming in,
>but I'm getting an error at the end of the message.
What error is that?
>The message from the mail server in question does not end with a "."
>which I know it needs according to the RFC's...
Well, yeah, but it's not just another picayune RFC requirement. The
"." indicates the end of the message. Without it, the receiving system
can't tell if it's received the entire message, and it won't see any
more SMTP commands from the client.
-Dave
At 12:37 AM 9/21/99 -0700, you wrote:
>
>There was a problem logging onto your mail server. Your Password was
>rejected. Account: 'grow.sd27.bc.ca', Server: 'grow.sd27.bc.ca', Protocol:
>POP3, Server Response: '-ERR this user has no $HOME/Maildir', Port: 110,
>Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
>
Read the error message
>-ERR this user has no $HOME/Maildir'
Pretty descriptive error in MHO
If you really need help su as the user and run /var/qmail/bin/maildirmake
then retry
Tim Hunter <[EMAIL PROTECTED]> wrote on Mon, 20 Sep 1999:
> >There was a problem logging onto your mail server. Your Password was
> >rejected. Account: 'grow.sd27.bc.ca', Server: 'grow.sd27.bc.ca', Protocol:
> >POP3, Server Response: '-ERR this user has no $HOME/Maildir', Port: 110,
> >Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
Do I read the Outlook error correctly, "Account: 'grow.sd27.bc.ca'",
is that the same as "user"? If so, then it's unlikely that the server
grow.sd27.bc.ca has a user called grow.sd27.bc.ca -- change that the
desired username in Outlook settings.
Mikko
--
// Mikko H�nninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
"What I need is a list of specific unknown problems we will encounter."
Quoting Mikko H�nninen ([EMAIL PROTECTED]):
> Tim Hunter <[EMAIL PROTECTED]> wrote on Mon, 20 Sep 1999:
> > >There was a problem logging onto your mail server. Your Password was
> > >rejected. Account: 'grow.sd27.bc.ca', Server: 'grow.sd27.bc.ca', Protocol:
> > >POP3, Server Response: '-ERR this user has no $HOME/Maildir', Port: 110,
> > >Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
>
> Do I read the Outlook error correctly, "Account: 'grow.sd27.bc.ca'",
> is that the same as "user"? If so, then it's unlikely that the server
> grow.sd27.bc.ca has a user called grow.sd27.bc.ca -- change that the
> desired username in Outlook settings.
My installation of qmail-pop3d says "-ERR authorization failed" when I
supply an invalid username. Reading the above Outlook error.. well
it's wierd. Wouldn't surprise me if Outlook was just goofing up its
error output!
Aaron
> > >rejected. Account: 'grow.sd27.bc.ca', Server: 'grow.sd27.bc.ca',
Protocol:
> > >POP3, Server Response: '-ERR this user has no $HOME/Maildir', Port:
110,
> > >Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
>
> Do I read the Outlook error correctly, "Account: 'grow.sd27.bc.ca'",
> is that the same as "user"? If so, then it's unlikely that the server
> grow.sd27.bc.ca has a user called grow.sd27.bc.ca -- change that the
> desired username in Outlook settings.
That is just an "easy to remember name" outlook assigned to the account. I
could have called it "myaccount" or "growmail" or whatever. ..
Lets eliminate the *slight* possibly that Outlook could flub up the error
message and just telnet grow.sd27.bc.ca 110 so that we can test properly.
At 08:56 AM 9/20/99 -0700, you wrote:
>Quoting Mikko H�nninen ([EMAIL PROTECTED]):
> > Tim Hunter <[EMAIL PROTECTED]> wrote on Mon, 20 Sep 1999:
> > > >There was a problem logging onto your mail server. Your Password was
> > > >rejected. Account: 'grow.sd27.bc.ca', Server: 'grow.sd27.bc.ca',
> Protocol:
> > > >POP3, Server Response: '-ERR this user has no $HOME/Maildir', Port:
> 110,
> > > >Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
> >
> > Do I read the Outlook error correctly, "Account: 'grow.sd27.bc.ca'",
> > is that the same as "user"? If so, then it's unlikely that the server
> > grow.sd27.bc.ca has a user called grow.sd27.bc.ca -- change that the
> > desired username in Outlook settings.
>
>My installation of qmail-pop3d says "-ERR authorization failed" when I
>supply an invalid username. Reading the above Outlook error.. well
>it's wierd. Wouldn't surprise me if Outlook was just goofing up its
>error output!
>
>Aaron
What error do you get when you try to telnet from the box to the email
server on 110 using that account name?
Greg
----- Original Message -----
From: Mikko H�nninen <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 20, 1999 3:08 PM
Subject: Re: Having trouble with pop
> Tim Hunter <[EMAIL PROTECTED]> wrote on Mon, 20 Sep 1999:
> > >There was a problem logging onto your mail server. Your Password was
> > >rejected. Account: 'grow.sd27.bc.ca', Server: 'grow.sd27.bc.ca',
Protocol:
> > >POP3, Server Response: '-ERR this user has no $HOME/Maildir', Port:
110,
> > >Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
>
> Do I read the Outlook error correctly, "Account: 'grow.sd27.bc.ca'",
> is that the same as "user"? If so, then it's unlikely that the server
> grow.sd27.bc.ca has a user called grow.sd27.bc.ca -- change that the
> desired username in Outlook settings.
>
>
> Mikko
> --
> // Mikko H�nninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
> // The Corrs list maintainer // net.freak // DALnet IRC operator /
> // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
> "What I need is a list of specific unknown problems we will encounter."
>
>Lets eliminate the *slight* possibly that Outlook could flub up the error
> message and just telnet grow.sd27.bc.ca 110 so that we can test properly.
Ok, I got the same message from telnet. But why does mail make it into the
Maildir/new directory from local and from other mail servers? I've done the
assign file thing and ran the qmail-newu on it. Is there some way to ask
qmail or whatever who 'it' thinks are valid pop users, (besides looking at
passwd & group). I keep thinking I did something wrong in this regard...
uh, let's use our heads for a minute here and not waste time. outlook
returned the exact error message:
-ERR this user has no $HOME/Maildir
<rant>
are you really saying that outlook somehow changed this error message? i
realize a lot of people on this list hate microsoft software, but let's at
least give them the benefit of the doubt that when they say "server
response" and an error message, it's really coming from the server.
</rant>
if you'll look at qmail-pop3d.c, line 65, you'll see the same thing. you
can see why these errors are raised if you look at the end of
qmail-pop3d.c - either the program is passed no arguments (incorrect usage)
or the program can't change to the user's directory (does not exist or
permissions are incorrect).
shag
=====
Judd Bourgeois | CNM Network +1 (805) 520-7170
Software Architect | 1900 Los Angeles Avenue, 2nd Floor
[EMAIL PROTECTED] | Simi Valley, CA 93065
Quidquid latine dictum sit, altum viditur.
----- Original Message -----
From: Tim Hunter <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Mon 20 Sep 1999 9.05
Subject: Re: Having trouble with pop
Lets eliminate the *slight* possibly that Outlook could flub up the error
message and just telnet grow.sd27.bc.ca 110 so that we can test properly.
At 08:56 AM 9/20/99 -0700, you wrote:
>Quoting Mikko H�nninen ([EMAIL PROTECTED]):
> > Tim Hunter <[EMAIL PROTECTED]> wrote on Mon, 20 Sep 1999:
> > > >There was a problem logging onto your mail server. Your Password was
> > > >rejected. Account: 'grow.sd27.bc.ca', Server: 'grow.sd27.bc.ca',
> Protocol:
> > > >POP3, Server Response: '-ERR this user has no $HOME/Maildir', Port:
> 110,
> > > >Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
> >
> > Do I read the Outlook error correctly, "Account: 'grow.sd27.bc.ca'",
> > is that the same as "user"? If so, then it's unlikely that the server
> > grow.sd27.bc.ca has a user called grow.sd27.bc.ca -- change that the
> > desired username in Outlook settings.
>
>My installation of qmail-pop3d says "-ERR authorization failed" when I
>supply an invalid username. Reading the above Outlook error.. well
>it's wierd. Wouldn't surprise me if Outlook was just goofing up its
>error output!
>
>Aaron
Not to side track this discussion, but there are some communications
difficulties which can cause a Microsoft agent to give you a strange result
(error message).
Here is a simple inconsistency in the error reporting of the two
Using Outlook express, this is the return error. However, if you were to use
a a telent, the error would return -ERR; $HOME/maildir.
This is against one of our test domains.-
Your server has unexpectedly terminated the connection. Possible causes for
this include server problems, network problems, or a long period of
inactivity. Account: 'poormans.net', Server: 'poormans.net', Protocol: POP3,
Port: 110, Secure(SSL): No, Error Number: 0x800CCC0F
Telnet seems to be the only consistent way to initiate the debugging
process. Or should I say the lowest level at which to start.
Greg
----- Original Message -----
From: Racer X <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; Tim Hunter <[EMAIL PROTECTED]>
Sent: Monday, September 20, 1999 7:06 PM
Subject: Re: Having trouble with pop
> uh, let's use our heads for a minute here and not waste time. outlook
> returned the exact error message:
> -ERR this user has no $HOME/Maildir
>
> <rant>
> are you really saying that outlook somehow changed this error message? i
> realize a lot of people on this list hate microsoft software, but let's at
> least give them the benefit of the doubt that when they say "server
> response" and an error message, it's really coming from the server.
> </rant>
>
> if you'll look at qmail-pop3d.c, line 65, you'll see the same thing. you
> can see why these errors are raised if you look at the end of
> qmail-pop3d.c - either the program is passed no arguments (incorrect
usage)
> or the program can't change to the user's directory (does not exist or
> permissions are incorrect).
>
> shag
> =====
> Judd Bourgeois | CNM Network +1 (805) 520-7170
> Software Architect | 1900 Los Angeles Avenue, 2nd Floor
> [EMAIL PROTECTED] | Simi Valley, CA 93065
>
> Quidquid latine dictum sit, altum viditur.
>
> ----- Original Message -----
> From: Tim Hunter <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Mon 20 Sep 1999 9.05
> Subject: Re: Having trouble with pop
>
>
> Lets eliminate the *slight* possibly that Outlook could flub up the error
> message and just telnet grow.sd27.bc.ca 110 so that we can test properly.
>
>
> At 08:56 AM 9/20/99 -0700, you wrote:
> >Quoting Mikko H�nninen ([EMAIL PROTECTED]):
> > > Tim Hunter <[EMAIL PROTECTED]> wrote on Mon, 20 Sep 1999:
> > > > >There was a problem logging onto your mail server. Your Password
was
> > > > >rejected. Account: 'grow.sd27.bc.ca', Server: 'grow.sd27.bc.ca',
> > Protocol:
> > > > >POP3, Server Response: '-ERR this user has no $HOME/Maildir', Port:
> > 110,
> > > > >Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC92
> > >
> > > Do I read the Outlook error correctly, "Account: 'grow.sd27.bc.ca'",
> > > is that the same as "user"? If so, then it's unlikely that the server
> > > grow.sd27.bc.ca has a user called grow.sd27.bc.ca -- change that the
> > > desired username in Outlook settings.
> >
> >My installation of qmail-pop3d says "-ERR authorization failed" when I
> >supply an invalid username. Reading the above Outlook error.. well
> >it's wierd. Wouldn't surprise me if Outlook was just goofing up its
> >error output!
> >
> >Aaron
>
>
>
>
>
>I have just installed RedHat 6.0 onto my PC. In the previous incarnation I had
>5.2 running with fetchmail, diald and qmail 1.03. I now find that when
>fetchmail tries to inject the message into the SMPT servier it gets connection
>refused.
You probably have sendmail installed. It is also probably possible
that your semdmail links in /usr/lib and /usr/sbin got overwritten.
Mate
Ta Mate,
Naw, first things I checked ...
..> ls -l /usr/lib | grep qmail
lrwxrwxrwx 1 root root 23 Sep 8 15:43 sendmail -> /var/qmail/bin/sendmail
..> ls -l /usr/sbin | grep qmail
lrwxrwxrwx 1 root root 23 Sep 8 15:43 sendmail -> /var/qmail/bin/sendmail
..> ps aux | grep sendmail
r.george 5026 0.0 0.6 1148 400 pts/2 S 19:56 0:00 grep sendmail
Any other suggestions?
Regards, Richard
[EMAIL PROTECTED] wrote:
>
> >
> >I have just installed RedHat 6.0 onto my PC. In the previous incarnation I had
> >5.2 running with fetchmail, diald and qmail 1.03. I now find that when
> >fetchmail tries to inject the message into the SMPT servier it gets connection
> >refused.
>
> You probably have sendmail installed. It is also probably possible
> that your semdmail links in /usr/lib and /usr/sbin got overwritten.
>
> Mate
--
Richard George Carthaginem esse Delendam [EMAIL PROTECTED]
Tel home : +49 7304 921707 fax home : +49 7304 919721
Richard George <[EMAIL PROTECTED]> wrote:
>I tried to telnet but get the following
>
>r.george> telnet george 25
>Trying 193.197.64.64...
>Connected to george.ul.bawue.de.
>Escape character is '^]'.
>Connection closed by foreign host.
>r.george>
>
>I start qmail-smtp with the following (1) line in the inetd.conf
>
>smtp stream tcp nowait qmaild /usr/sbin/tcpd /var/qmail/bin/tcp-env tcp-env
>/var/qmail/bin/qmail-smtpd
>
>Anyone offer any help?
Do a "killall -HUP inetd" and check your logs for message from
inetd. Make sure that:
/usr/sbin/tcpd
/var/qmail/bin/tcp-env
/var/qmail/bin/qmail-smtpd
are still there, intact, executable, and working properly. Verify that
smtp is still defined as port 25 in /etc/services.
-Dave
Ta Mate,
Naw, first things I checked ...
..> ls -l /usr/lib | grep qmail
lrwxrwxrwx 1 root root 23 Sep 8 15:43 sendmail -> /var/qmail/bin/sendmail
..> ls -l /usr/sbin | grep qmail
lrwxrwxrwx 1 root root 23 Sep 8 15:43 sendmail -> /var/qmail/bin/sendmail
..> ps aux | grep sendmail
r.george 5026 0.0 0.6 1148 400 pts/2 S 19:56 0:00 grep sendmail
Any other suggestions?
This line does not agree with the line given in the FAQ:
smtp stream tcp nowait qmaild /usr/sbin/tcpd /var/qmail/bin/tcp-env tcp-env
/var/qmail/bin/qmail-smtpd
Mate
Hi everyone,
I'm having problems with the popserver, when I send a message with 3megs or
so it downloads sometimes and sometimes it gets stuck in the middle of the
message. What should I do to fix it?. Is the pop server reliable to serve
big messages?
Many thanks!
Greetz,
Martin Paulucci
SysAdmin
Sintesoft.Net
[EMAIL PROTECTED]
"Olivier M." <[EMAIL PROTECTED]> wrote:
>Sending the mail outside isn't a problem (relaying for an IP class).
>But how can I tell the qmail server that the NT box is currently
>online and waiting for an smtp feed ? I guess I need a kind of trigger
>that will start a maildirsmtp command. Is it the right way ?
Dan's serialmail package includes maildir2smtp, which can be
configured into something he calls AutoTURN, which should do what
you're looking for.
See:
http://Web.InfoAve.Net/~dsill/lwq.html#serialmail
-Dave
On Mon, Sep 20, 1999 at 11:25:13AM -0400, Dave Sill wrote:
> >Sending the mail outside isn't a problem (relaying for an IP class).
> >But how can I tell the qmail server that the NT box is currently
> >online and waiting for an smtp feed ? I guess I need a kind of trigger
> >that will start a maildirsmtp command. Is it the right way ?
>
> Dan's serialmail package includes maildir2smtp, which can be
> configured into something he calls AutoTURN, which should do what
> you're looking for.
Thanks, I do know what maildir2smtp is, the problem is not here :
it's to know _when_ to launch the command, because the NT server
is only online once an hour.
I'll look at Autoturn... thanks for the hints!
Olivier
Hello,
I hope I'm not making late and useless interference, but I have also
Slackware Linux (4.0.0 kernel 2.2.6) running and installed qmail 1.03,
ucspi-tcp 0.84 and daemontools 0.61.
The first thing I want to say is that if you (Mark) also intend to use
daemontools 0.61 the startup/shutdown script in LWQ is no longer valid.
I'm using the following approach:
1. The rc.M file in /etc/rc.d looks as follows (just the part concerning
qmail):
# Commented out the sendmail lines
# Start the sendmail daemon:
# if [ -x /usr/sbin/sendmail ]; then
# echo "Starting sendmail daemon (/usr/sbin/sendmail -bd -q15m)..."
# /usr/sbin/sendmail -bd -q15m
# fi
#
# Start the qmail system
#
if [ -x /etc/rc.d/rc.qmail ]; then
echo "Starting qmail ..."
. /etc/rc.d/rc.qmail
fi
2. rc.qmail is a link to /var/qmail/rc
3. /var/qmail/rc looks as follows
#!/bin/sh
cd /var/qmail/services
/usr/bin/env - PATH="/usr/local/bin:/var/qmail/bin" ./svscan &
4. Note that I've created a directory /var/qmail/services. There I have a
copy of svscan. I had to cd to /var/qmail/services and start svscan there
because it didn't work otherwise.
5. /var/qmail/services contains two subdirectories: startup and smtpd both
containing a script run and a subdirectory log which again contains a
script run (for details please look at the documentation of daemontools
0.61 at ftp://koobera.math.uic.edu/www/daemontols.html - I got on this
site from www.qmail.org)
6. As an example I give here the run scripts in:
/var/qmail/services/startup
#!/bin/sh
# Using qmail-local to deliver messages to ~/Mailbox by default.
exec /usr/bin/env - PATH="/var/qmail/bin" \
qmail-start ./Mailbox
and /var/qmail/services/startup/log
#!/bin/sh
# Using multilog to log messages from qmail-send in /var/qmail/log/qmail
exec /usr/bin/env - PATH="/usr/local/bin" \
multilog t /var/qmail/log/qmail '-*'
7. Note that /var/qmail/services/startup and /var/qmail/services/smtpd
have the sticky bit set.
NOTE: I'm not sure that this is a really good way to setup qmail but till
now it worked and I rebooted the system two or three times to see if
everything works after and it does.
Best regards,
Serban
"Serban Udrea" <[EMAIL PROTECTED]> wrote:
>The first thing I want to say is that if you (Mark) also intend to use
>daemontools 0.61 the startup/shutdown script in LWQ is no longer valid.
Correct. I've given it some thought, and I can't justify the
additional complexity required by daemontools 0.61. LWQ now contains a
message to that effect:
Note: Although the latest version of daemontools is 0.61, 0.53 is
still available and adequate for our purposes. The user interface
changed substantially in 0.60, and these instructions will only work
right with 0.53.
Until Dan stops distributing 0.53, I don't see a pressing need to
switch LWQ to 0.61.
-Dave
Thanks a million.
I went back in and hosebagged my install, but I am going to redo it tonight.
I'm sure this is some of what I was missing. I did load the ucspi-tcp and
daemontools.
Markt.
>>> "Serban Udrea" <[EMAIL PROTECTED]> 09/20/99 01:34pm >>>
Hello,
I hope I'm not making late and useless interference, but I have also
Slackware Linux (4.0.0 kernel 2.2.6) running and installed qmail 1.03,
ucspi-tcp 0.84 and daemontools 0.61.
The first thing I want to say is that if you (Mark) also intend to use
daemontools 0.61 the startup/shutdown script in LWQ is no longer valid.
I'm using the following approach:
1. The rc.M file in /etc/rc.d looks as follows (just the part concerning
qmail):
# Commented out the sendmail lines
# Start the sendmail daemon:
# if [ -x /usr/sbin/sendmail ]; then
# echo "Starting sendmail daemon (/usr/sbin/sendmail -bd -q15m)..."
# /usr/sbin/sendmail -bd -q15m
# fi
#
# Start the qmail system
#
if [ -x /etc/rc.d/rc.qmail ]; then
echo "Starting qmail ..."
. /etc/rc.d/rc.qmail
fi
2. rc.qmail is a link to /var/qmail/rc
3. /var/qmail/rc looks as follows
#!/bin/sh
cd /var/qmail/services
/usr/bin/env - PATH="/usr/local/bin:/var/qmail/bin" ./svscan &
4. Note that I've created a directory /var/qmail/services. There I have a
copy of svscan. I had to cd to /var/qmail/services and start svscan there
because it didn't work otherwise.
5. /var/qmail/services contains two subdirectories: startup and smtpd
both
containing a script run and a subdirectory log which again contains a
script run (for details please look at the documentation of daemontools
0.61 at ftp://koobera.math.uic.edu/www/daemontols.html - I got on this
site from www.qmail.org)
6. As an example I give here the run scripts in:
/var/qmail/services/startup
#!/bin/sh
# Using qmail-local to deliver messages to ~/Mailbox by default.
exec /usr/bin/env - PATH="/var/qmail/bin" \
qmail-start ./Mailbox
and /var/qmail/services/startup/log
#!/bin/sh
# Using multilog to log messages from qmail-send in /var/qmail/log/qmail
exec /usr/bin/env - PATH="/usr/local/bin" \
multilog t /var/qmail/log/qmail '-*'
7. Note that /var/qmail/services/startup and /var/qmail/services/smtpd
have the sticky bit set.
NOTE: I'm not sure that this is a really good way to setup qmail but till
now it worked and I rebooted the system two or three times to see if
everything works after and it does.
Best regards,
Serban
"Warren 'Llama' Ernst" <[EMAIL PROTECTED]> wrote:
>OK, after following the LWQ installation guide, it seems like some of the
>things that should be executable, aren't.
If that's the case, you probably skipped some steps. If not, I'd
really like to hear more details so I can fix the problem.
>So I'm thinking of either
>following the INSTALL document instead, or maybe even using one of the RPMs
>out there (I'm using RedHat 6.0.). However, I assume I should get rid of all
>the stuff that the first install put around.
rm -rf /var/qmail /usr/local/src/qmail /etc/rc.d/*/*qmail*
ought to do it, but, again, I'd much rather help you work through the
LWQ instructions.
-Dave
Quoting sean ([EMAIL PROTECTED]):
> Hello,
>
> I use qmail and have noticed that the vast majority of spam that comes
> through is from <>
Hmm, that's funny, I've noticed that the vast majority of spam uses
valid, but forged, return addresses. In my experience, anyway.
> Is there an a means by which I can reject mail from <> or is there any
> problems associated with this?
Others have pointed out why this is a bad thing.. :)
Aaron
Hello,
is there anybody who has Qmail working together with HP Openmail 6.0 for
Linux ? Please tell me if it works and how it works.
Thank you
best regards
Stephan Hadan
Hermann A. Trautz Stephan Hadan
Schmuckwarenfabrik GmbH EDV-Abteilung
Herrenstrasse 9-17 Tel: +49 7231 77354
D-75180 Pforzheim Fax: +49 7231 77384
http://www.hat.de [EMAIL PROTECTED]
-------------------------------------------------------------------------
This email server is running an evaluation copy of the MailShield anti-
spam software. Please contact your email administrator if you have any
questions about this message. MailShield product info: www.mailshield.com
On Sun, Sep 19, 1999 at 12:56:45AM +0200, LRiva wrote:
Hi Lorenzo,
> I have two rather stupid questions as I'm a newbie with Qmail.
> I've just installed Qmail and set it to use maildir-like mailboxes.
> The question is:
> Mutt ask me to specify a file to use as spool mailbox: how should I set this ?
I also use Maildir and have had to put the following lines in my
/etc/Muttrc file
set folder="~/Maildir"
set mbox="~/Maildir"
set mbox_type="Maildir"
set sendmail="/usr/lib/sendmail" #this should though not be nessary now.
set spoolfile="~/Maildir"
> What are the function of the /tmp and /cur maildir subdirectories ?
Maildir/new/ is where new mail goes into
Maildir/cur/ is where readmail goes into
Maildir/tmp/ is possibly for Mutt's temporary files if any.
> Excuse me if they're RTFM, but I didn't found the answers in the manuals...
have a try and see if if works.
I did for me.
Jacob
How can I spawn this daemon using tcpserver? I'm using qmail-smtpd this
way but I'd like to switch imapd from inetd to tcpserver also, as it
often crashes under heavy loads.
Thanx in advance for your help!
Piotr Wanat
--
mailto:[EMAIL PROTECTED] | UIN:15871058
Piotr Wanat <[EMAIL PROTECTED]> wrote:
> How can I spawn this daemon using tcpserver? I'm using qmail-smtpd this
>way but I'd like to switch imapd from inetd to tcpserver also, as it
>often crashes under heavy loads.
Show us your inetd.conf entry, and we'll tell you how to run it under
tcpserver.
-Dave
Dave Sill wrote:
> Show us your inetd.conf entry, and we'll tell you how to run it under
> tcpserver.
Sure! Here we go:
imap stream tcp nowait root /usr/sbin/tcpd imapd
BTW: My second question is: I installed dot-forward and dotqmail2alias,
so aliases and forwarding worked fine when smtpd was run from inetd. But
after switching to tcpserver they don't anymore. Any idea?
Best regards...
Piotr Wanat
--
mailto:[EMAIL PROTECTED] | UIN:15871058
Piotr Wanat <[EMAIL PROTECTED]> wrote:
>Dave Sill wrote:
>
>> Show us your inetd.conf entry, and we'll tell you how to run it under
>> tcpserver.
>
> Sure! Here we go:
>imap stream tcp nowait root /usr/sbin/tcpd imapd
tcpserver -v -R 0 imap /path/to/imapd 2>&1 | \
/var/qmail/bin/splogger imapd &
If you're using host-based access control, you'll have to add:
-x/etc/tcp.imap.cdb
or something similar. See the tcpserver man page for details.
>BTW: My second question is: I installed dot-forward and dotqmail2alias,
>so aliases and forwarding worked fine when smtpd was run from inetd. But
>after switching to tcpserver they don't anymore. Any idea?
What did your old inetd entry for smtp look like? And what is
dotqmail2alias?
-Dave
Dave Sill wrote:
> tcpserver -v -R 0 imap /path/to/imapd 2>&1 | \
> /var/qmail/bin/splogger imapd &
Thanks!
> What did your old inetd entry for smtp look like? And what is
> dotqmail2alias?
smtp stream tcp nowait qmaild /var/qmail/bin/qmail-smtpd \
qmail-smtpd /var/qmail/bin/qmail-smtpd
dotqmail2alias is proggie that uses the .qmail aliases to create an
aliasesfile suitable for use with fastforward
Piotr Wanat
--
mailto:[EMAIL PROTECTED] | UIN:15871058
Piotr Wanat <[EMAIL PROTECTED]> wrote:
>dotqmail2alias is proggie that uses the .qmail aliases to create an
>aliasesfile suitable for use with fastforward
I don't know how dotqmail2alias works, but I seriously doubt it has
anything to do with how qmail-smtpd is started.
As for dot-forward, if you're still running it from your .qmail file
and/or your qmail-start invocation, it should still be working.
-Dave
Dave Sill wrote:
> As for dot-forward, if you're still running it from your .qmail file
> and/or your qmail-start invocation, it should still be working.
Well, I'm running qmail-smtpd from another script, which uses
tcpserver. It looks this way:
#!/bin/sh
# Qmail Startup
# Source function library.
. /etc/rc.d/init.d/functions
# See how we were called.
case "$1" in
start)
echo -n "Starting: "
env - PATH="/var/qmail/bin:/usr/local/bin" \
qmail-start ./Maildir/ /usr/local/bin/accustamp \
| /usr/local/bin/setuser qmaill /usr/local/bin/cyclog /var/log/qmail
&
echo -n "qmail "
env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver 0 pop-3 /var/qmail/bin/qmail-popup ananke.comarch.pl \
/home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir &
echo -n "pop "
env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver -c 100 -H -R -u503 -g503 0 smtp \
/var/qmail/bin/qmail-smtpd 2>&1 > /dev/null &
echo "smtp"
;;
stop)
echo -n "Stopping: "
killproc qmail-send
echo -n "qmail "
killproc tcpserver
echo "smtp "
;;
restart)
$0 stop
$0 start
;;
status)
status qmail
;;
*)
echo "Usage: qmail {start|stop|restart|status}"
exit 1
esac
exit 0
But it seems it's not tuned for my pyurposes. Any idea how should I fix
it so it works with dot-forward (started previously in rc) and accepts
external smtp connections?
Thanx in advance for your help.
Piotr Wanat
--
mailto:[EMAIL PROTECTED] | UIN:15871058
Piotr Wanat <[EMAIL PROTECTED]> wrote:
> But it seems it's not tuned for my pyurposes. Any idea how should I fix
>it so it works with dot-forward (started previously in rc) and accepts
>external smtp connections?
OK, you're starting qmail-send like so:
> env - PATH="/var/qmail/bin:/usr/local/bin" \
> qmail-start ./Maildir/ /usr/local/bin/accustamp \
> | /usr/local/bin/setuser qmaill /usr/local/bin/cyclog /var/log/qmail &
Which delivers to ./Maildir/. To deliver to dot-forward and
./Maildir/, change that to:
env - PATH="/var/qmail/bin:/usr/local/bin" \
qmail-start '| dot-forward .forward
./Maildir/' /usr/local/bin/accustamp \
| /usr/local/bin/setuser qmaill /usr/local/bin/cyclog /var/log/qmail &
And you're starting qmail-smtpd with:
> env - PATH="/var/qmail/bin:/usr/local/bin" \
> tcpserver -c 100 -H -R -u503 -g503 0 smtp \
> /var/qmail/bin/qmail-smtpd 2>&1 > /dev/null &
Which doesn't restrict external SMTP connections because you're not
using the -x option to tcpserver.
-Dave
[EMAIL PROTECTED] wrote:
>Is it possible to redirect all incoming email automatically from a specific
>email account on qmail server to another email account of different domain?
Yes.
>Any additional modules required?
No.
>Is it the same as the .forward of sendmail?
No, but it's very similar. The file is called .qmail, and the syntax
for forwarding to a remote address is:
&[EMAIL PROTECTED]
>I would like to build a hierarchical email account naming scheme, e.g.
>[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], etc .... Is
>it possible to do that on qmail?
It's possible to configure qmail to accept mail for those addresses.
>How it works?
That depends upon how you set it up. For example, you could handle
john.account via a system alias by creating
/var/qmail/aliases/.qmail-john:account (note the use of the colon [:]
instead of the dot [.]). In that file, you can direct the messages to
a local user, a remote user, a file, or a program.
>Since I use POP3 client to
>retrieve mail, any conflict with this naming scheme?
If you want people to have POP accounts matching these names, that
could be problem. Most POP daemons expect users to log in with real
usernames and passwords. However, there are virtual user setups, about
which I'm blissfully ignorant, that might be able to accomodate this.
-Dave
I searched the archives for this, and saw it mention several times, but I
couldn't find a definitive answer. I'm getting:
Sep 20 13:40:09 leviathan qmail: 937852809.494540 warning: trouble injecting bounce
message, will try later
Sep 20 13:40:09 leviathan qmail: 937852809.524814 warning: trouble injecting bounce
message, will try later
Sep 20 13:40:09 leviathan qmail: 937852809.555087 warning: trouble injecting bounce
message, will try later
Sep 20 13:40:09 leviathan qmail: 937852809.583407 warning: trouble injecting bounce
message, will try later
I haven't changed anything (that I know of). The server has been up
without incident now for 196 days. I did a qmail-qread and didn't see
anything really weird. I have plenty of disk space, did an ls -laR of the
entire /var/qmail/queue directory looking for anything large and didn't
see anything. Any thoughts on this? Thanks.
--
-----------------------------------------------------------------------
Andy Walden Work Email: [EMAIL PROTECTED]
Network Administrator, Pers Email: [EMAIL PROTECTED]
MTCO Communications Phone: (800) 859-6826
"A little nonsense now and then, is relished by the wisest men."
-Willi Wonka
I'm thinking of deploying RBL to try to cut down on spam, but before I did that
I wanted to poke around and see how effective it might be. So, I gathered up
some spam messages that I had received and looked up the mailserver's ipaddr in
RBL using rbl.maps.vix.com and rbl.dorkslayers.com, and not one host was
rejected from either RBL site. Even though I could see the messages looked like
they were going trough an open relay.
How good is this whole RBL thing anyway?
- David Harris
Principal Engineer, DRH Internet Services
The DUL and RRSS are more effective, in my experience.
dul.maps.vix.com and relays.radparker.com
For info see
http://maps.vix.com/dul/
http://www.mail-abuse.org/rss/
Jim Lippard [EMAIL PROTECTED] http://www.discord.org/
Unsolicited bulk email charge: $500/message. Don't send me any.
PGP Fingerprint: 0C1F FE18 D311 1792 5EA8 43C8 7AD2 B485 DE75 841C
On Mon, 20 Sep 1999, David Harris wrote:
>
> I'm thinking of deploying RBL to try to cut down on spam, but before I did that
> I wanted to poke around and see how effective it might be. So, I gathered up
> some spam messages that I had received and looked up the mailserver's ipaddr in
> RBL using rbl.maps.vix.com and rbl.dorkslayers.com, and not one host was
> rejected from either RBL site. Even though I could see the messages looked like
> they were going trough an open relay.
>
> How good is this whole RBL thing anyway?
>
> - David Harris
> Principal Engineer, DRH Internet Services
>
>
>
On Mon, Sep 20, 1999 at 02:41:43PM -0400, David Harris wrote:
}
} I'm thinking of deploying RBL to try to cut down on spam, but before I did that
} I wanted to poke around and see how effective it might be. So, I gathered up
} some spam messages that I had received and looked up the mailserver's ipaddr in
} RBL using rbl.maps.vix.com and rbl.dorkslayers.com, and not one host was
} rejected from either RBL site. Even though I could see the messages looked like
} they were going trough an open relay.
}
} How good is this whole RBL thing anyway?
dorkslayers no longer exists, AFAIK, having transmorgriphied into
ORBS. RBL has strict criteria for inclusion, so you won't get all
that many hits from them. The more effective MAPS services are the
DUL (dial up list) and the RSS (relay spam stopper). (I used ORBS for
awhile, but they're too aggressive, so you get a lot of false
positives, and the owner(s?) started putting people in who they simply
didn't like)
Currently I'm using RBL, DUL, and RSS. It stops almost all spam
attempts to this machine, but then this is a .gov, and spammers seem
to stay away from .gov addresses.
}
} - David Harris
} Principal Engineer, DRH Internet Services
}
}
--
--------
Paul J. Schinder
NASA Goddard Space Flight Center
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
> dorkslayers no longer exists, AFAIK, having transmorgriphied into
> ORBS. RBL has strict criteria for inclusion, so you won't get all
> that many hits from them. The more effective MAPS services are the
> DUL (dial up list) and the RSS (relay spam stopper). (I used ORBS for
> awhile, but they're too aggressive, so you get a lot of false
> positives, and the owner(s?) started putting people in who they simply
> didn't like)
>
> Currently I'm using RBL, DUL, and RSS. It stops almost all spam
> attempts to this machine, but then this is a .gov, and spammers seem
> to stay away from .gov addresses.
Right now I'm querying these addresses:
rbl.maps.vix.com
dul.maps.vix.com
relays.radparker.com
I'm going to setup a little program that will query RBL for these addresses and
then simply record the SMTP conversation with hosts (using recordio) that show
up as a positive. I can then review those conversations and see if I get any
false positives and if this is worth deploying.
I'll run this for a few days and let the list know what I find.
- David Harris
Principal Engineer, DRH Internet Services
In the immortal words of David Harris ([EMAIL PROTECTED]):
>
> I'm thinking of deploying RBL to try to cut down on spam, but before
> I did that I wanted to poke around and see how effective it might
> be. So, I gathered up some spam messages that I had received and
> looked up the mailserver's ipaddr in RBL using rbl.maps.vix.com and
> rbl.dorkslayers.com, and not one host was rejected from either RBL
> site. Even though I could see the messages looked like they were
> going trough an open relay.
>
> How good is this whole RBL thing anyway?
In my experience, the RBL is a _great_ tool for pressuring ISPs into
adopting rational anti-spam policies.
It is an _awful_ tool for actually cutting down on the amount of spam
an individual user gets. As your quick test above amply demonstrated,
the spammers just move their source addresses too quickly for the RBL
to be useful in stopping them.
ORBS (nee dorkslayers) is useful to system administrators in that they
will provide automatic reports on your netblocks, but isn't really any
more useful for actually lowering your spam intake, for mostly the
same reasons.
-n
------------------------------------------------------------<[EMAIL PROTECTED]>
"The Zapruder film confirms, beyond all reasonable doubt, that John F. Kennedy
was killed by having his fucking head blown almost completely off his fucking
shoulders." (--The Onion)
<http://www.blank.org/memory/>------------------------------------------------
David Harris [mailto:[EMAIL PROTECTED]] wrote:
> I'm going to setup a little program that will query RBL for these addresses
> and then simply record the SMTP conversation with hosts (using recordio)
> that show up as a positive. I can then review those conversations and
> see if I get any false positives and if this is worth deploying.
>
> I'll run this for a few days and let the list know what I find.
Somebody asked me if I'd open source this program, so here it is:
http://www.davideous.com/misc/rblefftest-1.00.tar.gz
Anybody else is free to run it. I'd just ask that you share your results with
me and/or the list.
I've got it running on my server right now, but I only receive about 15k smtp
connections per month, so it might be a while before I have the amount of data
that I'd like to see. When I tally the results, I'll let the list know.
- David Harris
Principal Engineer, DRH Internet Services
On Mon, 20 Sep 1999, David Harris wrote:
> I'm thinking of deploying RBL to try to cut down on spam, but before I did that
> I wanted to poke around and see how effective it might be. So, I gathered up
> some spam messages that I had received and looked up the mailserver's ipaddr in
> RBL using rbl.maps.vix.com and rbl.dorkslayers.com, and not one host was
> rejected from either RBL site. Even though I could see the messages looked like
> they were going trough an open relay.
>
> How good is this whole RBL thing anyway?
It's not terribly pro-active, and they won't RBL anyone if you just
forward them the headers from a spam, even if they have verified that it
came from an open relay.
You have to demonstrate that the server admin(s) of said relay was
unresponsive or uncooperative in taking steps to shut down the open relay
first.
I can certainly see why they do things this way, but it definitely limits
the RBL's effectiveness as a spam filtering mechanism. OTOH, it's been
outstanding in terms of getting lethargic providers (big and small) to
crack down on spamming customers.
It still appears to catch a significant number of spams (just not enough
to make an impact on my system or mailbox), and IMHO, is worth
implementing, but you should also employ the MAPS DUL, which appears to
catch almost all of the spam that comes directly from dialup accounts (not
through a relay). It also appears that the spammers have caught on to
that and have reverted to using open relays, and unfortunately, there's
still an abundance of them, and more coming on line all the time.
I've been toying with using ORBS (I already forward open relays to them),
but am reluctant for various reasons.
[EMAIL PROTECTED] wrote:
(...)
> Currently I'm using RBL, DUL, and RSS. It stops almost all spam
> attempts to this machine, but then this is a .gov, and spammers seem
> to stay away from .gov addresses.
So, we finally have THE universal solution against spam!
what about opening .forward accounts to everyone ?
-- no kidding!
Regards
Fabrice Scemama
On Mon, 20 Sep 1999, Fabrice Scemama wrote:
>
> [EMAIL PROTECTED] wrote:
> (...)
> > Currently I'm using RBL, DUL, and RSS. It stops almost all spam
> > attempts to this machine, but then this is a .gov, and spammers seem
> > to stay away from .gov addresses.
>
> So, we finally have THE universal solution against spam!
> what about opening .forward accounts to everyone ?
> -- no kidding!
They also seem to stay away from .org addresses as well (for the most
part). A .org address is a lot easier to get than a .gov.
Cheers,
Vern
--
\ \ / __| _ \ \ | Vern Hart
\ \ / _| / . | [EMAIL PROTECTED]
\_/ ___|_|_\_|\_|
On Mon, 20 Sep 1999, Vern Hart wrote:
> > > to stay away from .gov addresses.
> >
> > So, we finally have THE universal solution against spam!
> > what about opening .forward accounts to everyone ?
> > -- no kidding!
>
> They also seem to stay away from .org addresses as well (for the most
> part). A .org address is a lot easier to get than a .gov.
Not from my experience. They shamelessly spam [EMAIL PROTECTED], [EMAIL PROTECTED]
or any list or alias that's open.
On Mon, Sep 20, 1999 at 07:36:33PM -0400, James Smallacombe wrote:
}
} Not from my experience. They shamelessly spam [EMAIL PROTECTED], [EMAIL PROTECTED]
} or any list or alias that's open.
My guess has always been that they stay away from .gov because the
.gov is the one entity that can effectively shut them down. If most
of the cycles of Federal government computers were going towards
handling spam, then spam would quickly be stopped by law. If it were
coming from overseas, pressure would be put on those countries that
were hosting spammers. The US Federal government has the power to
deal with spammers, unlike most of their victims.
(My pobox.com address, on the other hand, gets plenty of spam, because
pobox's antispam methods are very poor. I only wish they used DUL,
which would get rid of most of the spam from that direction.)
}
--
Paul Schinder
[EMAIL PROTECTED]
Hi,
I've just started using qmail and friendson our (newly upgraded) live
Linux x86 server after mauling the var-qmail-<NN>-src.rpm
comprehensively on the offline tester and applying a selection of the
published patches (anti-uce, aol fix, etc) via the rpm spec and then
allowing the var-qmail process to continue. (Seemed the most sensible
way to proceed).
Apart from some teething problems with permissions, it all seems to
be working okay, relay-control is working via pop3d apop
authentication and procmail has integrated well. All seems fine
except for persistent delivery rejections of outgoing (and, I'm told,
incoming) email for some specific hosts. I haven't yet seen a copy of
the incoming rejection but the outgoing rejection reads:
"Hi. This is the qmail-send program at bel-epa.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
[...]
Remote host said: 550 rejected: cannot route to sender <[EMAIL PROTECTED]>"
The string "cannot route to sender" does turn up in search of the
qmail list archives but I can't see the relevance of that discussion
(dial-up user) to the problem I'm seeing, nor can I find anything
specific in the man pages or FAQ (hurry up with that O'Reilly book,
guys),
Given that qmail on the qmail-list server is happy to receive/send
email to me at this allegedly problematic address, I presume it's
some clash of anti-UCE measures, some DNS issue or something
malconfigured in my qmail setup.
Has anyone seen this before? Can anyone suggest a starting point for
my investigations. What information should I be providing to avert
the wrath of the hovering gurus?
Cheers,
Graham Higgins
--------------
Southfork Graphics Bristol, UK.
http://sfg.bel-epa.com
Dan Bernstein: Clarification on use of Maildir requested. Direct query to
you at the bottom of the mail.
Regarding a webmail system for maildirs, which creates a structure like
this to support webmail folders:
Maildir/.customfolder1/{new,cur,tmp}
Maildir/.customfolder2/{new,cur,tmp}
Maildir/localoptionfile1
Maildir/localoptionfile2
On Mon, Sep 20, 1999 at 01:37:04PM -0400, Sam wrote:
> On Mon, 20 Sep 1999, Randy Harmon wrote:
>
> > And yet it knows about folders, and munges a True Maildir into Not A True
> > Maildir in order to implement folders differently from True Maildir clients
> > like Mutt.
>
> DJB's specs on maildirs mention nothing about folders, so you cannot point
> to any implementation as being right or wrong, because there is no right
> or wrong way. Blame Dan Bernstein for an incomplete design.
Ah, just so. My opinions based entirely on just one or two implementations.
Perhaps asking him for a clarification would be more productive than placing
blame.
... time passes ...
I've just searched the qmail list archives rather thoroughly for Dan's
thoughts. On Tue, 07 Jan 1997, Dan Bernstien is attributed at
http://www.ornl.gov/its/archives/mailing-lists/qmail/1997/01/msg00205.html
to have said:
someone else> In particular, the handling of multiple folders needs to be
fully
someone else> specified.
Dan> You can set up several maildirs if you want. What's the question?
The response seemed to put off the person who asked the question, resulting
in no solution. Dan, the question is:
What is your recommendation for creating in Maildir format:
a) Multiple mail folders for use by MUAs
b) Sub-folders for use by MUAs
Two approaches have been used:
1) ~/Maildir/{new,cur} == INBOX and
~/Maildir/.foldername/{new,cur} == foldername
2) ~/Maildir/{new,cur} == INBOX and
~/foldername/{new,cur} == foldername
Thanks for the crossposted clarification.
Randy
> > DJB's specs on maildirs mention nothing about folders, so you cannot
point
> > to any implementation as being right or wrong, because there is no right
> > or wrong way. Blame Dan Bernstein for an incomplete design.
Maildir was designed to ensure that messages could be written safely by an
MTA without having to worry about locking out an MUA that's accessing the
folder at the same time. once the messages are on disk it's the UA's
problem to filter/move them around. yes, i'm considering a filtering
program run out of dot-qmail to be a UA; i don't think it's fair to consider
it part of the TA.
> What is your recommendation for creating in Maildir format:
somehow i doubt you're going to get an answer from dan on this one. my
personal feeling is "let the UA decide how it wants to make folders," as
it's an issue of policy and not function.
shag
On Mon, Sep 20, 1999 at 12:40:27PM -0700, Racer X wrote:
> > > DJB's specs on maildirs mention nothing about folders, so you cannot
> point
> > > to any implementation as being right or wrong, because there is no right
> > > or wrong way. Blame Dan Bernstein for an incomplete design.
>
> Maildir was designed to ensure that messages could be written safely by an
> MTA without having to worry about locking out an MUA that's accessing the
> folder at the same time. once the messages are on disk it's the UA's
> problem to filter/move them around. yes, i'm considering a filtering
> program run out of dot-qmail to be a UA; i don't think it's fair to consider
> it part of the TA.
>
> > What is your recommendation for creating in Maildir format:
>
> somehow i doubt you're going to get an answer from dan on this one. my
> personal feeling is "let the UA decide how it wants to make folders," as
> it's an issue of policy and not function.
And yet, if multiple MUAs are free to implement any way they feel, then
there is no recommended way and different MUAs cannot nicely co-exist. Take the
example of a Mutt user who uses a webmail program to access mail. If the
two MUAs work differently, they can't see each other's folders.
If there were a recommended way to implement these well-known features, it
could reduce confusion and support peaceful co-existence between UAs.
Thanks...
Randy
On Mon, 20 Sep 1999, Randy Harmon wrote:
> If there were a recommended way to implement these well-known features, it
> could reduce confusion and support peaceful co-existence between UAs.
It makes the most sense to me to just alter the 'normal' (to me at least)
method of laying out mail: a 'mail' directory, and instead of having the
different mail folders in mailbox format, just use Maildirs instead.
~/mail/qmail/{cur,new,tmp}
~/mail/ProFTPD/{cur,new.tmp}
etc.
Sub-maildirs are a little bit of a problem (because "cur", "new" and "tmp"
are taken already), but submaildirs are also not needed in the vast
majority of cases.
Just my $.02 CDN
.Shawn
> And yet, if multiple MUAs are free to implement any way they feel, then
> there is no recommended way and different MUAs cannot nicely co-exist.
Take the
> example of a Mutt user who uses a webmail program to access mail. If the
> two MUAs work differently, they can't see each other's folders.
>
> If there were a recommended way to implement these well-known features, it
> could reduce confusion and support peaceful co-existence between UAs.
as i mentioned in a message to the sqwebmail list earlier, there is already
a recommended way to handle this. see the maildir page on dan's site,
specifically the section about "info."
btw, "co-existence between UAs" is generally limited to unix systems where
the messages are stored in plain text files. it's not going to mean
anything for people on other systems where messages are stored in a database
particular to the UA (which, btw, makes for the vast majority of users).
shag
Asmodeus writes:
> On Mon, 20 Sep 1999, Randy Harmon wrote:
>
> > If there were a recommended way to implement these well-known features, it
> > could reduce confusion and support peaceful co-existence between UAs.
>
> It makes the most sense to me to just alter the 'normal' (to me at least)
> method of laying out mail: a 'mail' directory, and instead of having the
> different mail folders in mailbox format, just use Maildirs instead.
>
> ~/mail/qmail/{cur,new,tmp}
> ~/mail/ProFTPD/{cur,new.tmp}
> etc.
>
> Sub-maildirs are a little bit of a problem (because "cur", "new" and "tmp"
> are taken already), but submaildirs are also not needed in the vast
> majority of cases.
This is pretty much what I've done in sqwebmail, except that the code
transparently prefixes the name of each subdirectory with a . - they are
hidden subdirectories off the main Maildir. So a luser can create a 'new'
folder, if that's what the luser wants. I can't claim credit for this idea
- someone else suggested that approach about a year ago.
The only other thing I've done as well is automatically create a
zero-length file "maildirfolder" in each subdirectory. This is used by an
additional section of code shared by sqwebmail and maildrop that implements
a voluntary quota mechanism.
--
Sam
On Mon, Sep 20, 1999 at 05:12:22PM -0700, Racer X wrote:
> > > what's wrong with using the info field, in particular, info starting
> with
> > > "1," (experimental semantics)? if you don't like that, ask him to
> register
> > > another info field.
> >
> > I fail to see how this can be used to implement discrete folders.
>
> if it starts with "2," and it has an R after that, it's been read. if it
> starts with "1," and has an F after that, then immediately following the F
> is the folder name. no, this is not perfect, it's just what i thought of
> off the top of my head.
This is a creative solution that differs from the two creative solutions
already implemented in different UAs. Now there's at three ways that have
been discussed, which is more complex, not less.
> if you're talking about physically putting the files in different
> directories, i say that it's a UA problem to deal with, not a Maildir
> problem. don't blame the Maildir spec for not solving a problem it wasn't
> meant to solve.
It's really not about whether or not Maildir can be used to solve the folder
problem, and there's really no blame anyone is trying to place. We know
that a Maildir is a useful, safe place to deliver mail even simultaneously
with UA access and simultaneously with other deliveries (over NFS, without
locks).
We know that the Maildir format provides specifically for the above.
We're simply trying to establish a standard semantic for applying Maildir
to implement a common UA feature in a way that promotes interoperability
between Maildir-using UAs.
Without such a recommended standard semantic, authors will select something
they think is "nicest", which will be different from what other authors
select as being "nicest". Of course, all these authors will be right to
implement something that doesn't break Maildirs as useful, safe places to
deliver mail even simultaneously with UA access et cetera. Implementations
that break Maildirs' given functions will be broken implementations.
It's really just a matter of selecting one method that people can point to
as the preferred way. If the creator of the Maildir format would comment as
to the way he would suggest, then actually putting that method in place for
specific UAs could be done with confidence of compatibility with other UAs.
Er, ones whose authors listen to DJB's suggestion. Additionally, broken UAs
could be pointed at with confidence as implementing a broken version of
Maildir folders/subfolders.
If subfolders weren't part of some UA's folder semantics, I'm pretty sure
this wouldn't be at issue - we could use ~/Maildir/, ~/Maildir-foo/ etc and
be done. With subfolders, the ambiguity of whether alternative folders to
INBOX should be placed inside ~/Maildir/ or in ~/Maildir-foo/ is at issue.
Plus the second question of where subfolders should live. Of course, all
proposed methods _work_. But what single method should be used as standard?
Still hoping that the group can arrive at a single solution, perhaps with
Dan's assistance...
Randy
I am trying to write a wrapper function to assign directories to a number of
mailing lists (created by ezmlm), before, i was putting a line in assign
file of qmail for each mailing list like this
+joe-testing:joe:uid:gid:directory of the dot-qmail files:-:testing:
which works well and it handles the bounce messages as well, what i am doing
now is that i have putted a line in the assign file
+:joe:uid:gid:/mailinglist:-::
where /mailinglist is the directory of the wrapper function and a
.qmail-default file calling the wrapper function in this directory
|/mailinglist/mailinglist.pl
in this wrapper function, it will find out which directory the mailing
list's dot-qmail files are and calling qmail-local again to deliver the
messages.
I have no problem to receive messages by this wrapper function, which it can
still distribute mailing list messages to subscribers, but when there is a
bounce message from a invalid email address, it seems the bounce messages
have never reach the right .qmail files and it has nothing in the bounce
directory, that means the wrapper function has failed to deliver the bounce
messages to the mailing list.
I think i have mis-used the qmail-local program, does anyone has any idea
how can i use qmail-local to have the same results as i putted the
+joe-testing:joe:uid:gid:directory of the dot-qmail files:-:testing:
in assign file?
Thanks
Joe
I want to create a number of emails for one server (example,
[EMAIL PROTECTED], [EMAIL PROTECTED]), but I am at a loss as to how to do
this. I have created virtual email accounts for my other virtual domains
without a problem, they work great. But now I don't want to have to
create an "info" user just so I can have an "info" email for the server.
The "info" mail isn't for a virtual domain, it's for THE domain on my
server.
I've tried adding domain.com:info in the virtual domain file but that
didn't work. What do I need to do? Thanks for any help.
james
hi, all
When i use ofmipd to rewrite From: , Return-Path header, it's ok,
( Setup file: control/rewrite , control/idhost and /etc/ofmip.cdb ).
But ofmipd can't rewrite the mail-address host name of Message-ID .
Would you please tell me: How to use ofmipd to rewrite Message-ID using
control/rewrite or control/idhost.
thanks
xww
|
hi, all
I have two questions:
1. How to running maildrop at boot ( my system: redhat v6.0 )
?
2. How to using filtering language by maildrop to get the
"personal name" of To: header ?
Example:
Thanks for your reply.
xww
|
I would like to use qmail-inject to send the tail of a log file. What would
be the correct redirection and syntax for doing so? I've tried several
variations, but I'm not a very experienced shell programmer. So any help
would be most appreciated.
something like:
tail log | echo to: [EMAIL PROTECTED] | qmail-inject
sends a blank email even though there's text in the log file.
and
tail log > echo to: [EMAIL PROTECTED] | qmail-inject
doesn't seem to do anything at all.
As you can see I'm really not very clear on my redirects beyond the very
basic level.
THanks,
-Hawke
On Mon, 20 Sep 1999, Hawke wrote:
> I would like to use qmail-inject to send the tail of a log file. What would
> be the correct redirection and syntax for doing so? I've tried several
> variations, but I'm not a very experienced shell programmer. So any help
> would be most appreciated.
> something like:
> tail log | echo to: [EMAIL PROTECTED] | qmail-inject
> sends a blank email even though there's text in the log file.
> and
> tail log > echo to: [EMAIL PROTECTED] | qmail-inject
> doesn't seem to do anything at all.
> As you can see I'm really not very clear on my redirects beyond the very
> basic level.
> THanks,
> -Hawke
tail log | qmail-inject [EMAIL PROTECTED]
Or even better
tail log | mailsubj "log file details" [EMAIL PROTECTED]
This ensures a Subject: header, and it separates the headers from the
body of the message - even if there is a colon in the log file
details.
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
eServ. Pty Ltd [EMAIL PROTECTED]
Phone: +61 2 9206 3410 Fax: +61 2 9281 1301
"If you kill all your unhappy customers, you'll only have happy ones left"
Hi,
First of all I am a newbie to the *nix. I use supervise from deamon tools 0.61.
To run the following run file:
*********************************
Version a:
#!/bin/sh
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start "`cat /var/qmail/control/defaultdelivery`" \
setuidgid qmaill multilog t /var/log/qmail/mail
*********************************
Version b:
#!/bin/sh
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start "`cat /var/qmail/control/defaultdelivery`" | \
setuidgid qmaill multilog t /var/log/qmail/mail
When I use version a, logging does not work. I checked man page for qmail-start it
says the following is a calling
convention: qmail-start [ defaultdelivery [ logger arg ... ] ]. As far as I
understand that should work. What am I
missing.
When I use version b (piping) the logging does work. But I can not use svc -dx to stop
the service. I can see using ps
-ef that sh ./run is there after starting the file. After stopping (trying) the
service sh ./run is gone but the
qmail-send and the rest of the bunch is there. I can kill the service using kill or
killall, but it just drives me
nuts.
Sincerely,
Vladimir Berezniker
What I found was that if someone (me) has 'leave messages on the
server' set and reads the message from work, that's the last time it
is seen. The bulletin link gets moved from the new to cur directory
and stays there unreadable and unremovable even before the bulletin
is pulled. (Having 'pull messages from server' has no effect when I
try to read mail at home. The link is untouchable unless I get on the
server and delete it by hand.)
> Subject: race condition in qmail-popbull
>
>
> I think I've found a race condition in qmail-popbull. If you delete a
> bulletin just after qmail-popbull has run, but before the user has
> started to download that message, qmail-pop3d says "-ERR unable to
> open that message". If you delete a bulletin just after qmail-popbull
> has run, but the user doesn't get a chance to download the message,
> qmail-pop3d will leave that symlink lying around forever.
>
> So, to see if this is more than a theory, could people running
> qmail-popbull check to see if they have dangling symlinks in their
> user's directories?
>
> The fix, if necessary, is for qmail-pop3d to remove dangling symlinks
> when it finds them.
>
________________________________________________________
NetZero - We believe in a FREE Internet. Shouldn't you?
Get your FREE Internet Access and Email at
http://www.netzero.net/download/index.html
[EMAIL PROTECTED] (Claus F�rber) wrote:
> Much of work?
> All you have to do is (untested):
> controls/virtualdomains:
> .example.com:alias-piffle
> alias/.qmail-default:
> |forward "$DEFAULT"
> (Yes, that's less work than applying a patch!)
> Inconsistent?
> Maybe.
I see, but is that documented anywhere?
And I still think this is the "territory" auf control/locals because I do
not have a "virtual"domain, but a real one ;-)
Greetings
--
[EMAIL PROTECTED]
innominate AG
networking people
fon: +49.30.308806-45 fax: -77 web: http://innominate.de
Hi !
Please can Qmail use the ETRN protocol as described in RFC 1985 ? (see
http://rfc.fh-koeln.de/rfc/html/rfc1985.html).
As I think no :-/, I installed maildir2smtp but I get troubles getting the
dynamic IP adress from my clients with custommers when their SMTP want to
check mails...
Thank you.
--
Xon-Xoff - http://www.Xon-Xoff.fr
Publication et Commerce electronique sur le Web
Messagerie d'entreprise, Interconnexion et Securite des reseaux
On Tue, Sep 21, 1999 at 09:47:07AM +0200, Dimitri SZAJMAN wrote:
> Please can Qmail use the ETRN protocol as described in RFC 1985 ? (see
> http://rfc.fh-koeln.de/rfc/html/rfc1985.html).
>
> As I think no :-/, I installed maildir2smtp but I get troubles getting the
> dynamic IP adress from my clients with custommers when their SMTP want to
> check mails...
If you're assigning dynamic addresses to your customers, look at
http://www.qmail.org/turnmail
--
See complete headers for more info
I tried to run so many different configs and still no luck.
basic script for launching smtp looks like this:
tcpserver -v -u 508 -g 509 0 smtp /var/qmail/bin/qmail-smtpd \
2>&1 | /var/qmail/bin/splogger smtpd 3 &
But I cannot send message form any external host - I found in logs:
937900864.859093 tcpserver: warning: dropping connection, unable to run
qmail-smtpd: file does not exist
(of course qmail-smtpd exists in /var/qmail/bin/) Any idea?
Thx in advance!
Piotr Wanat
--
mailto:[EMAIL PROTECTED] | UIN:15871058
On Tue, Sep 21, 1999 at 10:12:42AM +0200, Piotr Wanat wrote:
> I tried to run so many different configs and still no luck.
> basic script for launching smtp looks like this:
>
> tcpserver -v -u 508 -g 509 0 smtp /var/qmail/bin/qmail-smtpd \
> 2>&1 | /var/qmail/bin/splogger smtpd 3 &
>
> But I cannot send message form any external host - I found in logs:
> 937900864.859093 tcpserver: warning: dropping connection, unable to run
> qmail-smtpd: file does not exist
>
> (of course qmail-smtpd exists in /var/qmail/bin/) Any idea?
The file may exist, but if /var/qmail/bin has the wrong permissions, the
qmaild user may not be able to look at the files. The usual mode is 755
for /var/qmail and /var/qmail/bin.
--
See complete headers for more info
