CINXE.COM

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head><script type="text/javascript" src="/_static/js/bundle-playback.js?v=HxkREWBo" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script>window.RufflePlayer=window.RufflePlayer||{};window.RufflePlayer.config={"autoplay":"on","unmuteOverlay":"hidden"};</script> <script type="text/javascript" src="/_static/js/ruffle/ruffle.js"></script> <script type="text/javascript"> __wm.init("http://web.archive.org/web"); __wm.wombat("https://lsoft.com/news/techtipLSV-issue1-2008-us.asp","20240305150723","http://web.archive.org/","web","/_static/", "1709651243"); </script> <link rel="stylesheet" type="text/css" href="/_static/css/banner-styles.css?v=S1zqJCYt" /> <link rel="stylesheet" type="text/css" href="/_static/css/iconochive.css?v=3PDvdIFv" />  <title>LISTSERV at Work - Issue 1, 2008</title> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <style type="text/css">  </style> </head> <body> <table> <tr><td> <table width="622" cellpadding="0" cellspacing="0" border="0" style="border:1px solid #CC6600"> <tr><td><a href="issue1-2008-us.asp"><img src="/web/20240305150723im_/https://lsoft.com/news/issue1-2008/header.jpg" alt="LISTSERV at Work" width="620" height="75" border="0"></a></td></tr> <tr><td bgcolor="#6699CC" width="650" height="5"></td></tr> <tr><td bgcolor="#3366CC" width="650" height="5"></td></tr> <tr><td bgcolor="#FFFFFF"> <table width="100%" cellpadding="10" cellspacing="0" border="0"> <tr><td> <p class="head">Tech Tip (LISTSERV) – Issue 1 – 2008</p> <p class="body"><b>Q: Why is it better to send links to large attachments through LISTSERV rather than the attachments themselves?</b></p> <p class="body"><b>Answer by John Harlan<br/>Vice President, Computer Services, L-Soft</b></p> <p class="body">One of the many extremely convenient features of LISTSERV has long been its ability to include attachments in electronic mailings. It is undeniably very handy to be able to send a file – a word processing document, a spreadsheet, a photograph, a sound file, or a PDF file – along with an email message to a group of recipients.</p> <p class="body">It certainly adds impact to an email message to your circle of family and friends ("I've just seen space aliens!") when you are able to attach your own digital photo of the smiling, waving space people and a sound file of your interview with them. Nothing makes something real like solid documentation.</p> <p class="body">Back at the office, it can also be extremely convenient to send a draft report and perhaps a supporting spreadsheet to your colleagues, in advance of a meeting.</p> <p class="body">Both examples represent reasonable uses of LISTSERV's attachment capability because both assume a relatively small recipient audience (in the latter example, usually all within a single organization's email system, and each with a probable need for possession of their own copy of your documents), and the sending of reasonably small documents not likely to exceed local mail system thresholds for message or attachment size, or user mailbox storage quotas.</p> <p class="body">Many email senders, however, choose to send general documents of all sizes – smaller ones such as flyers and brochures, as well as larger ones, such as newsletters – as attachments, usually as a PDF file. Often the information being sent as a PDF is already accessible on the sender's website, or could easily be placed there.</p> <p class="body">Is it possible to send your latest full-color brochure or newsletter as a PDF attachment to all of your recipients worldwide? "Yes," you're thinking, "I've been doing that forever." And you are correct: It <i>is</i> possible to <i>send</i> it. "Have most of your recipients actually been <i>receiving</i> it successfully (in a timely manner, without exceeding their mailbox storage quota, etc.)?" is the more relevant question. There is also the consideration of whether the attempted delivery has caused collateral damage along the way.</p> <p class="body"><i>Having</i> the capability to send large attachments to large numbers of recipients does not obligate anyone to <i>use</i> that capability – especially when there are so many good reasons not to do so.</p> <p class="body">First and foremost is recipient preference: Your recipients do not necessarily want to receive an actual attachment if they can access the document online via a link in your email message. Anecdotal evidence suggests many recipients actually prefer a link they can easily bookmark for convenient future reference. If they decide that they want their own copy of the document, the bookmarked link gives them that option; they can download at will.</p> <p class="body">Attachments can prove problematic for recipients for a variety of reasons:</p> <ul> <li class="body">They may not be accepted for delivery at all by some email systems (as a matter of site security configuration), or their delivery acceptance may be conditional based on file size or type.</li> <li class="body">They may run afoul of inbound Simple Mail Transfer Protocol (SMTP) servers, or mail filtering and virus scanning applications in the receiving email system's infrastructure.</li> <li class="body">Their delivery, if accepted, may be delayed due to the above.</li> <li class="body">Even if accepted for delivery by the recipient's mail system, they may themselves exceed the individual recipient's email storage quota, or contribute substantially to exceeding the quota, thus complicating life for the recipient.</li> </ul> <p class="body">These are a few of the possible issues for the recipient. Senders may encounter their own set of problems by including large attachments, such as triggering blocklisting by the intended recipient systems or by independent anti-spam monitoring services.</p> <p class="body">Aside from the immediate, logistical challenges presented by sending large attachments to large numbers of recipients, in this time of heightened awareness of resource conservation and efficiency, it should be noted that sending attachments uses more bandwidth – at both ends (sender and recipient) as well as everywhere in between – than sending links.</p> <p class="body">Another reason to send links rather than attachments involves electronic mailing management and assessment solutions, such as L-Soft's LISTSERV Maestro. LISTSERV Maestro makes it possible to track how many recipients follow the links included in an email message. Not only is the risk of possible delivery problems and recipient displeasure caused by sending big attachments eliminated, the link being sent instead can provide quantifiable result data: How many recipients accessed the document, how often, and (if desired), who they were.</p> <p class="body">How can control be exercised over attachments processed through a LISTSERV server?</p> <p class="body">At the server level, L-Soft gives LISTSERV administrators a site configuration keyword, FILEMAXL=, which determines the "maximum acceptable size, in lines, of an incoming non-mail file" accepted by LISTSERV. "Non-mail" files include other non-message traffic such as LISTSERV command communications, with the result that such files need to be allowed; this value should never be set to 0. Beyond a minimal size permitting such traffic, however, this setting becomes the control point for attachment size. (To locate this keyword from the LISTSERV 15.5 web interface, select "Server Administration" from the toolbar, select "Site Administration" from the pull down menu, select "Site Administration" a second time, select the "Optimization" tab, and scroll down to "FILEMAXL.")</p> <p class="body">The default value of FILEMAXL is 500000 lines. For calculation purposes, L-Soft Computer Services uses this in-house rule of thumb: 1 MB = approximately 16,000 lines, averaging 65 bytes per line, or 13,000 lines, averaging 80 bytes per line. LISTSERV's default setting works out somewhere between 31.3 MB (at 65 bytes per line) and 38.5 MB (at 80 bytes per line).</p> <p class="body">The LISTSERV default setting is generous – possibly to a fault – and for our in-house hosting services, L-Soft has recently begun experimenting with lowering the FILEMAXL setting to 150000 (9.4 MB at 65 bytes per line, to 11.5 MB at 80 bytes per line) on selected ListPlex nodes where extremely large attachments have been especially problematic.</p> <p class="body">L-Soft's object in adjusting this setting for our hosting customers is not to prevent their use of attachments, but to allow attachments in a way that is still useful, but protects both sender and recipient from the problems described above, and is more Internet-friendly of L-Soft as a major opt-in / double opt-in hosting service provider.</p> <p class="body">At the list level, L-Soft gives list owners the ATTACHMENTS= and SIZELIM= list configuration keywords, specifying (respectively) whether (and if so, what type of) attachments are allowed to be sent through the list, and the size limitation for messages (including their attachments) sent through the list. Like FILEMAXL, the SIZELIM= value can be specified in number of lines (see rule of thumb calculation guidelines above); SIZELIM= can also be specified in kilobytes (K) or megabytes (M).</p> <p class="body">From the LISTSERV 15.5 web interface, select "List Management" from the toolbar, select "List Configuration" from the pull down menu, select "List Configuration Wizard," and select the "Access Control" tab for the ATTACHMENTS= keyword or the "List Maintenance" tab for the SIZELIM= keyword.</p> <p class="body">As always, L-Soft's world-class support, training and consulting staff are available to assist you with the particulars of LISTSERV configuration for attachment use. Please contact your L-Soft sales representative at <a href="http://web.archive.org/web/20240305150723/mailto:sales@lsoft.com">sales@lsoft.com</a>, or L-Soft customer support at <a href="http://web.archive.org/web/20240305150723/mailto:support@lsoft.com">support@lsoft.com</a> for details.</p> </td></tr> </table> </td></tr> <tr><td bgcolor="#3366CC" width="650" height="3"></td></tr> <tr><td background="/web/20240305150723im_/https://lsoft.com/news/issue1-2008/footer.jpg" width="620" height="24"> <table width="100%" cellspacing="0" cellpadding="4" border="0"> <tr> <td width="50%" height="24" nowrap><p style="font-family: verdana, arial, helvetica, sans-serif; font-size:11px; font-weight: bold; color: #000000; text-align:left"><a href="n-about.asp" style="font-family: verdana, arial, helvetica, sans-serif; font-size:11px; font-weight: bold; color: #000000; text-decoration: none">About Newsletter</a> | <a href="n-subscribe.asp" style="font-family: verdana, arial, helvetica, sans-serif; font-size:11px; font-weight: bold; color: #000000; text-decoration: none">Subscription</a> | <a href="n-archives.asp" style="font-family: verdana, arial, helvetica, sans-serif; font-size:11px; font-weight: bold; color: #000000; text-decoration: none">Archives</a> | <a href="n-contact.asp" style="font-family: verdana, arial, helvetica, sans-serif; font-size:11px; font-weight: bold; color: #000000; text-decoration: none">Contact</a></p></td> <td width="50%" height="24" nowrap><p style="font-family: verdana, arial, helvetica, sans-serif; font-size:11px; font-weight: bold; color: #000000; text-align:right">© L-Soft 2008. All Rights Reserved</p></td> </tr> </table> </td></tr> </table> </td></tr> </table> <script async src="http://web.archive.org/web/20240305150723js_/https://www.googletagmanager.com/gtag/js?id=UA-3167554-2"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-3167554-2'); </script> </body> </html>