qmail Digest 31 May 1999 10:00:01 -0000 Issue 657

Topics (messages 26122 through 26135):

dynamic IP + maildirsmtp/remote dialup server solved.. one question
        26122 by: Adam H <[EMAIL PROTECTED]>

mail relay for any IP,but only for valid logins - how??
        26123 by: Keith Burdis <[EMAIL PROTECTED]>

tcp-wrappers, qmail-1.03 and Solaris 2.7
        26124 by: Eric Dahnke <[EMAIL PROTECTED]>

Fwd: Warning: message 10nNFt-0004ji-00 delayed 24 hours
        26125 by: Frederik Lindberg <[EMAIL PROTECTED]>
        26129 by: "Sam" <[EMAIL PROTECTED]>
        26131 by: Jason Haar <[EMAIL PROTECTED]>
        26134 by: Justin Bell <[EMAIL PROTECTED]>

Homebrew list performance?
        26126 by: Joe Mahan <[EMAIL PROTECTED]>

~/Mailbox and "you have mail"
        26127 by: Balazs Nagy <[EMAIL PROTECTED]>
        26132 by: Wilson Fletcher <[EMAIL PROTECTED]>

migrating to sendmail in a different way.
        26128 by: Engineer <[EMAIL PROTECTED]>

local delivery. different domain, different user
        26130 by: Joao Paulo Pagaime <[EMAIL PROTECTED]>

...no mailbox...(#5.1.1) and other stuff
        26133 by: Wilson Fletcher <[EMAIL PROTECTED]>

Qmail-1.03, FreeBSD 3.2, DNS lookup problems?
        26135 by: Andrzej Szydlo <[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]


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


I realized I could use PHP3's $REMOTE_ADDR variable and call with
lynx-dump in my ip-up script... and then have php exec maildirsmtp with
the IP.
One thing, how do I know when mail has finihsed being transferred from
server to dialup so I can hang up the modem?


Thanks,
Adam






On Wed 1999-05-26 (17:16), olli wrote:
> On Sun, 23 May 1999, Per Birkeby wrote:
> 
> I'm sorry for noise, but I didn't find that in FAQ.. Well , I need to
> allow mail relaying for anyone ( if it is easy to do this on a per user
> basis  - very fine ) who have valid pop3/smtp account on my server. In
> /etc/tcp.smtp I can allow IPs.. Is it possible to allow/deny users with
> tcpserver? I'll be glad to see a name of the manual or url where I can
> find detailed explanation of tcp.cmtp used with tcpserver. Sorry -
> unfortunately I've got a lot of other work , so it's almost impossible
> for me (at least in 2 nearest weeks) to search the web w/ this
> question... Could anyone help,please? :)~

Perhaps you need this:

  Russell Nelson has a system to allow relaying to any host which
  authenticates itself through a POP3 connection. Only thing is, it's
  dependent upon the user to do the right thing, because at least Eudora and
  Netscape send mail before checking for new mail. You can turn that feature
  off, but still the user needs to get into the habit of checking for mail
  before sending mail. 

See www.qmail.org under the User-Contributed Software for Qmail section.

> Bye.Olli.

  - Keith
-- 
Keith Burdis - MSc (Com Sci) - Rhodes University, South Africa  
Email   : [EMAIL PROTECTED]
WWW     : http://www.rucus.ru.ac.za/~keith/
IRC     : Panthras                                          JAPH

"Any technology sufficiently advanced is indistinguishable from a perl script"

Standard disclaimer.
---




I've had this problem with Linux, upon upgrading to tcp_wrappers-7.6-4
problem solved.

Search the archives, and you'll find a few messages about this problem.

Regards - eric

Mark Recio escribi�:
> 
> Hello!
> 
> I had the tcp-wrappers/relayclient happily running along on one of our
> Solaris 2.5.1 boxes with out any problems.
> 
> However, we have just upgraded to Solaris 2.7, recompiled tcp-wrappers
> for sunos5, and now when a user attempts to send a message, they get a
> time out message for port 25 of the given machine. Without washing the
> connection through tcpd, everything works fine.
> 
> Anyone have any suggestions?
> 
> Thanks,
> 
> Mark
> 
> --
> Mark I. Recio
> mailto:[EMAIL PROTECTED]

-- 
+ + + + + + + + + + + + + + + + + + + +
Spark Sistemas E-mail
   - presentado por IWCC Argentina S.A.
   Tel: 4702-1958
   e-mail: [EMAIL PROTECTED]
+ + + + + + + + + + + + + + + + + + + +




Jason Haar writes:

> On Sat, May 29, 1999 at 01:37:29PM -0400, Sam wrote:
> hours" messages as bounces - it bumped me into djb's "possibly badaddress
> list" and some weeks later I got a monitoring message from ezmlm checking [...]
> considered a 4-hour warning to be a bounce... I mentioned it to Dan and he
> didn't think it was a problem. As it doesn't actually drop you from the list
> after a warning-bounce, it's probably not a bug - but a feature ;-)

