qmail Digest 1 Aug 1999 10:00:01 -0000 Issue 715

Topics (messages 28398 through 28429):

Internet draft for VERP
        28398 by: Russell Nelson <[EMAIL PROTECTED]>
        28422 by: Scott Schwartz <[EMAIL PROTECTED]>
        28428 by: "D. J. Bernstein" <[EMAIL PROTECTED]>

Qmail problem
        28399 by: [EMAIL PROTECTED]
        28401 by: <[EMAIL PROTECTED]>
        28406 by: Steve Vertigan <[EMAIL PROTECTED]>

global forwarding
        28400 by: "Cris Daniluk" <[EMAIL PROTECTED]>
        28407 by: Russell Nelson <[EMAIL PROTECTED]>

Maildir support for Pine 4.10
        28402 by: "Gavin Cameron @ mail.itworks.com.au" <[EMAIL PROTECTED]>
        28408 by: Russell Nelson <[EMAIL PROTECTED]>
        28410 by: [EMAIL PROTECTED]
        28419 by: Chris Bond <[EMAIL PROTECTED]>
        28420 by: [EMAIL PROTECTED]
        28424 by: Frederik Lindberg <[EMAIL PROTECTED]>
        28425 by: Faried Nawaz <[EMAIL PROTECTED]>
        28426 by: "David Harris" <[EMAIL PROTECTED]>

POP3, SMTP and secure (ssh) port forwarding issue
        28403 by: Dinesh Punjabi <[EMAIL PROTECTED]>
        28404 by: <[EMAIL PROTECTED]>
        28418 by: Dinesh Punjabi <[EMAIL PROTECTED]>

problem with pop-ing my mail.
        28405 by: "Eric S. Raymond" <[EMAIL PROTECTED]>

unable to bind
        28409 by: Robert <[EMAIL PROTECTED]>
        28412 by: John Gonzalez/netMDC admin <[EMAIL PROTECTED]>
        28413 by: [EMAIL PROTECTED]
        28414 by: Robert <[EMAIL PROTECTED]>
        28415 by: Robert <[EMAIL PROTECTED]>
        28416 by: "Sam" <[EMAIL PROTECTED]>
        28429 by: <[EMAIL PROTECTED]>

Eliding quotes in envelope?
        28411 by: Scott Schwartz <[EMAIL PROTECTED]>
        28427 by: "D. J. Bernstein" <[EMAIL PROTECTED]>

2 qmail-pop3d
        28417 by: Paul Farber <[EMAIL PROTECTED]>
        28423 by: Frederik Lindberg <[EMAIL PROTECTED]>

(no subject)
        28421 by: [EMAIL PROTECTED]

Administrivia:

To subscribe to the digest, e-mail:
        [EMAIL PROTECTED]

To unsubscribe from the digest, e-mail:
        [EMAIL PROTECTED]

To bug my human owner, e-mail:
        [EMAIL PROTECTED]

To post to the list, e-mail:
        [EMAIL PROTECTED]


----------------------------------------------------------------------


D. J. Bernstein writes:
 > then people expect the service addresses for that list to be
 > 
 >    Jim+Joe-Bob#3-request

Ya gotta admit that -request is *the* standard, at least among the
people who know that there *is* a service address and that requests
*don't* go to the list itself.  :(

-- 
-russ nelson <[EMAIL PROTECTED]>  http://crynwr.com/~nelson
Crynwr sells support for free software  | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | can outdo them. Homeschool!




"D. J. Bernstein" <[EMAIL PROTECTED]> writes:
| Scott Schwartz writes:
| > I think it's strange that qmail-inject uses '-' to seperate the mailbox
| > from the verp part, even when some other conf-break character is in
| > effect for that user.  This surely violates the principle of least
| > surprise,
| 
| Certainly not. If a mailing list is named
| 
|    Jim+Joe-Bob#3
| 
| then people expect the service addresses for that list to be
| 
|    Jim+Joe-Bob#3-request
|    Jim+Joe-Bob#3-owner
|    Jim+Joe-Bob#3-subscribe
|
| and so on. What follows Jim+Joe-Bob#3 is _always_ a dash. It doesn't
| matter whether these addresses are controlled by Jim, or Jim+Joe, or
| Jim+Joe-Bob, or Fred.

Most people traditionally think of list-request as a seperate alias,
not as a submailbox, because user names can and do have hyphens in
them, and because mailing lists are usually not users.  You want to
conflate those usages, though, and so you are arguing here that
conf-break should always be '-'.  However, you're also the one who
decided that conf-break is allowed to be something else, and lots of
people do set it to something else.  

