When bouncesaying messages bounce I get a failure notice. Usually it
is about bouncing to username which does not exist because the
original bounce messages was spam from a bogus email address. Is
there any way to stop getting these bounced bounced messages and
still get legitimate failed
On Thu, Mar 29, 2001 at 07:30:38PM +0200, Filip Salomonsson wrote:
[snip]
Qmail isn't handling virtual domains correctly, as far as I can tell.
Wut?
Greetz, Peter.
On Thu, Mar 29, 2001 at 07:30:38PM +0200, Filip Salomonsson wrote:
[snip]
Qmail isn't handling virtual domains correctly, as far as I can tell.
Peter van Dijk:
Wut?
Greetz, Peter.
From the dot-qmail man page:
When qmail-local forwards a message as instructed in
On Fri, Mar 30, 2001 at 05:03:59PM +0200, Filip Salomonsson wrote:
[snip]
Oh, great. here's a line from my virtualdomains file:
netdesign.se:salo
in ~salo/.qmail-filip:
./Maildir/
[EMAIL PROTECTED]
in ~salo/.qmail-filip-owner:
[EMAIL PROTECTED]
A message is recieved for
"Filip Salomonsson" [EMAIL PROTECTED] wrote:
A message is recieved for [EMAIL PROTECTED], delivered locally to
salo-filip, which puts the message in my maildir and forwards a copy to
[EMAIL PROTECTED] The envelope sender for the forwarded message is set to
[EMAIL PROTECTED], just as the docs say
Filip Salomonsson:
The -owner files render themselves completely useless.
Dave Sill:
So create ~salo/.qmail-salo-filip-owner or ~salo/.qmail-salo-default.
Well, that's what I've done. Works like a charm. But what if there was a
salo@ address(and/or salo-filip@ with a corresponding -owner
Filip Salomonsson:
Also, any message sent to [EMAIL PROTECTED] will have "Delivered-To:
[EMAIL PROTECTED]" in the header, which is confusing.
[EMAIL PROTECTED] would be "correct". As would
[EMAIL PROTECTED] (the "me" control file says
kepler.netdesign.se).
Peter van Dijk:
Delivered-To
On Fri, Mar 30, 2001 at 06:56:06PM +0200, Filip Salomonsson wrote:
Me:
Sure. But while it's there, why not make it as useful as possible? I'm not
saying that there's anything wrong with the way Delivered-To lines are
written today. I'm only suggesting something that I think would
be a
Hi!
I wonder if anyone has written a real "bouncesaying" (qmails bouncesaying
just exits with an exit code that makes qmail-local do the actual
bouncing.
I want to pipe a message to bouncesaying from mutt, like this:
| boucesaying "No subject specified"
and it should
* Johan Almqvist [EMAIL PROTECTED] [010329 11:21]:
I wonder if anyone has written a real "bouncesaying" (qmails bouncesaying
just exits with an exit code that makes qmail-local do the actual
bouncing.
With a few pointers from Frank Tegtmeyer, I've now made what I wanted
myself. May
On Thu, Mar 29, 2001 at 03:06:40PM +0200, Johan Almqvist wrote:
* Johan Almqvist [EMAIL PROTECTED] [010329 11:21]:
I wonder if anyone has written a real "bouncesaying" (qmails bouncesaying
just exits with an exit code that makes qmail-local do the actual
bouncing.
With a fe
- It says 'this is the qmail-send program'. It is not. 'qmail-send' is
not a fixed string in the QSBMF, so why not change it?
True - when I first wrote it I took the text from Qmails bounces.
Feel free to change it :)
Regards, Frank
Johan Almqvist:
With a few pointers from Frank Tegtmeyer, I've now made what I wanted
myself. Maybe someone else finds this useful...
Peter van Dijk:
Without testing it, a short glance over the code reveals one quirk and
one change I'd like:
- You are using a predictable filename in /tmp
Thus spake Johan Almqvist ([EMAIL PROTECTED]):
I wonder if anyone has written a real "bouncesaying" (qmails bouncesaying
just exits with an exit code that makes qmail-local do the actual
bouncing.
And what is your problem with that?
Felix
* Felix von Leitner [EMAIL PROTECTED] [010329 19:43]:
Thus spake Johan Almqvist ([EMAIL PROTECTED]):
I wonder if anyone has written a real "bouncesaying" (qmails bouncesaying
just exits with an exit code that makes qmail-local do the actual
bouncing.
And what is your problem wit
Thus spake David Benfell ([EMAIL PROTECTED]):
do with it except try to unsubscribe, as I have. But Debian doesn't
use a rational mailing list manager. I try to follow its directions
and I still get mail from the lists. I want this killed.
Hundreds of people subscribe and unsubscribe on
On Mon, Feb 05, 2001 at 09:49:58AM +0100, Felix von Leitner wrote:
Thus spake David Benfell ([EMAIL PROTECTED]):
do with it except try to unsubscribe, as I have. But Debian doesn't
use a rational mailing list manager. I try to follow its directions
and I still get mail from the lists.
On Mon, Feb 05, 2001 at 08:45:17AM -0800, David Benfell wrote:
[unsubscribing for Debian lists]
I have made several attempts to unsubscribe from their lists and I've
tried to contact them. It doesn't work.
But it can't be user error, right?
I don't know why and it's not my job to know why.
On Mon, Feb 05, 2001 at 03:37:29PM -0500, Alex Pennace wrote:
Subscription and unsubscription works for everyone else. Subscription
obviously worked for you, but you can't manage unsubscription. Why is
this Debian's problem?
Self-righteousness only goes so far.
You invited yourself to
is it possible to somehow use a newline command in the message that the
bouncesaying command sends?
so that the error mail from the sending smtp server back to the envelope
sender would contain deliberate line breaks?
wolfgang
On Sun, Feb 04, 2001 at 05:40:19PM +0100, Wolfgang Zeikat wrote:
is it possible to somehow use a newline command in the message that the
bouncesaying command sends?
try
|bouncesaying "`cat filename`"
or
|bouncesaying "`printf 'line1\nline2'`"
you can
On Sun, Feb 04, 2001 at 10:28:16PM -0800, David Benfell wrote:
I see the error message printed out, but watching the log, I don't see
the bounce going out. Looking at some old mail, I see that
bouncesaying doesn't, by itself, bounce anything.
bouncesaying exits with 100, which qmail
Hello all,
I'm trying to get maildrop to invoke bouncesaying. This is what I
have right now:
if ( /lists.debian.org/ )
{
`/var/qmail/bin/bouncesaying "Numerous attempts to unsubscribe from all Debian
lists have failed."`
to /dev/null
}
I see the error message p
hello friends
i have created ~alias/.qmail-prashant file , file contents are
|bouncesaying "please, try [EMAIL PROTECTED]"
file permissions 644 then alos tried with 755 even 777 not working
i have also inserted space between "|" and word "bounce
What do the logs say?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 02, 2001 6:00 AM
To: [EMAIL PROTECTED]
Subject: urgent bouncesaying not working
hello friends
i have created ~alias/.qmail-prashant file , file contents
[EMAIL PROTECTED] writes:
file permissions 644 then alos tried with 755 even 777 not working
Without meaning to sound like a broken record, "what do the logs say?"
You have all the information you need at your fingertips, and we lack
it completely. You don't seem to be doing anything
The man page for bouncesaying is rather misleading.
bouncesaying feeds each new mail message to program with
the given arguments. If program exits 0, bouncesaying
prints error and bounces the message.
This isn't true so far as I can tell. bouncesaying does
David Dyer-Bennet [EMAIL PROTECTED] wrote:
The man page for bouncesaying is rather misleading.
[...]
| bouncesaying "This address no longer accepts mail"
[EMAIL PROTECTED]
As described by the man page, this should send a bounce message, and
then deliver a copy via
Charles Cazabon [EMAIL PROTECTED] writes on 1 September 2000 at 13:35:04
-0600
David Dyer-Bennet [EMAIL PROTECTED] wrote:
The man page for bouncesaying is rather misleading.
[...]
| bouncesaying "This address no longer accepts mail"
[EMAIL PROTECTED]
As
hi,
in my fastforwad alias table i got this line:
old.address : "| bouncesaying 'This address no longer
exists!'"
but this does not work always! in my logfile i get this message when a mail
for [EMAIL PROTECTED] has arrived:
Jul 25 16:39:15 km3 qmail: 964535
Hi all,
I have a ~alias/.qmail-bouncer file with the contents
|bouncesaying 'This is an automated bounce message' exit 0
When I send this address a messages I expect to have it bounced back at
me...
My logs show:
Jul 24 18:04:30 maybe smtpd: 964425870.197821 tcpserver: status: 0/40
Jul 24
Gavin Cameron writes:
I have a ~alias/.qmail-bouncer file with the contents
|bouncesaying 'This is an automated bounce message' exit 0
bouncesaying tries to execvp() the given program; it doesn't use a
shell to run the program. So it can't run a shell built-in command.
Instead of above
Hi all,
I just discovered the 'bouncesaying' utility from someone
elses post. Does anyone know why this is not installed anywhere
by default but it's man pages are installed? Are there other useful
utilities/programs that are built but not installed?
Thanks,
Dave
this:
./Mailbox
vev
|bouncesaying "No mailbox here called: $RECIPIENT"
I send a message to asdf (which doesn't exist) and it goes into the file
~alias/Mailbox and I get the bounce. I never get the copy the second line
of the file is supposed to do. According to dot-qmail(5)
-existant
addresses but I want to make sure I didn't miss one. So I set up
~alias/.qmail-default like this:
./Mailbox
vev
|bouncesaying "No mailbox here called: $RECIPIENT"
- From man dot-qmail:
ERROR HANDLING
If a delivery instruction fails, qmail-local stops immedi-
Vince Vielhaber writes:
According to dot-qmail(5) each line is a
delivery instruction, so shouldn't each line be exec'd?
The '' forwards are all collected together, and performed at the end
of the .qmail file processing. If the mail bounces, the forward will
never occur. Try using
to the sender. This, of course, would be for non-existant
addresses but I want to make sure I didn't miss one. So I set up
~alias/.qmail-default like this:
./Mailbox
vev
|bouncesaying "No mailbox here called: $RECIPIENT"
- From man dot-qmail:
ERROR HANDLING
If a delivery i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4 Jan 00, at 9:53, Keith Warno wrote:
| The '' forwards are all collected together, and performed at the
end | of the .qmail file processing. If the mail bounces, the forward
will | never occur. Try using '|forward vev'.
Hmm that's
- Original Message -
From: "Petr Novotny" [EMAIL PROTECTED]
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| On 4 Jan 00, at 9:53, Keith Warno wrote:
| | The '' forwards are all collected together, and performed at the
| end | of the .qmail file processing. If the mail
Vince Vielhaber writes:
|forward vev
That works, it leaves this in the bounce message: forward: qp 68503
but I can live with that.
Then do |forward vev 2/dev/null
--
-russ nelson [EMAIL PROTECTED] http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what
Keith Warno writes:
From: "Russell Nelson" [EMAIL PROTECTED]
| The '' forwards are all collected together, and performed at the end
| of the .qmail file processing. If the mail bounces, the forward will
| never occur. Try using '|forward vev'.
Hmm that's potentially extremely
On Tue, 4 Jan 2000, Russell Nelson wrote:
Vince Vielhaber writes:
|forward vev
That works, it leaves this in the bounce message: forward: qp 68503
but I can live with that.
Then do |forward vev 2/dev/null
Don't know why that never occurred to me, but does indeed work!
Vince.
Vince Vielhaber writes:
On Tue, 4 Jan 2000, Russell Nelson wrote:
Then do |forward vev 2/dev/null
Don't know why that never occurred to me, but does indeed work!
One caveat is that if forward fails, you'll get a completely empty
bounce message. That would be confusing since you
Hello all.
I would like to filter incoming messages, on a per-Mailbox basis, via a
user's .qmail and various calls to bouncesaying in that .qmail. Each call
to bouncsaying will run a program that checks for a particular condition,
and perhaps bounce the message if such a check fails
--I would say, why leverage condredirect for this purpose?
And I suppose I should also have included my negation operator.
Why not leverage condredirect for this purpose?
Sorry,
-Martin
45 matches
Mail list logo
