> "Charles Cazabon" <[EMAIL PROTECTED]> wrote:
> Please learn to quote properly. I've fixed the quoting for this reply.
>
I would if I could send to the list using my normal mail client (Outlook
Express (and yes, I have it patched and virus protected)). But, I'm having
to cut and paste everything over my webmail client. I hope this time is
better.
> eric <[EMAIL PROTECTED]> wrote:
> > > Attila Csosz <[EMAIL PROTECTED]> wrote:
> > > > How to delete a mail from the the queue? ( this messages appear in
> > > > qmail-qread, qmail-qstat ).
> > > What problem are you trying to solve? Having a few messages show up
> > > in the qmail-qstat output for a few days is perfectly normal.
>
> > Will someone PLEASE define "few." I've got over 400 BOUNCE messages
> > alone in my queue. Some of them for almost a week (I know they'll
> > timeout after a week (and that the timeout is configurable), but this
> > is ridiculous.
>
> Why is it ridiculous? Mail sometimes can't be delivered; hosts are
> down, networks are down, services are down or busy, users make typos.
> "A few" depends on a lot of things; if your server handles a hundred
> messages a day, maybe "a few" == 5 or 10. If your server handles
> millions of messages a day, "a few" might be in the tens of thousands.
It's ridiculous because if qmail-send could do the lookup and
reject for invalid users, I would not have hardly any bounced
messages.
>
> > I have tons of mail in the queue going to pm0.net (see
> > www.postmastergeneral.com). Almost all of it is bounce messages.
> > Almost all of it from where someone who owns a mailing list on
> > postmastergeneral.com is STILL sending email to now-defunct email
> > addresses (email accounts that were cancelled).
>
> Okay, so whoever runs postmastergeneral.com needs to be educated about
> running mailing lists. No surprise there.
>
Yep. But getting them to change is gonna be darn near impossible.
> > I have looked at the problem long and hard and have yet to come up
> > with a workable solution. I use qmail-1.03 and vpopmail-3.4.11. It
> > seems that when using virtual doamins, qmail-smtp will NEVER reject a
> > recipient - even if that user does not exist.
>
> Exactly as documented.
Someone, somewhere must have come up with a workaround/patch for this.
BTW,
I guess I overlooked that "documented feature" when I installed all of this
well over a year ago. Looks like I'll be looking for other solutions if
I can't find a workaround for this.
>
> > Instead, it relies on the qmail-local (or in my case, vdelivermail
> > since I'm using vpopmail) to send a bounce. However, it looks like
> > postmastergeneral.com (and others) is not removing addresses from
> > lists based on the bounce messages that I'm sending.
>
> So the problem is with them, not qmail.
Again, getting them to change will be darn near impossible. But, the real
point here is that I'm wondering if there is any way to change the default
bounce message to something they will process.
>
> > I know I can change the default text of the bounce message using the
> > ".no-user.msg" file, but a) I'm not sure where this file should be (is
> > it global or per virtual domain), and b) I don't know what to put in
> > it so that listservers will properly handle the bounces.
>
> No idea; that's not qmail, it's vpopmail. Try asking on the vpopmail
> list. You wouldn't phone Chrysler and ask them how to fix your Toyota,
> would you?
>
I am crossposting this to both lists. Been asking there as well. I
just thought there might be someone else on the qmail list who uses
qmail AND vpopmail (especially since vpopmail ONLY works with qmail AFAIK).
> > One more caveat about my setup. I am using vpopmail with mysql
> > support and all the user/domain information is kept in mysql tables.
> >
> > Anybody got any ideas on how to solve this?
>
> Use tcpserver to refuse all connections from pm0.net. Voila, no more
> problem.
>
tcpserver (unless patched) requires IP ADDRESSES. IP addresses for
all the mailservers of pm0.net can change at any time. And,
pm0.net is not the only one I'm having problems with -
edirectnetwork.net is another. And I'm sure there are others, but
these two are by far the biggest problems. PLUS, the patch that I found
that will allow you to block by domain is for an older version of tcpserver
than I'm currently using. PLUS, there is legitimate mail coming in from
both of those servers for valid users. Doing it this way, I'd be blocking
that as well.
Eric Calvert
Caveland Connection