The problem is that if conf-break isn't '-', then qmail-inject's "m"
and "r" options will turn replyable addresses into VERPs that are not
replyable addresses (ironic, considering VERP's ostensible purpose).
That's pretty damn surprising.

It's (doubly) surprising because qmail makes a big deal about
user-controlled subaddresses, and the manpages say what conf-break is
set to and talk about how users/assign works, and so people who ask
qmail-inject to generate a VERP probably expect it to generated a
usable one without having to also manually insert subaddresses into the
envelopes of outgoing messages.

Moreover, a VERP isn't intended as a rendezvous, entirely unlike
list-request addresses.  Outsiders have no idea what conf-break is on
some other system, nor should they.  On the other hand, the person who
generates a VERP does know what conf-break is, so the surprise is if
the VERP generator ignores conf-break, not if conf-break differs from
some convention in a documented way.

If you disagree, then, as I suggested in private mail, I think you
ought to augment the documentation to warn people that changing
conf-break will cause them extra hassles.






Scott Schwartz writes:
> The problem is that if conf-break isn't '-', then qmail-inject's "m"
> and "r" options will turn replyable addresses into VERPs that are not
> replyable addresses (ironic, considering VERP's ostensible purpose).

If your conf-break is +, for example, and you set environment variables

   QMAILINJECT=rm
   QMAILSUSER=schwartz+dsn

then a typical message will have an envelope sender address of

   schwartz+dsn-987654321.12345-recip=aol.com

which will automatically be controlled by ~schwartz/.qmail-dsn-default.
What's the problem?

> so you are arguing here that conf-break should always be '-'.

I said nothing of the sort. If your conf-break is +, you might have a
mailing list called

   [EMAIL PROTECTED]

with service addresses such as

   [EMAIL PROTECTED]
   [EMAIL PROTECTED]
   [EMAIL PROTECTED]

which would normally be handled by

   ~schwartz/.qmail-trolling-default

The + after schwartz has nothing to do with the dash later in the
address. What's the problem?

There is one situation where it helps for conf-break to be a dash,
namely when a list is run by an account of the same name:

   [EMAIL PROTECTED]

If conf-break is a dash, the angels-request address will automatically
be controlled by the angels user. Otherwise, to use that address, you'll
have to put an extra line into users/assign.

---Dan








                   I have spent the last couple of weeks trying to get qmail to work, 
I have a
                   number of problems - not least of which is how do you get help from 
a mailing
                   list, with no E-mail facility.  I solved that with this web-mail 
thing,  I always
                   wondered what is was good for :-).

                   I am running RH6.0,  on 2.2.5 - we have a small network with 6 
computers at
                   present 4 running Windows and using OE as the client.   The last 
two including
                   the server run RH6.0.

                   I have set-up Qmail as per the howto, and have added vchkpw to 
authenticate
                   users.  Two major problems present themselves, the first is the 
dirty R word, yes
                   relaying - the stock  reply to this seems to be RTFM, so as not to 
be tarred with
                   that brush I have done so a number of times, and followed the 
directions
                   regarding tcp.smtp and tcprules with great care a number of times.  
  Every time
                   I get told to take my mail away - this doesn't impress my users.   
I have checked
                   the tcp.smtp file in a number of editors and no spurious control 
codes are
                   present.

                   Just to be thorough, I heve checked what is running with top at 
startup, I have
                   qmail-rspawn, qmail-lspawn, qmail-clean and accustamp running under 
qmail-send,
                   which in turn runs under supervise.   I have two instances of 
tcpserver running
                   under two instances of supervise.   Does this sound normal?

                   When I create a mail with qmail-inject, I can't log on to 
qmail-pop3d to retrieve
                   it from the network, I get a 'no socket' error.   

                    The setup is for no local users at all,  all are virtual domains 
and users. 
                   except for postmaster ( thats me, but I am not very busy at the 
moment ).  I have
                   run out of ideas ( the building isn't high enough to make dropping 
the PC out of
                   the window awefully satisfying :-) ) - anyone else got any ideas?

                   Dudley Brooke
______________________________________________________
Get Your Free Email at http://mail.euroseek.com




On Sat, 31 Jul 1999 [EMAIL PROTECTED] wrote:
> 
> I have set-up Qmail as per the howto, and have added vchkpw to authenticate
> users. Two major problems present themselves, the first is the dirty R word, yes
> relaying - the stock reply to this seems to be RTFM, so as not to be tarred with
> that brush I have done so a number of times, and followed the directions
> regarding tcp.smtp and tcprules with great care a number of times. Every time
> I get told to take my mail away - this doesn't impress my users. I have checked
> the tcp.smtp file in a number of editors and no spurious control codes are
> present.

firstly I'd stop ttrying to get virtual domains working, and make sure
qmail itself is working and delivering mail to postmaster's mailbox on the
machine itself. Once this is working virtual domains can be added
afterwards. then as you move forwards in developing the mail service you
can ask for help, and when something breaks undo what you did last and
things will works again.

