qmail Digest 8 Jan 2001 11:00:01 -0000 Issue 1238
Topics (messages 54824 through 54862):
Newbie question
54824 by: Roger Arnold
54843 by: Jeff Lacy
Re: qmail-1.03-qmtpc-mailroutes.patch
54825 by: Johan Almqvist
54827 by: Johan Almqvist
Re: control/mailroutes (was: QMTP autoreply tester)
54826 by: Johan Almqvist
54830 by: Greg Owen
54838 by: richard.illuin.org
Re: qmail pop3d
54828 by: ksemat
Re: spam filter
54829 by: Brian Longwe
54842 by: Harald Hanche-Olsen
54858 by: Brian Longwe
54860 by: Jenny Holmberg
Re: List archives.
54831 by: Greg Owen
54832 by: kate.katewerk.com
Local configuration error
54833 by: Franco Galian
54834 by: Henning Brauer
54835 by: Chris Johnson
54837 by: Franco Galian
qmail, SMTP AUTH and vmailmgr
54836 by: Lars Rusdorf
message numbers repeating?
54839 by: Johan Almqvist
54840 by: James Raftery
Italian qmail howto
54841 by: Davide Giunchi
FIX! (was: qmail-1.03-qmtpc-mailroutes.patch)
54844 by: Johan Almqvist
54846 by: melo.isp.novis.pt
54849 by: Ricardo Cerqueira
54857 by: Magnus Bodin
54861 by: James Raftery
Re: etern
54845 by: Marc-Adrian Napoli
dns question
54847 by: Andrew Alford
54853 by: Al Sparks
About Qmail & Ldap
54848 by: one
Stopping a single address
54850 by: Phil Barnett
54852 by: paul.anastrophe.com
qmail & pine
54851 by: kat
54854 by: Al Sparks
54859 by: Irwan Hadi
badmailpattern
54855 by: Marc-Adrian Napoli
54856 by: Brett Randall
Speed Problem
54862 by: Michael Maier
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Roger Arnold wrote:
How do you make a users file using "qmail-pw2u" from your /etc/passwd
file ?
If I execute /var/qmail/qmail-pw2u with no extensions I would have
thought that it would have created an assignments file from /etc/passwd,
however all that happens is that it goes into never-never land, and not
return to the command prompt.
Are there any indepth documentation relating to this and other qmail
commands other than the man files ?
Thanks in advance
Roger
Hello Roger,
qmail-pw2u wants the contents of /etc/passwd to be passed/piped to it. If
you wanted to create an assignment file from the /etc/passwd, you might try
something like
cat /etc/passwd | /var/qmail/bin/qmail-pw2u > /var/qmail/users/assign
If you do that though, be sure you delete people who won't need mail. Or
you could make your own assign file, but you would have to figure that out
yourself :-) ALSO REMEMBER TO RUN /var/qmail/bin/qmail-newu AFTER YOU HAVE
AN ASSIGN FILE. This has caused me a little trouble in the past :-D
Jeff
----- Original Message -----
From: "Roger Arnold" <[EMAIL PROTECTED]>
To: "Qmail Users" <[EMAIL PROTECTED]>
Sent: Sunday, January 07, 2001 5:01 AM
Subject: Newbie question
> Roger Arnold wrote:
>
> How do you make a users file using "qmail-pw2u" from your /etc/passwd
> file ?
>
> If I execute /var/qmail/qmail-pw2u with no extensions I would have
> thought that it would have created an assignments file from /etc/passwd,
> however all that happens is that it goes into never-never land, and not
> return to the command prompt.
>
> Are there any indepth documentation relating to this and other qmail
> commands other than the man files ?
>
> Thanks in advance
>
> Roger
>
On Sun, Jan 07, 2001 at 01:48:02AM +0000, Ricardo Cerqueira wrote:
> > I made a few modifications to Russell's patch. You can now specify routes
> > for QMTP just as you can for SMTP. Ths filename is changed to
> > control/mailroutes and the format changed a tad, but the old file will
> > still work if moved.
> I was about to write a mail asking for qmtproutes, so great!
> But... Do you mean your solution ignores control/smtproutes? Or can you
> have both smtproutes for SMTP _and_ mailroutes for QMTP?
There is one file for both SMTP and QMTP routes. It is called mailroutes.
I found that design clearer than havning two files - I couldn't figure out
which file I would want to have precedence, and reading from two files had
been messier anyhow.
However, you can just copy your smtproutes file to mailroutes and it will
work. I have just extended the format but SMTP is assumed if no protocol
is given.
I think there may be a little glitch left: an explicit SMTP route may not
be able to override MXPS-based QMTP routing. I'll look into this later
today.
I will also look inte patching qmail-showctl and the manpages for
qmail-remote and qmail-control if people actually use this patch...
I'm still looking for feedback on the actual code...
-Johan
--
Johan Almqvist
On Sun, Jan 07, 2001 at 02:03:30PM +0100, Johan Almqvist wrote:
> I think there may be a little glitch left: an explicit SMTP route may not
> be able to override MXPS-based QMTP routing. I'll look into this later
> today.
Nope, that seems to work just fine...
> I will also look inte patching qmail-showctl and the manpages for
> qmail-remote and qmail-control if people actually use this patch...
> I'm still looking for feedback on the actual code...
-Johan
--
Johan Almqvist
On Sat, Jan 06, 2001 at 10:28:26PM -0700, Andy Bradford wrote:
> Thus said Ricardo Cerqueira on Sun, 07 Jan 2001 01:50:16 GMT:
> > Hmmm... OK, disregard my previous mail.
> > Personally, I'd rather have one file for SMTP, and another for QMTP. Does
> > anyone else here agree with me?
I'd really like to discuss this further... Could you please elaborate on
> This seems more logical to me as it allows finer control over the
> entire system. Oh well, I suppose it isn't critical as qmail-remote
> will just have to determine which to use by probing I guess---unless of
> course it is accompanied by a port number on which QMTP runs.
The format I propose for control/mailroutes is the following:
--- snip ---
Two example lines looks like this:
almqvist.net:beta.lunds.lu.se:209:qmtp
propellerheads.org:mail-relay.df.lth.se
In the first case, QMTP will be used to transfer messages for
the almqvist.net domain to beta.lunds.lu.se, port 209.
In the second case, SMTP will be used to transfer messages for
the propellerheads.org domain to mail-relay.df.lth.se, port 25.
PLEASE NOTE that SMTP will be assumed as protocol even if you
specify 209 as the port, but no protocol. In fact, SMTP will be
used in all cases except if the last field is exactly 'qmtp'.
PLEASE NOTE that you cannot specify only a protocol. If you wish
to specify a protocol, you MUST specify a port. Bad things may
happen.
--- snap ---
If there were two files, I'd basically have to "merge" them internally
anyway... Or one file would have to have precedence over the other - but
what happens if I specify a wildcard in one file but one of that
domain's subdomains in the other?
-Johan
--
Johan Almqvist
Andy Bradford said:
> Thus said Ricardo Cerqueira on Sun, 07 Jan 2001 01:50:16 GMT:
> > Personally, I'd rather have one file for SMTP, and another
> > for QMTP. Does anyone else here agree with me?
>
> This seems more logical to me as it allows finer control
> over the entire system.
It also seems to me that one of the design traits of qmail is
simplicity of config files - I can't find the reference, but I thought
somewhere DJB said that having to parse complex config files is a cause of
problems. Parseing two files, one for SMTP and one for QMTP, seems more in
line with that philosophy than having one file that must be parsed for
meaning rather than just correctness.
Just my .02.
--
gowen -- Greg Owen -- [EMAIL PROTECTED]
SoftLock.com is now DigitalGoods!
On Sat, 6 Jan 2001, Andy Bradford wrote:
> Thus said Ricardo Cerqueira on Sun, 07 Jan 2001 01:50:16 GMT:
>
> > Hmmm... OK, disregard my previous mail.
> > Personally, I'd rather have one file for SMTP, and another for QMTP. Does
> > anyone else here agree with me?
>
> This seems more logical to me as it allows finer control over the
> entire system. Oh well, I suppose it isn't critical as qmail-remote
> will just have to determine which to use by probing I guess---unless of
> course it is accompanied by a port number on which QMTP runs.
the difficulty with two files is precidence... if you have files like
this:
smtproutes:
.com:mail-relay1.internal
mail.example.com:mail-relay1.internal
qmtproutes:
:mail-relay2.internal
example.com:mail-relay2.internal
mail.example.com:mail-relay2.internal
then you have to read the files at the same time to determine which route
to use; what do you do if you have two entries for the same domain in both
files -> which one takes priority? would you notice mail.example.com
appears in both files?
Added complexity makes for more bugs.
RjL
>
> TH> HOWTOs, which are excellent on all other aspects, just say, oh
> TH> stick
> TH> in a line that says:
>
> TH> tcpserver 0 pop3 /var/qmail/bin/qmail-popup YOURHOST \
> TH> /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &
If you're using redhat or SuSE linux, a script in redhat like this could
help
#!/bin/sh
# to start qmail pop3d
case "$1" in
start )
echo "starting qmail pop3d"
/path to/tcpserver 0 pop3 etc etc....
;;
stop )
echo "shutting down qmail pop3d"
killall -9 qmail-pop3d
;;
* ) echo "usage {start|stop}"
;;
esac
pu this as say qmail-pop3d in /etc/rc.d/init.d for redhat or /sbin/init.d
for SuSE.
then if say you start in runlevel 3 change to /etc/rc.d/init.d/rc3.d and
put symbolic links like say S35qmail-pop3d and K35qmail-pop3d both
pointing to your script. this should start qmail-pop3d on boot. of course
for suse that would mean /sbin/init.d/rc3.d or whatever runlevel it is
that you boot into.
Your observation is correct, the text I pasted is an incoming message. The
point is, the only reason it bounced and is being sent back to the user (and
me, the postmaster) is because the address got messed up with control
characters. There are probably many others with correct addresses going out
through my system.
I *do* want to receive these bounce messages. But I want to find a way to
stop the culprit from sending all this junk through my system. To me it
looks like the "from" address that shows in the outgoing messages is
[EMAIL PROTECTED], how can I block messages with this originating address
(or subject line) from going through the system?
Thanks,
Brian
> -----Original Message-----
> From: Harald Hanche-Olsen [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, January 06, 2001 5:42 PM
> To: [EMAIL PROTECTED]
> Subject: Re: spam filter
>
>
> + "Brian Longwe" <[EMAIL PROTECTED]>:
>
> | Hi,
> |
> | I want to filter out messages with the following header from being
> | sent out by a user on my system:
> | ---------------------------------------------
> | Hi. This is the qmail-send program at relay.ispkenya.com.
> | I tried to deliver a bounce message to this address, but the
> bounce bounced!
> |
> | <[EMAIL PROTECTED]</=>:
> | Sorry, I couldn't find any host named compuserve.com</=. (#5.1.2)
> |
> | --- Below this line is the original bounce.
> [ ...]
> | ---------------------------------------------
> |
> | I have tried putting some portions of the above in the
> badmailfrom control
> | file to no avail. Any tips?
>
> That doesn't work because not only is the above text not in the header
> - it is in the body of the incoming message - but the badmailfrom file
> only controls messages based on the envelope from, which is not even
> in the header, it's outside the message itself. (Read the
> envelopes(5) man page to see what I mean.)
>
> In this case, the message is a doublebounce, so the envelope sender
> will be <#@[]> (it will be in the Return-Path header field after the
> message is finally delivered).
>
> Here is what you can do:
>
> # cat > /var/qmail/alias/.qmail-doublebounce << 'EOT'
> |if grep '[EMAIL PROTECTED]'; then exit 99; else exit 0; fi
> &postmaster
> EOT
> # echo doublebounce > /var/qmail/control/doublebounceto
>
> Then restart qmail.
>
> To understand what this all means, read the dot-qmail, qmail-command
> and qmail-send manual pages. Read them before you do anything; the
> above advice is just off the top of my head and untested, and you
> should understand the solution and its consequences yourself before
> implementing it.
>
> - Harald
>
+ "Brian Longwe" <[EMAIL PROTECTED]>:
| But I want to find a way to stop the culprit from sending all this
| junk through my system. To me it looks like the "from" address that
| shows in the outgoing messages is [EMAIL PROTECTED], how can I
| block messages with this originating address (or subject line) from
| going through the system?
Uh-oh. I guess I wasn't reading your original message well enough.
Now it seems to me you're running an open relay, allowing email from
anywhere to anywhere else through your system. Believe me, you don't
want to do that. You will never be able to keep the spammers away by
trying to filter out messages of certain characteristics.
Read about relaying, what it is, and how to stop it here:
http://Web.InfoAve.Net/~dsill/lwq.html#relaying
- Harald
Harald
I'm not running an open relay. I am using tcpserver and allowing relaying
only for IP addresses that belong to my network (RELAYCLIENT). The problem
here is that it's one of my customers who has an application that is sending
out all this junk mail. How do I set up a filter to block until I can get
them to disable the application?
Brian
> -----Original Message-----
> From: Harald Hanche-Olsen [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 08, 2001 1:54 AM
> To: [EMAIL PROTECTED]
> Subject: RE: spam filter
>
>
> + "Brian Longwe" <[EMAIL PROTECTED]>:
>
> | But I want to find a way to stop the culprit from sending all this
> | junk through my system. To me it looks like the "from" address that
> | shows in the outgoing messages is [EMAIL PROTECTED], how can I
> | block messages with this originating address (or subject line) from
> | going through the system?
>
> Uh-oh. I guess I wasn't reading your original message well enough.
> Now it seems to me you're running an open relay, allowing email from
> anywhere to anywhere else through your system. Believe me, you don't
> want to do that. You will never be able to keep the spammers away by
> trying to filter out messages of certain characteristics.
>
> Read about relaying, what it is, and how to stop it here:
>
> http://Web.InfoAve.Net/~dsill/lwq.html#relaying
>
> - Harald
>
"Brian Longwe" <[EMAIL PROTECTED]> writes:
> Harald
>
> I'm not running an open relay. I am using tcpserver and allowing relaying
> only for IP addresses that belong to my network (RELAYCLIENT). The problem
> here is that it's one of my customers who has an application that is sending
> out all this junk mail. How do I set up a filter to block until I can get
> them to disable the application?
echo "[EMAIL PROTECTED]" >> /var/qmail/control/badmailfrom
--
"I live in the heart of the machine. We are one."
> Where may I find them, (if they exist)?
There are three archives linked to in the second paragraph at
http://www.qmail.org/top.html. At least one is searchable.
--
gowen -- Greg Owen -- [EMAIL PROTECTED]
SoftLock.com is now DigitalGoods!
On Sun, 7 Jan 2001, Greg Owen wrote:
> > Where may I find them, (if they exist)?
>
> There are three archives linked to in the second paragraph at
> http://www.qmail.org/top.html. At least one is searchable.
Thanks all. Found what I was looking for. :)
--
Kate
http://www.katewerk.com
I have some problems with a qmail installed on OpenBSD 2.8, which is running
tinydns as nameserver.
Outside mail reaches with no problem to my Maildir (ie. if I mail from
mail.yahoo.com), but when I try to mail from the localhost I get the
following error:
[From /var/log/maillog]
Jan 7 13:22:32 obsd sendmail[30065]: f07GMU930065: from=root, size=40,
class=0, nrcpts=1, msgid=<[EMAIL PROTECTED]>,
relay=root@localhost
Jan 7 13:22:32 obsd sendmail[6680]: f07GMU930065: SYSERR(root): MX list for
galian.com.ar. points back to obsd.galian.com.ar
Jan 7 13:22:32 obsd sendmail[6680]: f07GMU930065: [EMAIL PROTECTED],
ctladdr=root (0/0), delay=00:00:02, xdelay=00:00:00, mailer=esmtp,
pri=30040, relay=galian.com.ar., dsn=5.3.5, stat=Local configuration error
Jan 7 13:22:33 obsd sendmail[6680]: f07GMU930065: f07GMX806680: DSN: Local
configuration error
Jan 7 13:22:33 obsd sendmail[6680]: f07GMX806680: to=root, delay=00:00:00,
xdelay=00:00:00, mailer=local, pri=30140, dsn=2.0.0, stat=Sent
[...]
[From /var/qmail/control/locals]
galian.com.ar
obsd.galian.com.ar
[From /var/qmail/control/rcpthosts]
galian.com.ar
The other problem that I've found is that when I mail to franco@localhost or
[EMAIL PROTECTED] it delivers mail to /var/mail/franco (however I've
specified in /var/qmail/rc that qmail should use Maildir as the default
format)
Thanks in advance
Ps: I have a similar configuration at work, only that it does not handle
mail from the outside and it has no nameserver running. It is a SuSE 6.4 and
works just fine.
_________________
Franco Galian
[EMAIL PROTECTED]
Am Sonntag, 7. Januar 2001 17:36 schrieb Franco Galian:
> I have some problems with a qmail installed on OpenBSD 2.8, which is
> running tinydns as nameserver.
> Outside mail reaches with no problem to my Maildir (ie. if I mail from
> mail.yahoo.com), but when I try to mail from the localhost I get the
> following error:
[sendmail errors]
You missed one installation step, replacing the sendmail binary by qmail's
sendmail-wrapper.
Anyway, there's a better option in OpenBSD: just provide the correct pathes
in /etc/mailer.conf; OpoenBSD's /usr/bin/sendmail ist just a wrapper checking
this file.
> _________________
> Franco Galian
> [EMAIL PROTECTED]
--
Henning Brauer | BS Web Services
Hostmaster BSWS | Roedingsmarkt 14
[EMAIL PROTECTED] | 20459 Hamburg
www.bsws.de | Germany
On Sun, Jan 07, 2001 at 01:36:32PM -0300, Franco Galian wrote:
> I have some problems with a qmail installed on OpenBSD 2.8, which is running
> tinydns as nameserver.
> Outside mail reaches with no problem to my Maildir (ie. if I mail from
> mail.yahoo.com), but when I try to mail from the localhost I get the
> following error:
>
> [From /var/log/maillog]
> Jan 7 13:22:32 obsd sendmail[30065]: f07GMU930065: from=root, size=40,
> class=0, nrcpts=1, msgid=<[EMAIL PROTECTED]>,
> relay=root@localhost
> Jan 7 13:22:32 obsd sendmail[6680]: f07GMU930065: SYSERR(root): MX list for
> galian.com.ar. points back to obsd.galian.com.ar
> Jan 7 13:22:32 obsd sendmail[6680]: f07GMU930065: [EMAIL PROTECTED],
> ctladdr=root (0/0), delay=00:00:02, xdelay=00:00:00, mailer=esmtp,
> pri=30040, relay=galian.com.ar., dsn=5.3.5, stat=Local configuration error
> Jan 7 13:22:33 obsd sendmail[6680]: f07GMU930065: f07GMX806680: DSN: Local
> configuration error
> Jan 7 13:22:33 obsd sendmail[6680]: f07GMX806680: to=root, delay=00:00:00,
> xdelay=00:00:00, mailer=local, pri=30140, dsn=2.0.0, stat=Sent
> [...]
That's sendmail talking, not qmail (see how it says "sendmail" all over the
place?). You must not have followed the installation instructions explicitly.
>
> [From /var/qmail/control/locals]
> galian.com.ar
> obsd.galian.com.ar
>
> [From /var/qmail/control/rcpthosts]
> galian.com.ar
>
> The other problem that I've found is that when I mail to franco@localhost or
> [EMAIL PROTECTED] it delivers mail to /var/mail/franco (however I've
> specified in /var/qmail/rc that qmail should use Maildir as the default
> format)
Again, that's because sendmail is handling your mail.
Chris
Ok thanks Chris and Henning, the problem was that I have installed Qmail
with OpenBSD2.7 and I have little or no testing at all, and then I've
upgraded to OpenBSD 2.8 and started to notice that problem. Thank you very
much I've missed that possibility
Franco
-----Mensaje original-----
De: Chris Johnson [mailto:[EMAIL PROTECTED]]
Enviado el: Domingo, 07 de Enero de 2001 01:49 p.m.
Para: Franco Galian
CC: Qmail
Asunto: Re: Local configuration error
On Sun, Jan 07, 2001 at 01:36:32PM -0300, Franco Galian wrote:
> I have some problems with a qmail installed on OpenBSD 2.8, which is
running
> tinydns as nameserver.
> Outside mail reaches with no problem to my Maildir (ie. if I mail from
> mail.yahoo.com), but when I try to mail from the localhost I get the
> following error:
>
> [From /var/log/maillog]
> Jan 7 13:22:32 obsd sendmail[30065]: f07GMU930065: from=root, size=40,
> class=0, nrcpts=1, msgid=<[EMAIL PROTECTED]>,
> relay=root@localhost
> Jan 7 13:22:32 obsd sendmail[6680]: f07GMU930065: SYSERR(root): MX list
for
> galian.com.ar. points back to obsd.galian.com.ar
> Jan 7 13:22:32 obsd sendmail[6680]: f07GMU930065:
[EMAIL PROTECTED],
> ctladdr=root (0/0), delay=00:00:02, xdelay=00:00:00, mailer=esmtp,
> pri=30040, relay=galian.com.ar., dsn=5.3.5, stat=Local configuration error
> Jan 7 13:22:33 obsd sendmail[6680]: f07GMU930065: f07GMX806680: DSN:
Local
> configuration error
> Jan 7 13:22:33 obsd sendmail[6680]: f07GMX806680: to=root,
delay=00:00:00,
> xdelay=00:00:00, mailer=local, pri=30140, dsn=2.0.0, stat=Sent
> [...]
That's sendmail talking, not qmail (see how it says "sendmail" all over the
place?). You must not have followed the installation instructions
explicitly.
>
> [From /var/qmail/control/locals]
> galian.com.ar
> obsd.galian.com.ar
>
> [From /var/qmail/control/rcpthosts]
> galian.com.ar
>
> The other problem that I've found is that when I mail to franco@localhost
or
> [EMAIL PROTECTED] it delivers mail to /var/mail/franco (however
I've
> specified in /var/qmail/rc that qmail should use Maildir as the default
> format)
Again, that's because sendmail is handling your mail.
Chris
Hi :)
has anybody a running system with qmail, SMTP AUTH patch and user
management by vmailmgr ? I run into problems by using the checkvpw program
of vmailmgr ... my first problem was that checkvpw wanted to change group
and user ... as it was started by qmaild. I solved this one by setting
suid and sgid for checkvpw ... but now it still ends with an authorization
failure ... anyone out there who can help me with this ?
Regards
Lars
This is from my mail log:
Jan 7 21:03:13 alpha qmail: 978897793.668139 end msg 26226
Jan 7 21:03:17 alpha qmail: 978897797.017629 new msg 26226
No, I didn't tinker with the clock. These lines are immediately after
each other. And it's not syslog sync problems either, I believe:
[johan@alpha johan]$ grep 'msg 26226$' /var/log/maillog | tail
Jan 7 20:30:39 alpha qmail: 978895839.019739 new msg 26226
Jan 7 20:30:39 alpha qmail: 978895839.700460 end msg 26226
Jan 7 20:34:37 alpha qmail: 978896077.553056 new msg 26226
Jan 7 20:34:38 alpha qmail: 978896078.792728 end msg 26226
Jan 7 21:03:11 alpha qmail: 978897791.864174 new msg 26226
Jan 7 21:03:13 alpha qmail: 978897793.668139 end msg 26226
Jan 7 21:03:17 alpha qmail: 978897797.017629 new msg 26226
Jan 7 21:03:17 alpha qmail: 978897797.663223 end msg 26226
Jan 7 21:03:47 alpha qmail: 978897827.825925 new msg 26226
Jan 7 21:03:48 alpha qmail: 978897828.517892 end msg 26226
This kinda worries me. Also makes log analysis a pest. What's wrong?
Bruce G's rpms, by the way.
-Johan
--
Johan Almqvist
http://www.almqvist.net/johan/qmail/
On Sun, Jan 07, 2001 at 09:12:18PM +0100, Johan Almqvist wrote:
> This kinda worries me. Also makes log analysis a pest. What's wrong?
Hi,
Absolutely nothing. The message ID is the inode number of the messages
queue file. These do get reused. See the qmail-log(5) man page for
details of qmail's logging output.
james
--
James Raftery (JBR54)
"Managing 4000 customer domains with BIND has been a lot like
herding cats." - Mike Batchelor, on [EMAIL PROTECTED]
Hi all.
I've written an "Italian qmail HOWTO", this document (in italian
language) explain how
to install,configure and running qmail.
This isn't a translation of the english "qmail howto" but is a new
document write.
It can be found in
http://www.folug.cjb.net/qmail/qmail-HOWTO.html
I hope that it could be useful for all qmail users.
I will post the link to qmail.org and ILDP (italian linux doc project)
Regards.
--
Davide Giunchi. Duke_Nuke on ircnet
Membro del FoLUG (Forlí Linux User Group) - http://folug.cjb.net
GPG Key available on http://www.keyserver.net
Hi!
There patch I released earlier wasn't quite as careful about memory
allocation (or rather, failures of memory allocation) as the rest of Dan's
code. I have released a new version, available from
http://www.almqvist.net/johan/qmail/
I'm still very eager to hear your comments. I'll stick with the mailroutes
design for now, though :->
-Johan
--
Johan Almqvist
http://www.almqvist.net/johan/qmail/
PGP signature
On Mon, Jan 08, 2001 at 02:40:39AM +0100, Johan Almqvist wrote:
> Hi!
>
> There patch I released earlier wasn't quite as careful about memory
> allocation (or rather, failures of memory allocation) as the rest of Dan's
> code. I have released a new version, available from
>
> http://www.almqvist.net/johan/qmail/
>
> I'm still very eager to hear your comments. I'll stick with the mailroutes
> design for now, though :->
One comment: if smtproutes is compatible with mailroutes, why not use
smtproutes instead of mailroutes?
--
Pedro Melo Cunha - <[EMAIL PROTECTED]>
Novis - Dir. Rede - ISP - Infraes. Portal <http://www.novis.pt/>
Ed. Atrium Saldanha - Pça. Dq. Saldanha, 1 - 7º / 1050-094 Lisboa
tel: +351 21 0104340 - Fax: +351 21 0104301
On Mon, Jan 08, 2001 at 01:00:49AM +0000, [EMAIL PROTECTED] wrote:
> On Mon, Jan 08, 2001 at 02:40:39AM +0100, Johan Almqvist wrote:
> > Hi!
> >
> > There patch I released earlier wasn't quite as careful about memory
> > allocation (or rather, failures of memory allocation) as the rest of Dan's
> > code. I have released a new version, available from
> >
> > http://www.almqvist.net/johan/qmail/
> >
> > I'm still very eager to hear your comments. I'll stick with the mailroutes
> > design for now, though :->
>
> One comment: if smtproutes is compatible with mailroutes, why not use
> smtproutes instead of mailroutes?
Because the name is too confining... It implies smtp. mail is more generic
:)
But I still prefer having smtp and qmtp separately (keeping the good
tradition of the multiple qmail conf files)
RC
--
+-------------------
| Ricardo Cerqueira
| PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42
| Novis Telecom - Engenharia ISP / Rede Técnica
| Pç. Duque Saldanha, 1, 7º E / 1050-094 Lisboa / Portugal
| Tel: +351 2 1010 0000 - Fax: +351 2 1010 4459
PGP signature
On Mon, Jan 08, 2001 at 03:26:21AM +0000, Ricardo Cerqueira wrote:
> >
> > One comment: if smtproutes is compatible with mailroutes, why not use
> > smtproutes instead of mailroutes?
>
> Because the name is too confining... It implies smtp. mail is more generic
> :)
> But I still prefer having smtp and qmtp separately (keeping the good
> tradition of the multiple qmail conf files)
But what about precedence as Johan mentioned earier?
(e.g. Message-ID: <[EMAIL PROTECTED]>)
What could be done is to use BOTH smtproutes and mailroutes. Then it's sort
of backwards compatible. smtproutes will be read first. Then mailroutes. I
don't have an opinion about precedence here, but at least a smtproutes-file
would not be ignored. Which is most important.
A future qmail needs a qmail-lint shipped with it. As djbdns today ships
with nice tools like dnstrace, there is a definitive need for
trace/lint-tools for qmail.
/magnus
--
http://x42.com/
On Mon, Jan 08, 2001 at 07:54:04AM +0100, Magnus Bodin wrote:
> On Mon, Jan 08, 2001 at 03:26:21AM +0000, Ricardo Cerqueira wrote:
> >
> > But I still prefer having smtp and qmtp separately (keeping the good
> > tradition of the multiple qmail conf files)
>
> But what about precedence as Johan mentioned earier?
> (e.g. Message-ID: <[EMAIL PROTECTED]>)
I don't think it's a difficult problem to solve. There's an existing set
of config. file that can cause conflict: locals and virtualdomains. The
issue was solved in that case by stating clearly in the docs that locals
is processed first and so will win in a conflict situation.
My preference is for seperate files to specify artificial routes for
smtp and qmtp, and for the instructions in qmtproutes to be processed
first, thereby winning in any conflict situation.
james
--
James Raftery (JBR54)
"Managing 4000 customer domains with BIND has been a lot like
herding cats." - Mike Batchelor, on [EMAIL PROTECTED]
hi,
yup etern works if you patch a few of the qmail source files. (there is a
patch floating around somewhere)
we've done it, and when the customer has a static IP address it works not a
problem.
Regards,
Marc-Adrian Napoli
Network Admin
Connect Infobahn Australia
+61 2 9212 0387
> On Sat, 6 Jan 2001, Bill Hults wrote:
>
> > Hi
> > I need to grab mail from a qmail server via etern. Can this be done?
> > Thanks
>
> No.
>
> James Smallacombe PlantageNet, Inc. CEO and Janitor
> [EMAIL PROTECTED] http://3.am
> =========================================================================
>
>
Is it necessary, even if you can ping on the internet your "mail.xyz.com
or smtp.xyz.com", to have your mx server listed with your registrar?
--- Andrew Alford <[EMAIL PROTECTED]> wrote:
> Is it necessary, even if you can ping on the internet your "mail.xyz.com
> or smtp.xyz.com", to have your mx server listed with your registrar?
Well, your question is vague. Are you pinging from outside or inside
your intranet? You haven't done a true test if you don't ping from
outside your intranet.
What it comes down to, does the outside see those addresses. If the
outside can then it's not "necessary". On the other hand, when you
register your name with ICANN, you are required to provide 2 DNS
servers you can be reached from. It's typical to place MX records on a
DNS server that's outside your network as well as inside your network
(though outside your firewall).
If you have a lot of questions about DNS, you're probably better off
finding a list that specializes in it, though I suspect there's plenty
of expertise on this list.
=== Al
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/
|
Hi :
How I config qmail and ldap ?
Why I cannot patch qmail-ldap and How ? Is
error.
Where I can find more info about qmail-ldap ?
Can you help me ?
Thank : you
Someone
|
Is it outlined somewhere how to block a single mail address to a
single mail address.
I have a user who is being harrassed and I need to intervene.
--
Phil Barnett mailto:[EMAIL PROTECTED]
WWW http://www.the-oasis.net/
FTP Site ftp://ftp.the-oasis.net
If someone is harrassing one of your users, then it would be reasonable to
presume that in doing so, they give up the privilege to email *anyone* at
your site. Therefore, adding the offender's email address to
/var/qmail/control/badmailfrom will do the trick.
Phil Barnett writes:
>
> Is it outlined somewhere how to block a single mail address to a
> single mail address.
>
> I have a user who is being harrassed and I need to intervene.
>
>
> --
> Phil Barnett mailto:[EMAIL PROTECTED]
> WWW http://www.the-oasis.net/
> FTP Site ftp://ftp.the-oasis.net
---------------------------------
Paul Theodoropoulos
[EMAIL PROTECTED]
Senior Unix Systems Administrator
Syntactically Subversive Services, Inc.
http://www.anastrophe.net
Downtime Is Not An Option
Hello all,
I am a newbie to both qmail and UNIX. Just a few days back I
have installed qmail 1.03 on my home machine. I have followed
all the standard instruction in INSTALL.* docs in the qmail
package.
I can send and
receive messsages from one user to another and have configured
my KDE email cleint to work with it.
Now, I want some client from shell mode such as Pine to work.
How can I get my Pine to work with it? I use RedHat Linux with
Pine 4.21.
Thanks in advance and eagerly looking foward for the replies
from all you people out there.
--
Best regards,
kat mailto:[EMAIL PROTECTED]
You weren't specific enough. Did you configure qmail to use the
Maildir email format or the old INBOX format>
Pine uses the INBOX format natively. If you're using the Maildir
format then you'll have to set up a pop3 or imap daemon to still use
pine.
While I've never used it, I understand that Mutt is an excellent text
based email shell client that uses the Maildir format.
=== Al
--- kat <[EMAIL PROTECTED]> wrote:
> Hello all,
> I am a newbie to both qmail and UNIX. Just a few days back I
> have installed qmail 1.03 on my home machine. I have followed
> all the standard instruction in INSTALL.* docs in the qmail
> package.
> I can send and
> receive messsages from one user to another and have configured
> my KDE email cleint to work with it.
> Now, I want some client from shell mode such as Pine to work.
> How can I get my Pine to work with it? I use RedHat Linux with
> Pine 4.21.
> Thanks in advance and eagerly looking foward for the replies
> from all you people out there.
>
> --
> Best regards,
> kat mailto:[EMAIL PROTECTED]
>
>
Do You Yahoo!?
Yahoo! Photos -
Share your holiday photos online!
At 10:08 PM 1/7/01 -0800, Al Sparks wrote:
>You weren't specific enough. Did you configure qmail to use the Maildir
>email format or the old INBOX format> Pine uses the INBOX format natively.
>If you're using the Maildir format then you'll have to set up a pop3 or
>imap daemon to still use pine. While I've never used it, I understand that
>Mutt is an excellent text based email shell client that uses the Maildir
>format. === Al --- kat wrote: > Hello all, > I am a newbie to both qmail
>and UNIX. Just a few days back I > have installed qmail 1.03 on my home
>machine. I have followed > all the standard instruction in INSTALL.* docs
>in the qmail > package. > I can send and > receive messsages from one user
>to another and have configured > my KDE email cleint to work with it. >
>Now, I want some client from shell mode such as Pine to work. > How can I
>get my Pine to work with it? I use RedHat Linux with > Pine 4.21. > Thanks
>in advance and eagerly looking foward for the replies > from all you
>people out there. > > -- > Best regards, > kat mailto:[EMAIL PROTECTED] > >
Well,if you use pine just update the inbox path to
~/Mailbox if you use Mailbox or ~/Maildir/ if you use Maildir/
Remember this is with Pine 4.30, I don't know for older version.
has anyone used this file with success?
and if not why is it still in the docs?
Regards,
Marc-Adrian Napoli
Network Admin
Connect Infobahn Australia
+61 2 9212 0387
On Mon, 8 Jan 2001, [EMAIL PROTECTED] wrote:
> has anyone used this file with success?
>
> and if not why is it still in the docs?
Do you mean badmailfrom? Yes I have used it with success, very easy to use.
--
B r e t t R a n d a l l
http://xbox.ipsware.com/
brett _ @ _ ipsware.com
Hi again!
I'm running qmail with big concurrency and big todo patch under Solaris
7 on a mirrored Disk.
It's horrible slow and sometimes there is a Message while sending Mail:
"451 qq trouble creating files in queue(#4.3.0)"
Possible Bottlenecks could be the semaphore Mechanism or the Solaris
File System but it's very uncommon.
So maybe you People could help me out of this Disaster! It's a SUN Netra
T1 Machine. qmail Config is:
qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 2045.
subdirectory split: 521.
user ids: 100, 101, 102, 0, 103, 104, 105, 106.
group ids: 100, 101.
badmailfrom: (Default.) Any MAIL FROM is allowed.
bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.
bouncehost: (Default.) Bounce host name is hermes.flatfox.de.
concurrencylocal: Local concurrency is 250.
concurrencyremote: Remote concurrency is 400.
databytes: (Default.) SMTP DATA limit is 0 bytes.
defaultdomain: Default domain name is flatfox.de.
defaulthost: Default host name is hermes.flatfox.de.
doublebouncehost: (Default.) 2B recipient host: hermes.flatfox.de.
doublebounceto: (Default.) 2B recipient user: postmaster.
envnoathost: (Default.) Presumed domain name is hermes.flatfox.de.
helohost: (Default.) SMTP client HELO host name is hermes.flatfox.de.
idhost: (Default.) Message-ID host name is hermes.flatfox.de.
localiphost: (Default.) Local IP address becomes hermes.flatfox.de.
locals:
Messages for flatmail.flatfox.de are delivered locally.
Messages for flatmail.flatfox.com are delivered locally.
Messages for zeus.flatfox.de are delivered locally.
Messages for hermes.flatfox.de are delivered locally.
Messages for localhost are delivered locally.
me: My name is hermes.flatfox.de.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: Plus domain name is flatfox.de.
qmqpservers: (Default.) No QMQP servers.
queuelifetime: Message lifetime in the queue is 259200 seconds.
rcpthosts:
SMTP clients may send messages to recipients at flatfox.de.
SMTP clients may send messages to recipients at flatmail.flatfox.de.
SMTP clients may send messages to recipients at zeus.flatfox.de.
SMTP clients may send messages to recipients at flatfox.com.
SMTP clients may send messages to recipients at flatfox.co.uk.
SMTP clients may send messages to recipients at flatfox.fr.
SMTP clients may send messages to recipients at localhost.
SMTP clients may send messages to recipients at e-trend.de.
morercpthosts: (Default.) No effect.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: SMTP greeting: 220 flatfox service.
smtproutes:
timeoutconnect: SMTP client connection timeout is 60 seconds.
timeoutremote: SMTP client data timeout is 1200 seconds.
timeoutsmtpd: SMTP server data timeout is 1200 seconds.
virtualdomains: (Default.) No virtual domains.
defaultdelivery: I have no idea what this file does.
Thanks a lot!
Michael..