From owner-freebsd-isp Tue Jun 11 21:32: 2 2002 Delivered-To: freebsd-isp@freebsd.org Received: from ren.sasknow.com (ren.sasknow.com [207.195.92.131]) by hub.freebsd.org (Postfix) with ESMTP id 4749D37B407 for ; Tue, 11 Jun 2002 21:31:58 -0700 (PDT) Received: from localhost (ryan@localhost) by ren.sasknow.com (8.11.6/8.11.6) with ESMTP id g5C4Vva66132 for ; Tue, 11 Jun 2002 22:31:57 -0600 (CST) (envelope-from ryan@sasknow.com) Date: Tue, 11 Jun 2002 22:31:57 -0600 (CST) From: Ryan Thompson To: freebsd-isp@freebsd.org Subject: sendmail(8) meets the digital camera Message-ID: <20020611220627.U63701-100000@ren.sasknow.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Here's the funny story: One of our very nice hosting customers returned from vacation at 8am this morning... complete with a 3 megapixel digital camera. The guy constructed a ~5MB email and sends it out in one shot to a list of no fewer than 228 of his very closest contacts. You can do the math on that. :-) The traffic was no problem (we've had a lot worse), but a long time ago, I set up a cron job to process the sendmail queue every 15 minutes. Now, in the wake of this post-vacation payload, I'm seeing some different unusual things every fifteen minutes with two (and only two) of the recipients of the same message: Jun 11 21:58:27 ren sendmail[64424]: g5BDvL606361: to=, delay=14:01:05, xdelay=00:03:34, mailer=esmtp, pri=15502013, relay=theirisp.com. [205.136.0.57], dsn=4.0.0, stat=I/O error Is there any way to track down this "I/O" error? Surely, it's on "theirisp"'s end... probably a broken mailserver? Jun 11 21:58:30 ren sendmail[64424]: g5BDvL606361: to=, delay=14:01:08, xdelay=00:00:03, mailer=esmtp, pri=15502013, relay=diffisp.com. [200.50.68.3], dsn=4.3.1, stat=Deferred: 452 Message for would exceed mailbox quota That is a bit unorthodox, no? Why wouldn't diffisp just accept delivery and then send a bounce back to the sender as usual, instead of forcing us to keep it in our queue and hammer them until *their* user gets around to cleaning out his/her inbox? :-) I would guess their setup is just broken. Am I right? These two entries have been recurring in maillog every time the queue script runs, and it's getting more than a little irritating. :-) For now I've just backed off the sendmail queue script to run half as often. Any ideas/suggestions as to what I could do to avoid this problem, both immediately, and for similar occurences in the future? Thanks, - Ryan -- Ryan Thompson SaskNow Technologies - http://www.sasknow.com 901 1st Avenue North - Saskatoon, SK - S7K 1Y4 Tel: 306-664-3600 Fax: 306-664-3630 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message