> Just to be thorough, I heve checked what is running with top at startup, I have
> qmail-rspawn, qmail-lspawn, qmail-clean and accustamp running under qmail-send,
> which in turn runs under supervise. I have two instances of tcpserver running
> under two instances of supervise. Does this sound normal?

yes, one for qmail-smptd, and one for qmail-pop3d 

> When I create a mail with qmail-inject, I can't log on to qmail-pop3d to retrieve
> it from the network, I get a 'no socket' error. 

1/ what command lines are you using to start the popmail service? post the
actual scripts you use, not anything else, and don't obfusticate/edit them.
2/ did the mail arrive in the right location on the system
3/ of the pop3 tcpserver is (say) PID 98765 do something like:
   strace -ff -o /tmp/pop3 -p 98765

   and try ONCE to download the mail. there should be a whole bunch of
files in /tmp called pop3 and pop3.nnnnnn read them and see which one
failed and why.

(ps when using the webmail thingy you are using keep your lines VERY short,
it seems to put lots of space in at the beginnning of each line.)

RjL
==================================================================
The problems of the world || Fax: +44 870 0521198 
can't be solved by fixing || Email: [EMAIL PROTECTED]
the working -- C. Daniluk || 





[EMAIL PROTECTED] wrote:

>                    When I create a mail with qmail-inject, I can't log on to 
>qmail-pop3d to retrieve
>                    it from the network, I get a 'no socket' error.

In qmail's documentation, the pop3 port is always specified as "pop3", however in 
Redhat port 110 is
actually referred to as "pop-3", you either want to add pop3 to your etc/services file 
or change the
tcpserver invocation.

Regards,
--Steve





I'd like to forward everything at @domain.com to @domain2.com. i.e. [EMAIL PROTECTED] goes to [EMAIL PROTECTED], and [EMAIL PROTECTED] goes to [EMAIL PROTECTED]. I'm almost positive I've read how to do this in the documentation before but I cannot find it again.
 
Thanks,
 
Cris Daniluk
Digital Services Network, Inc.
 




Cris Daniluk writes:
 > I'd like to forward everything at @domain.com to
 > @domain2.com. i.e. [EMAIL PROTECTED] goes to [EMAIL PROTECTED], and
 > [EMAIL PROTECTED] goes to [EMAIL PROTECTED] I'm almost positive I've
 > read how to do this in the documentation before but I cannot find
 > it again.

Create a virtualdomain for domain.com like this:

echo 'domain.com:alias-domain' >>/var/qmail/control/virtualdomains

Now forward all that mail to domain2 like this:

echo '|forward "$LOCAL"@domain2.com' >~alias/.qmail-domain-default

-- 
-russ nelson <[EMAIL PROTECTED]>  http://crynwr.com/~nelson
Crynwr sells support for free software  | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | can outdo them. Homeschool!




Hi,

Can someone point me to a patch to give me Maildir support for Pine 4.10?

Thanks
Gavin







Gavin Cameron @ mail.itworks.com.au writes:
 > Hi,
 > 
 > Can someone point me to a patch to give me Maildir support for Pine 4.10?

There are (now) two paragraphs on www.qmail.org that talk about that
issue.  Could someone who cares about Pine and/or IMAP please examine
these two patches and tell me if the new one is better in every way
than the old one?

<li>Bloodhounds International wrote maildir patches for the <a
href="http://www.flounder.net/qmail">c-client library</a> (now
distributed by Adam McKenna), which is used by Pine and IMAP2.  Dean
Gaudet has a patch to it that lets you work with <a
href="bh-pine-patch">multiple inboxes</a>.

<li><img src="new.gif" alt="new" width=31 height=12 date="7/31">
Ragnar Kj�rstad has adjusted the maildir patches for pine 4.00 to work
with <a href="ftp://ftp.vestdata.no/pub/linux/c-client/">pine 4.10,
and imapd 4.5</a>.

-- 
-russ nelson <[EMAIL PROTECTED]>  http://crynwr.com/~nelson
Crynwr sells support for free software  | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213  | +1 315 268 9201 FAX   | can outdo them. Homeschool!




I didn't think Pine supported Maildir.  If it does NOW, please post it as
well.

Eric


Gavin Cameron @ mail.itworks.com.au writes:

> Hi,
> 
> Can someone point me to a patch to give me Maildir support for Pine 4.10?
> 
> Thanks
> Gavin
> 
> 
> 


President.and.CEO
The.Public.Network
http://www.thepublic.net
[EMAIL PROTECTED]





Pine doesn't but qmail 
does!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Wju cos 
qmail rules !!!!!!

Quoting [EMAIL PROTECTED]:

