RE: [vchkpw] doublebounces non-.qmail-default | /var/vpopmail/bin/vdelivermail '' delete
The .qmail-doublebouncetonull goes in the /var/qmail/alias dir.
Shane
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, 15 August 2003 8:10 PM
To: [EMAIL PROTECTED]
Subject: RE: [vchkpw] doublebounces non-.qmail-default |
/var/vpopmail/bin/vdelivermail '' delete
Tom, I've been tracking this thread with great interest. But it's
implementation didn't make complete sense. If I understand correctly:
/var/qmail/control/doublebounceto
: doublebouncentonull
.qmail-doublebouncetonull
#
This method pipes a doublebounce to a comment, which is essentially a
/dev/null and the message dies quietly.
What I'm not understanding is where to put the
.qmail-doubnull file
in the vpopmail domains structure given that I have multiple domains
hosted?
Does it go into the qmail (/var/qmail/{alias|users}) environment or the
vpopmail environment? Per domain or single instance? Where to put the
.qmail
Thanks for helping clarify, this sounds really helpful.
D.
::Beware that this does not seem to work 100% with vpopmail. Check
::the archives
::for a better answer.
::
::As a side note, # is not like /dev/null, but perhaps
you knew that.
Upon further reflection I can see how that might be inferred.
Just to be clear... dotqmail files are used as delivery
instructions for
qmail... and a # is actually nothing more than a comment... and with
nothing
else in the dotqmail file... the delivery agent doesn't know
what else to
do
with the message and basically drops it to the floor and moves on.
And in response to the vpopmail issue, which I wasn't aware
of... if you
created a .qmail-null file with a # in it... then it would bypass the
vpopmail delivery agent... (Thank you Oden for bringing that to my
attention.)
I have used a .qmail file on my null user in both 5.2.1 and 5.3.20
(currently in production) with no problems.
Same end result...
Tom Walsh
Network Administrator
http://www.ala.net/
RE: [vchkpw] doublebounces non-.qmail-default | /var/vpopmail/bin/vdelivermail '' delete
::Tom, I've been tracking this thread with great interest. But it's
::implementation didn't make complete sense. If I understand correctly:
::
::/var/qmail/control/doublebounceto
::: doublebouncentonull
::
::.qmail-doublebouncetonull
::#
::
::This method pipes a doublebounce to a comment, which is essentially a
::/dev/null and the message dies quietly.
::
::What I'm not understanding is where to put the .qmail-doubnull file
::in the vpopmail domains structure given that I have multiple domains
::hosted?
::
::Does it go into the qmail (/var/qmail/{alias|users}) environment or the
::vpopmail environment? Per domain or single instance? Where to put the
::.qmail
::
::Thanks for helping clarify, this sounds really helpful.
::D.
D.
As others have eluded to in follow-ups to your post... There are a couple of
different ways to accomplish this... It all depends on how you want to
implement it.
I am sure you can't put a fully qualified email address in doublebounceto
(been there done that)... qmail affixes the local domain
(/var/qmail/control/me) to your name in doublebounceto OR you can also add
another directive to the /var/qmail/control/... doublebouncehost... this
will concatenate with doublebounceto to create a fully qualified email
address to send double bounces to.
So for instance if you had in your /var/qmail/control/doublebounceto:
null
and your /var/qmail/control/me has:
mail.domain.com
then the null in the doublebounceto file will be expanded to:
[EMAIL PROTECTED]
OR if /var/qmail/control/doublebouncehost has:
domain2.com
then the null in the doublebounceto file will be expanded to:
[EMAIL PROTECTED]
If you don't have mail.domain.com or domain2.com as a vpopmail virtual
domains (entry in /var/qmail/users/assign), then qmail will assume that it
is a local user delivery (at least for mail.domain.com, an MX lookup would
be done for domain2.com if it isn't local ie: rcpthosts, morercpthosts,
etc). It will then consult the /var/qmail/alias/ dir to see if there is a
.qmail-null file there.
On the other hand if mail.domain.com or domain2.com _are_ vpopmail virtual
domains then you can put the .qmail-null file in the
~vpopmail/domains/mail.domain.com or ~vpopmail/domains/domain2.com
directory. Once again delivery will be handled properly.
To answer your other questions... the /var/qmail/control is qmail wide... so
all domains that qmail/vpopmail handle are covered by those directives.
Fun huh? :)
Tom Walsh
Network Administrator
http://www.ala.net/
RE: [vchkpw] doublebounces non-.qmail-default | /var/vpopmail/bin/vdelivermail '' delete
Just put a comment in the .qmail or .qmail-username file... no need to invoke vdelivermail when you are going to throw it to /dev/null anyways... I have an account created on my mail server named null... in his .qmail file I have # nothing else... Has the same effect... Also note that .qmail-username is called before any vpopmail interaction. Any even better way to deal with doublebounces is to never let them into the queue in the first place... with tonix patch (smtpd-chkusr). Tom Walsh Network Administrator http://www.ala.net/ ::-Original Message- ::From: leonard [mailto:[EMAIL PROTECTED] ::Sent: Thursday, August 14, 2003 12:36 PM ::To: [EMAIL PROTECTED] ::Subject: [vchkpw] doublebounces non-.qmail-default | ::/var/vpopmail/bin/vdelivermail '' delete :: :: ::-BEGIN PGP SIGNED MESSAGE- ::Hash: SHA1 :: ::Hello, :: ::To deal with spam/double-bounces, ::I wrote in /var/qmail/control/doublebounceto : doublebounce ::which is the name for a .qmail-doublebounce file ::and in it I used | /var/vpopmail/bin/vdelivermail '' delete ::... like it was a .qmail-default. :: ::Is this possible for regulars .qmail-aliases too ? ::If not where do the eMails go ? :: ::Thank you, ::Maybe I found an easy way to deal w/ doublebounces... :: ::Guillaume :: ::-BEGIN PGP SIGNATURE- ::Version: GnuPG v1.2.1 (GNU/Linux) :: ::iD8DBQE/O8hooqOw021SWZYRAkXnAJwKfqEGnnGOJqV411VuciijYcBYrACffFPg ::rHK4gdi7Y0/OSWahNlcmIP4= ::=gdL7 ::-END PGP SIGNATURE- :: ::
Re: [vchkpw] doublebounces non-.qmail-default | /var/vpopmail/bin/vdelivermail '' delete
torsdagen den 14 augusti 2003 20.34 skrev Tom Walsh: Just put a comment in the .qmail or .qmail-username file... no need to invoke vdelivermail when you are going to throw it to /dev/null anyways... I have an account created on my mail server named null... in his .qmail file I have # nothing else... Has the same effect... Beware that this does not seem to work 100% with vpopmail. Check the archives for a better answer. As a side note, # is not like /dev/null, but perhaps you knew that.
RE: [vchkpw] doublebounces non-.qmail-default | /var/vpopmail/bin/vdelivermail '' delete
::Beware that this does not seem to work 100% with vpopmail. Check ::the archives ::for a better answer. :: ::As a side note, # is not like /dev/null, but perhaps you knew that. Upon further reflection I can see how that might be inferred. Just to be clear... dotqmail files are used as delivery instructions for qmail... and a # is actually nothing more than a comment... and with nothing else in the dotqmail file... the delivery agent doesn't know what else to do with the message and basically drops it to the floor and moves on. And in response to the vpopmail issue, which I wasn't aware of... if you created a .qmail-null file with a # in it... then it would bypass the vpopmail delivery agent... (Thank you Oden for bringing that to my attention.) I have used a .qmail file on my null user in both 5.2.1 and 5.3.20 (currently in production) with no problems. Same end result... Tom Walsh Network Administrator http://www.ala.net/
