> Sorry, guys, I couldn't resist: > > -----Original Message----- > From: Frank A. Vorstenbosch > > > >You're obviously ignorant of how email works -- a POP server can't split > >attachments from the emails they came with, because the attachments are > just > >like text to the server. Your email (client) program may make it look > >like it's separate, of course ** UNLESS YOU'RE READING THE DIGEST **. > > > > > >Me too. All those stupid ms-tnef attachments, HTML attachments and > binaries > >should be caught by the listserver and not sent out. > > ********** > So, the listserver can discern the attachments, but the POP server can't? > Hmmm. I've obviously been in this business too long to see the forest > anymore. It would be fairly trivial to have the listserver check the mail for some specific parameter before it resent the messages to the world. A listserver receives the messages and normally just turns around and sends them out. Having them check if the e-mail is above a certain size or has attachments is not a big deal. As for the pop-server, are you running your own pop-server so you can get in and modify the code? I am running a pop-server for about 3K users, and am not about to modify the code so some of them can set no-attachments. As it sits my (and almost everyone elses) users have a choice, download the mail message or let it sit in their mailbox until their box fills up and I start rejecting mail. POP is NOT IMAP, which lets you look at headers and delete things without reading them, at least not without a new, more intelligent client. Think of it this way, the post office (listserv and MTA) can refuse to take your package, however, once the package is accepted it is going to end up on the recipients doorstep (on his machine). Now I know why I don't try to tell the electronic guru's their business, so far I've been told spurious things about POP, and I've also been told that JPEG's are not fit for sending schematics by someone that looked at an overly compressed jpeg on a bad viewer once. Roger