> I didn't think Pine supported Maildir.  If it does 
NOW, please post it as
> well.
>
> Eric
>
>
> Gavin Cameron @ mail.itworks.com.au writes:
>
> > Hi,
> >
> > Can someone point me to a patch to give me Maildir 
support for Pine 4.10?
> >
> > Thanks
> > Gavin
> >
> >
> >
>
>
> President.and.CEO
> The.Public.Network
> http://www.thepublic.net
> [EMAIL PROTECTED]
>
> 



--
  --==== Chris Bond ====--
     [EMAIL PROTECTED]
    --================--





I hate replying to a mailing list just to correct someone, when it has
nothing to do with the mailing list.  But oh well.

Chris Bond: Uh, Pine is a mail CLIENT.
Pine can read mbox and mailbox formats.

Qmail is a mail SERVER.  
Qmail can write to mailbox or Maildir formats.

Pine can not read Maildir which is the format "I" am using on my system to
be compatible (and stable).

The original person that posted this email to the list was asking for a
patch for Pine to read Maildir.  If there was such a patch, I was unaware
and wanted more information.  

But a patch is not available for Pine to read Maildir formats.  Therefore
another discussion came up talking about installing IMAP to use Maildir
support.  Unfortantly there seems to be no clean way to install these
patches to IMAP.

IMAP is a daemon that runs on a box on a port and allows IMAP clients to
connect and read mail.

IMAP normally supports mbox and mailbox formats.  On the Qmail main page,
there seems to be a few patches to IMAP to make it read Maildir formats.

Why is this patch for IMAP important?  Pine can read IMAP just fine.
Therefore, you WANT to install IMAP on a server using Maildir to get Pine
to work on the system.

