Re: bounce handling
Joshua Nichols [EMAIL PROTECTED] wrote: I have ezmlm installed, and really like it's bounce detection, but for certain reasons I must use a different mailing list manager. I'd like to take advantage of it's bounce handling though. Is there a way to have qmail watch for a certain header, and then implement bounce tracking on a non-ezmlm message? No need for a special header; there are options to qmail-inject to make qmail use per-recipient VERP. Handling the bounces is up to you; in essence, you create a .qmail-something-default file and pipe the messages to a script of your choosing. In your case, you'd just log the $DEFAULT portion to a file. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
RE: bounce handling
Charles Cazabon [EMAIL PROTECTED] wrote: No need for a special header; there are options to qmail-inject to make qmail use per-recipient VERP. Handling the bounces is up to you; in essence, you create a .qmail-something-default file and pipe the messages to a script of your choosing. In your case, you'd just log the $DEFAULT portion to a file. What I'd like to do though, is take advantage of the ~20 day testing that ezmlm provides. I don't want to end up unsubscribing people because of an Out of office message or a temporary errors like mailbox full unless they've been occurring for a few weeks. If I understand the documentation correctly, VERP will just add the recipient address (or certain other info) to the envelope, and I don't see how that helps me. If I set up a .qmail-something file, and then piped all the messages through a script, wouldn't that catch ALL messages (misdirected unsubscribes, out of office, mailbox full, delivery delays, etc.)? Or, are you saying that duplicating this is just a matter of using VERP and writing my own ezmlm-warn and ezmlm-return? Heh, just... --joshua.
Re: bounce handling
Joshua Nichols [EMAIL PROTECTED] wrote: Charles Cazabon [EMAIL PROTECTED] wrote: No need for a special header; there are options to qmail-inject to make qmail use per-recipient VERP. Handling the bounces is up to you; in essence, you create a .qmail-something-default file and pipe the messages to a script of your choosing. In your case, you'd just log the $DEFAULT portion to a file. What I'd like to do though, is take advantage of the ~20 day testing that ezmlm provides. I don't want to end up unsubscribing people because of an Out of office message or a temporary errors like mailbox full unless they've been occurring for a few weeks. Your previous message seemed to imply you wanted to do this manually, based on a record of what recipients bounced. That's why I suggested just logging $DEFAULT. If I understand the documentation correctly, VERP will just add the recipient address (or certain other info) to the envelope, and I don't see how that helps me. If I set up a .qmail-something file, and then piped all the messages through a script, wouldn't that catch ALL messages (misdirected unsubscribes, out of office, mailbox full, delivery delays, etc.)? Not all -- it only appears in the envelope sender. People are extremely unlikely to send to that address with unsubscription requests (although that would actually _help_ you), etc. Autoresponders are of course a problem, but if your message appears to be a mailing list message (Precedence: bulk, etc headers), any well-written autoresponder will not respond to it. Note that 50% of the autoresponders out there are _not_ well-written. Or, are you saying that duplicating this is just a matter of using VERP and writing my own ezmlm-warn and ezmlm-return? Heh, just... If you want to use ezmlm, you can edit the appropriate script file to only remove the automatically unsubscribe after the probe bounces step, and replace that with a step that logs the username or emails you, or electrifies your chair. Your choice. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
bounce handling
Hey all-- I have ezmlm installed, and really like it's bounce detection, but for certain reasons I must use a different mailing list manager. I'd like to take advantage of it's bounce handling though. Is there a way to have qmail watch for a certain header, and then implement bounce tracking on a non-ezmlm message? That is, let's say I send out a message to the list nicholsfamily. If I put a header in the message that says X-List-Message: yes-nicholsfamily I'd like qmail to treat it like an outgoing ezmlm message, so that if it bounces, it's tracked in the ezmlm manner. At the last minute though, when ezmlm would unsubscribe the user, I'd like it to do something else, like add the user to a text file, or send an email to a specific address--probably ideal would be to just run a script, that way the script could do any combination of the above as the admin saw fit. Does anybody have or know of anything that aproximates this kind of behavior in qmail? I think it would be a very useful feature for many users of qmail who run other mailing list managers for whatever reason. thanks, --joshua.
bounce handling
Hi, I have a couple of questions: 1. How does qmail handle bounces? any pointers or documentation which describes this? 2. Can qmail's bounce handling be configured, i.e. the number of tries and the frequency. thanks, ketan _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.
Bounce handling--VERP
What's the best way to build a bounce-handling capability in coordination with qmail? What are the proper source files to look at in ezmlm to discover how it does it? The qmail-ezmlm bounce picture would be helpful, something in higher detail than "ezmlm uses qmail's VERPs to send a bounce-probe and unsubscribe" I'm not necessarily interested in using ezmlm, but I'll also ask this question on the ezmlm list. Brad Johnson [EMAIL PROTECTED]
Bounce handling: newbie
I know this is a newbie-esque q, but what's the best way of knowing what the intended email address was on a bounce? I know there are VERPs and QSBF involved, but I'm not sure where to go next. My basic understanding is that the best way is to have outgoing messages have a special Return-Path header so that you have the headers To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] Is that a VERP? Once that's been set up, then what? Are the MAILER-DAEMON "failure notice" messages useful? Here's specifics: I run a specially configured moderated mailing list, and don't really want to try to use ezmlm because the current setup functions (but needs to be improved). (For example, people can't subscribe to the list by sending a request to the list.) There's a server that handles the database of subscribers and incoming mail. (list.com) I'm using perl to handle incoming messages. (A basic NT SMTP server receives them and dumps them in a folder.) There's a FreeBSD server whose only purpose is to run qmail to send outgoing mail. (qmailer.backend.com). When a message needs to be sent off, list.com hands off the messages to qmailer.backend.com. No problem, everything cool. Then list.com gets all the [EMAIL PROTECTED] bounce messages (and all the other bounce messages, like AOL's bounce). I want to unsubscribe the bounces. (Is there any reason I shouldn't?) My guess is that ezmlm's bounce handler is the best method, but what exactly is it? I know it sends out a probe, but what's the mechanism for emulating that behavior? Is just grepping the MAILER-DAEMON messages for the QSBF a reasonable option? It seems like there should be a better way.
