Parsing Bounces for permanent and temporary errors
Hello, I am looking for any prior work or tutorial that explains the best way to parse bounced email messages to see if the failure reason is permanent (eg username not found) or temporary (eg user's mailbox full). It would be great if anyone could point me toward a list of phrases or things from different isp's standard bounced messages I could look for in my parser with regex. Thanks! __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
adding custom bounce headers (was Re: How do you handle the double bounces?)
Frank Tegtmeyer [EMAIL PROTECTED] writes: If the TMDA-bounces would be marked somehow (inserted header or something like that) they could be sorted out from the double bounces. For that tmda-filter would have to inject a self made bounce message and use a result code of 99 instead of 100. It's a little more complicated but would heavily increase my acceptance of TMDA (speaking as postmaster, of course). [copying the qmail list on this one to solicit a wider audience] I'm willing to entertain this because I also want the ability to add a Reply-To header to bounce messages containing the valid tagged address so that legitimate senders can reply more easily to bounces. While I'm there I could add a second header distinguishing the bounce as TMDA generated. But the question is how to best implement this. Is there an easy way to add custom headers to qmail bounce messages? I'd like to avoid duplicating qmail-send's bounce generation code. This could get complicated having to take into account qmail-control settings like `bouncefrom', `bouncehost' and stuff. Any suggestions? -- (TMDA - http://tmda.sourceforge.net/) (A qmail-based SPAM reduction system)
Re: Qmail, double-bounces, and RFC2821
[EMAIL PROTECTED] (Patrick J. LoPresti) wrote: This is the new RFC which supersedes RFC821 as the SMTP specification: http://www.faqs.org/rfcs/rfc2821.html The grammar in sections 4.1.2 and 4.1.3 appears not to permit [] as the domain portion of a mailbox in an address. In particular, the address #@[], which Qmail uses as the envelope sender for double-bounces, is not syntactically valid according to this grammar. I believe #@[] was invalid under RFC821, as well--and is one of the reasons that particular string was selected, so this is nothing new. Double bounces should be delivered locally, so RFC821/2821 doesn't apply. -Dave
Qmail, double-bounces, and RFC2821
(I searched the mail archives briefly but did not see any discussion of this. My apologies if I missed it.) This is the new RFC which supersedes RFC821 as the SMTP specification: http://www.faqs.org/rfcs/rfc2821.html The grammar in sections 4.1.2 and 4.1.3 appears not to permit [] as the domain portion of a mailbox in an address. In particular, the address #@[], which Qmail uses as the envelope sender for double-bounces, is not syntactically valid according to this grammar. Feel free to double-check me on this, as I would be happy to be wrong. Comments? Thoughts? - Pat P.S. Incidentally, the Lotus Domino SMTP server already rejects Qmail double-bounce messages as syntactically invalid. Until a few days ago, I could claim that Domino was in violation of the relevant RFC (821). But by this new RFC, Domino is right and Qmail is wrong. And now that RFC2821 has been released, I fear that other MTAs may start rejecting these messages too.
Re: handling bounces
You can use VERP without using ezmlm. Checkout QMAILINJECT=r as discussed in the qmail-inject manpage. Regards. On Wed, Mar 21, 2001 at 12:33:18PM -0800, Brett wrote: In qmail-inject, I'm Bcc-ing a LOT of people. What's the best method for handling bounces? I want to be able to extract a list of addresses into a file and deal with them later. I can't use ezmlm mainly because this Bcc list needs to be able to change on the fly (i.e. I can't just setup a static mailing list with ezmlm and have the bounce unsubscription automated through that since there's no such thing as a static mailing list in this situation). I've searched the usual places but can't find too much helpful info on this. Any help is appreciated, thanks.
[vmailmgr] email to virtual user bounces
Qmail is installed, and properly receives email to users with full accounts and Mailbox files in their $HOME. I installed vmailmgr and want to run virtualdomains (multiple domains, multiple IPs, multiple virtual users per domain). PROBLEM: Outside mail to virtual aliases bounces saying "Sorry, no mailbox here by that name." INFO: I created /var/qmail/control/virtualdomains with: .mydomain.com:aw I did the following: useradd aw su - aw vsetup vadduser herman edit /etc/inetd.conf and add pop-3 stream tcp nowait root /var/qmail/bin/qmail-popup qmail-popup mydomain.com /usr/local/bin/checkvpw /var/qmail/bin/qmail-pop3d Mailbox restart inetd (using init.d script) restart qmail (using init.d script) __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
bounce mail allways double bounces because the 'to' in the envelope is empty?
Hi, I'm running qmail+vpopmail in a redhat 6.2 box. Instaled yesterday and never installed before, only managed some systems already installed. It seems I doesn't have a mail defined for the bounce mails to go for? I mean, for checking I sended a mail to [EMAIL PROTECTED], thatemail I'm sure that doesn't exist. I thought I would recibe some bounce mail in [EMAIL PROTECTED], so I checked, but received this: --- Hi. This is the qmail-send program at tuxar.com.I tried to deliver a bounce message to this address, but the bounce bounced!@tuxar.com:Sorry, no mailbox here by that name. vpopmail (#5.1.1)--- Below this line is the original bounce.Return-Path: Received: (qmail 12560 invoked from network); 16 Jan 2001 03:47:46 -Received: from unknown (HELO pepe) (192.168.1.2) by ol50-71.fibertel.com.ar with SMTP; 16 Jan 2001 03:47:46 -asdf --- It seems all bounced mail double-bounces and finally got to postmaster. How can I solve this? Is this important? Would cause any damage? Bellow is the output for qmail-showctl, that I thought It may be usefull for you: --- qmail home directory: /var/qmail.user-ext delimiter: -.paternalism (in decimal): 2.silent concurrency limit: 120.subdirectory split: 23.user ids: 512, 513, 514, 0, 515, 516, 517, 518.group ids: 512, 513. badmailfrom: (Default.) Any MAIL FROM is allowed. bouncefrom: (Default.) Bounce user name is MAILER-DAEMON. bouncehost: (Default.) Bounce host name is tuxar.com. concurrencylocal: (Default.) Local concurrency is 10. concurrencyremote: (Default.) Remote concurrency is 20. databytes: (Default.) SMTP DATA limit is 0 bytes. defaultdomain: Default domain name is tuxar.com. defaulthost: (Default.) Default host name is tuxar.com. doublebouncehost: (Default.) 2B recipient host: tuxar.com. doublebounceto: (Default.) 2B recipient user: postmaster. envnoathost: (Default.) Presumed domain name is tuxar.com. helohost: (Default.) SMTP client HELO host name is tuxar.com. idhost: (Default.) Message-ID host name is tuxar.com. localiphost: (Default.) Local IP address becomes tuxar.com. locals: me: My name is tuxar.com. percenthack: (Default.) The percent hack is not allowed. plusdomain: Plus domain name is tuxar.com. qmqpservers: (Default.) No QMQP servers. queuelifetime: (Default.) Message lifetime in the queue is 604800 seconds. rcpthosts: SMTP clients may send messages to recipients at tuxar.com. morercpthosts: (Default.) No effect. morercpthosts.cdb: (Default.) No effect. smtpgreeting: (Default.) SMTP greeting: 220 tuxar.com. smtproutes: (Default.) No artificial SMTP routes. timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds. timeoutremote: (Default.) SMTP client data timeout is 1200 seconds. timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds. virtualdomains: Virtual domain: tuxar.com:tuxar.com rcpthosts.lock: I have no idea what this file does. virtualdomains.lock: I have no idea what this file does. locals.lock: I have no idea what this file does.--- Sorry If this is docummented elsewhere and I missed. Thanks in advance, Sebastian Brocher www.tuxar.com
Re: bounce mail allways double bounces because the 'to' in the envelope is empty?
--- Hi. This is the qmail-send program at tuxar.com. I tried to deliver a bounce message to this address, but the bounce bounced! @tuxar.com: Sorry, no mailbox here by that name. vpopmail (#5.1.1) --- Below this line is the original bounce. Return-Path: Received: (qmail 12560 invoked from network); 16 Jan 2001 03:47:46 - Received: from unknown (HELO pepe) (192.168.1.2) by ol50-71.fibertel.com.ar with SMTP; 16 Jan 2001 03:47:46 - asdf --- A complet bounce message with all of the headers including the original message would be much appriciated. To me it looks like your envelope sender address is bogus, but I can't realy be 100% sure if I don't see the rest of the bounce! MVH Andr Paulsberg
Mass email to database/checking bounces
Repost as I posted a HTML message last time (darn Outlook Express..) --- I have a database of over 50,000 customer e-mails that we wish to send a newsletter to, probably monthly, from a RH System running Qmail. Would this require any special configuration changes or should a stock Qmail install work just fine? At the moment sending mail is working fine from the machine. This database is in MySQL. I was thinking of using PHP to retrieve and send each individual e-mail; is this the best way, or is there another way I should do it? Also, I would like to manage bouncebacks somehow - how could I track any failed e-mails and either remove this from the database or add them to a new database that I could check each time I send this e-mail. Finally, any good utilities around to help with composing MIME e-mail? Ideally I could construct the e-mail on a Windows PC and then copy it over to the RedHat box.. I'm looking for resources, pointers etc.. as I can probably send all the things now but don't want it dying halfway through! Many thanks in advance John
Re: Mass email to database/checking bounces
On Sat, Jan 06, 2001 at 08:45:58PM -, John P wrote: I have a database of over 50,000 customer e-mails that we wish to send a newsletter to, probably monthly, from a RH System running Qmail. Would this require any special configuration changes or should a stock Qmail install work just fine? At the moment sending mail is working fine from the machine. This database is in MySQL. I was thinking of using PHP to retrieve and send each individual e-mail; is this the best way, or is there another way I should do it? Also, I would like to manage bouncebacks somehow - how could I track any failed e-mails and either remove this from the database or add them to a new database that I could check each time I send this e-mail. Finally, any good utilities around to help with composing MIME e-mail? Ideally I could construct the e-mail on a Windows PC and then copy it over to the RedHat box.. I'm looking for resources, pointers etc.. as I can probably send all the things now but don't want it dying halfway through! I would definitely recommend ezmlm, the qmail-friendly mailing list manager. Or, rather, ezmlm-idx. Go to http://www.ezmlm.org/ There are options for MySQL interfacing, the bounce handling is very, very good and you can set up a list that definitely only you can post to. The creation of the message could be done on the Win machine and sent directly to the list. -Johan -- Johan Almqvist
Re: Mass email to database/checking bounces
I would definately suggest ezmlm-idx also. Works like a charm. It is also quite easy to whip up a small shell script calling qmail-inject; I have done this several times for quick and dirty one-time mailings. --Pete On Sat, 6 Jan 2001, John P wrote: Repost as I posted a HTML message last time (darn Outlook Express..) --- I have a database of over 50,000 customer e-mails that we wish to send a newsletter to, probably monthly, from a RH System running Qmail. Would this require any special configuration changes or should a stock Qmail install work just fine? At the moment sending mail is working fine from the machine. This database is in MySQL. I was thinking of using PHP to retrieve and send each individual e-mail; is this the best way, or is there another way I should do it? Also, I would like to manage bouncebacks somehow - how could I track any failed e-mails and either remove this from the database or add them to a new database that I could check each time I send this e-mail. Finally, any good utilities around to help with composing MIME e-mail? Ideally I could construct the e-mail on a Windows PC and then copy it over to the RedHat box.. I'm looking for resources, pointers etc.. as I can probably send all the things now but don't want it dying halfway through! Many thanks in advance John
Re: Potentially stupid question about bounces...
- Original Message - From: "Charles Cazabon" [EMAIL PROTECTED] To: "QMail Mailing List" [EMAIL PROTECTED] Sent: Monday, December 18, 2000 7:44 PM Subject: Re: Potentially stupid question about bounces... Kris Kelley [EMAIL PROTECTED] wrote: I'm trying to get an idea of exactly how qmail does bounce messages, since I will probably have to write various delivery programs to deal with special quotas and such in the near future. You're not clear on what you're trying to accomplish here. You're right, I'm not. Right now all sorts of exotic quota ideas are being bandied about the office: x number of messages sent/received in y time, different numbers for different senders and recipients, and on and on. Any of these ideas that gets turned into a requirement will need a custom delivery instruction to go with it, if it's not already covered by programs like Sam Varshavshik's deliverquota. qmail-local signals delivery status to qmail-lspawn with its exit codes. You can do things in a .qmail file and exit with the appropriate codes to get the behaviour you want; man qmail-command and man dot-qmail for more details. I think that answers my question. I'll study those man pages a little more closely. Thanks. ---Kris Kelley
Potentially stupid question about bounces...
I'm trying to get an idea of exactly how qmail does bounce messages, since I will probably have to write various delivery programs to deal with special quotas and such in the near future. Simply put, are all bounce messages generated by qmail-send? If so, that means a delivery program only has to exit with the right error code for a bounce to be generated, correct? Sorry if I seem to be overlooking the obvious, but the qmail docs don't give a clear picture about this, and I can tell from the list archives that there has been plenty of confusion about bouncing! ---Kris Kelley
Re: Potentially stupid question about bounces...
Kris Kelley [EMAIL PROTECTED] wrote: I'm trying to get an idea of exactly how qmail does bounce messages, since I will probably have to write various delivery programs to deal with special quotas and such in the near future. You're not clear on what you're trying to accomplish here. Just thought I'd mention that if it's virtual domain quotas, vmailmgr has this covered already. Users in a virtual domain was on Bruce's todo list, although I'm not sure if he's finished it yet. Simply put, are all bounce messages generated by qmail-send? If so, that means a delivery program only has to exit with the right error code for a bounce to be generated, correct? qmail-local signals delivery status to qmail-lspawn with its exit codes. You can do things in a .qmail file and exit with the appropriate codes to get the behaviour you want; man qmail-command and man dot-qmail for more details. qmail-remote does things a little differently; it signals its status by printing letter codes. 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: all mail forwarding and catching all bounces
* Alex Kramarov [EMAIL PROTECTED] [001210 16:53]: |grep -q MAILER-DAEMON || exit 99 - this works, but cause a loop in the system because every message forwarded to a user specified after this line (me of course) eventually goes again through qmail-queue and gets replicated to the log alias again. Change the whole setup to: |grep -q MAILER-DAEMON || exit 99 /var/qmail/alias/LOG/ To deliver *locally* to a Maildir/, rather than forwarding it off of the machine. (You'll want to ``maildirmake'' the destination Maildir/ if you use the above...) /pg -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- The generation of random numbers is too important to be left to chance.
Re: all mail forwarding and catching all bounces
Alex Kramarov [EMAIL PROTECTED] wrote: I am new to this list, but i am a diligent reader, and after reading all documentation on q-mail i couldn't find two things i need a lot , after I successfully installed a qmail server and put it instead of my old exchange, which was giving me a lot of trouble before ... This is quite possibly the best "newbie" message to the list I've seen in months. Thank you for doing your research. 1. Is it possible to copy every bounce message generated to any user to another user (in this case - me : i want to know when my users do not succeede sending, or someone from the outside is sending mail to a wrong address in my domain) A bounce message is just another message to qmail. What you could do is use the QUEUE_EXTRA feature to send copies of all mail to an alias (msglog is a common choice). Then have a file ~alias/.qmail which does something like: |grep -q MAILER-DAEMON exit 99 you@yourdomain This should forward copies of qmail bounces to you. You could make the grep term a little more flexible to catch bounces from other MTAs. 2. Is it possible to forward all mail (except the local mail, as listed in control/local) to another host - and I am not talking of smtproutes, which takes place after the original e-mail has been parsed and copies of it has been generated to every domain it's destined to go. I want to forward all non-local mail to the server of my provider, so that if someone sends a 2MB mail to 50 recipients, which unfortunately my users do sometimes, that will not take my 128 bit line till the rest of the day sending 50 copies of the mail (and instead, of course, forward 1 mail to my provider's server, so he would have to send these 50 copies). Once a message hits qmail-queue, it will be sent once for each recipient. An alternative would be to have a wrapper around qmail-queue which determines if the message is to a local or remote address; if its local, it calls qmail-queue; otherwise it sends it directly to your ISP's smarthost (using nullmailer perhaps?). 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: all mail forwarding and catching all bounces
* Charles Cazabon [EMAIL PROTECTED] [001210 10:19]: 1. Is it possible to copy every bounce message generated to any user to another user (in this case - me : i want to know when my users do not succeede sending, or someone from the outside is sending mail to a wrong address in my domain) A bounce message is just another message to qmail. What you could do is use the QUEUE_EXTRA feature to send copies of all mail to an alias (msglog is a common choice). Then have a file ~alias/.qmail which does something like: |grep -q MAILER-DAEMON exit 99 Shouldn't this use ``||'' instead of ``''? If he wants to see only the bounces... Also, it might be a good idea to use the mess822 package to only grep for MAILER-DAEMON in the headers, where it makes sense. /pg -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- For mad scientists who keep brains in jars, here's a tip: why not add a slice of lemon to each jar, for freshness? (Jack Handey)
Re: all mail forwarding and catching all bounces
Peter Green [EMAIL PROTECTED] wrote: |grep -q MAILER-DAEMON exit 99 Shouldn't this use ``||'' instead of ``''? If he wants to see only the bounces... Actually, I meant to type 'grep -qv', but changing either would work. Also, it might be a good idea to use the mess822 package to only grep for MAILER-DAEMON in the headers, where it makes sense. An excellent suggestion. 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: all mail forwarding and catching all bounces
Thank you all for this advice, and it did seem a good idea, until I somehow brought my server to his knees (good thing it is after work hours) just by recompiling and running "make setup check" - I was unable to start qmail with the "alert: cannot start: unable to read controls" messages in the log. Well now I am past it. I now have all messages duplicated to the log alias, but there is a problem... |grep -qv MAILER-DAEMON exit 99 - this does not catch anything at all ... |grep -q MAILER-DAEMON exit 99 - this one causes the message to log to be deferred. |grep -q MAILER-DAEMON || exit 99 - this works, but cause a loop in the system because every message forwarded to a user specified after this line (me of course) eventually goes again through qmail-queue and gets replicated to the log alias again. Any suggestions (and if you could please tell me where can I read how that line functions - I am not familiar with this command form.) Thank you. Alex Incredimail Admin. -Original Message- From: Peter Green [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 10, 2000 7:53 PM To: [EMAIL PROTECTED] Cc: Charles Cazabon Subject: Re: all mail forwarding and catching all bounces * Charles Cazabon [EMAIL PROTECTED] [001210 10:19]: 1. Is it possible to copy every bounce message generated to any user to another user (in this case - me : i want to know when my users do not succeede sending, or someone from the outside is sending mail to a wrong address in my domain) A bounce message is just another message to qmail. What you could do is use the QUEUE_EXTRA feature to send copies of all mail to an alias (msglog is a common choice). Then have a file ~alias/.qmail which does something like: |grep -q MAILER-DAEMON exit 99 Shouldn't this use ``||'' instead of ``''? If he wants to see only the bounces... Also, it might be a good idea to use the mess822 package to only grep for MAILER-DAEMON in the headers, where it makes sense. /pg -- Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED] --- For mad scientists who keep brains in jars, here's a tip: why not add a slice of lemon to each jar, for freshness? (Jack Handey)
all mail forwarding and catching all bounces
I am new to this list, but i am a diligent reader, and after reading all documentation on q-mail i couldn't find two things i need a lot , after I successfully installed a qmail server and put it instead of my old exchange, which was giving me a lot of trouble before ... 1. Is it possible to copy every bounce message generated to any user to another user (in this case - me : i want to know whenmy users do notsucceede sending, or someone from the outside is sending mail to a wrong address in my domain) 2. Is it possible to forward all mail (except the local mail, as listed in control/local) to another host - and I am not talking of smtproutes, which takes place after the original e-mail has been parsed and copies of it has been generated to every domain it's destined to go.I want to forward all non-local mail to the server of my provider, so that if someone sends a 2MB mail to 50 recipients, which unfortunately my users do sometimes, that will not take my 128 bit line till the rest of the day sending 50 copies of the mail (and instead, of course, forward 1 mail to my provider's server, so he would have to send these 50 copies). I thank you in advance and patiently waiting for your answer ... Alex Incredimail Admin __Created and best viewed with IncrediMail!Get your free copy at: www.incredimail.com
Re: bounces and mime encapsulation
On Fri, Nov 17, 2000 at 05:30:17PM -0500, Russell Nelson wrote: torben fjerdingstad writes: When I as postmaster receive bounces from mailer-daemon on my qmail system, the spam is concatenated in-line to the bottom of the error mail. How do I get it as a mime attach instead? Is this what you're looking for? liFred Lindberg has a patch which causes qmail-send to preserving the MIME-ness whena href="http://www.ezmlm.org/pub/patches/qmail-mime.tgz"bouncing MIME messages/a. It requires and includes a patch to ezmlm, since it breaks a href="http://cr.yp.to/proto/qsbmf.txt"QSBMF/a. Exactly. Thanks! ;) -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | The best way to help the poor 521 Pleasant Valley Rd. | +1 315 268 1925 voice | is to help the rich build Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | up their capital. -- Med venlig hilsen / Regards Netdriftgruppen / Network Management Group UNI-C Tlf./Phone +45 35 87 89 41Mail: UNI-C Fax. +45 35 87 89 90 Bygning 304 E-mail: [EMAIL PROTECTED] DK-2800 Lyngby
bounces and mime encapsulation
When I as postmaster receive bounces from mailer-daemon on my qmail system, the spam is concatenated in-line to the bottom of the error mail. How do I get it as a mime attach instead? That way, I can easily isolate the original letter from the errror messages with my MUA (mutt), and I will see the subject of the spam instead of the famous subject "failure notice". When I get bounces from a sendmail host hear, it has mime encapsulated the different parts. That's what I like. In mutt, it looks like this when I go to the view attachment menu. Here, I can easily submit attach #6 for a spam complaint, RSS, whatever. 1 no description [text/plain, 7bit, 0.4K] 2 no description [message/delivery-s, 7bit, 0.3K] 3 Returned mail: User has moved; please tr [message/rfc822, 7bit, 2.8K] 4 no description [text/plain, 7bit, 0.4K] 5 no description [message/delivery-s, 7bit, 0.2K] 6 Money you never have to repay![message/rfc822, 7bit, 1.4K] 7 no description[text/plain, 7bit, 0.7K] -- Med venlig hilsen / Regards Netdriftgruppen / Network Management Group UNI-C Tlf./Phone +45 35 87 89 41Mail: UNI-C Fax. +45 35 87 89 90 Bygning 304 E-mail: [EMAIL PROTECTED] DK-2800 Lyngby
Re: bounces and mime encapsulation
torben fjerdingstad writes: When I as postmaster receive bounces from mailer-daemon on my qmail system, the spam is concatenated in-line to the bottom of the error mail. How do I get it as a mime attach instead? Is this what you're looking for? liFred Lindberg has a patch which causes qmail-send to preserving the MIME-ness whena href="http://www.ezmlm.org/pub/patches/qmail-mime.tgz"bouncing MIME messages/a. It requires and includes a patch to ezmlm, since it breaks a href="http://cr.yp.to/proto/qsbmf.txt"QSBMF/a. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | The best way to help the poor 521 Pleasant Valley Rd. | +1 315 268 1925 voice | is to help the rich build Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | up their capital.
bounces...but configured right
I am forwarding bounce warnings from 2 mailing lists I subscribe to...(imp, and vmailmgr) I want to know...I found that there was not a carraige return after the bryant.dsc.k12.ar.us entry in control/rcpthosts , I just added one, but is that why these messages have been bouncing...but sometimes go through... I thought I had been getting most of my mail from these lists...in fact I was watching the vmailmgr one today, and know I got a message on it... why don't messages bounce all the time on an error like this? Thanks, Barry Smoke Bryant Public Schools using qmail for 3 years...and loving it! Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] Messages to you from the imp mailing list seem to have been bouncing. I've attached a copy of the first bounce message I received. If this message bounces too, I will send you a probe. If the probe bounces, I will remove your address from the imp mailing list, without further notice. I've kept a list of which messages from the imp mailing list have bounced from your address. Copies of these messages may be in the archive. To retrieve a set of messages 123-145 (a maximum of 100 per request), send an empty message to: [EMAIL PROTECTED] To receive a subject and author list for the last 100 or so messages, send an empty message to: [EMAIL PROTECTED] Here are the message numbers: 584 585 586 587 588 589 590 591 596 594 595 592 597 598 601 602 593 599 600 603 604 619 606 610 608 611 613 612 623 625 629 605 626 627 628 607 631 609 616 617 621 614 622 615 624 618 620 630 --- Enclosed is a copy of the bounce message I received. Return-Path: Received: (qmail 94209 invoked for bounce); 5 Nov 2000 06:39:09 - Date: 5 Nov 2000 06:39:09 - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: failure notice Hi. This is the qmail-send program at horde.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: 165.29.94.240 does not like recipient. Remote host said: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) Giving up on 165.29.94.240. Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. I'm working for my owner, who can be reached at [EMAIL PROTECTED] Messages to you from the vmailmgr mailing list seem to have been bouncing. I've attached a copy of the first bounce message I received. If this message bounces too, I will send you a probe. If the probe bounces, I will remove your address from the vmailmgr mailing list, without further notice. I've kept a list of which messages from the vmailmgr mailing list have bounced from your address. Copies of these messages may be in the archive. To retrieve a set of messages 123-145 (a maximum of 100 per request), send an empty message to: [EMAIL PROTECTED] To receive a subject and author list for the last 100 or so messages, send an empty message to: [EMAIL PROTECTED] Here are the message numbers: 4111 4112 4113 4114 --- Enclosed is a copy of the bounce message I received. Return-Path: Received: (qmail 32690 invoked for bounce); 5 Nov 2000 02:59:47 - Date: 5 Nov 2000 02:59:47 - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: failure notice Hi. This is the qmail-send program at daedalus.bfsmedia.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. [EMAIL PROTECTED]: 165.29.94.240 does not like recipient. Remote host said: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) Giving up on 165.29.94.240.
bounceroute? -- how to offload bounces
Howdy, all. Our outbound mail server spends the vast majority of its resources (attempting to) bounce mail (usually from spam :( ). The result is that sometimes, when load is very heavy, normal outbound deliveries sit in the queue and wait a while. So... I'd like to set up a dedicated machine to handle bounces. The bounce* and doublebounce* control files don't appear to be useful here. And I don't see how I can garner the help of smtproutes, either. What I really want is the following logic: "A message needs to be bounced? Relay it first to 192.168.N.N and let him handle it." Thanks in advance for any suggestions! Dave
Removing attachments from bounces
Good evening one and all Question: I want to strip attachments from bounces, as we are wasting stacks of bandwidth watching attachments bounce from incorrectly-typed addresses. What is the best way of doing this? Thanks -- === |User: |Href: |Status:| --- |Brett Randall |http://xbox.ipsware.com/|Hibernating| === Generated by Microsoft Ass-Watcher s/(c)/(!c)/g 2003
RE: Removing attachments from bounces
There's a qmail-bounce.patch on the qmail site that adds the ability to put a bouncemaxbytes file in your control directory and in it you specify, in bytes, the maximum size of a bounce, the rest gets stripped. I use it and it works great, I only bounce 25k messages now. Dave -Original Message- From: Brett Randall [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 12, 2000 4:26 AM To: [EMAIL PROTECTED] Subject: Removing attachments from bounces Good evening one and all Question: I want to strip attachments from bounces, as we are wasting stacks of bandwidth watching attachments bounce from incorrectly-typed addresses. What is the best way of doing this? Thanks -- === |User: |Href: |Status:| --- |Brett Randall |http://xbox.ipsware.com/|Hibernating| === Generated by Microsoft Ass-Watcher s/(c)/(!c)/g 2003
HELP! Post vpopmail install, everything bounces
I've got a client site down right now because: 1. I installed vpopmail into their functioning qmail system; 2. I stupidly set up a virtual domain with the *same* name as their primary domain; 3. I immediately deleted the virtual domain; 4. But everthing sent to the domain ([EMAIL PROTECTED]) bounces, with a qmail-send error message saying the domain "is not in controls/locals". I've checked the locals file and it's got the following entries: localhost mail.nethan.com nethan.com The rcpthosts file has the same entries. Our backup server is picking up the inbound mail but I need to fix this ASAP and am stumped. Thanks, Barry Dwyer
RE: Help! Post vpopmail install, everything bounces
Problem solved with a reboot. Nothing helpful in the logs: the alert log showed line after line after line of "can't start - qmail-send already running" (or something to that effect), starting long before the vpopmail install this afternoon. Odd, given that if I did a 'qmail stop', qmail-stat showed all three (send, smtp and pop3) down. A subsequent 'qmail start', followed by a 'stat' showed all new pids. I ran ./configure, then had someone at the site reboot the mail server. It works. One of life's mysteries. Barry
Re: Help! Post vpopmail install, everything bounces
I ran ./configure, then had someone at the site reboot the mail server. It works. = If you ran a ./config you might want to re-check your /control/locals and /control/rcpthosts. I did that the other day and it removed the information I had in it. HTH, tonyC
Re: Help! Post vpopmail install, everything bounces
I had to manually edit the locals and rcpthosts file to add the line "nethan.com" b/c ./configure only had "mail.nethan.com". Tony Campisi wrote: I ran ./configure, then had someone at the site reboot the mail server. It works. = If you ran a ./config you might want to re-check your /control/locals and /control/rcpthosts. I did that the other day and it removed the information I had in it. HTH, tonyC
trouble with bounces
I have just looked at my qmail-debug logs which is showing the message: warning: trouble injecting bounce message, will try later. this is coming up a lot... like several of them in the span of a second... they started yesterday some time which coincides with some problems I was having with my swap partition. ie; the drive was corrupted and caused me no end of problems with my web server, so processes with screwed up names, qmail, etc... I restarted everything that seemed to crap out and it all seems to be going OK, but the system is quite low on resources... it floats between 3 and 20Mb of RAM free out of 384Mb... I had to kill the swap partition till we can get a new HD to replace the swap drive, so basically, it may have stemmed from a memory corruption... it's quite odd, any advice or opinions welcome. ta. -- Spiro Harvey Linux Systems Engineer A.Net Communications / ( http://www.anet.co.nz ) -- Spiro Harvey Linux Systems Engineer A.Net Communications / ( http://www.anet.co.nz )
Re: Redirecting double bounces
Ben Beuchler [EMAIL PROTECTED] wrote: We are getting a ton of double bounces, mostly spam bouncing back to non-existent addresses. In an attempt to thin out my inbox, I set the double bounces to got to a seperate address ([EMAIL PROTECTED]). Here's the relevant snippet from qmail-showctl: - doublebouncehost: 2B recipient host: bitstream.net. doublebounceto: 2B recipient user: doublebounce. - Despite this fact, I'm still getting double bounces delivered to postmaster! And I did send a HUP to qmail-send. In "man qmail-send": WARNING: qmail-send reads its control files only when it starts. If you change the control files, you must stop and restart qmail-send. Exception: If qmail-send receives a HUP signal, it will reread locals and virtualdomains. -Dave
Redirecting double bounces
We are getting a ton of double bounces, mostly spam bouncing back to non-existent addresses. In an attempt to thin out my inbox, I set the double bounces to got to a seperate address ([EMAIL PROTECTED]). Here's the relevant snippet from qmail-showctl: - doublebouncehost: 2B recipient host: bitstream.net. doublebounceto: 2B recipient user: doublebounce. - Despite this fact, I'm still getting double bounces delivered to postmaster! And I did send a HUP to qmail-send. Note that the periods at the end of those lines do not exist in the actual control files. They were apparently added by qmail-showctl. At least I assume it's a double bounce. Here's the first part of the message(s): - Hi. This is the qmail-send program at amazhan.bitstream.net. I tried to deliver a bounce message to this address, but the bounce bounced! - Sounds like a double bounce to me. Any ideas why they are not being handled as directed by doublebouncehost and doublebounceto? Thanks, Ben -- The spectre of a polity controlled by the fads and whims of voters who actually believe that there are significant differences between Bud Lite and Miller Lite, and who think that professional wrestling is for real, is naturally alarming to people who don't. -- Neal Stephenson
VERP bounces on the local qmail server
Hello, Once in a while I have to send messages thousands of users that are listed in a dynamic database. Is not viable for me to use a mailing list manager. To handle bounces I use VERP by connecting to the Qmail SMTP server directly like this: HELO localhost MAIL FROM:[EMAIL PROTECTED]@[] RCPT TO:[EMAIL PROTECTED] RCPT TO:[EMAIL PROTECTED] RCPT TO:[EMAIL PROTECTED] DATA Headers: here Message here. . QUIT Qmail delivers messages to the remote MX hosts of domain1.com, domain2.com, domainn.com and if that is the bounces are returned as expected to: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] However, if instead of bouncing in the remote hosts, the messages bounces right in the local host on which qmail is running and to which messages are relayed, instead the above, qmail waits for the message queue time limit and bounces a single message to [EMAIL PROTECTED] noticing the bounced addresses. I was expecting to get separate bounced messages to be delivered to the VERP address after expanded. I am doing something wrong or qmail is just not supposed to work like I expected? Another problem is about some SMTP servers do not set the To: header of the bounces to the return-path address of the messages sent that should have been the VERP address after expanded for the original recipient. Anybody knows a way to ensure that the VERP expanded address can be recovered? To handle the bounces I have a POP3 based dump account to which all unknown addresses for phpclasses.UpperDesign.com are delivered. I just don't seem to be able to make the original recipient address be extracted because not all SMTP servers set the To: or any other header with the original message return path. Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?[EMAIL PROTECTED] -- E-mail: [EMAIL PROTECTED] URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp --
Re: Recipient MTA is rejecting bounces
Yusuf Goolamabbas [EMAIL PROTECTED] writes: Hi, I have a qmail-1.03 machine saw in my queue a few bounces in them. Also, looking at my logs I saw the following message @40003905243f24daf1b4 delivery 34: deferral: Connected_to_204.68.180.50_but_sender_was_rejected./Remote_host_said:_451_#@[]..._unresolvable_host_name_[],_see_RFC_1123,_sections_5.2.2_and_5.2.18./ A bounce message bounced. When this happens, qmail generates a double-bounce and tries to send it to the local postmaster address. It uses the completely invalid envelope sender "#@[]" to ensure that double-bounces can't then bounce again and generate mail loops. You apparently are forwarding postmaster mail to another system which is doing resolveable name checks on envelope senders, and doesn't like qmail's special double-bounce sender. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Re: Recipient MTA is rejecting bounces
A bounce message bounced. When this happens, qmail generates a double-bounce and tries to send it to the local postmaster address. It uses the completely invalid envelope sender "#@[]" to ensure that double-bounces can't then bounce again and generate mail loops. You apparently are forwarding postmaster mail to another system which is doing resolveable name checks on envelope senders, and doesn't like qmail's special double-bounce sender. That is true, However I changed the forwarding to another system which doesn't do resolveable name checks and yet the messages are continuing to go the old system. (I changed /var/qmail/alias/.qmail-postmaster) and restarted qmail. Is this appropiate ? What are the alternatives to clear these messages from the queue Also, Do people see the benifit in doing resolvable name checks. Doesn't it hurt in the above scenario Thanks, Yusuf
Re: Recipient MTA is rejecting bounces
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25 Apr 00, at 19:36, Yusuf Goolamabbas wrote: That is true, However I changed the forwarding to another system which doesn't do resolveable name checks and yet the messages are continuing to go the old system. (I changed /var/qmail/alias/.qmail-postmaster) and restarted qmail. Is this appropiate ? Unless your /var/qmail/control/doublebounceto says other than postmaster, this is appropriate. However, that doesn't clear the messages that have already been forwarded from postmaster to elsewhere. What are the alternatives to clear these messages from the queue Well, if they cause that much trouble, there are ways to delete them. But I'd think they're mostly harmless, unless there's too many of them. (In that case, search the archives of this list; there have been way too many questions "How to delete all messages to person/host ?" answered.) Also, Do people see the benifit in doing resolvable name checks. I personally don't think they give you much benefits; what do you do if you get temporary DNS error? Temporarily reject the mail? I wouldn't like to see much of that. However, there _are_ cases where it can help, I believe. And I also think that any mail administrator is smart enough to count the odds and evens :-) -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOQV3QVMwP8g7qbw/EQK8OwCeOXzSGVog+3HAjWO1vIYuDzoL66EAn19j l2YOboCp4/JbwNxODSWbpQQH =rWIB -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: Recipient MTA is rejecting bounces
Also, Do people see the benifit in doing resolvable name checks. Doesn't it hurt in the above scenario It encourages spammers to abuse real domain names so that someone can sue them. There have been a couple of successful law suits over sending spam with someone else's domain name. It keeps the bounce on the injecting system. This keeps your postmaster from dealing with misconfigured email clients at other sites.
Re: Recipient MTA is rejecting bounces
Yusuf Goolamabbas [EMAIL PROTECTED] writes: That is true, However I changed the forwarding to another system which doesn't do resolveable name checks and yet the messages are continuing to go the old system. (I changed /var/qmail/alias/.qmail-postmaster) and restarted qmail. Is this appropiate ? You didn't actually need to restart qmail. The problem that you're seeing is probably just that previous messages are already in the queue and qmail's already read the older .qmail file and figured out what addresses to send them to. It'll keep trying until they bounce, but all new messages should now be going to the new machine. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Recipient MTA is rejecting bounces
Hi, I have a qmail-1.03 machine saw in my queue a few bounces in them. Also, looking at my logs I saw the following message @40003905243f24daf1b4 delivery 34: deferral: Connected_to_204.68.180.50_but_sender_was_rejected./Remote_host_said:_451_#@[]..._unresolvable_host_name_[],_see_RFC_1123,_sections_5.2.2_and_5.2.18./ Is the recipient MTA correct in its behaviour or have I misconfigured something on my side Regards, Yusuf -- Yusuf Goolamabbas [EMAIL PROTECTED]
bounces from a spam filter
I just started using qmail, for outgoing mail only. (I'm on a DSL line, and the DSL ISP's mail servers are flakey. Incoming mail -- via a different ISP that hosts my domain -- works fine. Unfortunately, I can't use their outgoing SMTP server since I'm not dialed in on one of their lines.) Most of my email gets sent successfully (this post, for example). But I've run into one site that bounces messages with a "Your SPAM not welcome" error. I've noticed that vrfy reports the same error: vrfy -vv [EMAIL PROTECTED] vrfy '[EMAIL PROTECTED]' at 'xyz.somewhere.gov' connecting to xyz.somewhere.gov (x.y.z.w) port 25 220 xyz.somewhere.gov ESMTP Sendmail 8.9.3/8.9.3; Wed, 29 Mar 2000 18:06:06 -0500 (EST) VRFY [EMAIL PROTECTED] 550 Your SPAM not welcome Your SPAM not welcome QUIT 221 [EMAIL PROTECTED] closing connection [EMAIL PROTECTED] ... User unknown My qmail control files look like this: defaultdomain foolabs.com defaulthostfoolabs.com idhost foolabs.com locals localhost.localdomain me adsl-63-197-235-82.dsl.snfc21.pacbell.net plusdomain foolabs.com rcpthosts localhost.localdomain Locals and rcpthosts are bogus, but this shouldn't matter for outgoing mail, as I understand it. Me is ugly, but it's a valid host name that resolves to my IP address. Do I have a qmail configuration problem here? The only other thing I've noticed is that xyz.somewhere.gov attempts to talk to identd (port 113) on my system, which is being rejected by my firewall. Is it common for people to configure sendmail to refuse to accept mail from systems not running identd? - Derek
Re: bounces from a spam filter
On Wed, 29 Mar 2000, Derek B. Noonburg wrote: defaultdomain foolabs.com defaulthostfoolabs.com idhost foolabs.com locals localhost.localdomain me adsl-63-197-235-82.dsl.snfc21.pacbell.net plusdomain foolabs.com rcpthosts localhost.localdomain Locals and rcpthosts are bogus, but this shouldn't matter for outgoing mail, as I understand it. Me is ugly, but it's a valid host name that resolves to my IP address. Do I have a qmail configuration problem here? The only other thing I've noticed is that xyz.somewhere.gov attempts to talk to identd (port 113) on my system, which is being rejected by my firewall. Is it common for people to configure sendmail to refuse to accept mail from systems not running identd? - Derek Derek, it's possible that the site you are trying to send mail to has pacbell's DSL IP range in its filters, much like many ISP's filter out AOL dialups, etc, etc. In this case, you may wish to make friends with someone close that runs an SMTP server on non filtered space. ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 4:40pm up 65 days, 37 min, 4 users, load average: 0.10, 0.11, 0.13
Re: bounces from a spam filter
Derek, it's possible that the site you are trying to send mail to has pacbell's DSL IP range in its filters, much like many ISP's filter out AOL dialups, etc, etc. In this case, you may wish to make friends with someone close that runs an SMTP server on non filtered space. I've heard that some(?) of PacBell's mail servers are on the ORBS list. I forgot to mention in my first email that I checked all of the public spam lists I know of: 82.235.197.63.rbl.maps.vix.com 82.235.197.63.dialups.mail-abuse.org 82.235.197.63.relays.mail-abuse.org 82.235.197.63.relays.orbs.org None of these are currently listing my IP address. Are there other common ones I'm missing? (I suppose this site could be using their own list, but it seems unlikely.) Thanks for the quick response. - Derek
Handling bounces from mailing lists on a virtual domain
I was wondering how others are handling this. For instance, say I have virtualdomains with: mydomain.com:test Then in ~test/.qmail-mylist: validname1 validname2 bogusname On my system, bounces from the above scenario get directed to [EMAIL PROTECTED] and require the file .qmail-test-mylist-owner to contain bounce mailing instructions, as opposed to what I would expect (.qmail-mylist-owner). I'm not sure exactly how the redirection for list bouncing occurs, but it seems that it is inserting the username before the list-owner name before delivery. Has anyone else run into this? Do they solve it by simply using .qmail-domain-list-owner files? (seems redundant). Or do I have something set up wrong? -- ·.¸¸.·´¯`·. Glenn R. Crownover ·.¸¸.·´¯`·. Owner/CEO - Investor's Network Cafe ·.¸¸.·´¯`·. http://www.investnetcafe.com/ ·.¸¸.·´¯`·. reply to: [EMAIL PROTECTED]
bounces
Hi all Why could be the cause of the bounces "doesn't bounce"?; I mean: all the bounces goes directly to ~alias/Mailbox without notify to sender. (TEST.deliver #4 give me a "success", not a "__#5.1.1_/" error message. All the bounces goes with a "success" to ~alias/Mailbox .qmail-mailer-daemon is defined, etc Everything is working fine besides this point. I've another qmail installations without this problem; Thanks for any advice, regards - Abel Lucano E-mail: [EMAIL PROTECTED] Aolsa
Re: bounces
On Thu, Jan 20, 2000 at 11:07:18AM +, Abel Lucano wrote: Maybe you have a ~alias/.qmail-default. That traps mail for all unknown users. Hi all Why could be the cause of the bounces "doesn't bounce"?; I mean: all the bounces goes directly to ~alias/Mailbox without notify to sender. (TEST.deliver #4 give me a "success", not a "__#5.1.1_/" error message. All the bounces goes with a "success" to ~alias/Mailbox .qmail-mailer-daemon is defined, etc -- See complete headers for more info
Re: bounces
On Thu, 20 Jan 2000, Anand Buddhdev wrote: On Thu, Jan 20, 2000 at 11:07:18AM +, Abel Lucano wrote: Maybe you have a ~alias/.qmail-default. That traps mail for all unknown users. indeed! that's the answer; sorry! best regards - Abel Lucano E-mail: [EMAIL PROTECTED] Aolsa
Re: Local bounces vs. VERP
On Tue, 4 Jan 2000, Russell Nelson wrote: Pavel Kankovsky writes: And it bounces to "user-bounce-@hostname" Yup. When the VERP part is empty, then you know that it's an QSBMF, but Qmail's Bounce Message Format is Simple to Parse. What's the big deal? 1. QSBMF may be Simple to Parse but it cannot be as simple as $EXTn 2. qmail-VERP combo should not be advertised and/or documented as something *eliminating* the need to parse bounces completely --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] "Resistance is futile. Open your source code and prepare for assimilation."
Re: Local bounces vs. VERP
Pavel Kankovsky writes:
1. QSBMF may be Simple to Parse but it cannot be as simple as $EXTn
Just about. See below.
2. qmail-VERP combo should not be advertised and/or documented as
something *eliminating* the need to parse bounces completely
Sheesh, Pavel, get a life or something! The statement of the problem
that VERP solves is that there are N+1 foreign bounce message formats,
where N is the number that you have seen before. VERP lets you
totally escape having to parse remote bounce messages. Local bounce
messages use QSBMF. Is this such a big deal??
Here's some perl code which splits out bounces, and also prunes some
stupid sendmail warnings.
$list = shift;
$_ = $ENV{LOCAL};
($addr) = m/$list-owner-(.*)/i or die "doesn't match the list name";
if ($addr) {
$addr =~ s/=([^=]*)$/\@$1/;
while() {
exit 99 if /THIS IS A WARNING MESSAGE ONLY/;
exit 99 if /^Subject: WARNING: message delayed at/;
exit 99 if /^Subject: Warning From uucp/;
exit 99 if /^Subject: Returned mail: Deferred/;
}
handle_addr($addr);
} else {
$/="";
$_=; # get rid of the email header.
$_=; # get the QSBMF
/^Hi. This is the/ or die "This is not a qmail bounce message";
while() {
last if /^-/;
/^(.*)/ or die "No recipient address";
handle_addr($1);
}
}
--
-russ nelson [EMAIL PROTECTED] http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Local bounces vs. VERP
(I am not the person complaining about this. See
http://www.ornl.gov/its/archives/mailing-lists/qmail/1997/09/msg00085.html)
I send a VERP'ed message:
QMAILUSER=user-bounce QMAILINJECT=r qmail-inject [EMAIL PROTECTED]
And it bounces to "user-bounce-@hostname" rather than to
"user-bounce-bounceme=blahblah.blah@hostname" if the bounce is generated
by the local qmail daemon. Argh.
It is easy to find what is responsible for this behaviour---the following
lines in injectbounce() in qmail-send.c:
/* owner-@host-@[] - owner-@host */
if (sender.len = 5)
if (str_equal(sender.s + sender.len - 5,"-@[]"))
{
sender.len -= 4;
sender.s[sender.len - 1] = 0;
}
I understand VERP would make the things more complicated because one would
have to generate one bounce message per failed recipient (and it would
also made bounce-bombing much easier) but this behaviour contradicts all
the marketing surrounding VERP ("VERPs---automatic recipient
identification for mailing list bounces", "If God is forwarding His mail,
the bounce message will still go to djb-sos-owner-God=heaven.af.mil@
silverton.berkeley.edu." etc) and might contradict qmail documentation (it
depends on your interpretation of the docs). Anyway, the "feature" is a
nasty suprise to anyone deluded to think qmail VERP support makes it
completely unnecessary to parse the bounces in order to figure out the
recipient address.
Fix it or document it, please. :)
--Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ]
"Resistance is futile. Open your source code and prepare for assimilation."
Re: Local bounces vs. VERP
Pavel Kankovsky writes: And it bounces to "user-bounce-@hostname" Yup. When the VERP part is empty, then you know that it's an QSBMF, but Qmail's Bounce Message Format is Simple to Parse. What's the big deal? -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | "Ask not what your country 521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
limiting the file size of bounces ?
How do I limit the filesize in bounces? Too often, a customer sent a huge mail mail through our mail relay which could not be delivered to the destination because of the size. It could not be returned to the sender either, because it is too large. And the whole message ends up in my postmaster mailbox as a double bounce :-( Then, I lowered databytes to 1Mb, because it had to be lower than on our customers mail servers to solve the problem above. A customer suggests that I instead just bounce the mail headers and the error messages back to the sender. (and discard the content of the original letter). How is that done? -- Med venlig hilsen / Regards Netdriftgruppen / Network Management Group UNI-C Tlf./Phone +45 35 87 89 41Mail: UNI-C Fax. +45 35 87 89 90 Bygning 304 E-mail: [EMAIL PROTECTED] DK-2800 Lyngby
RE: limiting the file size of bounces ?
their is a patch available for limitting bounce sizes. Maybe it is still on the qmail pages, otherwise search in the mailarchives (someone recently posted it again). Franky -- From: torben fjerdingstad[SMTP:[EMAIL PROTECTED]] Sent: Tuesday, September 07, 1999 9:34 AM To: [EMAIL PROTECTED] Subject: limiting the file size of bounces ? How do I limit the filesize in bounces? Too often, a customer sent a huge mail mail through our mail relay which could not be delivered to the destination because of the size. It could not be returned to the sender either, because it is too large. And the whole message ends up in my postmaster mailbox as a double bounce :-( Then, I lowered databytes to 1Mb, because it had to be lower than on our customers mail servers to solve the problem above. A customer suggests that I instead just bounce the mail headers and the error messages back to the sender. (and discard the content of the original letter). How is that done? -- Med venlig hilsen / Regards Netdriftgruppen / Network Management Group UNI-C Tlf./Phone +45 35 87 89 41Mail: UNI-C Fax. +45 35 87 89 90 Bygning 304 E-mail: [EMAIL PROTECTED] DK-2800 Lyngby
.qmail - deliveries and bounces
I'm still using qmail-1.01 on that machine. Today I noticed something did (no longer) work, what I thought already did (and I have a few of the emails in my folder dated later than the last modification date of the .qmail file) I want to create a bounce message for accounts of ppl that no longer work here, but I also want to drop the mail into a valid users mailbox. ~alias/.qmail-joe: [EMAIL PROTECTED] | (cat /var/qmail/alias/NO-WORKER.TXT; exit 100) (which I thought already worked, doesn't any longer) only a bounce message is delivered. However if I use ~alias/.qmail-joe: |forward [EMAIL PROTECTED] | (cat /var/qmail/alias/NO-WORKER.TXT; exit 100) it works as expected. WHY? :-)) and are the few messages I had in my box "an accident" ? \Maex -- SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses Research Development| mailto:[EMAIL PROTECTED] | you funny and you need Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0| a mouse to delete files D-80807 Muenchen | Fax: +49 (89) 32356-299 |
Re: limiting the file size of bounces ?
Van Liedekerke Franky wrote: their is a patch available for limitting bounce sizes. Maybe it is still on the qmail pages, otherwise search in the mailarchives (someone recently posted it again). I upchucked the patch at the following URL : http://www.jedi.claranet.fr/qmail-bounce.patch Anyway, it would be kewl if it was added to the Qmail home page (as a local copy because that URL will soon disappear) . Best regards, -- Frank DENIS aka Jedi/Sector One aka DJ Chrysalis [EMAIL PROTECTED] - Software : http://www.jedi.claranet.fr - - Music : http://www.mp3.com/chrysalis -
Re: .qmail - deliveries and bounces
On Tue, 7 Sep 1999, Markus Stumpf wrote: ~alias/.qmail-joe: [EMAIL PROTECTED] | (cat /var/qmail/alias/NO-WORKER.TXT; exit 100) (which I thought already worked, doesn't any longer) only a bounce message is delivered. However if I use ~alias/.qmail-joe: |forward [EMAIL PROTECTED] | (cat /var/qmail/alias/NO-WORKER.TXT; exit 100) it works as expected. WHY? :-)) and are the few messages I had in my box "an accident" ? Because forward deliveries () are always processed at last, and exit code 100 means permanent failure which prevents all not processed deliveries, which includes all forwards, because the failing delivery was a program delivery, so all forwards were to be processed. If you use 99, then it will process all previous delivery instructions in file order, so even if they were forwards, but no deliveries of the unread part of the .qmail file. This imitates the mentioned behaviour most closely, but this does not give an error message. Or of course you can use exit 0. See more at the end of the manpage of dot-qmail. Robert Varga
Re: .qmail - deliveries and bounces
Markus Stumpf writes:
I want to create a bounce message for accounts of ppl that no longer
work here, but I also want to drop the mail into a valid users mailbox.
~alias/.qmail-joe:
[EMAIL PROTECTED]
| (cat /var/qmail/alias/NO-WORKER.TXT; exit 100)
(which I thought already worked, doesn't any longer) only a bounce
message is delivered.
No, it never worked.
However if I use
~alias/.qmail-joe:
|forward [EMAIL PROTECTED]
| (cat /var/qmail/alias/NO-WORKER.TXT; exit 100)
it works as expected.
Right. That's because program deliveries are handled in order, while
forwards ('' deliveries) are done all at once at the end. Actually,
what you're doing in the second version is unreliable in the general
case. What if the second program delivery sometimes succeeded,
sometimes exited 100 and sometimes 111 (depending on the contents of
the email message, say). Well, every time it exited 111, the |forward
delivery would be re-executed and you'd get mail duplication.
The reliable way to do two program deliveries is to do one of them in
one .qmail file, and the other in another. Like this:
cat ~alias/.qmail-joe EOF
|forward [EMAIL PROTECTED]
joe-bounce
EOF
cat ~alias/.qmail-joe-bounce EOF
|cat NO-WORKER.TXT; exit 100
EOF
BTW, you don't need to put those commands in parens -- those two
commands don't need to be executed by the same shell invocation.
Also, the current directory for a program delivery in a .qmail is the
controlling user's home directory.
--
-russ nelson [EMAIL PROTECTED] http://russnelson.com
Crynwr sells support for free software | PGPok | Government schools are so
521 Pleasant Valley Rd. | +1 315 268 1925 voice | bad that any rank amateur
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | can outdo them. Homeschool!
Other People's Bounces
I'm having some problems today with people getting a bounce message for mail that they did not send. I'm looking in /var/qmail/queue, and finding LatnGrnQQs as a string in files in the bounce/ directory, and nowhere else. I'm assuming that the number in the filename must map to the other parts of the queue. If I can find no other references to that number, is it acceptable to delete those things in bounce/ ? Thanks, Monte Mitzelfelt
filtering out spam triggered double bounces
Does anybody have a filter to throw away all these double bounces I get from blocked SPAM? I don't think it would be too hard to recognize that the double bounce is from SPAM (can't find the host and the original message is itself a bounce message), but I haven't studied enough messages to know exactly what to do. Chris -- Chris Garrigues virCIO http://www.DeepEddy.Com/~cwg/ http://www.virCIO.Com +1 512 432 4046 +1 512 374 0500 4314 Avenue C O- Austin, TX 78751-3709 My email address is an experiment in SPAM elimination. For an explanation of what we're doing, see http://www.DeepEddy.Com/tms.html Nobody ever got fired for buying Microsoft, but they could get fired for relying on Microsoft. PGP signature
Re: Double Bounces
On Sat, Jul 03, 1999 at 09:25:47AM -0400, Andrew Beebe wrote: Is there a way to have double bounce messages deleted instead of delivered to the Postmaster (me)? In control/doublebounceto, put something like: doublebounce And in ~alias/.qmail-doublebounce, put a single '#' See the qmail-send man page for more on control/doublebounceto. Chris
Re: Message-ID and bounces
On Tue, 8 Jun 1999, Peter Haworth wrote: Mark Carroll wrote: The sysadmin of one of the machines I receive mail on will soon be rejecting messages that have no Message-ID, as apparently virtually all (snip) Can't you get this sysadmin to relax the rule for bounce messages? It's not like messages with as the sender are hard to spot, especially as he's going to the trouble of finding a Message-Id. Against his better judgment, he has now agreed to relax this particular policy. (-: Thanks for all the responses! -- Mark
Message-ID and bounces
The sysadmin of one of the machines I receive mail on will soon be rejecting messages that have no Message-ID, as apparently virtually all such mail that comes in with no Message-ID is unsolicited spam with the surprising exception of qmail bounce messages. Sure, I know that there's no requirement to include a Message-ID line, but isn't it eminently sensible to? I was just wondering if there was any good reason why qmail's bounce messages appear not to have one, and if there is any prospect of them acquiring one by default in the future. If this has already been covered, please point me to the appropriate message in the archive - I couldn't find it in a search. Thanks, Mark
Re: Message-ID and bounces
On 1999-06-08T16:53:04, Mark Carroll [EMAIL PROTECTED] said: The sysadmin of one of the machines I receive mail on will soon be rejecting messages that have no Message-ID, as apparently virtually all such mail that comes in with no Message-ID is unsolicited spam with the surprising exception of qmail bounce messages. Sure, I know that there's no requirement to include a Message-ID line, but isn't it eminently sensible to? I wrote a "NetiquetteEnforcer" script which I use in conjunction with ezmlm to check for specific, uhm, misunderstandings on the senders part (all windows are 160 characters wide etc), and also to check the mail as per RFC822 (at least somewhat). Basically, there are some programs out there which do not include a Message-Id - I had such a case comeing in from a popular German mail service (gmx.de/net), and RFC822 says Message-Id is optional. While I personally think thats a bug and should be made mandatory, I am not sure what a message-id would gain you in an automatic bounce. Especially with qmail, which does not log the message-id header anyway... ;-) Sincerely, Lars Marowsky-Brée -- Lars Marowsky-Brée Network Management teuto.net Netzdienste GmbH - DPN Verbund-Partner
Re: Message-ID and bounces
On Tue, 8 Jun 1999, Lars Marowsky-Bree wrote: On 1999-06-08T16:53:04, Mark Carroll [EMAIL PROTECTED] said: The sysadmin of one of the machines I receive mail on will soon be rejecting messages that have no Message-ID, as apparently virtually all (snip) (gmx.de/net), and RFC822 says Message-Id is optional. While I personally think thats a bug and should be made mandatory, I am not sure what a message-id would gain you in an automatic bounce. Especially with qmail, which does not log the message-id header anyway... ;-) It would gain me the ability to still receive bounces from others' qmails even when I'm sending mail from machines where the sysadmins refuse Message-ID-less mail on the basis that it's probably spam! (-: -- Mark
Re: Message-ID and bounces
Mark Carroll wrote: The sysadmin of one of the machines I receive mail on will soon be rejecting messages that have no Message-ID, as apparently virtually all such mail that comes in with no Message-ID is unsolicited spam with the surprising exception of qmail bounce messages. Sure, I know that there's no requirement to include a Message-ID line, but isn't it eminently sensible to? Can't you get this sysadmin to relax the rule for bounce messages? It's not like messages with as the sender are hard to spot, especially as he's going to the trouble of finding a Message-Id. -- Peter Haworth [EMAIL PROTECTED] "Paranotions, which designate constructs, may now contain metanotions and ``hypernotions'' have been introduced in order to designate protonotions" -- A. van Wijngaarden et al., _ALGOL 68 Revised Report_
Re: Message-ID and bounces
Unfortunately, medical science has determined that the type of brain damage that leads to rejection of mail based on no message-id is often associated with symptoms of rejecting null envelope senders, i.e. bounces. These patients often claim that "the voices" have told them that both of these items are spam markers. Treatment is available, and we're all hoping for a cure. -- Jeff Hayward :-) On Tue, 8 Jun 1999, Peter Haworth wrote: Mark Carroll wrote: The sysadmin of one of the machines I receive mail on will soon be rejecting messages that have no Message-ID, as apparently virtually all such mail that comes in with no Message-ID is unsolicited spam with the surprising exception of qmail bounce messages. Sure, I know that there's no requirement to include a Message-ID line, but isn't it eminently sensible to? Can't you get this sysadmin to relax the rule for bounce messages? It's not like messages with as the sender are hard to spot, especially as he's going to the trouble of finding a Message-Id.
Re: Message-ID and bounces
On Tue, 8 Jun 1999, Jeff Hayward wrote: Unfortunately, medical science has determined that the type of brain damage that leads to rejection of mail based on no message-id is often associated with symptoms of rejecting null envelope senders, i.e. bounces. These patients often claim that "the voices" have told them that both of these items are spam markers. (-: Fortunately, null envelope senders will still be fine AFAICT. -- Mark
receiving bounces...
This is strange. We have a customer who sends out a monthly newsletter to about 20,000 people. He's done this every month for about 5 months, but last month, for some reason, all the bounces came to ME. This is definitely quite mysterious because it is actually placing my email address, with the full system host name as the Return-path. The mail is being sent via qmail-inject and even when a proper Return-path is specified, it still replaces it with my personal email address. Like I said, no aliases are attached to it. The only possible explanation I can come up with for qmail knowing my email address is that I was su'd to root from my account when I compiled it but I haven't recompiled it for at least 4 months. Any one have any ideas? Thanks -- Cris Daniluk [EMAIL PROTECTED] - Digital Services Network, Inc. http://www.dsnet.net 1129 Niles-Cortland Road, Warren, Ohio 44484 [EMAIL PROTECTED] (330) 609-8624 ext. 20 Fax (330) 609-9990 The Web Hosting Specialists -
Re: receiving bounces...
Check to see if the QMAILINJECT environment variable is set.. -Dustin On Sat, 29 May 1999, Cris Daniluk wrote: This is strange. We have a customer who sends out a monthly newsletter to about 20,000 people. He's done this every month for about 5 months, but last month, for some reason, all the bounces came to ME. This is definitely quite mysterious because it is actually placing my email address, with the full system host name as the Return-path. The mail is being sent via qmail-inject and even when a proper Return-path is specified, it still replaces it with my personal email address. Like I said, no aliases are attached to it. The only possible explanation I can come up with for qmail knowing my email address is that I was su'd to root from my account when I compiled it but I haven't recompiled it for at least 4 months. Any one have any ideas? Thanks -- Cris Daniluk [EMAIL PROTECTED] - Digital Services Network, Inc. http://www.dsnet.net 1129 Niles-Cortland Road, Warren, Ohio 44484 [EMAIL PROTECTED] (330) 609-8624 ext. 20 Fax (330) 609-9990 The Web Hosting Specialists -
bounces
I received a bunch of these today: Subject: failure notice Date: 19 Apr 1999 07:38:51 - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi. This is the qmail-send program at julia.argo.be. I tried to deliver a bounce message to this address, but the bounce bounced! [EMAIL PROTECTED]: Connected to 207.112.133.160 but sender was rejected. Remote host said: 501 bogus mail from --- Below this line is the original bounce. snip I am correct in assuming that the other side is refusing these messages because it can't handle ? Or is there something misconfigured at my side? bt -- Bart Blanquart [EMAIL PROTECTED] tel (02)50 51 916 fax (02)50 51 930 I Fear A State That Kills Far More That I Fear A Man Who Has Killed.
Re: bounces
On Mon, Apr 19, 1999 at 11:48:10AM +0200, Bart Blanquart wrote: Hi. This is the qmail-send program at julia.argo.be. I tried to deliver a bounce message to this address, but the bounce bounced! [EMAIL PROTECTED]: Connected to 207.112.133.160 but sender was rejected. Remote host said: 501 bogus mail from --- Below this line is the original bounce. snip I am correct in assuming that the other side is refusing these messages because it can't handle ? Or is there something misconfigured at my side? That machine is running Windows IMail, which is refusing an envelope sender of . It's broken. There is no misconfiguration on your side. If you want to do something about it, write to the postmaster there and tell them to read RFC 821 sections 5.2.9 and 5.3.3 -- System Administrator See complete headers for address, homepage and phone numbers
RE: aol.com bounces... our problem or their problem?
According to the FAQ: 2.5. How do I deal with ``CNAME lookup failed temporarily''? The log showed that a message was deferred for this reason. Why is qmail doing CNAME lookups, anyway? Answer: The SMTP standard does not permit aliased hostnames, so qmail has to do a CNAME lookup in DNS for every recipient host. If the relevant DNS server is down, qmail defers the message. It will try again soon. -Original Message- From: Sam [mailto:[EMAIL PROTECTED]] Sent: Monday, April 19, 1999 11:02 AM Cc: [EMAIL PROTECTED] Subject: Re: aol.com bounces... our problem or their problem? David A Galbraith CIRT writes: I'm getting a bunch of these in the logs... 921710651.349026 starting delivery 46759: msg 2501 to remote [EMAIL PROTECTED] 921710651.378220 delivery 46759: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/ Is this something I should fix/can fix? or is this something aol has broken? Most likely is that the large DNS response packet for the aol.com is getting truncated, breaking Qmail. Either hardcode one of AOL's mail servers into your smtprouters, or patch Qmail to support larger DNS packets. -- Sam
Re: aol.com bounces... our problem or their problem?
David A Galbraith CIRT [EMAIL PROTECTED] writes:
| 921710651.349026 starting delivery 46759: msg 2501 to remote [EMAIL PROTECTED]
| 921710651.378220 delivery 46759: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/
|
|
| Is this something I should fix/can fix? or is this something aol has
| broken?
Yes, it's a deliberate bug in dns.c. The simplest fix is this:
diff -r1.1 dns.c
24c24
static union { HEADER hdr; unsigned char buf[PACKETSZ]; } response;
---
static union { HEADER hdr; unsigned char buf[115]; } response;
aol.com bounces... our problem or their problem?
I'm getting a bunch of these in the logs... 921710651.349026 starting delivery 46759: msg 2501 to remote [EMAIL PROTECTED] 921710651.378220 delivery 46759: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/ Is this something I should fix/can fix? or is this something aol has broken? Thanks, -d. +---+ | David Galbraithdgalb@ University Of New Mexico | |Systems Analyst unm.edu(505)-277-8499| +---+
Re: aol.com bounces... our problem or their problem?
David A Galbraith CIRT writes: I'm getting a bunch of these in the logs... 921710651.349026 starting delivery 46759: msg 2501 to remote [EMAIL PROTECTED] 921710651.378220 delivery 46759: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/ Is this something I should fix/can fix? or is this something aol has broken? Most likely is that the large DNS response packet for the aol.com is getting truncated, breaking Qmail. Either hardcode one of AOL's mail servers into your smtprouters, or patch Qmail to support larger DNS packets. -- Sam
Re: aol.com bounces... our problem or their problem?
On Mon, Apr 19, 1999 at 09:35:29AM -0600, David A Galbraith CIRT wrote: I'm getting a bunch of these in the logs... 921710651.349026 starting delivery 46759: msg 2501 to remote [EMAIL PROTECTED] 921710651.378220 delivery 46759: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/ Is this something I should fix/can fix? or is this something aol has broken? This came up a few days ago. The problem is that AOL is returning greater than 512 bytes for an "any" lookup, and qmail doesn't handle that. (There was a huge flame war with Dan on the subject several months ago.) There are a couple of solutions to the problem. One is to patch qmail to handle these larger DNS responses. Check http://www.qmail.org for patches. The easier solution is to avoid AOL DNS lookups altogether by making an entry in smtproutes for AOL. Look up the MX records for aol.com manually, and put one of the best-preference MX exchangers in control/smtproutes, like so: aol.com:za.mx.aol.com Chris
Re[2]: Foreign language and qmail bounces
Hello Frank, Friday, April 16, 1999, 12:28:22 PM, you wrote: Do you have any suggestion or solution? FT I wouldn't do it. It would help your users but confuse more people around FT the world that cannot understand your localized bounce messages. Bounces FT typically go to outside users. FT In any case your users still get bounce messages from mailers all over the FT world in English. It's kinda difficult to explain 'message bounce' to some stupid clients. So _adding_ other language text to the bounce is a good thing... I'd like this feature, but only if it will add "Content-Type: text/plain; charset=koi8-r" to the header as well -- otherwise it will be nearly useless, at least with Russian (hell,there are 6 enconding types). -- Roman V. Isaev http://www.gunlab.com.ru Moscow, Russia
Foreign language and qmail bounces
Hi, I am thinking about include failure description translations in qmail bounce messages, without violate QSMBF nor HCMSSC specs. This change would help our users and user support department. I read the source code a little and the description labels are spreaded in many files and some of them are composed with several hardcoded parts. Even more, there are string comparisons between labels and failure buffers. So, I'm worried about if this change could break the qmail behaviour. Do you have any suggestion or solution? Thanks, David. = = = David Jorrin [EMAIL PROTECTED] Get your free email from AltaVista at http://altavista.iname.com
Bounces and envelope sender
This is not a qmail question per se, but a general "internet mail" question which came up because my qmail system got in a mail loop with someone else's SLMail system. I'm asking here because this falls into the domain of expertise that most people on this list excel at ;. Most mail systems I've dealt with, when bouncing email, set the envelope sender to "" (and the header sender to "mailer-daemon" or "postmaster" or some such). This keeps it from double-bouncing back to the original system. Is this the result of any particular mail-related RFC, or a widespread but unofficial convention, or an unofficial convention which I incorrectly assumed was widespread? -- gowen -- Greg Owen -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] Please note my new [EMAIL PROTECTED] address which will become my default address in March, and which works now.
Re: Bounces and envelope sender
It absolutely is a standard! I got into a pissing match the other day
with an NT mail server admin somewhere in Vancouver, WA, who's mail
server was rejecting email with NULL return-paths. I told him his
customers would not know their mail is bouncing when sending to a
large number of domains.. well he basically started telling me that I
should be setting the bounce envelope sender to something other than
NULL, and I told him "no way". After he called me a "d*ck" I hung
up the phone :)
BTW, he instituted the block on null return-paths due to being
mailbombed or something by someone. As if the dude couldn't have
done the same thing with a forged return address somewhere at aol.com.
Goodness.
Aaron
To quote RFC 821 (SMTP):
If a server-SMTP has accepted the task of relaying the mail and
later finds that the forward-path is incorrect or that the mail
cannot be delivered for whatever reason, then it must construct an
"undeliverable mail" notification message and send it to the
originator of the undeliverable mail (as indicated by the
reverse-path).
This notification message must be from the server-SMTP at this
host. Of course, server-SMTPs should not send notification
messages about problems with notification messages. One way to
prevent loops in error reporting is to specify a null reverse-path
in the MAIL command of a notification message. When such a
message is relayed it is permissible to leave the reverse-path
null. A MAIL command with a null reverse-path appears as follows:
MAIL FROM:
To quite RFC 1123 (Requirements for Internet Hosts) section 5.2.9:
5.2.9 Command Syntax: RFC- 821 Section 4.1.2
The syntax shown in RFC- 821 for the MAIL FROM: command omits the
case of an empty path: "MAIL FROM:" (see RFC- 821 Page 15). An
empty reverse path MUST be supported.
Quoting Greg Owen {gowen} ([EMAIL PROTECTED]):
This is not a qmail question per se, but a general "internet mail"
question which came up because my qmail system got in a mail loop with
someone else's SLMail system. I'm asking here because this falls into the
domain of expertise that most people on this list excel at ;.
Most mail systems I've dealt with, when bouncing email, set the
envelope sender to "" (and the header sender to "mailer-daemon" or
"postmaster" or some such). This keeps it from double-bouncing back to
the original system.
Is this the result of any particular mail-related RFC, or a
widespread but unofficial convention, or an unofficial convention which I
incorrectly assumed was widespread?
--
gowen -- Greg Owen -- [EMAIL PROTECTED] -- [EMAIL PROTECTED]
Please note my new [EMAIL PROTECTED] address which will
become my default address in March, and which works now.
--
Aaron L. Meehan [EMAIL PROTECTED]
Systems Administrator Central Oregon Internet
http://www.coinet.com/
Re: Bounces and envelope sender
On Tue, 6 Apr 1999, Aaron L. Meehan wrote: with an NT mail server admin somewhere in Vancouver, WA, who's mail server was rejecting email with NULL return-paths. I told him his It isn't just NT, sadly. I believe the sendmail.cf that ships with RedHat rejects NULL return-paths, also in the name of anti-spam. (I can't verify this because I don't have any vanilla sendmail.cf's around for my Linux boxen...) Aaron, thanks for the RFC references. I'll forward them to the other admin and let him take it up with the vendor if he so chooses... -- gowen -- Greg Owen -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] Please note my new [EMAIL PROTECTED] address which will become my default address in March, and which works now.
Re: Sending mail with bounces going elsewhere
: I'm presently trying to send out mail where the sender and from fields : are different. I'm using the line : :env - QMAILUSER=$From QMAILSUSER=$Sender qmail-inject $Recipient msg : : and the mail arrives with a "From " string of $Sender$From, no "Sender:" line, : and a "From:" field of $From. Is there any way to get the "Sender:" field in : there (I already tried putting it in the message) and to get the "From " field : to just show the sender and not a concatenation of the two strings? : : : If you are trying to send the retuned mail someplace else, modify the : Return-Path: emailaddress Actually, I hadn't tried modifying that line directly but I did find that if I specified QMAILSUSER and QMAILSHOST along with QMAILUSER then it worked. The values of the QMAILS variables get put in the Return-Path and From fields and the other get's put in the From: field. -- Matthew Harrell Beauty is in the eye of the beer Simulation Technology Division, SAIC holder. [EMAIL PROTECTED]
Re: Specific bounces
On Thu, Mar 25, 1999 at 11:00:08AM -0500, Jean Caron wrote:
Hi all,
Just wondering how much is involved in creating a "unique" bounce message
for a specific user. I wouldn't want to damage the regular process, just
had to it. Basically, if John Doe sends a message to a valid address,
bounce it anyway using this "modified" version of the bounce text/message.
It depends on whether you want to append a specific message to the usual
bounce message generated by qmail, or generate a completely different
bounce message.
For the former, stick this into a .qmail file for the valid address:
|bouncesaying "some specific message" [ "$SENDER" = "John.Doe@whatever" ]
./Mailbox
This will return a normal qmail bounce ("Hi. This is the ...") to John Doe,
with "some specific message" as the reason for the bounce.
If you want to construct a completely specific bounce message, then you'll
have to check if the sender is John Doe, and inject a *new* message to him,
with a null envelope sender, and a From: header of [EMAIL PROTECTED],
and consisting of a body of your choice. Something in .qmail like:
|if [ "$SENDER" = "John.Doe@whatever" ] then; (echo "From:
[EMAIL PROTECTED]; echo ""; echo body) | qmail-inject -f '';fi
./Mailbox
This is not tested code, just a pointer to how it can be done.
--
System Administrator
See complete headers for address, homepage and phone numbers
Specific bounces
Hi all, Just wondering how much is involved in creating a "unique" bounce message for a specific user. I wouldn't want to damage the regular process, just had to it. Basically, if John Doe sends a message to a valid address, bounce it anyway using this "modified" version of the bounce text/message. What do you think ? John --
Bounces off of incorrect smtproutes
Short summary: I screwed something up and bounced a lot of mail. It seems to me that the mistake I made could be handled differently, and I'd just like to explore it as an idea, see if it makes sense to anyone else. I'm not blaming qmail or saying "qmail should definitely do this." I'm just exploring an idea. I have 2 qmail mail relays. Currently, they forward all mail to a Xerox mail relay, which then relays it through the Xerox firewall to the (ex-)Xerox company where I work. We are migrating to our own network, and yesterday we installed the firewall and planned to go live. (We didn't go live because of other problems that cropped up). As part of the attempted switch, I took down the internal mail server to transfer its files to the new mail server (the old one will remain up as a Xerox host for a while). Since I expected the new mail server would be accepting mail by the end of the day, I stopped the mail relays from passing mail onto the Xerox relay. I did this by configuring smtproutes to route to an (unreachable) internal network address. We spent the entire day setting up the firewall and running tests on a small test network. Several tests failed, so at 4:30 we gave up on the plan to switch users over and re-enabled the old (Xerox) internal mail server. Then I reconfigured the external mail relays to relay through Xerox again. Unfortunately, after a long day of intensive work with 5 subnets and 2 domain names, I messed up and reset the smtproutes file on the main relay to "mailer-east.scansoft.com" instead of "mailer-east.xerox.com," the Xerox relay. Of course, "mailer-east.scansoft.com" doesn't exist. Qmail looked it up in DNS, found it didn't exist, and bounced the 300 or so messages in its queue back to their senders. I didn't think that was a lot of mail, but the VP of Sales sure did ;. Now, it seems to me that a case where the smtproutes - an internal control file set by the mail administrator - is wrong like that, might be treated differently. Perhaps rather than bouncing the (innocent ;) mail messages, they could remain queued, and mail be sent to the postmaster. Of course, if the postmaster is relayed to that smtproute, he wouldn't get it, but presumably he'd notice sooner or later that a) he wasn't getting mail from that system he just modified and b) the disks on it were filling up. Again presumably, he'd check the logs, see the error messages that clue him in to his internal mistake, and let him fix it without losing mail. Obviously, qmail requires almost everything to be kosher DNS wise for security and spam reasons. But it seems to me an invalid smtproute is pretty clearly an administrator error as opposed to an attempt to spoof, overload, enter, or otherwise attack the server. So, what do you think of the following ideas? 1) qmail could treat unresolvable hosts in its control files as operator errors and leave affected mail in the queue rather than bouncing, and also try to notify the operator. 2) Perhaps changes to control files could somehow require something like qmail-lint that checks stuff like this? (I note qmail-lint doesn't check smtproutes). But the key would be requiring a check made before changes would take affect. The key to this question is, it seems to me that some changes (like smtproutes) take affect immediately, and that limits checkability. Or maybe I'm misunderstanding... 3) get a smarter and more careful sysadmin. For the obvious reasons, I heartily disapprove of this option. Any thoughts on all this? -- gowen -- Greg Owen -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] Please note my new [EMAIL PROTECTED] address which will become my default address in March, and which works now.
Re: qmail bounces cc messages
Hi, Sometimes when somebody sends e-mails with cc, one of cc bounces saying that the envelope does not exist. Any ideas? Yes. The domain part of whatever return address you're using is not in DNS. Look at what return address is being used, and why it's not in DNS.