I WILL BE THE TEST BED for this procedure on the webpage and I'll post the
results here when I finish.  Mainly because I miss Pine.  :(


Eric Duncan

President.and.CEO
The.Public.Network
http://www.thepublic.net
[EMAIL PROTECTED]




Chris Bond writes:

> Pine doesn't but qmail 
> does!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Wju cos 
> qmail rules !!!!!!
> 
> Quoting [EMAIL PROTECTED]:
> 
> > I didn't think Pine supported Maildir.  If it does 
> NOW, please post it as
> > well.
> >
> > Eric
> >
> >
> > Gavin Cameron @ mail.itworks.com.au writes:
> >
> > > Hi,
> > >
> > > Can someone point me to a patch to give me Maildir 
> support for Pine 4.10?
> > >
> > > Thanks
> > > Gavin
> > >
> > >
> > >
> >
> >
> > President.and.CEO
> > The.Public.Network
> > http://www.thepublic.net
> > [EMAIL PROTECTED]
> >
> > 
> 
> 
> 
> --
>   --==== Chris Bond ====--
>      [EMAIL PROTECTED]
>     --================--






[EMAIL PROTECTED] writes:

> 
> I hate replying to a mailing list just to correct someone, when it has
> nothing to do with the mailing list.  But oh well.
> 
> Chris Bond: Uh, Pine is a mail CLIENT.
> Pine can read mbox and mailbox formats.
> 
> Qmail is a mail SERVER.  
> Qmail can write to mailbox or Maildir formats.
> 
> Pine can not read Maildir which is the format "I" am using on my system to
> be compatible (and stable).

See in

ftp://ftp.id.wustl.edu/pub/pine/

Not for the latest version of pine, but works very well here for pine3.96
(well, pine cores sometimes when qmail-pop3d zaps messages that pine
assumes are still there, but that's minor).

-Sincerely, Fred
Frederik Lindberg, Inf. Dis, WashU, St. Louis, MO




[EMAIL PROTECTED] writes:

  I hate replying to a mailing list just to correct someone, when it has
  nothing to do with the mailing list.  But oh well.

  [...]

  Pine can not read Maildir which is the format "I" am using on my system to
  be compatible (and stable).
  
  The original person that posted this email to the list was asking for a
  patch for Pine to read Maildir.  If there was such a patch, I was unaware
  and wanted more information.  
  
  But a patch is not available for Pine to read Maildir formats.  Therefore
  another discussion came up talking about installing IMAP to use Maildir
  support.  Unfortantly there seems to be no clean way to install these
  patches to IMAP.

As pointed out elsewhere in this thread, thare are multiple patches that
let pine read maildir folders.  Check the qmail web site.

  
  Why is this patch for IMAP important?  Pine can read IMAP just fine.
  Therefore, you WANT to install IMAP on a server using Maildir to get Pine
  to work on the system.

No, you don't.
  
  
Faried.
-- 
HALL MONITOR





[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] wrote:
> But a patch is not available for Pine to read Maildir formats.  Therefore
> another discussion came up talking about installing IMAP to use Maildir
> support.  Unfortantly there seems to be no clean way to install these
> patches to IMAP.

Not so. I have a set of patches that cleanly applies to the UW IMAP server.

http://www.davideous.com/imap-maildir/

 - David Harris
   Principal Engineer, DRH Internet Services






I have successfully configured ssh-client
(kindof a telnet client) on my Windows 95/NT
PC. It is also configured to do secure port
forwarding, i.e. my mail client communicates
with the local ssh client which tunnels all 
TCP/IP packets securely to the machine which
runs POP & SMTP daemons (and sshd daemon).

How can I configure the POP & SMTP server 
to ONLY accept secure port forwarding requests ?
In other words, is it possible to configure
POP & SMTP to reject any TCP/IP packets other
than the ones that originate on the local 
server box from the sshd daemon ?

Your help will be very much appreciated. Thanks.

_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com





On Sat, 31 Jul 1999, Dinesh Punjabi wrote:

> I have successfully configured ssh-client (kindof a telnet client) on
> my Windows 95/NT PC. It is also configured to do secure port
> forwarding, i.e. my mail client communicates with the local ssh client
> which tunnels all TCP/IP packets securely to the machine which runs
> POP & SMTP daemons (and sshd daemon).
> 
> How can I configure the POP & SMTP server to ONLY accept secure port
> forwarding requests ? In other words, is it possible to configure POP
> & SMTP to reject any TCP/IP packets other than the ones that originate
> on the local server box from the sshd daemon ?

Assuming you have installed tcpserver you add rules to smtp.rules (and
thence to smtp.cdb).

If you're using tcpwrappers, then the rules go into hosts.allow and
hosts.deny

without knowing how you have setup SMTP and POP on your system its
impossible to help further.

How do you start qmail-smtpd and qmail-pop3d?

Richard Letts





Thanks for your response. Not sure if tcpwrappers
is the same thing as invoking qmail smtp 
using tcpserver. I am using Eudora's latest qpopper
package. 

--- [EMAIL PROTECTED] wrote:
> On Sat, 31 Jul 1999, Dinesh Punjabi wrote:
> 
> > I have successfully configured ssh-client (kindof
> a telnet client) on
> > my Windows 95/NT PC. It is also configured to do
> secure port
> > forwarding, i.e. my mail client communicates with
> the local ssh client
> > which tunnels all TCP/IP packets securely to the
> machine which runs
> > POP & SMTP daemons (and sshd daemon).
> > 
> > How can I configure the POP & SMTP server to ONLY
> accept secure port
> > forwarding requests ? In other words, is it
> possible to configure POP
> > & SMTP to reject any TCP/IP packets other than the
> ones that originate
> > on the local server box from the sshd daemon ?
> 
> Assuming you have installed tcpserver you add rules
> to smtp.rules (and
> thence to smtp.cdb).
> 
> If you're using tcpwrappers, then the rules go into
> hosts.allow and
> hosts.deny
> 
> without knowing how you have setup SMTP and POP on
> your system its
> impossible to help further.
> 
> How do you start qmail-smtpd and qmail-pop3d?
> 
> Richard Letts
> 
> 

_____________________________________________________________
Do You Yahoo!?
Free instant messaging and more at http://messenger.yahoo.com





[EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> The command issued was:-
> # fetchmail -f /etc/system.fetchmailrc
> # cat /etc/system.fetchmailrc 
> poll mailhost.brunel.ac.uk protocol pop3 username cspgccm password "secret"
> 
> The response I get is as follows:-
> 91 messages (90 seen) for cspgccm at mailhost.brunel.ac.uk (1119833 bytes).
> skipping message 1 not flushed
> skipping message 2 not flushed
> ...
> skipping message 89 not flushed
> skipping message 90 not flushed
> reading message 91 of 91 (463 bytes) fetchmail: SMTP connect to localhost failed
> fetchmail: SMTP transaction error while fetching from mailhost.brunel.ac.uk
> fetchmail: Query status=10
> 
> There was actually one new message in the mailbox (#91).
> 
> Would you be able to shed some light on what is happening, and how the
> problem can be solved?

For starters, it looks like you don't have a local sendmail daemon running
in listener mode.
-- 
                <a href="http://www.tuxedo.org/~esr">Eric S. Raymond</a>

Sometimes it is said that man cannot be trusted with the government
of himself.  Can he, then, be trusted with the government of others?
        -- Thomas Jefferson, in his 1801 inaugural address




Hello,
 I recently install qmail on a BSDI 4.01 server, and I'm having a really
bad time trying to get it running.  I read the HOWTO located here
http://www.flounder.net/qmail/qmail-howto.html#10 I did everything as
explained, but I'm getting this error in /var/log/qmail/qmail-smtpd:

xxxxxx.xxxxxxx tcpserver: fatal: unable to bind: address already used

I dug through the archives and found someone having the same problem,
but there were no real answers as to why it was happening.  I commented
out anything referring to SMTP,POP,POP3,port 25 or 110 in inetd.conf.  I
also ran netstat to see if there was anything using the ports, and there
doesn't appear to be.  I even went as far as to comment out the
reference to SMTP in /etc/services thinking it may somehow reserve that
port for sendmail.  I knew this couldn't be the case, but I'm getting
desperate at this point.  Has anyone ever had this problem and actually
corrected it?  Any help would be greatly appreciated!!  Please let me
know if I'm missing something.

Thank you,
Robert




After you commented out the sendmail line in your inetd.conf file, you
made sure that you also killed the sendwhale process as well, didnt you?

ps auxw | grep sendmail

should show you whats running. Also there is a utility that can tell you
what program is using what port, but i cant think of the name right now.

On Sat, 31 Jul 1999, Robert wrote:

>Hello,
> I recently install qmail on a BSDI 4.01 server, and I'm having a really
>bad time trying to get it running.  I read the HOWTO located here
>http://www.flounder.net/qmail/qmail-howto.html#10 I did everything as
>explained, but I'm getting this error in /var/log/qmail/qmail-smtpd:
>
>xxxxxx.xxxxxxx tcpserver: fatal: unable to bind: address already used
>
>I dug through the archives and found someone having the same problem,
>but there were no real answers as to why it was happening.  I commented
>out anything referring to SMTP,POP,POP3,port 25 or 110 in inetd.conf.  I
>also ran netstat to see if there was anything using the ports, and there
>doesn't appear to be.  I even went as far as to comment out the
>reference to SMTP in /etc/services thinking it may somehow reserve that
>port for sendmail.  I knew this couldn't be the case, but I'm getting
>desperate at this point.  Has anyone ever had this problem and actually
>corrected it?  Any help would be greatly appreciated!!  Please let me
>know if I'm missing something.
>
>Thank you,
>Robert
>

  _    __   _____      __   _________      
______________  /_______ ___  ____  /______  John Gonzalez/Net.Tech
__  __ \ __ \  __/_  __ `__ \/ __  /_  ___/ MDC Computers/netMDC!
_  / / / `__/ /_  / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052
/_/ /_/\___/\__/ /_/ /_/ /_/\__,_/  \___/ http://www.netmdc.com
[---------------------------------------------[system info]-----------]
  3:45pm  up 9 days, 38 min,  3 users,  load average: 0.02, 0.09, 0.08





I had similar whoas from time to time with ports.  One thing always comes
to mind, "Did you check to see if anything is running in mem that is using
it?  I.e. reboot?"

Try looking through your rc files in /etc for anything that has smtp in the
line.  

[root@box1] cat /etc/rc* | grep smtp

or

[root@box1] cat /etc/rc* | grep 25

If anything is found, comment them out before booting.  After all of what
you described below and the above, there seems to be nothing left. 
Firewall?  I use a dummy net device that gives this issue from time to time
on my mail server.  I just flush/restart it.


Eric Duncan



Robert writes:

> Hello,
>  I recently install qmail on a BSDI 4.01 server, and I'm having a really
> bad time trying to get it running.  I read the HOWTO located here
> http://www.flounder.net/qmail/qmail-howto.html#10 I did everything as
> explained, but I'm getting this error in /var/log/qmail/qmail-smtpd:
> 
> xxxxxx.xxxxxxx tcpserver: fatal: unable to bind: address already used
> 
> I dug through the archives and found someone having the same problem,
> but there were no real answers as to why it was happening.  I commented
> out anything referring to SMTP,POP,POP3,port 25 or 110 in inetd.conf.  I
> also ran netstat to see if there was anything using the ports, and there
> doesn't appear to be.  I even went as far as to comment out the
> reference to SMTP in /etc/services thinking it may somehow reserve that
> port for sendmail.  I knew this couldn't be the case, but I'm getting
> desperate at this point.  Has anyone ever had this problem and actually
> corrected it?  Any help would be greatly appreciated!!  Please let me
> know if I'm missing something.
> 
> Thank you,
> Robert


President.and.CEO
The.Public.Network
http://www.thepublic.net
[EMAIL PROTECTED]





I also tried:
cat /etc/* | grep smtp

All references were commented out or were those that I made in /etc/rc
for starting the service except a couple.  There were 8 lines in the
sendmail.cf file.  I shouldn't need to comment those out should I?  I
have disabled the daemon, and it isn't running so it wouldn't use that
would it??

[EMAIL PROTECTED] wrote:
> 
> I had similar whoas from time to time with ports.  One thing always comes
> to mind, "Did you check to see if anything is running in mem that is using
> it?  I.e. reboot?"
> 
> Try looking through your rc files in /etc for anything that has smtp in the
> line.
> 
> [root@box1] cat /etc/rc* | grep smtp
> 
> or
> 
> [root@box1] cat /etc/rc* | grep 25
> 
> If anything is found, comment them out before booting.  After all of what
> you described below and the above, there seems to be nothing left.
> Firewall?  I use a dummy net device that gives this issue from time to time
> on my mail server.  I just flush/restart it.
> 
> Eric Duncan
> 
> Robert writes:
> 
> > Hello,
> >  I recently install qmail on a BSDI 4.01 server, and I'm having a really
> > bad time trying to get it running.  I read the HOWTO located here
> > http://www.flounder.net/qmail/qmail-howto.html#10 I did everything as
> > explained, but I'm getting this error in /var/log/qmail/qmail-smtpd:
> >
> > xxxxxx.xxxxxxx tcpserver: fatal: unable to bind: address already used
> >
> > I dug through the archives and found someone having the same problem,
> > but there were no real answers as to why it was happening.  I commented
> > out anything referring to SMTP,POP,POP3,port 25 or 110 in inetd.conf.  I
> > also ran netstat to see if there was anything using the ports, and there
> > doesn't appear to be.  I even went as far as to comment out the
> > reference to SMTP in /etc/services thinking it may somehow reserve that
> > port for sendmail.  I knew this couldn't be the case, but I'm getting
> > desperate at this point.  Has anyone ever had this problem and actually
> > corrected it?  Any help would be greatly appreciated!!  Please let me
> > know if I'm missing something.
> >
> > Thank you,
> > Robert
> 
> President.and.CEO
> The.Public.Network
> http://www.thepublic.net
> [EMAIL PROTECTED]




I also rebooted serveral times, and I'm not running behind any firewalls
or the like.

[EMAIL PROTECTED] wrote:
> 
> I had similar whoas from time to time with ports.  One thing always comes
> to mind, "Did you check to see if anything is running in mem that is using
> it?  I.e. reboot?"
> 
> Try looking through your rc files in /etc for anything that has smtp in the
> line.
> 
> [root@box1] cat /etc/rc* | grep smtp
> 
> or
> 
> [root@box1] cat /etc/rc* | grep 25
> 
> If anything is found, comment them out before booting.  After all of what
> you described below and the above, there seems to be nothing left.
> Firewall?  I use a dummy net device that gives this issue from time to time
> on my mail server.  I just flush/restart it.
> 
> Eric Duncan
> 
> Robert writes:
> 
> > Hello,
> >  I recently install qmail on a BSDI 4.01 server, and I'm having a really
> > bad time trying to get it running.  I read the HOWTO located here
> > http://www.flounder.net/qmail/qmail-howto.html#10 I did everything as
> > explained, but I'm getting this error in /var/log/qmail/qmail-smtpd:
> >
> > xxxxxx.xxxxxxx tcpserver: fatal: unable to bind: address already used
> >
> > I dug through the archives and found someone having the same problem,
> > but there were no real answers as to why it was happening.  I commented
> > out anything referring to SMTP,POP,POP3,port 25 or 110 in inetd.conf.  I
> > also ran netstat to see if there was anything using the ports, and there
> > doesn't appear to be.  I even went as far as to comment out the
> > reference to SMTP in /etc/services thinking it may somehow reserve that
> > port for sendmail.  I knew this couldn't be the case, but I'm getting
> > desperate at this point.  Has anyone ever had this problem and actually
> > corrected it?  Any help would be greatly appreciated!!  Please let me
> > know if I'm missing something.
> >
> > Thank you,
> > Robert
> 
> President.and.CEO
> The.Public.Network
> http://www.thepublic.net
> [EMAIL PROTECTED]





On Sat, 31 Jul 1999, Robert wrote:

> I also rebooted serveral times, and I'm not running behind any firewalls
> or the like.

This should not be such a great mystery.  If tcpserver complains that it
can't bind to a port, then something else must be using this port.

Period.

No exceptions.  Therefore, you need to establish and verify two items of
information:

A) What port tcpserver is trying to bind.  Examine your command line
arguments to tcpserver.

B) What is listening on the same port.  netstat will show you that.  Don't
forget to use the -a option to netstat.





On Sat, 31 Jul 1999, Robert wrote:

> Hello,
>  I recently install qmail on a BSDI 4.01 server, and I'm having a really
> bad time trying to get it running.  I read the HOWTO located here
> http://www.flounder.net/qmail/qmail-howto.html#10 I did everything as
> explained, but I'm getting this error in /var/log/qmail/qmail-smtpd:
> 
> xxxxxx.xxxxxxx tcpserver: fatal: unable to bind: address already used

are you sure sendmail isn't running? 
ps ax | fgrep sendmail

RjL





"D. J. Bernstein" <[EMAIL PROTECTED]> writes:
|    * the address, eight characters long in this example: A B@ARPA
|    * an SMTP command specifying that address: RCPT TO:<"A B"@ARPA>

| So why are you having so much trouble with SMTP-encoded email addresses?

Notice that when qmail sends a bounce message it presents the non-smtp
encoded address in a context where the encoded version is expected,
including the angle brackets:  ``<A B@ARPA>''





Scott Schwartz writes:
> Notice that when qmail sends a bounce message it presents the non-smtp
> encoded address in a context where the encoded version is expected,
> including the angle brackets:  ``<A B@ARPA>''

That's the QSBMF encoding, which is line-delimited and has no special
quoting characters. Why do you think the QSBMF encoding should be the
same as the SMTP encoding?

Correct address handling is conceptually quite straightforward:

   * SMTP writers encode addresses as specified in RFC 821.
   * SMTP readers decode addresses as specified in RFC 821.
   * Standard header writers encode addresses as specified in RFC 822.
   * Standard header readers decode addresses as specified in RFC 822.
   * QSBMF writers encode addresses as specified in the QSBMF spec.
   * QSBMF readers decode addresses as specified in the QSBMF spec.

And so on. Everything works fine if the encoders and decoders are
properly implemented---as they are in MMDF, for example, and in qmail.

---Dan




hello all

I'm tring to set up two qmail-pop3d daemons using tcpserver on a RH 5.2
box.  I've modified the qmail-pop3d.init files and added the service
(vpop-3 108/tcp) and it starts up.

I want to use vchpwd and qmailadmin to host more than one virtual domain.
The INSTALL and FAQ don't cover what to do when you are adding vchkpw and
still keep the original qmail-pop3d service running.

Any advice?

Paul D. Farber II
Farber Technology
Ph. 570-628-5303
Fax 570-628-5545
[EMAIL PROTECTED]





Paul Farber writes:

> I want to use vchpwd and qmailadmin to host more than one virtual domain.
> The INSTALL and FAQ don't cover what to do when you are adding vchkpw and
> still keep the original qmail-pop3d service running.

You can tell tcpserver which IP and port to work with. You can run as many
instances of qmail-pop3d as you want. My host has 2 interfaces and 2 IP for
the public interface. I run 3 tcpserver -> qmail-pop3d. One internal (open)
one external (restricted to some hosts) and one on the alternative IP (a
vmailmgr virtual domain). 

-Sincerely, Fred
Frederik Lindberg, Inf. Dis, WashU, St. Louis, MO




vchkpw uses the same qmail-pop3d.  All you have to do is change your
startup script for qmail to remove the default 'checkpoppasswd' (or
whatever it to called).  Then insert the compiled program
'/home/popusers/bin/vchkpw' in place of it.  Here's my Qmail startup
scripts from BEFORE and AFTER:

Before:

/usr/local/bin/tcpserver -R -H -c 20 0 pop3 /var/qmail/bin/qmail-popup
thepublic.net /var/qmail/users/checkpoppasswd /var/qmail/bin/qmail-pop3d
Maildir &
^- All on one line.

(I know you can break this up, but why complex things?)

See that I am using /var/qmail/users/checkpoppasswd?  This is a modified
checkpoppasswd that I have done.

When you install vchkpw, all you do is change to:

After:

/usr/local/bin/tcpserver -H -R -c 20 0 pop3 /var/qmail/bin/qmail-popup
thepublic.net /home/popusers/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir
&
^- All on one line.

See.  No mystery here.  vchkpw is a different user authentication.  vchkpw
also re-writes several files in the /var/qmail/control/* directory. 
Including virtualdomains and rctphosts.  So back them up before continuing.
 You can edit them later.

vchkpw also rewrites the /var/qmail/users/assign file to it's format.  So
this means any passwords you might have stored here already will be gone. 
You can backup a copy of it and delete what you have.  Then edit the
directories later.

That's basically the procedure for 'upgrading' to vchkpw.  I use the
default qmail-pop3d and smtpd.  As well as Qmail's 4 daemon's running,
hosting close to 200 domains now.  It hasn't flinched.  Not bad for a
little program called Qmail and vchkpw.  :)


Eric Duncan

President.and.CEO
The.Public.Network
http://www.thepublic.net
[EMAIL PROTECTED]



Paul Farber writes:

> hello all
> 
> I'm tring to set up two qmail-pop3d daemons using tcpserver on a RH 5.2
> box.  I've modified the qmail-pop3d.init files and added the service
> (vpop-3 108/tcp) and it starts up.
> 
> I want to use vchpwd and qmailadmin to host more than one virtual domain.
> The INSTALL and FAQ don't cover what to do when you are adding vchkpw and
> still keep the original qmail-pop3d service running.
> 
> Any advice?
> 
> Paul D. Farber II
> Farber Technology
> Ph. 570-628-5303
> Fax 570-628-5545
> [EMAIL PROTECTED]
> 


President.and.CEO
The.Public.Network
http://www.thepublic.net
[EMAIL PROTECTED]


Reply via email to