Wireshark mailing list archives

Re: Test


From: Mark Murawski <markm-lists () intellasoft net>
Date: Tue, 9 Jan 2018 15:21:58 -0500

So weird! I sent the same message twice, and only when I changed the url did it go through... perhaps coincidence. Let's see if this reply makes it through.



On 01/09/18 15:20, Maynard, Chris wrote:
I'm not aware of any constraints with respect to URL's.

Here's a test of your message with the original URL you intended to write; let's see if this goes through ...
- Chris


Hi,

Is there anyone who knows of an updated sharktooks that works with the latest wireshark (2.2+) ?
https://github.com/armenb/sharktools

I've contacted the author and haven't heard anything back yet.  Is there someone who may be willing to help update 
sharktools to work with modern wireshark?

I've done a tiny little bit of porting work so far on it, but I still have a ways to go and I'm not familiar with the 
history/refactors that wireshark has gone through to really do a proper port.  I'm getting a bit lost in the details.

Thanks


-----Original Message-----
From: Wireshark-dev [mailto:wireshark-dev-bounces () wireshark org] On
Behalf Of Mark Murawski
Sent: Tuesday, January 9, 2018 3:14 PM
To: wireshark-dev () wireshark org
Subject: Re: [Wireshark-dev] Test

What are the constraints for posting on this list?  It does look like url links
contained in a post body will cause the post to be completely blocked with no
explanation/notification.



On 1/9/18 3:10 PM, Mark Murawski wrote:
I tried replying to this message with my other (real) message and it's
not going through.  It must be tripping some anti-spam filters or
something like that.


On 1/8/18 5:39 PM, Kennedy, Smith (Wireless  & Standards Architec) wrote:
Ack.

On Jan 8, 2018, at 3:06 PM, Mark Murawski
<markm-lists () intellasoft net> wrote:

I don't believe my last message went through.

Testing

1
2
3












CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsidiaries and 
may contain proprietary, confidential or trade secret information.  This message is intended solely for the use of the 
addressee.  If you are not the intended recipient and have received this message in error, please delete this message 
from your system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is 
strictly prohibited.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
              mailto:wireshark-dev-request () wireshark org?subject=unsubscribe



___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread: