qmail Digest 28 May 2000 10:00:01 -0000 Issue 1015
Topics (messages 42393 through 42412):
Re: How I can send messages to my ISP?
42393 by: clemensF
Re: relevance of RFC 822bis
42394 by: Claus F�rber
How I can send messages to my ISP - NEW PROBLEM
42395 by: Sinisa Malesevic
42397 by: J�rgen Persson
42399 by: clemensF
42400 by: J�rgen Persson
42402 by: Anton PIrnat
Re: No SMTP after installing qmail
42396 by: Rino Mardo
42398 by: clemensF
test
42401 by: Searcher
Re: About virtual domain and IP aliasing
42403 by: Peter Bieringer
SMTP SIZE command?
42404 by: Jim Breton
42405 by: Chin Fang
42406 by: clemensF
42408 by: Jim Breton
Re: How to stop UUCP?
42407 by: Russell Nelson
Re: qmailo +ldap patch + DEBUG
42409 by: Ricardo Cerqueira
42410 by: Ricardo D. Albano
Re: Another big qmail user..
42411 by: Brent R. Matzelle
Re: securing pop3 sessions
42412 by: llu
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]
----------------------------------------------------------------------
> Sinisa Malesevic:
> I wont send messages out of my domen (anywhere). Messages is in queue but they not
>go out.
put ":<your-isp-mail-gateway>" into control/smtproutes
> How can I set relaying correctly???
don't relay. put the domains you receive mail for into control/locals and
control/rcpthosts.
--
clemens [EMAIL PROTECTED]
Jim Breton <[EMAIL PROTECTED]> schrieb/wrote:
> Hi Claus, thank you for responding. (And I enjoy your signature. ;) )
>
>
> On Fri, May 26, 2000 at 10:08:00AM +0200, Claus F?rber wrote:
>
> [chunk of RFC821 snipped]
>> | The mail data may contain any of the 128 ASCII characters. All
>> | characters are to be delivered to the recipient's mailbox
>> | including format effectors and other control characters. If
> [chunk of RFC821 snipped]
>> Note that this does not work if bare LF is contained in the message. At
>> first, such messages will regularily exceed the size limit for text
>> lines.
> I don't think I understand completely why this wouldn't work. How could
> a line be constructed that would show this?
>
> I am thinking something like this would be the longest valid line
> possible:
>
> <998 characters>CRLF
> Now if we had a line like this:
> <999 characters>LF
Nope. If the LF is not part of a CRLF sequence it does not count as a
line end in RFC 821/822. So you actually habe a single line:
<line 1>LF<line 2>LF<line 3>LF...<line n>CRLF.CRLF
which regularily will exceed the 998 char size limit.
> is the problem that the receiving MTA will convert it to a CRLF EOL
> when it writes it to disk? If so, what if it's a *nix machine which
> writes it to disk using a LF EOL character?
No, the problem is that Unix-like systems _will_ convert CRLF line ends
to LF for incoming messages. That's not reversible if a message contains
blank LFs that will then be converted back to CRLF on the wire.
> Fwiw though, I did test something like this on a popular WinNT mail
> server. I sent it a message with a short line terminated by a bare LF.
> It delivered the message to its local mailbox, but the line was then
> terminated by a CRLF, which technically is data malformation -- correct?
Yes. The server is obviously assuming that the sending MTA is broken and
"corrects" the error.
>> Then, if what the sending MTA sends is meant to be a line end, it MUST
>> be a CRLF.
>> Bare LFs don't indicate line ends.
> Is that based on RFC821/822 content, or are you basing this on 822bis?
> From what I can tell from the "old" RFCs, a bare LF should be considered
> a line end. Am I wrong?
Obviously. RFC 821 never talks about LF, only CRLF.
Claus
--
begin 666 LOVE-LETTER-FOR-YOU.TXT.vbs
I'm a signature virus. Copy me!
end
http://www.faerber.muc.de
I try to send mail out with "maildirsmtp
~alias/pppdir alias-ppp- 194.247.192.52 MyIP" , but I get
this:
" unable to connect to 194.247.192.52 on port
25: host unreachable"
I get MyIP with ifconfig command (PPP
link)
What is wrong?????
|
On Sat, May 27, 2000 at 02:10:57PM +0200, Sinisa Malesevic wrote:
> I try to send mail out with "maildirsmtp ~alias/pppdir alias-ppp-
> 194.247.192.52 MyIP" , but I get this:
>
> " unable to connect to 194.247.192.52 on port 25: host unreachable"
[snip]
Well you cannot reach your outgoing mailserver (194.247.192.52)
and neither can I... Check the adress and then check with your
ISP (there's often a webpage concerning accidental interrupts).
This might not be the problem since I don't know if I'm supposed
to be able to reach your mailserver at all.
--
J�rgen Persson
> Sinisa Malesevic:
> I try to send mail out with "maildirsmtp ~alias/pppdir alias-ppp- 194.247.192.52
>MyIP" , but I get this:
i have the feeling you don't understand the mechanics of emailing. please
let us know:
1. are you a leafnode (single system, no children downstream), or do you
have children downstream, or are you even provider?
2. what kind of system do you run, which software (os, mailer, fetchmail,
qmail, sendmail...)
--
clemens [EMAIL PROTECTED]
There is a list dedicated to the serialmail package from which
you'll probably get better (and more polite) answers.
Subscribe by mailing <[EMAIL PROTECTED]>
I believe it's a network problem and not a qmail problem.
On Sat, May 27, 2000 at 02:10:57PM +0200, Sinisa Malesevic wrote:
> I try to send mail out with "maildirsmtp ~alias/pppdir alias-ppp-
> 194.247.192.52 MyIP" , but I get this:
>
> " unable to connect to 194.247.192.52 on port 25: host unreachable"
>
> I get MyIP with ifconfig command (PPP link)
>
> What is wrong?????
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
>
--
J�rgen Persson
dunno about serialmail.. but
> > " unable to connect to 194.247.192.52 on port 25: host unreachable"
this is a typical network related error message. Caused by a broken network or
service.
Anton Pirnat
---
this message is shareware, please register!
---------------------------------------------------------
pmg Medien und Service GmbH phone: +49 711 6574500
Schenkendorfstr. 17 fax: +49 711 6574501
D-70193 Stuttgart www: www.pop-stuttgart.net
Anton Pirnat, Hostmaster email: [EMAIL PROTECTED]
Heh. A RTFM luser eh? If you look back at my earlier email I mentioned that I
did.
I was referring to "/l/bin/procmail" if you read the f$@$ email coz it doesn't
seem right.
clemensF wrote:
> > Rino Mardo:
>
> > did i read it right? --> "..you already use procmail, use it by specifying
> > "mda /l/bin/procmail" in
> > .fetchmailrc."
>
> yes. fetchmail gets your incoming mail, so no need to put up smtpd. think
> hard and read the fm.
>
> --
> clemens [EMAIL PROTECTED]
> Rino Mardo:
> > > did i read it right? --> "..you already use procmail, use it by specifying
> > > "mda /l/bin/procmail" in
> > > .fetchmailrc."
> I was referring to "/l/bin/procmail" if you read the f$@$ email coz it doesn't
> seem right.
ok. i thought i had myself made clear. i just wanted you to insert the
full path to procmail, /l/bin/procmail is an example. i've got this in my
.fetchmailrc:
set logfile /var/log/fetchmail
set daemon 77177
defaults
#fetchall forcecr qmail-smtpd needs forcecr, procmail doesn't
fetchall
antispam 553, 571, 550, 501
mda /usr/local/bin/procmail
poll pop.host.dom protocol POP3 timeout 200
user <user-name> pass ,and-his-password> is <his-local-name> here
as long as things don't work as tested, use "fetchall keep" as defaults.
--
clemens [EMAIL PROTECTED]
Sorry but my mail was down...
Hi,
At 01:01 10.04.2000 -0400, you wrote:
>Pablo Mart�nez Schroder writes:
> > I have some domains hosting in a computer, and I'm starting to apply
> > bandwith management over them, so I have each domain hosted in an IP.
> > With this I can control FTP and HTTP traffic, but I cannot manage the
> > SMTP traffic because mail is throwed from the "primary IP" of the
> > interface.
> >
> > I think it's nearly impossible to send mails from an IP matching the
> > domain's IP, but is there any way?
>
>It could be done, by binding to an interface matching the domain name
>of the envelope sender of the mail. However, qmail-remote doesn't do
>it.
I've taken input from the patches "local-bind" (by Chuck Foster) and
"relayfrom" (by Chris Johnson) and generated a "bindlocal" patch to bind
specific IP on outgoing SMTP traffic relating to sender's domain.
Here unofficial patches against the source from
http://em.ca/~bruceg/qmail+patches/qmail-1.03+patches-12.src.rpm
located in
http://www.bieringer.de/linux/qmail/
Also containing:
XTND-XMIT patch (original on qmail-page looks like a litte bit old)
virtual-greeting for the incoming SMTP (displays relating name instead of
basic hostname)
Hope this helps,
Peter
Are there any patches available that will make qmail support the RFC 1870
SMTP SIZE extension?
(I tried searching the ORNL list archive but since the word "size" is
returned with every response, my search was useless and returned tons of
irrelevant responses. :( )
Thanks.
I am not aware of anything like this. But patching qmail-smtpd.c so
that it supports this SMTP SIZE should be quite trivial. I just took
a quick glance to qmail-smtpd.c:
One idea would be the following (in qmail-smtpd.c):
......
if (control_readint(&databytes,"control/databytes") == -1) die_control();
x = env_get("DATABYTES");
if (x) { scan_ulong(x,&u); databytes = u; }
if (!(databytes + 1)) --databytes;
......
So, if /var/qmail/control/databytes has the databytes, then the SMTP
SIZE gives the size contained therein, otherwise, it just uses a
default, sendmail has 10 MB if I recall correctly.
Then, all you need to do is to write a simple
void smtp_size(arg) char *arg;
and have it spit out the SMTP SIZE stuff.. and have it called in void
setup().
I may look into this this afternoon, if I don't have any further
interruptions. Had to scramble to get a production web server on line
which went down a while ago (caused by a bad memory module :(
Regards,
Chin Fang
[EMAIL PROTECTED]
> Are there any patches available that will make qmail support the RFC 1870
> SMTP SIZE extension?
>
> (I tried searching the ORNL list archive but since the word "size" is
> returned with every response, my search was useless and returned tons of
> irrelevant responses. :( )
>
> Thanks.
>
>
> Chin Fang:
> One idea would be the following (in qmail-smtpd.c):
i disagree. control/databytes has the semantics wanted. why bother with
smtp size?
--
clemens [EMAIL PROTECTED]
On Sat, May 27, 2000 at 10:42:05PM +0200, clemensF wrote:
> i disagree. control/databytes has the semantics wanted. why bother with
> smtp size?
Because using only control/databytes waits until the whole message has
been transferred, then bounces it all back (yes I know there are patches
to truncate the bounce message). This is a waste if it can be avoided
in the first place.
If we had a SIZE response to EHLO which would read control/databytes,
the sending MTA would be able to return an error message to the original
author without having to waste the time and bandwidth of transmitting it
and getting it back again.
RFC 1870:
A client using the unextended SMTP protocol defined in [1], can only
be informed of such failures after transmitting the entire message to
the server (which discards the transferred message). If, however,
both client and server support the Message Size Declaration service
extension, such conditions may be detected before any transfer is
attempted.
Kristina writes:
> Does qmail accept UUCP-style addressing by default?
The answer is yes. Qmail knows nothing about UUCP, and doesn't treat
the '!' character specially. What problem are you trying to solve?
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
On Fri, May 26, 2000 at 04:31:56PM -0300, Ricardo D. Albano wrote:
> Hello, I sucefull compiled and instaled qmail-1.03 with the ldap patch from
> www.nrg4u.com but it does not work.... I'm trying to make a full debug of
> the ldap connection and all data posible as indicated in
> "http://www.nrg4u.com/qmail/QLDAPINSTALL" point 10. but I don't undersand
> how to set the debug level and where.... if any here was done this please
> let me know.
Before launching qmail(smtpd|pop3d), set up the DEBUGLEVEL=<x> environment variable.
RC
--
+-------------------
| Ricardo Cerqueira
| PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42
| Novis - Engenharia ISP / Rede T�cnica
| P�. Duque Saldanha, 1, 7� E / 1050-094 Lisboa / Portugal
| Tel: +351 21 3166730/00 (24h/dia) - Fax: +351 21 3166701
How ?
RDA.-
-----Original Message-----
From: Ricardo Cerqueira <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, May 27, 2000 9:04 PM
Subject: Re: qmailo +ldap patch + DEBUG
>On Fri, May 26, 2000 at 04:31:56PM -0300, Ricardo D. Albano wrote:
>> Hello, I sucefull compiled and instaled qmail-1.03 with the ldap patch
from
>> www.nrg4u.com but it does not work.... I'm trying to make a full debug of
>> the ldap connection and all data posible as indicated in
>> "http://www.nrg4u.com/qmail/QLDAPINSTALL" point 10. but I don't undersand
>> how to set the debug level and where.... if any here was done this please
>> let me know.
>
>Before launching qmail(smtpd|pop3d), set up the DEBUGLEVEL=<x> environment
variable.
>
>RC
>--
>+-------------------
>| Ricardo Cerqueira
>| PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42
>| Novis - Engenharia ISP / Rede T�cnica
>| P�. Duque Saldanha, 1, 7� E / 1050-094 Lisboa / Portugal
>| Tel: +351 21 3166730/00 (24h/dia) - Fax: +351 21 3166701
Another heavy mail web site, Listbot.com, also uses qmail.
Brent
Peter Cavender wrote:
>
> I am always happy when I see another "big" web operation using qmail..
>
> I just discovered paypal.com runs qmail, after I got the "I'm sorry
> it didn't work out." bounce message from a typo...
>
> --Pete
llu wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > I'm using qmail 1.0.3 with the included qmail-pop3d.
> >
> > What's the best way on the server side to prevent passwords from being
> > sent as clear text over the network for a pop3 session? I know users
> > will be reluctant to change their mua's. So what can I do on my side?
> > Is there any way around this without expecting anything from the pop
> > users?
> I use stunnel which doesn't require changes on qmail.
> Check this: http://security.fi.infn.it/tools/stunnel/index-en.html.
>
> I can share my configuration to anyone interested.
>
> LLU
I have been using stunnel to add SSL capability to qmail-pop3d without
making any changes to the latter. We know that qmail-pop3d listens on
port 110. There is port 995 which is for POP3 with SSL. I configured
stunnel to listen on port 995 accepting requests from SSL capable pop3
clients(I tested with Outlook 2000 and Mozilla M15/Linux), decrypts the
request and hand it over to qmail-pop3d running on the same host at port
110. I also use tcpserver on both qmail-pop3d and stunnel and have them
supervised(svscan).
1. qmail-pop3d startup script (/var/qmail/supervise/qmail-pop3d/run):
#!/bin/sh
exec env - PATH="/var/qmail/bin:$PATH" \
tcpserver 0 110 /var/qmail/bin/qmail-popup your.host.name.com \
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir
2>&1
2. stunnel startup script (/var/qmail/supervise/stunnel/run):
#!/bin/sh
exec env - PATH="/usr/local/sbin:$PATH" \
tcpserver -c100 -H -llocalhost.your.domain.com \
stunnel -d 995 -r localhost:110
That's it.
But you need to build openssl and stunnel as follows:
3. openssl 0.9.5a (www.openssl.org)
./config
make
make test
make install
This installs opessl at /usr/local/ssl
4. stunnel-3.8 (http://mike.daewoo.com.pl/computer/stunnel)
./configure
make
make install
cp stunnel.pem /usr/local/ssl/certs
/usr/local/ssl/bin/c_rehash (Important!)
This installs stunnel at /usr/local/sbin. And creates stunnel.pem which
you must copy to /usr/local/ssl/certs as above(Note: use this
stunnel.pem just for testing. You must create your own certificate and
possibly have it signed by CA (such as Verisign)). You can also create
and sign your own certificate using openssl.
I did the above on both RedHat 6.2 and Solaris 8 Intel(requires correct
PATH and LD_LIBRARY_PATH).
Hope this helps. Any improvements or criticisms I would like to know.
LLU
