Re: Messages reinjected to this mailing list
Mark Weinem writes: D. J. Bernstein: This sort of idiocy happens much more often than most subscribers know, thanks to a broken piece of software by Eric Raymond called fetchmail. Is there a good fetchmail alternative? I think that fetchmail can be configured to work reliably, but it isn't by default. -- -russ nelson [EMAIL PROTECTED] http://crynwr.com/~nelson Crynwr supports Open Source(tm) Software| PGPok | Good parenting creates 521 Pleasant Valley Rd. | +1 315 268 1925 voice | an adult, not a perfect Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | child.
Re: Messages reinjected to this mailing list
D. J. Bernstein: This sort of idiocy happens much more often than most subscribers know, thanks to a broken piece of software by Eric Raymond called fetchmail. Is there a good fetchmail alternative? Mark Weinem
Re: Messages reinjected to this mailing list
On Sat, 12 Jun 1999, Mark Weinem wrote: D. J. Bernstein: This sort of idiocy happens much more often than most subscribers know, thanks to a broken piece of software by Eric Raymond called fetchmail. Is there a good fetchmail alternative? Perl, C, even shell will do. The POP3 protocol is so trivial, that any scripting language will do the job. I took one look at what a pig fetchmail is, I got rid of it ASAP, and quickly coded my own client in C++.
Re: Messages reinjected to this mailing list
On Sat, 12 Jun 1999 03:45:53 +0200 "Mark Weinem" wrote: D. J. Bernstein: This sort of idiocy happens much more often than most subscribers know, thanks to a broken piece of software by Eric Raymond called fetchmail. Is there a good fetchmail alternative? Fetchmail to pick up mail from a POP3 or IMAP mailbox and deliver it locally is reasonable. Not a great program, but it mostly works. When fetchmail is used to turn a single POP3 or IMAP maildrop into a mail spool for a whole domain there are problems. To do this fetchmail wants to: (i) download the mail (fair enough) (ii) figure out the envelope sender and recipient addresses (Danger!) (iii) re-inject the mail into a local mail spool (hmm) Much goes wrong at point (ii), since sendmail sometimes trashes envelope recipient information. There are also opportunities to mess up at (iii), either by misconfiguration or when the MTA the mail is injected into is really lame. Good alternatives for spooling mail for a domain for later retrieval include serialmail, on-demand SMTP and even UUCP. Regards, Giles
Re: Messages reinjected to this mailing list
Is there a way of doing on-demand SMTP without an IP for the client machine? (Ie., the client is IP masqueraded, and uses a private network IP-ETRN requires an IP.) Russ Nelson has some great hacks around serialmail. One of the best uses a dummy POP mailbox, and every time there's a successful login on that POP mailbox, fires up serialmail to send all of the spooled mail to the IP that's POP-ing. It was about three lines of code. If your client dials in using PPP to a Unix box, it's usually easy to start serialmail from the PPP startup script, again to whatever IP they're connected on, so the mail gets delivered each time they call in. -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 [EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
Re: Messages reinjected to this mailing list
+ "D. J. Bernstein" [EMAIL PROTECTED]: | Last night, [EMAIL PROTECTED] reinjected thirty old messages | from various authors to [EMAIL PROTECTED] In case anyone, like me, would like to purge their own archives of this list of the reinjected messages, they appear to be the messages numbered 31855-31884 inclusive, as numbered in envelope sender addresses. These were all injected into the queue by uid 0 on mail.ordertek.com in the 66 second time period from 4 Jun 1999 22:40:33 - to 4 Jun 1999 22:41:39 -. - Harald
Messages reinjected to this mailing list
Last night, [EMAIL PROTECTED] reinjected thirty old messages from various authors to [EMAIL PROTECTED] This sort of idiocy happens much more often than most subscribers know, thanks to a broken piece of software by Eric Raymond called fetchmail. Fortunately, qmail and ezmlm have loop-prevention mechanisms that stop these messages before they are distributed to subscribers. The messages end up bouncing to the wrong place, thanks to another fetchmail bug, but at least the mailing list is protected. However, in this case, [EMAIL PROTECTED] eliminated all the fields that could possibly stop a loop---Delivered-To, Mailing-List, Received, Message-ID, even Date---before reinjecting the messages. Neither qmail nor ezmlm realized that these weren't valid new messages. ---Dan
Re: Messages reinjected to this mailing list
Dan and everyone else, Please accept my apology for this screw up on my part. This was of course unintentional and I regret and probelms this may have caused. I was forced to switch pop/imap servers (from the UW patched one to cryus ) and was left with a bunch of mail sitting in users maildirs. Of course cyrus doesn't use maildirs so the only way I could think to "move" them was to "remail" them. I spent hours combing the mailing list archives and found several soultions. It appears that a few of my attempts failed badly. Again I apologize to Dan and anyone else that was inconvienced by my stupidity. --Dave At 03:02 PM 6/5/99 , D. J. Bernstein wrote: Last night, [EMAIL PROTECTED] reinjected thirty old messages from various authors to [EMAIL PROTECTED] This sort of idiocy happens much more often than most subscribers know, thanks to a broken piece of software by Eric Raymond called fetchmail. Fortunately, qmail and ezmlm have loop-prevention mechanisms that stop these messages before they are distributed to subscribers. The messages end up bouncing to the wrong place, thanks to another fetchmail bug, but at least the mailing list is protected. However, in this case, [EMAIL PROTECTED] eliminated all the fields that could possibly stop a loop---Delivered-To, Mailing-List, Received, Message-ID, even Date---before reinjecting the messages. Neither qmail nor ezmlm realized that these weren't valid new messages. ---Dan
