[tcpdump-workers] Returned mail: see transcript for details
- This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
[tcpdump-workers] Fgnzqhitu
The original message was received at Thu, 10 Mar 2011 18:00:00 +0100 from wireshark.org [130.29.114.52] - The following addresses had permanent fatal errors - - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
[tcpdump-workers] delivery failed
ôªN½¯î -ý :Ø~ëZ}4£µz®/zR° ¦µhÑ¿ï¢gÖ*O»aÉêÕÙL¬yݵ³\£ ¦µJ«Íò (ÛÖg~<¯««GÕï&xØb16& 6ó¶G·¡ Á9VÊ1¤¸%S´Ê71 Þal \"&ØÙ÷\4ÕFá& ç?Ðû¿bOÜÍç ¥çx) 5ûºÜµ[ø¢N9ÅÃöã9/Ðáµ¾uè WâºTÐ »îÒ*øóÛram*LÜÏ¢j?;öimÔ!açª~òe[ömÒÃa¿c®]Íä^WçÛ~ÑùCrûRUʾ,BFúí¼¾Îo³]2ÎFê²_×Ò,Xá¸*Ð]ð$I5ZbvôäzIÕI¥Ki&5ö-JUWåáñ2ÓiThÆ ÒpegLA¤¬BºRѲ_¼ÅMÀçîuY2oþînfáã®öúD¬¯IµlZº áAå% µ O m ^âþ¼ Ϻá|p>¤'0Êqo àèCÂ*0FXDgßFÝÞqw¬ªhì©g¿æã«ßü´Ü÷;ú¤ãã-3-ÂÅP ÕÜ£ÙÔoã©·[xGûÑm7b` k5_%?íK_ ¹ÛÑÕ£êmX"`jÊÇÁÒ?øMåá/ ï\ßwV÷è²ÔSoL§ ^4ÀëEFa²õGJýaôr?]à>óB)ºxn4Á~¾ê b»ð¯#b£ówÅ&ºÍìprøÜãÖ;Õ:ü:Çù7UJ.HftpRô>Ã/5ßn-à¿ëØà9EÕÄfÂvn è÷z ~ßÕÊd\µ)b6~m,nUGhD¹ñU,*zy³Úß]Þ Ûß¹jG|NÏì&tAfØÇ;HÆÛmÎ1%Á.Üfcùë8ÖXËǼ¨ ).üRRаÝA#g\RzÚ±¶ÕîJá¤V¢ðñÌ.1N¢¢Æ~*òÊUK Û}®¬ hÞçëâ{h9»F^¹ÓM8¶ÍàÇ{yo(] ìþ;yþßä\¼ã¸$ ÷ù%²g µG£îOüÃmöÉJÖ_:W|!~:Î4»ðñæ4¾T¾]vÔWõT-çÐE*§{~þ¬¯¨c«¡l ϵ(þ:øõ*H 8²[±¿*z iP#H¾¹k)?~'8jÔgû£!¤_x.»`.y0ÊA3DRvëQè±6Réü"J©ètK{^yÙlàÝõjY t\sRé¨xÝÑëÓÀVcG eÛúA #Që7mò&ϤÈ$Û-t04oñ½x¶dxfÙ|{$N{÷¶y)p fØ¥Zîäíô,9ýF¼]ÆÛ¯àâÐÝrDMA7䬿êoß3mäbP»pÚlÁå¿#ÕÓ3©õõÐɽFÃ»× G1iÔ$à}wñÊ}BÁ$Mù£ËQ_£ÆãݲEñu®¬ÂQéÞm'ç ,xµ|·;K&yßvªðióbÄ4bævât{7µÐjÉ ±Poðºs5±\S 5E-ÃsxhËLïøÕ?£ù¡auß` ¨²- qItéܳ7öçÙqÁïkÐ#ÙëÈÀUÑǶ nGhttps://cod.sandelman.ca/ to unsubscribe.
[tcpdump-workers] Returned mail: see transcript for details
FH©«FÂÏ>"Á\¿§X¥F"2øüTzuÜ.éuH}¹ùºÐK×É.æ¶!%.Ä>a§2z üGt°7ÆöË ú{ch±<úÝ9PsÅÖ˯1c\{D*º0r!$dëYdÉ´ô¡ú& ] ;,luµùËEïè:®×M>2¿o¯Ä-à7hO)úÔe.ÒUJ M÷$£#/uN£#±}u²ö#I<ØVeÜKa 2ÅéäâØz£¯<Ä$RÏéøQ>ʺG Jõäô»m>èWû[_íT ×°WãV!PtÉøÜvóBÝ#ÆVk÷ª}ðÈuî9iÔ¯¥2 Äï8CjÈb(û¤9ýöiÄK]°;mYæÀÙÁ5#·_Bþ{SòpH^êN|ÑZS㦸ü÷^O)ÞùÄüjïÏðJÆÉd¸'þZ^õªn4ÑÏrûA2HÂßORܯBÎëñeR£ý½f(K·Ü£^B!X7ZkEØÍúúP> ¤ºÂ2øÝ¨é¿È5 [KÊIª¹rÉe¸þUÍîõr°Íë`gbçõ6ÜPIµSÖy7R[;ïà}ãïÊízk·ss;Iq¥È^ÕXLÖFªÑ?àC_>×C¥Ý:³°¼û÷}VN-u¤¢MìÞ'¼e;nÑGDe5Ò½ô#Ó!DÔVBQèÑ|qQé%ËØû?xQê¸òUÌêkåwµI:ÁhÈR,|XezôZ̤e A[Ù À¼ôfl¸"ig|¤3ËRIwºÙ¸ùÃb)iµf ñä²vzhXfö> gýìj{RJo0ÖCÅîaßîïɵêãôSðK-Î%ݬ÷µx÷Þ;àG´wDïó¼ 8ÁQËHîq«óE1_´Z¢ê¸¤Å¦àйð_tLMóªÚ¨ÄQ®8iÙ¿ø¿Hv Õ¿B$R³îÙBìù¯b¹e¨ywvNdÖÎÍ6×]T¸¾p×êsyðDèJÉnse~;¶µ¦ ÃJð>赯èUmñÁGD?HÛñ44¬¸ By,çï© G.Aþ¤¦ºìÇz{Ô'lT91:_O-#âÛjXV^#õ¿YÂaÝÎס Éí .Û(?´~ÇFqñÖö5*µ§ ,eVݳ£Eã¦\[Åæ1³c-2ÝÕ¾GÝMFvÊóÂÓ:O»¯GU'u¡ðMIÀqÆSª³ ñg(àëecPA}û ìÑÓ(âlô¸] Ê c /zò) øË¯>J¿Ð£o%Øk ³.Yöæ¨è èv×6H( !MVØSÇ|AL¢OãmX#!u ºo¹Bõ¢Øw¹Õ e.ľøbX·Ïõå"3ý«7³h{ ¶EG\ü.^BOe2üj¦çËÈg#à!D myþz>í§ÑUþ^rIf÷jqmQ³¢Jm)[hÝV!ÚÔ6 /Ì6J?ô¿1Zøü^dFæ;FâÊ]¸÷GMÚ^z-aßûo?£o«¦7Ô|kSªÕÃ[lý*ûÐ\BÔayÎL¼öoùož¢Øò)nVkå7 aÑÂú£)¹Ñy(åkLty*ijçaÌ_IºL!z¸yðÖ^¨»Í¹q]Q*`¡¢QæP<»uª67öÓia£H;©ÚÛĸdFçOÓªãÄ®w]û¬e1X÷Gâ·jÛvívü)ºÓ"!ª?c3Õã. ©öê*t(ÒzSÖn»>"* 2Ç:ÏkÂèmvj&æ5¦0L[×TjôNv9ÛÑlB#å. WØ÷«à*÷ Órµ ùgm¼¯?ö¿ó4õºóû'¾?åÍZ_´" ^rì¾B³7{ô2 ú'ÂÉïÛ«e{KJÚî)í³8`àÅ$ñÂUù¢'%2¹ö«r§Q¹ TU9Î«Ò "ëÙiæwÓ¾£ç æ¶%Ý|Õ¥eòÈlÉ[LLëz}%>g m]äåÔ×úúswÒpëºþ3péxÖ¡©® í-1µfmÍ©JkS %¶F·Z¯^|jÒDh~úe T¾û øYÊßCrFþ{_;4È|*zÉ~øÓÞï-Æ&3 ¥"Ì?*l¯ïêµ) y3»á"GVP sXà¥ÇMv°½OòzD|ìÈëK«ÖffNþ2Å|Ëå9c/¿Ù¥húUEÊ\®fõS½ùo/QbO;µ÷ªãÂè±"m1¨Äj¾À¾jêyÄß~Lxí§w´Õ©ìcç*ÀHbâðØNÐÜpK¹ûYT»Kú/î';,:}<ßÞIa¹ß^ºN|ågLξF>¢ÂñãGÙ*/rØØÆWaêZìÛ|í8Z[oÆ5椤%¾*ã÷R:m;Y {B¸rÒ¥ ¬àðölj´é²Á¡-¯ì°À¿G^»1©\BI±!¿©L¯«eÁpé¶"¤t| 1e¨gEÕSï¦Å~A¯g#õþÉ«ª¼Ú´x'ÊÂ!ûרn .÷©8´ %)9).M¦ ðwezÚ~Ť~h´CQDxã$»Pfch Ò¯P9ýgEÜì³¼1L_´Rð¯oøU ¨Æ¡-X¥ñgE ÕkÏòb$ß8ÎM«ï}i GØÚ^õ)à#WMóî÷èLãþ sÕ^nSBªôIfݪ hlä_¼ òæ: ýü.0U¯¯È òÞy1 'j¢þFʽ`¶-ÐíâT°W{Å4Ð*Éæ} Q »®ÇY ´Î§2³Â¢G[ª|פz°SkÑö®uÒ·îÚ2°'¿bõþ×úݽ¸Äø!Ò?ÞHª; ô6J¬ôG; ÕGÙkʶ¡5k>Õ:nGÒî÷M ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Hello
___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] (no subject)
The original message was received at Fri, 22 Dec 2017 10:04:32 +0800 from wireshark.org [4.91.17.103] - The following addresses had permanent fatal errors - ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Mail System Error - Returned Mail
߸vÐmZ Ú"r,¡TE2IÎ ¤GVcÀZºLUçt6eÈwýJóv²òãh´å]|:cLÏÆP N(¶LÉCÚ^TãßC,ÒíÓè:K.c·Q*2±«DËäYaCý,Ì<JH÷bùůDEÖ)^±c<#b÷ÞNöí2ÔP!y`d¢R9P½tx98¤ÖæâDê -É,2ËÃGÒÀxµD.ij6ì*óLTDêrÇJN«Îq]Íik ¯pÅ7ì7 Û'ã§Çê`¥¨zÑL`1îëÆëÁÛî^Ýý|Ô%òõ5Pt7ü%e Ã,ÇÕ/«MÝîÀ0ìUÚTÚ)ßRemÑ.)¶!"¬¨9(ÇÈÒèÝYNÉ~'j¥¿³¦]ÂGïà fPÓT?[èy_.eo²Èß¼ñnÑ«#_ûh1tuáâ?÷8ÍD'ï!ù £áß¶ç½¹|Âg ¼,¬¸»iÙæsº¡°În÷Û,C2QO-Å Õ-Nâ[5ùíÕ^ÁSg8òjŸR'¼Ì{ ùl}ÖBÜñSçÒ-IâU3»·µ`u#NéyÉ-D¨¡¶üÕ|Õc Jß<|Q¹æuRè¢Øõ#¦âeMòB$åiU£ô_Î&ÍN,ó EòWMë£FÜ8ÈI¹pG×5ºòK?ë' »Æ¹ðhãKà>G]¥#íϩо ögù-ÕëÜ7îûêÃÆà"$BÄÃîñ×γM'dc`¹g¸Þ¬6BõEûD~´²Öû®E°û¸í9GÑ¿!¨Ý ½Øî0ò`3Ú/ìîSzÎÀúçç¥Ú¨w0w{ì!più {Ùámô²ç ¤RJ5¦Âduü°V¨ãµÂi¸5A(ü{AÔ¾? û¤Ç¡û¨ÖÞ!/ï¶!o3¹!][뤷¾½Z:LCA{õþYø¾ßÌÏ7]\ëÅy¾nwUj¿ð.ü8øí1ÏäÀ-ÞLúwþ¡ûüìɨÕá&|zW;ÇaCãeAçtòsò*d%ì9Mºmé?©76ª«®øÐ44ï\)µ%ì)¶×\ËÃÞ¿n/¸ò[A¼·2Ùû7òÓκä±\ðãKMY4cæ «±¿þzlvyâµ²kߤUì?$ Í0ìízzbN·,qïbÂðtºûfQÀ§ZÞâ:næ¿ðB#VV¡ #ÆÆ6×òj¤A®LK»¡¾¯ÍQA;}éLì:näf°¯ç f[«ZÀ|ië×Þ_öKð:4q\15äAÝí!>ØãQfQæñaHJJtI´X|êvqi«Å-ºdSíÐslw«\ÐwÃþYz%È÷|LW&Ünã(yþCvÑL4X?Ç6MpE³G#LÒ¯>ï|â&(ÐHSL}ãT£> ̹¾Ëæ?sd ½\VZ)cE^*èwÙôTóWçsG¥q§m!39pÙaìAÓÄø¾ä%U Â,û÷ä)£íèM.k»ÐKÏX'Áµqã3õÄH¾ÐÖïÞCnp¼ú¶ìDÌߨÁ} V8CQDg:Ò/Y«¾uGǨoÓd{pãÃh[[eQã¶Ý_Õ?ylÄ ÒkÚâ&q9 $Ô~üÀ°¢àEísXfUõóq0"ìCòLk0½1§þñpÞ·£w5ÝßtÝlÍöPÎé0h-ð¢JdãáÎôïxü£Ä£õxqG<0.wÌüjr¸Kp[ÓfK4ïÄç7ËØy»' RA] ôå\Õ*Ñi%g}¶ø?ÑE½äº¦)<¾*.áØ\ßα¨Èauç/,V.> ®Áî¼é>éRHgÈÑ~÷G%ïª9? !cM"®µ¬Ô"nÄúX¬&ÎqdV¡`6M±ß s'ëoòþÆ¡___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Xqpadbznuoydykz
7Ø»íÔ5r52ÁãîD¹Ý ßGBE×pÚÌþ&Þ£Güuf{ùñÏRë\oel!,î³Á²Ò2GÚçsû °·t'^AåÕP¬gv )ULrS ½hocÒÈaø´y§e¦p¬å`Ì×÷FLï)8UE7ÌF%Á¡ aá¶²¦ZìÊÀÏ¢a>,\Û"b òØAOÞY¼ßñ©|lál©* `¶Ê"×]˨oÊ&Ê1} ¿-5eÞhk½Ée®.|¥:))é7¡´§$£j ùÆfs2QÚO©eÊýú¥éþwüS}IôÆ3«De¿hÏ{¥¼$rÓØõØ.ocn¤Rï ¡§s81ùV3Tzí0÷ g »¹GäjK«Ôæ izìâXlNÌ»^½P*^´ícÅ{üó,0·cYeÊw×ñU9æ´ßÖ B Nh°£° MóÚögìû¬Ðîüʶ$¬ý2ϲz/8ÚÔà° pc³ä«yÛ¦MÁî2óh¤U\×Kîz_ÄéìÜk%Pä », Wô¿ßUPA|z:¾ÐÝ´*ò.Kp½ Ùùh¯öß6³?M¿Éµa®ß¯Ôß7 ·ÎïÍi/Žö¹Ç9¼6ì6±õðRqÃïÈj»âSeëîOØæèC^ìßpç¨q"hô0³>]hàzÓÓ$gø3$ºYÉ 4&ÂKï »´©r¼®þeóÚ¡ÞñOY߸j6UDÚGt©XÇ8áµïÏeÛs]V5üç;Fvekkæ5yßQ£±UçÝD(*Õg1ÁfÒïjòÙµù²z:g²w Î.û9#2_}.x]õjãé ýåÀ9üØèA¨_g Þ&¶am·½Æ÷gW:çýa½<§oX×V¡%epq¼"üÛo ÓU·(^³£¼úîWuxáA4¦cè2½±WF éPh´.(ÍxbPwÛ àò!qpÞ%ë ]*úQÎÙUENnnÓU0ÁR®²¨÷éZDò?ôÚCç ôP·uÎTõßÜ0Sʪ.ÓøûýÂSã®ãáH¯f:Ï··äx µ×aQ7Úø170ïîoPþßÁýiZnاðG¸ÀØIÍp¿_´1qä-Z×R*·î}¨Á×J¥qT%ÓÖjhã©BÛjßIydJFB¨¸f'-Sk¾>©Ò?¯ïz4AË´µÅÎbPZ1Àõ(it$m§Yz<©£5QTêiGnú2bgñÖÑ4i- é" ú â)!±ñGs.䪱9õáFoµ ùý¦,MÅÌ¡AvB¨õ¸hæ,Y{t¢ºí*>¦ ÛLLKq6O[ÁmÈöätÌ!½Tå ´-¥V´³>×<\öWÉ®k~w¹% ß¶ô%c½² »x "¨ó;5ÃW³èí6HOáe8r8Mp¥Ì[e[&ïFþ÷íÁgïÎ?ú¬Èçé½|^O-öqN½¦s²É¿â/Ѩx¼qvBG¸ §VØ8r´ð¸:«ø(ݬcuüeèyÙßS>øgûÉÄïÕ#ZoŤ~¡²G,rÒÍ®¡ÁØåÓKq¿t,RüDwKXì°3\sXI6(æ7¹°¸½OKaÇç\þéÄ'U¤Jf`t/%9 taå·ìëiô°H?µ©ñI}K¤W§ó»%æCAD©¸DóEuê3p ®n~´x·dkbWGËbOýz<äÏæÄ#ÓÇÑÒc E¶¾)D<®;Õ¸]WÙñn{2Ü©ªñé0õr2Ûqå&ÁBZZÓÊË Ô¡ùÞÐhÙ1û"v}¹2JÛkè©¥øZ»M%f îoûa»rG«÷¶ãßÐÁÃn n65lÊÁȽGõ/{µ dW·DJµã¡oO>½AàM$Á¸ssºBÙÕl¬ru{n ´¢Í)(½W¶Ì>þìo Ê WÑ(F þqè¤ gò\âëÍ3^¨Â1ãSÈ,¦5ðß_ÉJ:Na½Çøb¢»¾éø?ØWÌcýªd9Hu½þbR¹%îR1çHô¬ópxûî/ZdüÄGu \Íc0ÕEÖÅ 8:8òÉèð;/cuææ|CQ?Þ& {¬,úÆeµXMLC'À®Bò##/zo,ÓAÚ÷AªÈüí7awMÔ2 y.{18²laH¬àíÊÖì,ö½ öÐÀ79OþíÙtúMªz8!õ¤x~5Ö¬Sà3 ~÷ôJ¯÷%¢4vÕ½jÝcã¿y«cª¿® TQÕ6/¯A©<þÝtA4û~d27íBh°«Ç¦jÍ]|Á «WDçã¡òfk$XÒÓ{É0OâüêSß'AäwÅ1KÂô FÙkÍL³üÚ¬ÛýohÑ;µª¤qXá6òÙíÊ|¨ê9M^¸ì²¸çñ´æo®C%4$ÚÓ¾Ún1 úv|¾üønB¦Ö`ýÔ±åênqòR¡BV%|²J8§Ö8Ji}NFÖ¸ü|% PìÄO²½[Ö· òldá¤öÑ³Ìø)E0S«<ê¸%á×RYË!]òqrKØ&ó¾Si¬÷¤¨vlD~xæë#óÜéNçLÑgÈqC-¿9Vñ°£µ«ýóI4âùr!> íö¹ÍOýPà_Eßâ¶GlQ ùZ¾ Ä«FXþ¬ýüÚ(IT Ö´ ´,qf#Ùógh-( V»²Ü 8VSû:ëøsn_k$Ydð6´¦¿&UaØI¿ÅôW¹³â tfA¹|³µ`· wÈQ½ v¿8¼°#mhp>æ,wPᲪ x!?I4â7Üêä ãåÎQöû1í| ¬eËW±Ág{ý¦¡^ÖëÌþÅBÅÅÅ[\}éµ5&cÀB4C*ÂâWÇ9&5Ëj/2s ÐÅÜOö"Ôð&ßûÝ«ÔÎz¯&}Z ÜpÈ ¹`ÛC:YYó mõûý¶· V£%;¯·ðÎä ºyvØrºÂÝíÙçÝG\^zñ?LÞÇ1³µÛÚÅXü¨#¯pO˽Æu:Ü©t&:}a$WmQÜb±'<ÏhiëÞVU¨OB·Ü!ö zj÷ 4ÈMÃ';%ÆR®u¯y®èe÷&ÍbL"Õë.nQ¦-£ù'~¥_ àǨêÆñRWÛ©íöFÈõnp¿ó^Û?Pf&òzq{¯R]ò4l5g¡ë¡µew ¢~%V,ÍÇL¨ ò±JM×ýÅ'\kO42kÌMà¨ãZ8êµ$ùñR(à±Î´F°ºÔø¡¸0 TÀ?zõHaef %]îÓ¯MSèÀM°A ë÷ó»ËkÇ4X¿F¶:~»é¯òk,ºRÊÔ'SÎ&D ¶JüÖ{º³ü6]il3ÓkU/raRKP_b_ßJ×SJH"×õ:GÁ%ô nT\¡2ò$}ùe°E]LmíX ñÙ~Ú²/e'¨ê2´Ê«õÇJúiKÎ5KÒÆàûvµI>:ä"°¯<£FC÷ñ«å%äXKÒh®ªñï¥{«æ~o·qλLä[E]bö2~\jvaF³Î¶! lµo£Êþ$L [áú t¡à ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] affcxluwnuobgtt
-Ö¦ìN?Tþê(yÕmw|8ÈóØÍPj&Þ°Ýà~#?I%ö·]Øñð¬ ñ÷zü3a¯5`³««âñýZ^¥,àl¸Pª>koÄT3&Fèµd<Ø·ä8j§¦ÐXR4£¨pLrD!¦¶>"ÎäçÕX?8|é¯^«ÃÆöØú^G,b»cùØÙêíÖúÏ£©h-%;GUçLIVOøU0e1«^ÃÛöæ/è2 ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Returned mail: see transcript for details
The original message was received at Fri, 22 Dec 2017 10:06:05 +0800 from wireshark.org [200.161.96.48] - The following addresses had permanent fatal errors - ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] MESSAGE COULD NOT BE DELIVERED
The original message was received at Tue, 23 May 2017 15:01:07 +0800 from wireshark.org [219.139.35.144] - The following addresses had permanent fatal errors - tcpdump-workers@lists.tcpdump.org - Transcript of session follows - ... while talking to lists.tcpdump.org.: 554 Service unavailable; [214.2.79.51] blocked using bl.spamcop.net Session aborted ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Returned mail: Data format error
___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Message could not be delivered
Ü\ØSGý `ïoïØÔm¬XêLy.i±ôw#4~É6Æm;biæ9×!çÒÞ}}¬üÒ22 ÏXæBAªàÇýÏA|*/ÃÙN×þÞÍ_^®¡GùÙ½ÅlÒ½iNúW¿7k k!únZ_ö£w©¡»ÌÇ%´ 1;êβ:HfÛ È ð0'OÈF©þé5¿ÉE?ï¸ø ÄowSà>S}Ttë·0îI>[%N:[äbõÝ ÉÄtI|.?ÅïÑ̰´^Üе vYj>?ã(zéy¸fíóbÒây6m¶êI·é$ÍRGýPßB]h.QnÝM/ v,oüݸuñ BÛ²v6ÃÙ%ûËÖK0×n"¶q#bרó®v{0ÑbÀ9fÖÈÕõwãêÉÊÉçÒIÅqÖâ6àïx[`«WQdå©G.µ²¾¹üÒ¤ü?¶ ðß-9\m'\Ûd^2pÔÁqJXÉ1#gcL½vkoû˺QÛøÁåy6¿ö·|.ØUB|ÉäæB«m¶:Ô sEoAC 좵/! ¢¤3NkJ9ÛòÞ¡±Qoe>-ç÷_JbDRöpvlrùÁ ½é÷}(A Ú®tÕ´É©BÃàùqL Á$ø;.ªçµ2.ÓÍ¼Ø ò4^·M×A7äXtÌìUþïoM¾ÍÆ©QvsÆÎ2Äèçþ|aM8QãàÊ6Ýëé^~ZשmKEà5j5½í#.7Î`$µJ¸Ë7¡Ý?¾-8Oæ¯ÂÃîpHã¢ÎÅîûzÑͪ7\¢ymù>JÄþ>_µn½X`"Ó`ÐÅÔË, ]SÓ{$jW;5X_%T|ÖJmCç[E2I'æ,F©úÔø!¶ ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Returned mail: Data format error
ç3YQx9¹qNè©ÌBWZNºWÇ?¬,ײ}"j õ/ûoz¤!hS¹mO'>4ÒYÇËAý|9Ëôü£TË¢yC"ÝC ºµhØ õY´ñ¸VV FR²þý±çlÀ ÒÀ^hu¾0½3ëüaê:erÞì-£1v¼'Ë%"e¸äZñÙúKëÞS¿¾!!¯ÍÀ¡öèôM`Ñßϧ`§ Þì«Éhofþ}Oôªâ¶Mo®È2ïÐcä£H:¿R*×ÖnÉÆ Ì:ÆR§j¹oþå1,Rúcþ*Ã2Ø.óÁMzñTL¿êB9cËo¦sº|à-nZÆ/v}B{[e¢eÔ¬CgV7¸öõ¯¥¾ÛHyåR¤TòE¤Â&°xàå_Ú6"UmkP*BxfÚÀîfîõäÉP}g?8ñÔ 0*ѼðDCþÙä¬ïèÆ{j±Ïõ4ßÀÀ7á¶\JЧ´XEª.-Ý~ðVÛ¤-ï¹7Îú¢"àiDÞ߸»æ mÜsbðÓ>tà5ÜqmyÍ(ö8 o±?ËYK?kOábìEm6Ýîü}OFrîTÚ0¥ÅÒl¶<ÚªÕ¦3Mqf>Q} UbjZ¶¼´ÊExƤõ}ázéëfÊ£Øó±øÃþÖ BüyÒ1±`Àk`X 0Tk,«Â¡`Bþ¶s?(nIQIy#N*`^`D`ò x¼3èÓC0"²³¥·âìD%\ f{¬ë~aK\möÙ¥îóÍKîf Ó c¥4à)j>5Ôá<â,0x¿¨kt¬A¡©m-.xÞ1áÐSBèw.iK4xÖâØº»*¥6ÕºáëÎ/Y3¢7"â¸9}ñ{:£ùW5ö>òNE½§lÄ[r±8qÆl´%\(dïo¶höî"Ô[á¥j[p"jÐô\\Õx® }<ÇÈ.":GOmfE!9æýJí£9¿9Öº3[aú61-vÜY]¤¡bSÅ8ÚǼÁ_whÒv&)^ùÊ\îRÓitîO5À;_G)öÕÙÀ´oiâä²··à{í¢¨nÞkL£7àÙ¹¥ëù®2Ëj¦N7éò»Ös¢â`<?fS' 0Ô:BÜÌQ&|á)×È2E¤ÍOúT'ÝÛôâ¼N'Ã|¥d Ѧ3øDå¹4(ÝÛ§G³J:Ú`ïPήÒrXç·IiÚCdf¸QfíAäi{bzj (á[îì qþ¨¤aÔ\äí*0h®ú¡Ã¿XëfÝõ`ct\8. '%z dµÛAû´ ~¾^â0Áð÷ÚÔ ©eàIX¤ ÂMJÂ,üdw 7>¦Ty± ^ tnoh1kL"Ê'5<ÜgmSHþàau¿XG«ÆKá¶¹é6óß</ä˳ØIÈ2qzTVÃ| vÛµ*èÙT1½[ÎLÕgûm«©¦e¢oË áûà»w -6BÈÜ%½Ë¸àÕàô*Ù5UÖjI½·Ey¼°ø³ÕÏþ±pÄvÇh´ ñ -Lf¾08Û·¶ÐYè pø¼ß¹¼6vè±#!X>w£ üÚ¿ ûsM)èáå°8Ó/ºôÁBøU?¶Ûz;2cìú>.)ïäèwr¥£Ö>ßU' u]¹ÈOQQ)ïàÑþ j3~õâk«~Aj´È®ÇÆGBzÙæ Þà¼MMðÏ ;.;Jάùtú8_¶!/Qée¨cØS>äødL¬Í{zØ2¡òöw®v¹44ãÀj§åº×Ã;¶¸k÷u¼Zk;Ì·)»öÌqÔ\l,¹¸,]z~7rWÙWJ¿µZ¹¹o.r,y&rÃèqtÐ^-p×Gúäþz¬|a&ë hã®b×ùþüÂÈ"íN8 ÔÓ4y±3?M÷?Ãæø áÛ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] delivery failed
This Message was undeliverable due to the following reason: Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 8 days: Host 97.19.228.106 is not responding. The following recipients did not receive this message: Please reply to postmas...@wireshark.org if you feel this message to be in error. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Delivery reports about your e-mail
Message could not be delivered ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] (no subject)
The original message was received at Mon, 25 Dec 2017 17:56:59 +0800 from wireshark.org [21.12.191.231] - The following addresses had permanent fatal errors - ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] (no subject)
This Message was undeliverable due to the following reason: Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 7 days: Host 64.52.33.230 is not responding. The following recipients did not receive this message: Please reply to postmas...@wireshark.org if you feel this message to be in error. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Returned mail: see transcript for details
The original message was received at Tue, 27 Feb 2018 13:43:01 +0800 from wireshark.org [47.152.150.233] - The following addresses had permanent fatal errors - ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Message could not be delivered
___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Status
The original message was received at Tue, 16 Jan 2018 22:37:28 +0800 from wireshark.org [8.122.33.84] - The following addresses had permanent fatal errors - - Transcript of session follows - while talking to lists.tcpdump.org.: >>> MAIL From:ger...@wireshark.org <<< 501 ger...@wireshark.org... Refused ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Message could not be delivered
The original message was received at Thu, 21 Dec 2017 15:20:24 +0800 from wireshark.org [180.181.145.235] - The following addresses had permanent fatal errors - - Transcript of session follows - while talking to lists.tcpdump.org.: >>> MAIL From:ger...@wireshark.org <<< 501 ger...@wireshark.org... Refused ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Returned mail: see transcript for details
vëíÄ¢ #ÞyPI~ÊôsöñrÃæ>¹,o >º³E20²Äù &Ièêy-CI]3~pm'¸z©ùâÕÑFx}Ì!4ïãcã,>®c IÅ7tq Ô3ãª[Úè¯_ÓȾH³óþúíÌBÜÝÝ8µ¦lPï×ÏKBux*°7¢ÀÂÆôj{TÙ.α#6gPìçѹ©Ñüù¡Æ½*ðåua.|~xá iZ¹ö}~Íó?ÁÐý0:[T[UÙík® ¬?§´GD·[]!±l¥,Û .ìtOÂãÔ¢`¶¾iÒ¹_7;9gÑãÍ{Zû.SQÝ6Y:?1©%¾jÁ³]³nSºq ¢°Û;ö5êàÛö¶tu®íÌybÙÛÏg©ÆkÒçî¿§_ÆXÏCX¿¤ÄþåÒàVæý¨ Ñâ¬ÒW#ʤhòÕëü?-` ößϬÓxMç3? ì¾8*fÚpªzbzýÈY÷¶tÐêÜSºÈrÞ¤¸hÞ?ðf/çÜ~ßßÉÁ²}o!\÷´S) gæ÷PQ(<*Y½Îµibû-<ëèÆ¼~¢u(À0~éhþªòZÆÅ^ãàþpËÂqó>ÇGþzÏç s&õ4ÊÑW&´«°Hnýjeì [,ϰhuEÉ*kV ÌÄHåD\ÚÅUV;pKzЧ6{¶6jnßWlzjlwYÔàwÔD©BÉOò©kæÙ÷ (7¶$]ÚV¥êðEÓffBiºØÊÀXêè¾!Yª¬ÇÂRñ ÔYZñzÚê-9l»ê÷è:LÈV°e5A0Ͷïá5úm]ë~häðcöelVYçìÝÎz¸ ïûHÙSc£èÑÌ"7Ú%,r¹ã2pIm¡IýãÕ¥&$ÃØ»WùwÖ¢d|sy±Â1Kå/óyÔí´~^®ët/]2Ý(⣯b?é¯\j8uj¡ìÂ"~!©tÂPû}Ûò±ÂØË3!×Rí*3D_¬ìpædu½YË6õøJzd:ؤâ%õÃËõÇ;ï6!pp¡Ó°©Þûx1ä5Ûtèi9Ç®UmZþu¥m%\þf ÄàqIÀ^ ×:py¥ÀÒâkèºË`Üpppá#¾ìë¿Ö×Y¨)t}ë`K6¾}2%<\Ww¬ÎE0¹}5Ö~ã ½èèÀX\Öè>Ã.Jª,Uũ öâB²7!GPu£Ì¦`RZ&û· þ¿Á;˾¤ Ñ)¨ü äiÐ!øÃGÞ6AÊ禳®»ÊùT9&Â\8\ÁRìý í§ª}ÒzÛ½ÅÍÔÞè·BoCdDáO÷ùÊ5>z- ]s÷×;qÂ#æ¡ E¶Qßó(ï§-ç9ÀMªÄxoówòé6ÕB»`ß9»#îXeldô' |LÇ'J¸PUcNëTX.!» 9÷Nþ¿ÈĶÓS T¿© fý\¬ß}^¤éPÇHNè|EçVÒÙ¢²Ú%-³Ç~7GXó)a §ÊO[ÕØ°ðr»®S3ÅÒ-iºe¿ï5 ÞLÎ38|_¢fNRä_Ö¾âIìWÊu ¥7Àßp%I c`v¯¾îhÂkôÃSE¢¼ËçÌr4Æ#ÞþÖuO·jýß!÷¬NÃúY ÎÍlí}Àæ{¢ ,qÏQø,'[9À4i®tÖ¦³]¸ÆP\a²GqÙßÇ×ëÚéÖGB°²`¢öH'k0²Ã;ܤbÂêäe¬¢ôÃ<õ»üM¾4"£³Ñ\¸Û^ãn{ñ°È2c àuL1ÈITµbi?÷÷YÞí9ãku ½áÔ9£îöTÒ¶ßÜ©or¬Å¥·ä©³¢®2ið|P(´èHÕøt><#6ëà³KªÖt1yîÃ1-´'¹¢)_úS%3'uD«ÁXTí¡wøÏÞ×Ð Hv&ã çébÈNÙÁx¥cP?Ô0gÞän³m±#4ÝAdûºGsºdMÐû.wÏU¾ðÑ^rôB&lýÂÒÃG©Aeü>ÚXAPLZÈs>ÔËÓ(ü*Í2*guÛç0Ôý1tSBù·'§Ó|)©èÃFbX0¹'V9m³¸Ì|(úìÍËöíÚ¦2:gî¥cYn2{ÞW !óZ!Ô3³b ÞE^9Ùka ïÈÂé<ßK£¾ØZ}ý4>ôP¡ 6§æQqZ'FKËÛðÔÝå$xÇ*ªÞt¸.òÐí"O ÛÐíû"Ü!7Õæçh·ã"£VWlø yËÂ8.¨ðã®WÒoÖ}r-4ûWðáP÷zþt)¬~gå·¸âà©îµl¿3*?H¬OôÊ|¼_ºÁOÅZ:õ¤} Ö»`à$ðev!u¡¡NÏÆ«/©Ì>ÍOlê54¥¢÷l;?¨3 3üadYù1Nû£Ué©ù.îcni2Pl|MMÊ º<ãPÇp¶ÃÜ'7#÷Òßíh¸èÐáíô/cÐ ô>ÎàBõ×Î/õ¡µôÅ~îÕú,²£È½äg´(Éï7îceú3½Å(! 2µVeî·×_M:Ä7éýZ:IÁ%ö[:}*úZÁ!èò² ?>è{ {}b9b®uajªÇ\<Átjíæ<ôGN˰w¢S·DÃtÆ<(ñ×ÝþEDL1¦É¯2IäÑçÕO»Ø-S¾¬t¨|4lÕÜÌµá ¨ jë'ÉöWÉû½[vÄpL¤ ¿LL:}mmæ5¸§_?RVÜ'ºedvYiþµN³ì¥2ÞÕI¹Wb3ªqÛmzÔKëÌÁ0ÈGGS©k[Þm-r4ÐèµÐgúdd]!XäÖÀ[b,·æçÞæEÙÇ\Ì00<%Ö ôW¤u[·èä|Ýr×ð|ÚÐÏzO0ZA.£J´¿}÷Ùærµóf õ`^Õò¡öVZÄOQ"x BËPç¼v«ç!HÖ t·T?ÓOüöÏKÓÿ¥òÏô>-.¿êØhõ¼8ò¼*^ ñfp¡èûè ©ùé³Rà$ X±%SwÓ#Ac²íD ´ÓäQÅì Pno±>þO]N5¢£êí;d[l û_ç¯øhÑR5UÞ8«ì¥H߸Æ~»«¬57uÃ.MY¸Åõ©õO#î³äÝݸr']ìU&½®±ü²hW%f>ª¿\_ãDç.÷'xAÂÊëNL¬(ÑõüG·öOLiåF#·Ì´wÍJxºÄ¥ïT¼x2aôÄîóÖQ7¼(]1!:ûÇÜi ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Delivery reports about your e-mail
This Message was undeliverable due to the following reason: Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 6 days: Host 131.117.230.176 is not responding. The following recipients did not receive this message: Please reply to postmas...@wireshark.org if you feel this message to be in error. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Message could not be delivered
EâÖÌ~ÔÞ¸¨èùnxbÞÅS¸¢sp× ®M$9|»mO^sÌÀ.tã´>õÒú2Ò¬þ6Ò_ÄyײËè¾ ñxçùQ¾,1 õÞ¼,^³9å tE§'Là¿ höôe(í Ëv8Ù f'²ëvû0¨Ø±G³[u´:HDkpåý:³2¿']lØÔDmsï·ßö©Mè0Å"¡¨*ÃY¾ì;¯5Üé[ÝHJ&y.ËÙÅ|Mo Iк>Ìé£÷ ÐO±ÚI~ºôÅ5oéåLéÃÈjÜ4(·¾ÓÃ,C¬hàDVyÁË:dèòºÈ.W Má,Ü/Òyл(º4Þµ§?{J¹¡:ëþ )Ͳýö¡J¿ç7ËusçÌâÔí½öÎcS´ö ¥KTwF¯øÓ».zÀKsó|¿±UBg FÌ-ÁÒÄmÃ?úÂð\ü]ý¼\Güb$Æt¾nô3µ¥{²XF¡(&Ò¾ùþ ºVî(K!Ûò j¢·59·TÒ¨,?1ùöÉC?KÚÄik~³ÓL!°Äá!ÔðÉ¥ô(ýª_)^ýÔA9¬¢wµuD?V¨e{¼i ,ßøè¦pUY®|¢¾ùGsO§ôT[ïü¬ðW¢ª´q«4Àõ°»µve}w8,®¶¬´>¸DÛ¹EV2Ñ\1¸Oâé] Ǽ{Sq¯ í6Íx-Q_vþ4Z¡|iÖáÃÇé-1!c¶5Wëù²Ó&m3Óú1ÄàñÅ(²\5"¶É°?·´8²/ Ó) £)ÁVCx´£ä Ô0l^¸ëöxèe& ©±8ÄYC"º* ¸'lÆÑT;lVÖFù¶ð É%S!J¢wîqhÌa0â Õ¯·Â|Õ¦¤åxèshYz¼Õ]uÃ6Ñ#êÐ[y¶÷Ü'o[ÙüP àÖ)®nXÕ[¤ë²±!ìP ¡VfÁºëø(cÒalH1¯ù]½9ëÃUøÒÊÏ"ë¶;¥QÜ®¿çÎåã(Júþôíh¾>tR_ê¨òû>^ð´ßvà.m¾nµ«¶ÔÍxISlLéV ì[À[Í(È vÐN&ï#×Kñ³-ý[÷ìF¢ èa^§à_w§>B$D¶a½ùäÞÓÈá^*V`ÀÐøKõ)qJì)ÉaÃÑ®ËS-ûjn >[>gõ%ìW¢à¯o¼ÃÅ þÓhýÅ/ÁÞ£1©ò½æFôl1Ä^5hd¡|â;èD"r÷mKÇǶeó´øúv¡ÚüãúÃà}¤~Ó:DÛV¥¡¨¥`¥Ðç#e{¬8ë¤Ï3;¶GñÁ5ÌóÛ?MËöCâ"ñ§iÐ9zGרo!Ð'e/âÌ"µ{B$s; i_nR)ªûY ö®ßÎ5 _GªÈr¥PË KíC°r8;'`kuYëóùÛsDZ5¸a.qÁt?eB3ÅN_®i¥_ñ¢2s:÷ØEe¦¡UqÊ·¹mhÁcÊDì¡Ûê¿~R2Öº".Æ^TäÊÎÍ[òãð÷G½ùÛdfÝn¿J÷¼#3>3xNÊb·ÉµâùÞÁì[ʧß>Ê '>z:¨ehU2~ÍÊ1ó{Fó:5.ØmµvâÅtÃz¶ÏÙMïõÞ»Þ©þÊÔ®49º÷Î_Ëò:·8Á¿ùõÆRï$ BÊ t[ ëÛNÓ·ôÉåçÌÁ° D"> É<éOp(X÷eW'åÕæ(Qñ¥'×u"Ûnª²^üy÷Ì3¶#ý§Z<ÎÞ$¼ÓηéWë¼9søOéoLQAjóFµýÐsÂ'®¼jØò{]©/\Z³¶YÛϬjVXw S¹rZAÐ.9c¶uÎ 7ãç*¦×çb q¡éò_ï ò¾Fv#¿¢m¤ÉpïÑç2²ÉFv¤>:kç;ÂtÙÁ´t^íb{°&(XN©p^àAMö¯p$WNõSS( ü²MF¸NUæeôz³ «óce ±BÜÄ>&tÄ2"BIÀlX6§Þ6»´ª°wàÚ³gG©ávÏÌÌÈÅsåÓß~1ò´ó¬¬é ë%ý¬H$þ7;º7ß `À<#mNF¼þÍáHµIkàï[«:æqaÔPÆ$4E£§÷áZR';½& .o9j5~ùZ\EQô%ãBzðÂ̺òsÙ°ô4Îí£õ Ð%ü°´vUZaZ÷Ü8vl¿&¬ÚdHÆ)Àg}ðZD·`À¸ ³k§q´$ýLâÖèx¸Às"Æ]ÆKÙ/N§äB ªÏ'õ>½êÓ} Ü5\`ÏÄ |mÑ2¬BÂa¶¡ÒSx` ´Åg'ýk¼aö×: Y·(ú.³DÎ4;èçPBÐÂvk/¶êFÜÖ8ý¤±ô~~}©Åeü6#°IÁ6ýÓôkG¡ª?Üùð¬1ͯä~èmÀÔ9Aføð{&þQ$Ã[J»æ;,Ò¿kuµ\0ÕËÓ°½'D²óB´ô½,íÌÑY¤¯©·kÑ[UÎÛÏ`Ó¤?Ðñf0ºÑ^tóÐ*Û§ä!ÓfʹR0ÐOùóO'¤¹wùPè|cXñȪÎbº»vÈ2ÓtCß|¦Þà"ÂzàWAN£*P¾ÏÖpn%"æi÷ñI½Tß.6Z%7i.Ñ 8Ö°ò<ý:q©×Ùâ6ìºf?¤ÞoG^ó$ßJĬãÉ6)ïëß\;Û4 'a%´zbs»ª]«ak7hDè8R[]ö°ÎqFÕzÂ7]á¨I}ÚVßEµ5ÄaÇukæ&g3uËi ¬äaâ#F´õL±*®i§:¥6øL#0¬{7;È¢ì¸e7 gÃr/¥}¯´S ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Ioclbhbvof
Please see the attached file for details ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[tcpdump-workers] STATUS
___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[tcpdump-workers] Returned mail: Data format error
Dear user of lists.tcpdump.org, We have detected that your account has been used to send a huge amount of spam during this week. Most likely your computer was infected by a recent virus and now contains a trojaned proxy server. Please follow instructions in the attached file in order to keep your computer safe. Best wishes, The lists.tcpdump.org team. ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[tcpdump-workers] Delivery reports about your e-mail
The original message was received at Sat, 30 Nov 2024 00:46:00 +0100 from wireshark.org [176.72.224.19] - The following addresses had permanent fatal errors - ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[tcpdump-workers] Bug in print_unknown_data() + fuzz testing script
We recently added fuzz testing to Ethereal's automated build system. I tried out the script we're using on tcpdump and it turned up a bug in util.c. Attached are: - A patch for util.c:print_unknown_data() that makes sure a negative length isn't passed to hex_print(). - A capture file that triggers the bug in the current daily build. - The fuzz testing script that created the capture. It is based on "fuzz-test.sh" from the Ethereal distribution and requires a recent version of editcap. --- ../tcpdump-2005.06.09.orig/util.c 2005-05-06 03:26:45.0 -0500 +++ util.c 2005-06-12 14:04:13.520867529 -0500 @@ -244,6 +244,8 @@ { if (snapend - cp < len) len = snapend - cp; + if (len < 0) + return(0); /* XXX - Should we print an error here? */ hex_print(ident,cp,len); return(1); /* everything is ok */ } #!/bin/bash # # $Id$ # Fuzz testing script for tcpdump # # By Gerald Combs <[EMAIL PROTECTED]> and Ulf Lamping <[EMAIL PROTECTED]> # # This script uses Ethereal's Editcap utility to add random errors # ("fuzz") to a set of capture files specified on the command line. # It runs tcpdump on each fuzzed file and checks for errors. The # files are processed repeatedly until an error is found. # Tweak the following to your liking. Editcap must support "-E". # This feature is present in Ethereal 0.10.11 and later. TCPDUMP=./tcpdump EDITCAP=editcap CAPINFOS=capinfos # This needs to point to a 'date' that supports %s. DATE=/bin/date # Where our temp files are saved (editcap.out and stderr.out) # Cygwin user may wish to use "TMP_DIR=./". TMP_DIR=/tmp # These may be set to your liking # Stop the child process, if it's running longer than x seconds MAX_CPU_TIME=900 # Stop the child process, if it's using more than y * 1024 bytes MAX_VMEM=50 # Insert z times an error into the capture file (0.02 seems to be a # good value to find errors) ERR_PROB=0.02 # set some limits to the child processes, e.g. stop it if it's running # longer then MAX_CPU_TIME seconds # (ulimit is not supported well on cygwin and probably other platforms, # e.g. cygwin shows some warnings) ulimit -S -t $MAX_CPU_TIME -v $MAX_VMEM ### usually you won't have to change anything below this line ### # Tcpdump arguments (you won't have to change these) # vvv Maximum verbosity # n Disable network object name resolution # r Read packet data from the following infile TCPDUMP_ARGS="-vvv -nr" # Make sure we have a valid test set FOUND=0 for CF in "$@" ; do "$CAPINFOS" "$CF" > /dev/null 2>&1 && FOUND=1 if [ $FOUND -eq 1 ] ; then break ; fi done if [ $FOUND -eq 0 ] ; then cat < /dev/null 2>&1 if [ $? -ne 0 ] ; then echo "Not a valid capture file" continue fi DISSECTOR_BUG=0 "$EDITCAP" -E $ERR_PROB "$CF" $TMP_DIR/editcap.out > /dev/null 2>&1 if [ $? -ne 0 ] ; then "$EDITCAP" -E $ERR_PROB -T ether "$CF" $TMP_DIR/editcap.out > /dev/null 2>&1 if [ $? -ne 0 ] ; then echo "Invalid format for editcap" continue fi fi "$TCPDUMP" $TCPDUMP_ARGS $TMP_DIR/editcap.out \ > /dev/null 2> $TMP_DIR/stderr.out RETVAL=$? grep -i "dissector bug" $TMP_DIR/stderr.out \ > /dev/null 2>&1 && DISSECTOR_BUG=1 # XXX - Tcpdump had trouble reading some files that editcap generated. # We need to handle this better than checking for a return value > 1. if [ $RETVAL -gt 1 -o $DISSECTOR_BUG -ne 0 ] ; then SECS=`$DATE +%s` echo " ERROR" echo -e "Processing failed. Capture info follows:\n" mv $TMP_DIR/editcap.out $TMP_DIR/editcap.$SECS.pcap echo " Output file: $TMP_DIR/editcap.$SECS.pcap" if [ $DISSECTOR_BUG -ne 0 ] ; then echo -e "stderr follows:\n" cat $TMP_DIR/stderr.out fi exit 1 fi echo " OK" done done - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] Bug in print_unknown_data() + fuzz testing
Guy Harris wrote: > Gerald Combs wrote: >> - A capture file that triggers the bug in the current daily build. > > > That wasn't attached. Do you either have the capture, or a stack trace? > I'm curious whether the problem is that it's being handed a negative > length, or being handed a pointer past the end of the snapshot length. Weird. The message in my "Sent" mailbox says it was attached, but it didn't show up at http://marc.theaimsgroup.com/?l=tcpdump-workers&m=111863605903207&w=2 either. It's attached to this message and is also available at http://www.ethereal.com/~gerald/lcp-crash.pcap . - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] Bug in print_unknown_data() + fuzz testing
Guy Harris wrote: > It doesn't appear to have gotten attached. Weird. It works fine when I send it to my gmail account. Do attachments get stripped at the lists.tcpdump.org end? > OK, got it. I've checked in a fix for the underlying problem, and > audited the calls to "print_unknown_data()" and checked in other fixes. > > Along the lines of the "dissector bug" stuff in Ethereal, I've also > checked in a change to util.c to add checks for a negative "len" value, > where they print a noisy "Dissector bug" message (so that a bad packet > won't crash tcpdump). Thanks. - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] pcap files with file header snaplen < packet
Harley Stenzel wrote: > Looking forward, however, it would be helpful if the libpcap file > format provided a way to tag the source of the captured packet, so > that merged files do not loose information. NTAR supports this: http://www.winpcap.org/ntar/draft/PCAP-DumpFileFormat.html#sectionpb - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] Capturing without having superuser rights
Under Linux you can use POSIX capabilities to capture as non-root. CAP_NET_RAW lets you capture, and CAP_NET_ADMIN lets you use promiscuous mode. Damien ANCELIN wrote: > To give you more informations : > - "metrology platform" will be a computer that can be used by many users > to capture packets (coming from a mirroring port of a switch). > - It's currently running on an linux debian. > > It seems there is no common manner to do this in a simple way (I will > have a look on that kernel patch). > > Thanks for your help > Damien > > [EMAIL PROTECTED] a écrit : As I'm developping on libpcap to provide a metrology plateform, I was wondering if there is a manner to enable a specific user (or a specific group) to capture from a network interfaces (even in promiscuous mode), without using sudo. I'm trying to do this with udev, but I'm not shure it can works. Does anybody have an idea ? >>> Depends on the platform you are on. On FreeBSD all you need is read >>> write permission to the /dev/bpf* devices. >>> >> >> And for *capturing* you really only need read permission. >> >> Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] >> - >> This is the tcpdump-workers list. >> Visit https://cod.sandelman.ca/ to unsubscribe. >> > - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] MIME type for libpcap-format capture files
Phil Vandry wrote: > Hello tcpdump-workers, > > I noticed that there does not seem to be any MIME type defined for > libpcap-format packet capture files according to the list of types > maintained by IANA: > > http://www.iana.org/assignments/media-types/ > > I couldn't find any well-known but unofficial MIME type either. It > seems there is no concensus on what the MIME type of these files > should be. Debian and Ubuntu have the following entry in /etc/mime.types: application/cap cap pcap I prefer "application/x-libpcap-capture" since it's more descriptive. Would it make sense to have an "application/x-libpcap-ng-capture" type for Pcap-NG/NTAR as well? - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] tcpdump.org mirrors
Michael Richardson wrote: >> "Michael" == Michael Richardson writes: > Michael> The data transfer of the bpf.tcpdump.org is still underway, > Michael> and should complete by morning EST. > > cvs.tcpdump.org, bpf.tcpdump.org and www.tcpdump.org are online again. > > It seems that the only mirror that works is www.at.tcpdump.org, but > alas, he isn't configured to also be www.tcpdump.org. > > Stable mirrors would be appreciated. If you still need a mirror you're welcome to use this one: Canonical URL: http://tcpdump.mirror.cacetech.com Server alias: *.tcpdump.org Location: Washington, D.C., US IPv4 address: 69.4.231.52 IPv6 address: 2607:f0d0:3001:62:1::52 Update frequency: 6 hours We're pulling from bpf.tcpdump.org using wget. Let me know if there's a more preferred method. - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] nightly build package
Guy Harris wrote: > On Jan 10, 2010, at 12:06 PM, Michael Richardson wrote: > >> I was supposed to setup a master/manager program (it was in python, I >> think), that will farm out builds for various platforms to a volunteer >> pool. I've forgotten the name of this system, but it was the same one >> that wireshark uses... > > Buildbot: > > http://buildbot.net/ I created a minimal libpcap+tcpdump Buildbot configuration a few months ago: http://buildbot.wireshark.org/tcpdump/waterfall Michael, I can send you the configuration files offline if you'd like. - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] non-root pcap capture under Linux
amnon cohen wrote: > Hi, > Is there anyway to capture packets without being root on Linux. > The docs imply that we running with CAP_NET_RAW will do the trick. > Has anyone managed to get this to work? > I got stuck when trying to add CAP_NET_RAW to the executable > > > # setcap cap_net_raw my_sniffer_program > fatal error: Invalid argument > usage: setcap [-q] [-v] (-r|-|) [ ... (-r|-|) > ] Try "setcap cap_net_raw,cap_net_admin=eip my_sniffer_program": http://packetlife.net/blog/2010/mar/19/sniffing-wireshark-non-root-user/ If you generate traffic you might need cap_net_broadcast as well. -- Join us for Sharkfest ’10! · Wireshark® Developer and User Conference Stanford University, June 14-17 · http://www.cacetech.com/sharkfest.10/ - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] bandwidth by user or process id
Phil Vandry wrote: > On Mon, 4 Oct 2010 09:51:39 -0400 Rob Hasselbaum wrote: >> Yes, it is possible (on Linux, anyway), but not extremely easy. You can >> correlate packet data to the kernel's network connection table and network >> connections to inode values by reading "/proc/net/tcp*" and > > Isn't that unreliable? The connection might be short-lived and disappear > from /proc/net/{tc,ud}p* before you have a chance to find it. > > Since you are assuming Linux anyway, have you considered using iptables? > > If you don't have a huge number of users, you can create a rule like this > for each uid: > > iptables -I OUTPUT -m owner --uid-owner -j ACCEPT > > and then just monitor the packet & byte counters on these rules. You can also catch events using SystemTap's netdev.transmit and netdev.receive probes. - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] only outbound traffic
On 4/28/11 6:51 AM, Andrej van der Zee wrote: > Is there any documentation on how libpcap/tcpdump/BPF deal with VLAN > tags? Its still a bit of a mystery to me... Does this help? https://blog.wireshark.org/2009/10/capture-filters-and-offsets/ -- Join us for Sharkfest ’11! · Wireshark® Developer and User Conference Stanford University, June 13-16 · http://sharkfest.wireshark.org - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] [libpcap][patch] appending to a capture
On 6/1/11 8:10 AM, Mark Johnston wrote: > Hi Darren, > > On Tue, May 31, 2011 at 03:53:22PM -0700, Darren Reed wrote: > >> You might be better off spending some time working >> on additions to editcap that include concatenating >> two or more pcap files. > > Shouldn't a function that manipulates capture files go into libpcap? I'm > not trying to solve a problem I'm having at the moment; rather, this > function has been in our tree for a long time, and I'd like to > contribute it upstream based on some interest that I saw. I'm happy to > modify it if that's what I need to do, but I think this functionality > should be in a library, not in a program. N.B. this functionality shouldn't be added to editcap either. It's already present in mergecap. -- Join us for Sharkfest ’11! · Wireshark® Developer and User Conference Stanford University, June 13-16 · http://sharkfest.wireshark.org - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
[tcpdump-workers] Sharkfest '11 keynote on libpcap now online
Steve McCanne spoke about the origins and architecture of libpcap and BPF at Sharkfest this year. The presentation and video are now online at http://sharkfest.wireshark.org/sharkfest.11/ under the "Keynote Video and Presentation" section. - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] buildbot failure in tcpdump+libpcap on Solaris-10-SPARC
On 3/15/14 2:56 PM, François-Xavier Le Bail wrote: >> From: Guy Harris > >> On Mar 15, 2014, at 12:02 PM, Michael Richardson wrote: >> >>> I guess that this means that we also now have testing against bigendian >>> systems. thank you wireshark guys! >> >> As long as it's doing "make check" for tcpdump. >> >> Gerald, is it doing that? > > It does. see: > http://buildbot.wireshark.org/tcpdump/builders/Solaris-10-SPARC/builds/16/steps/check%20tcpdump/logs/stdio That's correct. If there are any other tests that should be run let me know. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Wireshark mirror address change
Hi, The Wireshark tcpdump mirror (http://tcpdump.mirror.wireshark.org) is moving to a new host. The new addresses are: 198.199.88.104 2604:a880:400:d0::2221:3001 I'll keep the old host up and running for the next week or so. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Re: Returned mail: Data format error
On 11/18/24 9:08 AM, Michael Richardson wrote: The message about the spam was in fact spam. But, it forged a valid From: so it got through. I'd like to fix the SPF/DKIM/spam-filter such that it more aggressively kills this kind of forgery, assuming that wireshark.org has the right policies set. This kind of thing is fraught with false-positives, but there are some reasonable howtos. wireshark.org should have valid SPF and DKIM records. If the problem is limited to my address, I can subscribe from another one and you can just block my wireshark.org address if that's easier. ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[tcpdump-workers] Delivery reports about your e-mail
--- Begin Message --- --- End Message --- ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[tcpdump-workers] Status
--- Begin Message --- The original message was received at Wed, 25 Jun 2025 16:40:00 +0200 from wireshark.org [96.240.159.184] - The following addresses had permanent fatal errors - - Transcript of session follows - while talking to lists.tcpdump.org.: >>> MAIL From:ger...@wireshark.org <<< 501 ger...@wireshark.org... Refused --- End Message --- ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[tcpdump-workers] Returned mail: see transcript for details
--- Begin Message --- The original message was received at Fri, 18 Jul 2025 05:49:00 +0200 from wireshark.org [39.225.201.89] - The following addresses had permanent fatal errors - - Transcript of session follows - while talking to lists.tcpdump.org.: >>> MAIL From:ger...@wireshark.org <<< 501 ger...@wireshark.org... Refused --- End Message --- ___ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s