Not a feature, maybe a bug. One ca argue that dealing optimally with any
stupidity is necessary. Others draw the line at rfcs.

If you care to specify exaclty how DSN messages that are not bounces look,
I can add it to the ezmlm-idx version of ezmlm-weed.

Again, the problem is the delivery notification. Who cares that some dumb
host was unable to deliver the message? It's pointless noise. When it comes
to the communication endpoints, E-mail is like UDP. Only a second E-mail
(reply from the recipient) gives the relevant info - that the recipient has
read the message and acted on it.


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




On Sun, 30 May 1999, Frederik Lindberg wrote:

> If you care to specify exaclty how DSN messages that are not bounces look,
> I can add it to the ezmlm-idx version of ezmlm-weed.

It is specified fully by RFCs 1891 through 1894.  Mostly 1894, but some
details are in the other three. Briefly, it is a multipart MIME message. 
The top level will have a content-type of multipart/report, and the second
section of the multipart MIME message will be a message/delivery-status.

This is how all DSNs look like.  You will need to further distinguish
delayed mail notifications from failure notifications by parsing the
message/delivery-status subpart.  This section will contain one or more
sub-sections, separated by blank lines.  One section per receipient.  But
since you're dealing with Qmail's output, you will always have one
sub-section to deal with.  Each sub-section consists of RFC822 headers. 
You are looking for a sub-section with the header "Action: delayed". Since
you'll be dealing with bounces to VERPs, you will not need to parse the
other headers which specify the address of the receipient. 





On Sun, May 30, 1999 at 02:49:58PM +0000, Frederik Lindberg wrote:
> Again, the problem is the delivery notification. Who cares that some dumb
> host was unable to deliver the message? It's pointless noise. When it comes

"It's pointless noise" - that is an opinion I'm afraid - not a fact...

I think of Email the other way: The message _did_ get there unless I hear
otherwise (via DSN/bounces). After all, it's the 90's - not the 70's....


-- 
Cheers

Jason Haar

Unix/Network Specialist, Trimble NZ
Phone: +64 3 3391 377 Fax: +64 3 3391 417




On Mon, May 31, 1999 at 08:40:28AM +1200, Jason Haar wrote:
# On Sun, May 30, 1999 at 02:49:58PM +0000, Frederik Lindberg wrote:
# > Again, the problem is the delivery notification. Who cares that some dumb
# > host was unable to deliver the message? It's pointless noise. When it comes
# 
# "It's pointless noise" - that is an opinion I'm afraid - not a fact...
# 
# I think of Email the other way: The message _did_ get there unless I hear
# otherwise (via DSN/bounces). After all, it's the 90's - not the 70's....

unless it's from a mailing list

-- 
/- [EMAIL PROTECTED] --------------- [EMAIL PROTECTED] -\
|Justin Bell  NIC:JB3084| Time and rules are changing.         |
|Pearson                | Attention span is quickening.        |
|Developer              | Welcome to the Information Age.      |
\-------- http://www.superlibrary.com/people/justin/ ----------/




I am using an existing perl script to generate messages, and send them
(from the script), basically one at a time. Performance is slow, (a
basic qmail installation performs not better than sendmail) although I
have not yet done any tweaking at all.

Question:

    Is it neccessary to use a "qmail format" mailing list to take
advantage of concurrency? If so, I'll have to modify the perl script.
I'd just like to know before I go twiddling all the knobs on qmail.

Thanks,
Joe





On Sat, 29 May 1999, Brian Butler wrote:

> Problem is that everything "detecting" mail checks for the
> /var/spool/mail/user file, not ~/Mailbox.  I can't find documentation about
> how to have the "you have mail"/"you have new mail" etc. be based on the
> "real" mailbox in the home directory.

Give a chance to $MAIL and $MAILPATH variables.  $MAIL is intended to
specify your primary inbox file and $MAILPATH is a colon separated list of
your inbox mail folders (you can specify alternative arrival msg for each
element).

> Another issue is this:  I intend to get procmail (or is there a better way?)
> to sort out mailing lists from BOTH the  mailboxes written to by qmail, and
> the fetchpop'd ones.  Has anyone been through this?  I'm reading the man
> pages and they look good, but I'm looking for pointers in this particular
> unique situation.

Where can you run procmail?  I think you have to put procmail to .forward
and to .qmail too.  In this case you can specify alternative procmailrc
files (for default delivery).
-- 
Regards: Kevin (Balazs)





On Sunday, May 30, 1999 2:48 PM, Balazs Nagy [SMTP:[EMAIL PROTECTED]] wrote:
> On Sat, 29 May 1999, Brian Butler wrote:
>
> > Problem is that everything "detecting" mail checks for the
> > /var/spool/mail/user file, not ~/Mailbox.  I can't find documentation 
about
> > how to have the "you have mail"/"you have new mail" etc. be based on 
the
> > "real" mailbox in the home directory.

