Vince Vielhaber [EMAIL PROTECTED]
On 18-May-99 Arnt Gulbrandsen wrote:
[EMAIL PROTECTED]
Actually, qmail's VERP should allow you to be 100% successful; and
DSNs won't, since they're not widely supported.
Huh? What's your threshold for "widely supported"? Doesn't sendmail
have
I am in a process of setting up my linux box to relay mail for clients on a
192.168.0.X LAN. I am trying to follow the directions from
http://www.palomine.net/qmail/selectiverelay.html and here is something that
gives me trouble.
linux:/etc# tcpserver -x/etc/tcp.smtp.cdb -u1003 -g103 0 smtp
Looks like you have the SMTP port already running in /etc/inetd
Tony Wade
-Original Message-
From: Denis Voitenko [mailto:[EMAIL PROTECTED]]
Sent: 19 July 1999 09:46
To: [EMAIL PROTECTED]
Subject: relaying setup
I am in a process of setting up my linux box to relay mail for clients on
On Mon, Jul 19, 1999 at 03:46:10AM -0400, Denis Voitenko wrote:
I am in a process of setting up my linux box to relay mail for clients on a
192.168.0.X LAN. I am trying to follow the directions from
http://www.palomine.net/qmail/selectiverelay.html and here is something that
gives me trouble.
This might sound silly, but the line:
tcpserver -x/etc/tcp.smtp.cdb -u1003 -g102 0 smtp /var/qmail/bin/qmail
smtpd
takes action only if I run it after the system is booted and I logged in as
root. The entry in /etc/rc.d/rc.local does not take effect for some reason.
Has anyone encountered this
On Mon, Jul 19, 1999 at 05:25:54AM -0400, Denis Voitenko wrote:
tcpserver is normally installed in /usr/local/bin. However, this
directory is not usually found the system startup scripts' PATH. Try
using the full pathname in /etc/rc.d/rc.local, like this:
/usr/local/bin/tcpserver -x .
This thread died two months ago.
Vince.
On 19 Jul 1999, Arnt Gulbrandsen wrote:
Vince Vielhaber [EMAIL PROTECTED]
On 18-May-99 Arnt Gulbrandsen wrote:
[EMAIL PROTECTED]
Actually, qmail's VERP should allow you to be 100% successful; and
DSNs won't, since they're not widely
qmail Digest 19 Jul 1999 10:00:00 - Issue 702
Topics (messages 27907 through 27931):
CNAME_lookup_failed_temportarily
27907 by: Tom Walsh [EMAIL PROTECTED]
Qmail exited
27908 by: "Sam" [EMAIL PROTECTED]
27909 by: Stefan Paletta [EMAIL PROTECTED]
Tcpserver and
He,
I'am running qmail 1.03 on an RH 6.0 (2.2.5) box and I host mail for special
domain.
Our client's mail server (no Linux/Unix maschine) makes a dial-up connection to
the internet and then want's to to get his emails delivered from our server.
I've heard something about ETRN which is applied
Can anyone please tell me what outputs the
"x-commands" will generate the syntax for utilizing
"x-commands" (i.e. xsenders/xqp/xrec.) within QMAIL Analog?
I have gotten the "z-commands" to give certain outputs
Newbie to QMAIL
Thnx in ADV
Ume
I collect about 2 doz. accts from 2 (soon to be 3)domains. I was forced
to set up a dummy user (mailrelay) that fetchmail delivers all mail to.
This account has a .procmailrc which then sorts the mail and retransmits
to the appropriate local user.
Yan
Sim wrote:
On Fri, 16 Jul 1999, Dave
Vince Vielhaber writes:
This thread died two months ago.
Huh? What's your threshold for "widely supported"? Doesn't sendmail
have something like 80% market share and nice DSN support?
Not to mention the fact that sendmail's market share is 63% and slipping.
--
-russ nelson
Frank,
On Mon, 19 Jul 1999, you wrote:
I'am running qmail 1.03 on an RH 6.0 (2.2.5) box and I host mail for
special domain. Our client's mail server (no Linux/Unix maschine) makes
a dial-up connection to the internet and then want's to to get his
emails delivered from our server.
I've
On Mon, Jul 19, 1999 at 02:10:16PM +0200, Frank Greven wrote:
Ray has provided a solution for the client end, ie. to use fetchmail.
However, on your end, you need to setup a catch-all Maildir for them.
Detailed instructions for this are available in the serialmail package,
which you will need.
Problem:
Sometimes I see a line like that in /var/log/maillog
Jul 19 14:20:17 kserver qmail: 932386817.166513 starting delivery 8: msg
1331273 to local @kserver.localdomain
Jul 19 14:20:17 kserver qmail: 932386817.169277 delivery 8: success:
Last time that happened it was because the reply-to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[snip]
Qmail states that everything is fine, but that message will never be
received.
I know that the e-mail address in the example is wrong, but IMHO it is
wrong behaviour NOT to deliver and NOT to bounce the email.
Unfortunately, "holger"
What are the industry-standard names for the following email services:
-
1) They can have:
any_name@their_domain
and a separate POP for each. (.qmail-any_name)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was wondering how the following would work.
I have a few domains which o am going to run as virtualdomain and others
which are just going to have a smtproute to another server. I want to have
some Virtual users deliver to another machine and
Unfortunately, "holger" @vankoll.de is not the only way to make qmail
behave like that.
I fail to see what you consider erratic behaviour. Qmail received a
message and successfully delivered it to zero recipients.
Where is the sense in delivering to zero recipients?
Can this be called
What happened to email.com mail.com's clue? They're munging
envelope sender addresses by deleting everything up to an equal sign.
This is non-RFC behavior! You can see what I mean by telnetting to
port 25 on an email.com MX and issuing the following smtp commands.
I'm presuming that your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I fail to see what you consider erratic behaviour. Qmail received a
message and successfully delivered it to zero recipients.
Where is the sense in delivering to zero recipients?
Can this be called delivering?
Well, unless I'm mistaken,
Troy Morrison [EMAIL PROTECTED] wrote:
We have a fairly ongoing problem with some of the users at work who don't
seem capable of cleaning out their INBOX, so they end up with 100MB mail
spools with 7000 messages in them.
I had theorized that chunking over the 100MB mailbox was slow, and that
On Mon, Jul 19, 1999 at 01:25:15AM -0400,
Scott Schwartz [EMAIL PROTECTED] wrote:
Russell Nelson [EMAIL PROTECTED] writes:
| Command-line arguments are RFC821 addresses, but body addresses are
| RFC822 addresses.
I'm only talking about the envelope (rfc821 addresses). It's
inconsistent
Bruno Wolff III [EMAIL PROTECTED] writes:
| I ask this here a while back. The answer is that the arguments to qmail-inject
| are raw email addresses, they are NOT encoded.
Shouldn't that also be true of the address in RCPT TO during an SMTP session?
Dave Sill [EMAIL PROTECTED] writes:
| A clever MUA could maintain that
| information separately, but none that I'm aware of actually do.
What about xmh and exmh? (I don't think they properly mutex the cache,
though.)
I am having problems using tcpserver to log messages
I use this command to start my pop server
supervise /var/supervise/qmail/pop3d tcpserver -v 0 pop-3 /usr/sbin/in.pop3d
| setuser qmaill cyclog /var/log/qmail/pop3d/
This command for qmail-send
supervise /var/supervise/qmail/send
most MUA's will only handle mailboxes so big with
acceptable performance: they have to open each message file and
extract various header information. A clever MUA could maintain that
information separately, but none that I'm aware of actually do.
I think the Cyrus IMAP server falls into this
On Mon, Jul 19, 1999 at 12:31:31PM -0400,
Scott Schwartz [EMAIL PROTECTED] wrote:
Bruno Wolff III [EMAIL PROTECTED] writes:
| I ask this here a while back. The answer is that the arguments to qmail-inject
| are raw email addresses, they are NOT encoded.
Shouldn't that also be true of the
Bruno Wolff III [EMAIL PROTECTED] writes:
| No. That address is encoded according to rfc 821.
| Addresses in the headers are encoded according to rfc 822.
I am not talking about rfc822 headers, only about rfc821 envelopes.
To reiterate: qmail-smtpd strips quotes from RFC821 ENVELOPES (the
Scott Schwartz writes:
Bruno Wolff III [EMAIL PROTECTED] writes:
| No. That address is encoded according to rfc 821.
| Addresses in the headers are encoded according to rfc 822.
I am not talking about rfc822 headers, only about rfc821 envelopes.
To reiterate: qmail-smtpd strips quotes
On Mon, Jul 19, 1999 at 09:43:14PM +,
There may be some point of argument if the quoted portion can be accurately
transcribed as an an RFC822 atom, in which case an argument can be made
that quotes can be stripped. However, stripping quotes unilaterally is a
completely broken behavior.
Hello all,
I'm working on a qmail-sql patch and since I want to setup a server farm, it
would make more sense to compile qmail statically. I really only want the
servers to be a bare install. Anyone know if I will see a performance hit by
compiling static? I imagine there will be more memory
Bruno Wolff III writes:
On Mon, Jul 19, 1999 at 09:43:14PM +,
There may be some point of argument if the quoted portion can be accurately
transcribed as an an RFC822 atom, in which case an argument can be made
that quotes can be stripped. However, stripping quotes unilaterally is
On Mon, Jul 19, 1999 at 10:04:47PM +,
Sam [EMAIL PROTECTED] wrote:
If you do not handle the mail for example.com, don't screw around with
example.com's local address. Just pass it along to example.com, and let
them deal with it.
The way that is handled is requoting this that need to
Hello again,
We're in the process of switching to qmail but we have a cutomer who has 18
characters in their email. qmail is only allowing 15. is there anyway to
change the 15 to something higher?
Is there any documentation on aliasing?
I'd like to take all of my emails from one
Bruno Wolff III writes:
On Mon, Jul 19, 1999 at 10:04:47PM +,
Sam [EMAIL PROTECTED] wrote:
If you do not handle the mail for example.com, don't screw around with
example.com's local address. Just pass it along to example.com, and let
them deal with it.
The way that is
To make this more concrete, consider the following:
RCPT TO:"A B"@ARPA
That can be parsed by the grammer given in rfc821. On the other
hand, this cannot:
RCPT TO:A B@ARPA
because ``A B'' contains an SP, which must be quoted somehow.
If you send a message via qmail-smtpd to
If you look at the "Joe\,Smith" example in rfc 821, it speciifcally says
this represents a 9 character string with a comma being the fourth character.
However, only the recipient's mail server cares about Joe,Smith.
Intermediate mail servers don't care about it.
Exactly. That is why any
Hi all.
According to RFC822:
4.3.1. RETURN-PATH
This field is added by the final transport system that
delivers the message to its recipient. The field is intended
to contain definitive information about the address and route
back to the message's
On Mon, Jul 19, 1999 at 07:24:41PM -0400,
David Villeger [EMAIL PROTECTED] wrote:
Return-Path is added by the *final* transport system. So why is it added by
qmail-inject?
Are you sure about that? The man page indicates that it deletes return-path
headers. It does say that it will set
Another way I have found to do this is to write a script that runs from a
cron job say ~ every 10 minutes that checks if the customer has dialled into
you term server. If they have then the script just does a
'killall -HUP qmail-send' .. which forces everything deferred in the queue
to be sent
Bruno Wolff III [EMAIL PROTECTED] writes:
| The original envelope address is:
| A B@ARPA
|
| It is only encoded as:
| "A B"@ARPA
Rather than arguing about what "is" means, I simply observe (again)
that for any value of "is" qmail-smtpd wrongly transforms "A B"@ARPA
into A B@ARPA, and wrongly
David Villeger writes:
On the same subject, if I send an email message to [EMAIL PROTECTED] without
the Return-Path field (e.g. by using qmail-queue) but using VERP (so that
the envelop sender becomes [EMAIL PROTECTED]), the
email.com server writes the Return-Path as [EMAIL PROTECTED]
Sam writes:
David Villeger writes:
On the same subject, if I send an email message to [EMAIL PROTECTED] without
the Return-Path field (e.g. by using qmail-queue) but using VERP (so that
the envelop sender becomes [EMAIL PROTECTED]), the
email.com server writes the Return-Path as
On Mon, Jul 19, 1999 at 03:35:10PM -0400, Tim Hunter wrote:
I am having problems using tcpserver to log messages
I use this command to start my pop server
supervise /var/supervise/qmail/pop3d tcpserver -v 0 pop-3 /usr/sbin/in.pop3d
| setuser qmaill cyclog /var/log/qmail/pop3d/
This
Woops that should be killall -ALRM qmail-send
-Original Message-
From: Simon Elder [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: Tuesday, 20 July 1999 9:37
Subject: Re: ETRN
Another way I have found to do this is to write a script that runs from a
cron job say ~ every
On Mon, Jul 19, 1999 at 08:03:45PM -0400,
Scott Schwartz [EMAIL PROTECTED] wrote:
Bruno Wolff III [EMAIL PROTECTED] writes:
| The original envelope address is:
| A B@ARPA
|
| It is only encoded as:
| "A B"@ARPA
Rather than arguing about what "is" means, I simply observe (again)
that
I've read the "tips" section at qmail.org, but I don't quit understand how to
fix this problem.
I can't send mail to anybody unless I have that person's domain listed in the
rcpthosts file. How can this be fixed?
Quinn
===
---
~ Quinn P.
On Mon, Jul 19, 1999 at 10:09:07PM -0400, Quinn Coldiron wrote:
FAQ 5.4
I've read the "tips" section at qmail.org, but I don't quit understand how to
fix this problem.
I can't send mail to anybody unless I have that person's domain listed in the
rcpthosts file. How can this be fixed?
--
On Mon, Jul 19, 1999 at 06:28:05PM -0700, Sienna wrote:
qmail doesn't really limit the size of the local part of an email
address. Perhaps the OS is limiting the length of the username, when
qmail uses the qmail-getpw call to determine if an address is local. To
test this, run:
50 matches
Mail list logo