That's strange I just followed the INSTALL procedures and it seems to work 
OK for me and I'm certainly no guru. (I'm using mutt at the client end).

Did you follow the instruction in ... (???) (INSTALL.vsm ???) ie. create 
links in var/spool/mail to $HOME/Mailbox for each user ?





Thanx ..

Actually  I have following configurations .  

/usr/var/spool/mail/  which includes 24000 mailboxes (sendmail )

I have only one MX and two machines so at one of the MX I have to
constantly update my alias file whenever I create users at second pop so
alias file is constantly updating ..

I have been given a new machine with more capacity and I have to shift
the MX to this machine . Now I have decided to go towards qmail..

I have made the tar of mail directory and shifted it to the new machine
with the same passwd file and alias file. Now mailboxes are there at
/var/spool/mail of new machine .

Now how would I configure qmail in this term . I had already made qmail
to deliver local and international mail at its default format now I
would like to sense my users email boxes .

I don't want mails at /usr/var/spool/mail since it makes quite slow
(qmail documentation says) . I want to use qmail at its best any idea
with its orginality??

Anyway thanx  for your detailed answer..

Regards
Engineer.





Hello all

I would like to have qmail setup to receive mail
for 2 different domains. But would like the addresses
from those domains to be routed for different users on
the machine. Example:
        name@domain1 --> user 'abc'
        name@domain2 --> user 'def'
So I went to the users/assign and setup 
[EMAIL PROTECTED]
[EMAIL PROTECTED]
But qmail-lspawn doesn't seem to find these addresses.
I did a little snooping on qmail-lspawn.c and found out that
qmail-lspawn truncates the domain part  'r[at] = 0;', so
theres no way it will find out the address/user properly.

Can someone help me?  What am I doing wrong? Is there other
way of doing this ?

Thanks,
Joao Pagaime

PS: mail does get to "qmail-spawn" but it doesn't find out
the addresses on the table...





I had this problem and searching the lists on www-archive.ornl.gov was no 
help.

There seems to be a huge amount of messages with this problem so I wonder 
how many people out there might have had the same problem I had but with no 
solution offered.

So it appears the problem was with my home directory permissions. I haven't 
investigated it extensively but they were something like 750 (or something 
like that). Anyway at present I just changed them to 777 mainly because it 
was midnight and it was only a home PC that's not really connected often 
(once I get the good oil from you guys on what they should be, I'll change 
them).

So what should the permissions be for effective operation. (i.e.. I think I 
screwed up all the permissions on my system one night (really late) by 
doing a recursive chmod (almost as painful as rm *.*)) and oops,  I was in 
/ and logged in as root. (but at least NOTHING is [S|G]uid on my system at 
the moment because everything got reset.).

Incidently the way I discovered this was to try using .../users/assign and 
qmail-newu. This still failed for the user I was trying to send to but gave 
a more informative message i.e. instead of saying "...no mailbox..." it 
said something like "...can't access /home/frodo...permission denied..."

Anyway a definitive answer (or reference link) on the permissions for all 
qmail related stuff would be good.

While I'm at it. What's the best source of newbie info for setting up qmail 
at home on a dial up link. i.e.. I'd like to register my own domain name 
and have the mail stored on the ISP server and then traded when I connect 
my server (there is a use for 486 PCs after all).

Also, I see a lot of soap box speeches but are there any good references 
that explain why sendmail etc. suck and qmail is supposedly so good ? A 
comparative study would be good.

Thanks

Wilson Fletcher




Hello,

I'm running mail-1.03 on FreeBSD-3.2-STABLE, compiled from ports.
It fails to deliver messages to remote hosts. The log says:

May 31 11:29:40 hp qmail: 928142980.850128 new msg 6503
May 31 11:29:40 hp qmail: 928142980.852225 info msg 6503: bytes 196 from 
<[EMAIL PROTECTED]> qp 24242 uid 82
May 31 11:29:40 hp qmail: 928142980.966943 starting delivery 5: msg 6503 to 
remote [EMAIL PROTECTED]
May 31 11:29:40 hp qmail: 928142980.969027 status: local 0/10 remote 1/20
May 31 11:29:41 hp qmail: 928142981.245645 delivery 5: failure: 
Sorry,_I_couldn't_find_any_host_named_?????????._(#5.1.2)/

The host to which MX points does exist. It receives messages from other
systems except for this particular one. nslookup on the qmail box
finds it. Why qmail cannot find the host?

Same configuration worked for me on FreeBSD 3.1-STABLE, before I upgraded
to 3.2-STABLE.

Thanks for any suggestions.

Andrzej


Reply via email to