Date   

Re: more help on messaging please

Chris Curtis <kb0wlf@...>
 

Thanks again Lynn

 

That’s where I was heading.

Thanks for definite answer about how the igate should be sending.

 

Using this page:

http://www.findu.com/cgi-bin/entermsg.cgi

 

sender as kb0wlf

recipient as kb0wlf-1

the message ‘gets’ to kb0wlf-10 and does indeed send it out over rf.

(uiss likes this one fine)

 

I’ll look for a ‘better’ program for messaging =]

73

 

Chris

KB0WLF

 

From: aprsisce@... [mailto:aprsisce@...]
Sent: Saturday, March 05, 2016 8:03 PM
To: aprsisce@...
Subject: Re: [aprsisce] more help on messaging please

 

 

Seems like UISS doesn't like 3rd party packets, but that's how IGates are supposed to send them.

I checked http://aprs.fi/?c=message&call=KB0WLF-1 but I don't see any message TO KB0WLF-1 from the web?


Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32






.



Re: more help on messaging please

Lynn Deffenbaugh
 

Seems like UISS doesn't like 3rd party packets, but that's how IGates are supposed to send them.

I checked http://aprs.fi/?c=message&call=KB0WLF-1 but I don't see any message TO KB0WLF-1 from the web?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32



On 3/5/2016 1:55 PM, kb0wlf@... [aprsisce] wrote:

I apologize to the group in advance.

just add me to your ignore filter.


ok, so here I am again.


very specific this time so someone might be able to point out my stupidity.


all I want to do, at this point, is ask AO7 when it's coming around.


so, using UISS, I send an aprs message:

to: APRS

via: KB0WLF-10

for: AO7

msg: next pass


I hit the message button (f7 or click it)

my ht with Bluetooth tnc fires off the packet.

my aprsis32 1 hop igate receives the msg and gates it.

ao7 replies (I see this on the igate display)

my igate does send that reply out via rf.


NOW, here is where I'm getting frustrated.

UISS shows the packet:

Fm KB0WLF-10 To APWW10 Via WIDE1-1,WIDE2-1 [12:45:45]

}AO7>APWW10,KJ4ERJ-15,TCPIP,KB0WLF-10*::KB0WLF-1 :AOS 6m43s E NE^15 N 17m{ZC}


but it is not in GREEN letters signifying a msg for that instance of uiss.

uiss also does NOT send an ack, so the msg is repeated to me several times before giving up.


UISS is set to not send an ack but will give an ack upon request.


that's the problem I'm having.

to further frustrate me, if I go to findu and send an aprs message from the 'web' to kb0wlf-1, it goes through the 'system' and ends up showing green on the UISS display.


crazy.


thanks for your time, patience, and help.


chris

kb0wlf



more help on messaging please

kb0wlf@...
 

I apologize to the group in advance.

just add me to your ignore filter.


ok, so here I am again.


very specific this time so someone might be able to point out my stupidity.


all I want to do, at this point, is ask AO7 when it's coming around.


so, using UISS, I send an aprs message:

to: APRS

via: KB0WLF-10

for: AO7

msg: next pass


I hit the message button (f7 or click it)

my ht with Bluetooth tnc fires off the packet.

my aprsis32 1 hop igate receives the msg and gates it.

ao7 replies (I see this on the igate display)

my igate does send that reply out via rf.


NOW, here is where I'm getting frustrated.

UISS shows the packet:

Fm KB0WLF-10 To APWW10 Via WIDE1-1,WIDE2-1 <UI pid=F0 Len=77 >[12:45:45]

}AO7>APWW10,KJ4ERJ-15,TCPIP,KB0WLF-10*::KB0WLF-1 :AOS 6m43s E NE^15 N 17m{ZC}


but it is not in GREEN letters signifying a msg for that instance of uiss.

uiss also does NOT send an ack, so the msg is repeated to me several times before giving up.


UISS is set to not send an ack but will give an ack upon request.


that's the problem I'm having.

to further frustrate me, if I go to findu and send an aprs message from the 'web' to kb0wlf-1, it goes through the 'system' and ends up showing green on the UISS display.


crazy.


thanks for your time, patience, and help.


chris

kb0wlf


Re: igate to rf help

Lynn Deffenbaugh
 

Messages are gated from -IS to RF for stations that have been "recently" heard "locally". After a message is gated, the next position packet from the originating station will also be gated to RF. This is the so-called "courtesy" posit described at http://www.aprs-is.net/IGating.aspx specifically:

Passing all message packets also includes passing the sending station's position along with the message. ... The IGate should note the station(s) it has gated messages to RF for and pass the next position packet seen for that station(s) to RF.
But if you want to gate another APRS-IS station's posits to RF, you can do this in the development version using a "filtered" IGate feature. The process is:

1) Hit Control-G (for Filter Test) and enter a filter like "b/KJ4ERJ-12 +t/p". This filter selects all posit packets (+t/p) from KJ4ERJ-12 (b/KJ4ERJ-12). Monitor the Filter Test trace log for a while (hours or a day or two) to ensure that you only see the packets that you'd like to gate to RF.

2) With that filter in place, hit Control-I (for IGate). APRSIS32 will ask if you want to set the IGate filter. If you say yes, then all future packets that match that filter will be gated as 3rd party packets to RF.

Note that this setup has to be done each time you restart APRSIS32 as it is not currently persistent.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32




On 3/5/2016 10:13 AM, 'Craig 'Lumpy' Lemke' lumpy@digitalcartography.com [aprsisce] wrote:
Lynn W Deffenbaugh wrote:

...APRSISCE/32 has gated messages from
-IS to RF since shortly after RF ports were implemented...
Am I correct that's for MESSAGES only and not
position packets?

I'm currently in a situation (tracking my horses) where
I want to ORIGINATE an APRS posit on the IS (Android phone)
and gate it to RF (My chase truck). I seem to be able to
exchange messages just fine but I don't get POSITs from
the horse on my RF station in my truck.


Craig 'Lumpy' Lemke

www.n0eq.com




------------------------------------
Posted by: "Craig 'Lumpy' Lemke" <lumpy@digitalcartography.com>
------------------------------------


------------------------------------

Yahoo Groups Links




Re: igate to rf help

Craig 'Lumpy' Lemke
 

Lynn W Deffenbaugh wrote:

...APRSISCE/32 has gated messages from
-IS to RF since shortly after RF ports were implemented...
Am I correct that's for MESSAGES only and not
position packets?

I'm currently in a situation (tracking my horses) where
I want to ORIGINATE an APRS posit on the IS (Android phone)
and gate it to RF (My chase truck). I seem to be able to
exchange messages just fine but I don't get POSITs from
the horse on my RF station in my truck.


Craig 'Lumpy' Lemke

www.n0eq.com


Re: igate to rf help

Gene Young <n9mxq@...>
 

I believe it was something you posted years ago in the group. I left the group for a few years. Guess I'm out of date..

On 3/4/2016 8:22 PM, 'Lynn W Deffenbaugh (Mr)' kj4erj@... [aprsisce] wrote:
 

Huh?  Where'd you get that idea?  APRSISCE/32 has gated messages from -IS to RF since shortly after RF ports were implemented.  Arbitrary filtered packet gating from -IS to RF is only in the development release and is not persistent across IGate restarts.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32



On 3/4/2016 9:17 PM, Gene Young n9mxq@... [aprsisce] wrote:
As far as I can remember APRSISCE has never supported IP to RF gating

On 3/4/2016 7:03 PM, kb0wlf@... [aprsisce] wrote:
 

I should have added the specific to/from problem.


I send a msg to WHO-IS and the reply from WHO-IS stops at my iGATE box.

it does not tx to rf.


if I watch the igate box, I see the msg being gated and the reply from who-is as well.

just not sent over rf.  so who-is sends msg after msg since it doesn't get an ack from the originator.


same thing with the satsrvr


thanks

kb0wlf




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com






Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com






Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com






Re: igate to rf help

kb0wlf@...
 

thanks for the help. (and the program)

I was using the development version and rolled back to release.


whatever I broke, is unbroken now.


now, the only reason I am interested in internet to rf for a 'not recently heard' station is that I'd love to leave a client running but not have to 'beacon' at all.


so, I could still get an aprs message from internet over rf 2 or 3 days or a week after the last time I beaconed.

just my station though as I said originally.  not everything.


just for more info about me and my impact on the rf side of things:

looking at my qth you can see I'm the only digipeater/igate/repeater within 30 miles.

I shouldn't be congesting any rf side traffic unless I work really really hard :)


thanks again, I think I'm good for the time being.


73 all

chris

kb0wlf


Re: igate to rf help

Lynn Deffenbaugh
 

Huh?  Where'd you get that idea?  APRSISCE/32 has gated messages from -IS to RF since shortly after RF ports were implemented.  Arbitrary filtered packet gating from -IS to RF is only in the development release and is not persistent across IGate restarts.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32



On 3/4/2016 9:17 PM, Gene Young n9mxq@... [aprsisce] wrote:
As far as I can remember APRSISCE has never supported IP to RF gating

On 3/4/2016 7:03 PM, kb0wlf@... [aprsisce] wrote:
 

I should have added the specific to/from problem.


I send a msg to WHO-IS and the reply from WHO-IS stops at my iGATE box.

it does not tx to rf.


if I watch the igate box, I see the msg being gated and the reply from who-is as well.

just not sent over rf.  so who-is sends msg after msg since it doesn't get an ack from the originator.


same thing with the satsrvr


thanks

kb0wlf




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com






Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com




Re: igate to rf help

Lynn Deffenbaugh
 

Gating of messages to "recently" heard "local" stations is automatic.  However,  you do have to have a few Port settings correct.

Configure / Ports / APRS-IS - Must have IS to RF checked

Configure / Ports / - Must have IS to RF checked along with Messages and of course Xmit Enabled.

And it makes no sense (to me at least) to gate messages addressed to stations that have not been recently heard.  If you haven't heard them, then they're not likely to hear you and you're only QRMing the local RF channel to gate messages out to them.

If you bring up and enable the IGate, IGate(NOT), and Transmit logs, you should see the gated message show up there or possibly some reasons that it wasn't gated.  If it's there but not hitting the RF, you've got other problems (like possibly overrunning the TNC between the ack and the following message).

The full conditions for gating a message from -IS to RF are:

if (!NoPopups)		/* Not while recalling posits! */
if (IGateEnabled)						/* Don't bother if no RF Interface */
if (!IGateReceiveOnly)					/* or not transmitting */
if (ActiveConfig.APRSIS.IStoRFEnabled)
if (!*APRS->thirdCall)					/* We don't gate 3rd party packets */
if (!(APRS->Valid & APRS_TELEMETRYDEF_VALID))	/* Don't send Telemetry Definitions out */
if (!FromRF)							/* Don't put these back out there! */
if (!fromStat							/* Go ahead if we don't know the source */
|| !fromStat->HeardOnRF					/* or if we think the source is NOT on RF */
|| fromStat->HeardOnRF > LOCAL_MAX_HOPS+1)	/* or NOT local enough to be heard */
if (!Dupes[dp].RFDupeCount		/* Duplicates don't go out either */
&& !Dupes[dp].ISDupeCount)		/* Not even -IS dupes! */

which translates to:

Not during startup's recalling of station packets (NoPopups)
IGate must be enabled (set of flags including detection of an enabled RF interface)
IGate must be Xmit-Enabled
The APRS-IS port must be IStoRF enabled
It's not already a 3rd party packet
It's not telemetry definitions
It didn't come from an RF port
We must know it, have heard it on RF recently, and consider it local (based on hops)
And it must not be a duplicate packet

The IGate(NOT) log (if you have it enabled) will tell you if some of those things are not met, but not others of them.

Hopefully this'll be enough information to get you to the next level.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


On 3/4/2016 8:03 PM, kb0wlf@... [aprsisce] wrote:

I should have added the specific to/from problem.


I send a msg to WHO-IS and the reply from WHO-IS stops at my iGATE box.

it does not tx to rf.


if I watch the igate box, I see the msg being gated and the reply from who-is as well.

just not sent over rf.  so who-is sends msg after msg since it doesn't get an ack from the originator.


same thing with the satsrvr


thanks

kb0wlf



Re: igate to rf help

Gene Young <n9mxq@...>
 

As far as I can remember APRSISCE has never supported IP to RF gating

On 3/4/2016 7:03 PM, kb0wlf@... [aprsisce] wrote:
 

I should have added the specific to/from problem.


I send a msg to WHO-IS and the reply from WHO-IS stops at my iGATE box.

it does not tx to rf.


if I watch the igate box, I see the msg being gated and the reply from who-is as well.

just not sent over rf.  so who-is sends msg after msg since it doesn't get an ack from the originator.


same thing with the satsrvr


thanks

kb0wlf




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com






Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



Re: igate to rf help

kb0wlf@...
 

I should have added the specific to/from problem.


I send a msg to WHO-IS and the reply from WHO-IS stops at my iGATE box.

it does not tx to rf.


if I watch the igate box, I see the msg being gated and the reply from who-is as well.

just not sent over rf.  so who-is sends msg after msg since it doesn't get an ack from the originator.


same thing with the satsrvr


thanks

kb0wlf


Re: igate to rf help

Rob Giuliano
 

I guess I don't really see the point.
To control the network is to break the network.  Routing is controlled by the network and to take routes away means you introduce failures that should not exist. 

If I address a letter to a friend in another state, I don't know or care about the route, just that it gets there.
If a send a request for something over the internet, I don't care the route it takes there either, just that it makes the trip.

Now, as long as you can "prove" that you are "ABLE" to receive messages over RF, you have proven that part of the network is not broken.  This would be for testing purposes - short term one time events: disable the IS side and force only RF. 

Re-enable after so the network is "fully functional".
 
Robert Giuliano
KB8RCO



From: "Chris Curtis kb0wlf@... [aprsisce]"
To: aprsisce@...
Sent: Friday, March 4, 2016 4:40 PM
Subject: [aprsisce] igate to rf help

 
hello, kb0wlf here.

I am NOT interested in sending everything out the rf port ok?
:)

alright, now that that's clear;

I have my digipeater+igate running great.
I'm using aprsisce32 obviously.
it is running on wine in xubuntu.

everything works like it is supposed to except I'm having a hiccup with return messages.

I'm originating a message via rf.
it hits the target via the igate.
I see the target return a msg (spying on the aprsisce32 box)
I do NOT get the message over rf back to the originating device.

I can send a msg from the igate itself to the 'originating' device and it indeed sends it via rf.
I have sent a position report and receive the digipeated packet ok so I know it sees me as local.

how can I add a rule to always send traffic for kb0wlf-1 over rf regardless of 'last heard' ?

hope I've made that clear :)
kb0wlf-10 aprsisce32 1 hop igate
kb0wlf-1 pc in the house 100 yards from my repeater shack.

thanks for your time!

chris
kb0wlf



igate to rf help

Chris Curtis <kb0wlf@...>
 

hello, kb0wlf here.

I am NOT interested in sending everything out the rf port ok?
:)

alright, now that that's clear;

I have my digipeater+igate running great.
I'm using aprsisce32 obviously.
it is running on wine in xubuntu.

everything works like it is supposed to except I'm having a hiccup with return messages.

I'm originating a message via rf.
it hits the target via the igate.
I see the target return a msg (spying on the aprsisce32 box)
I do NOT get the message over rf back to the originating device.

I can send a msg from the igate itself to the 'originating' device and it indeed sends it via rf.
I have sent a position report and receive the digipeated packet ok so I know it sees me as local.

how can I add a rule to always send traffic for kb0wlf-1 over rf regardless of 'last heard' ?

hope I've made that clear :)
kb0wlf-10 aprsisce32 1 hop igate
kb0wlf-1 pc in the house 100 yards from my repeater shack.

thanks for your time!

chris
kb0wlf


APRS balloon SP9UOB-11 expected to reach West Coast on March 5th (probably 11-15 UTC)

Krzysztof SQ5NWI
 

Small foil balloon with CONTESTIA/CW/APRS tracker left Japan air 16
hours ago and is heading to West Coast.

http://aprs.fi/#!mt=roadmap&z=11&call=a%2FSP9UOB-11&timerange=604800&tail=604800
http://tracker.habhub.org/#!mt=roadmap&mz=7&qm=All&mc=32.53613,138.28567&q=sp9uob-11

According to prediction from Tomasz SP9UOB it should reach the range of
ground stations of LA/San Francisco area somewhere between 11 and 15 UTC
on Saturday, 5th.

Tracker works in triple mode:
- Contestia 32/1000 followed by RSID on 432.210MHz USB - transmission
every 5 minutes or every 18 minutes if temperature is lower than -40
Celsius degrees
- CW transmitting "HI" every 30 seconds between Contestia and Callsign
transmitted 30 seconds before Contestia transmission
- APRS every 6 minutes on APRS frequency appropriate for the balloon
location (144.390MHz for US I believe)

To receive and decode Contestia mode you need to use dl-fldigi in HAB mode.
Here you can find details: https://ukhas.org.uk/guides:tracking_guide
Put your attention to RxID or RSID setting which simplifies tracking a lot.

Please, pass this info to everyone who can help to receive even one
single frame from the tracker.
It is powered from battery - no solar panel - and foreseen power down is
in 2-3 days from now, so there is real risk that it will not survive
Pacific fly over.
Anyway, there is still a chance that it will do it!

Thank you in advance for support!

PS. Today we had US balloon guest over Poland. :-) WB8ELK-6 arrived at
morning and flew in North direction, but unfortunately it disappeared
late afternoon over central Poland. I hope we'll see polish balloon over
US on weekend. ;-)

---
Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast.
https://www.avast.com/antivirus


Re: Fw: important message

Dave
 

Forgot to add "hang in there Ron" 👍


On Feb 28, 2016, at 12:21 PM, 'Steve' steve@... [aprsisce] <aprsisce@...> wrote:

 

It happens on occasion and nobody is being accused of actually spamming, the spammers get in somehow on occasion and fake an id

 

Steve

G6UIM

 


From: aprsisce@... [mailto:aprsisce@...]
Sent: 28 February 2016 18:10
To: aprsisce@...
Subject: RE: [aprsisce] Fw: important message

 

 

On Sun, 28 Feb 2016 14:19:06 -0000, "'Steve'
steve@... [aprsisce]" <aprsisce@...>
wrote:
> Message removed and the user has been switched to moderated. At least
for
> the time being
>
> Steve
>
> G6UIM
>
> -------------------------
Hi Steve,
I, too, am still fighting this problem. If I'm not already on moderation,
perhaps I'd better be. I have killed my ARRL account, added a 21 character
password and raised he^^ with my ISP. No one seems able (or willing) to
help.

thanks for your patience and 73, Ron
+++++++++++++++++++++++++++++++
>
> FROM: aprsisce@... [mailto:aprsisce@...]
> SENT: 28 February 2016 14:13
> TO: aprsisce@...
> SUBJECT: Re: [aprsisce] Fw: important message
>
> I think you're spewing spam...
>
> Sent from my iPhone
>
> On Feb 28, 2016, at 7:51 AM, norbertchemconsult@... [1]
> [aprsisce] wrote:
>
> Hello!
>
> NEW MESSAGE, PLEASE READ http://123adreszoeken.nl/name.php [3]
>
> norbertchemconsult@... [4]
>
>


Re: Fw: important message

Dave
 

Yup.... That stuff really stinks.....grrrr.    Good luck on getting it resolved.  At minimum... It's  annoying.  73's.  Kc5uta 


On Feb 28, 2016, at 12:21 PM, 'Steve' steve@... [aprsisce] <aprsisce@...> wrote:

 

It happens on occasion and nobody is being accused of actually spamming, the spammers get in somehow on occasion and fake an id

 

Steve

G6UIM

 


From: aprsisce@... [mailto:aprsisce@...]
Sent: 28 February 2016 18:10
To: aprsisce@...
Subject: RE: [aprsisce] Fw: important message

 

 

On Sun, 28 Feb 2016 14:19:06 -0000, "'Steve'
steve@... [aprsisce]" <aprsisce@...>
wrote:
> Message removed and the user has been switched to moderated. At least
for
> the time being
>
> Steve
>
> G6UIM
>
> -------------------------
Hi Steve,
I, too, am still fighting this problem. If I'm not already on moderation,
perhaps I'd better be. I have killed my ARRL account, added a 21 character
password and raised he^^ with my ISP. No one seems able (or willing) to
help.

thanks for your patience and 73, Ron
+++++++++++++++++++++++++++++++
>
> FROM: aprsisce@... [mailto:aprsisce@...]
> SENT: 28 February 2016 14:13
> TO: aprsisce@...
> SUBJECT: Re: [aprsisce] Fw: important message
>
> I think you're spewing spam...
>
> Sent from my iPhone
>
> On Feb 28, 2016, at 7:51 AM, norbertchemconsult@... [1]
> [aprsisce] wrote:
>
> Hello!
>
> NEW MESSAGE, PLEASE READ http://123adreszoeken.nl/name.php [3]
>
> norbertchemconsult@... [4]
>
>


Re: Fw: important message

sbd sbd
 

It happens on occasion and nobody is being accused of actually spamming, the spammers get in somehow on occasion and fake an id

 

Steve

G6UIM

 


From: aprsisce@... [mailto:aprsisce@...]
Sent: 28 February 2016 18:10
To: aprsisce@...
Subject: RE: [aprsisce] Fw: important message

 

 

On Sun, 28 Feb 2016 14:19:06 -0000, "'Steve'
steve@... [aprsisce]" <aprsisce@...>
wrote:
> Message removed and the user has been switched to moderated. At least
for
> the time being
>
> Steve
>
> G6UIM
>
> -------------------------
Hi Steve,
I, too, am still fighting this problem. If I'm not already on moderation,
perhaps I'd better be. I have killed my ARRL account, added a 21 character
password and raised he^^ with my ISP. No one seems able (or willing) to
help.

thanks for your patience and 73, Ron
+++++++++++++++++++++++++++++++
>
> FROM: aprsisce@... [mailto:aprsisce@...]
> SENT: 28 February 2016 14:13
> TO: aprsisce@...
> SUBJECT: Re: [aprsisce] Fw: important message
>
> I think you're spewing spam...
>
> Sent from my iPhone
>
> On Feb 28, 2016, at 7:51 AM, norbertchemconsult@... [1]
> [aprsisce] wrote:
>
> Hello!
>
> NEW MESSAGE, PLEASE READ http://123adreszoeken.nl/name.php [3]
>
> norbertchemconsult@... [4]
>
>


Re: Fw: important message

kc8sfq
 

On Sun, 28 Feb 2016 14:19:06 -0000, "'Steve'
steve@daniels270.eclipse.co.uk [aprsisce]" <aprsisce@yahoogroups.com>
wrote:
Message removed and the user has been switched to moderated. At least
for
the time being

Steve

G6UIM

-------------------------
Hi Steve,
I, too, am still fighting this problem. If I'm not already on moderation,
perhaps I'd better be. I have killed my ARRL account, added a 21 character
password and raised he^^ with my ISP. No one seems able (or willing) to
help.

thanks for your patience and 73, Ron
+++++++++++++++++++++++++++++++

FROM: aprsisce@yahoogroups.com [mailto:aprsisce@yahoogroups.com]
SENT: 28 February 2016 14:13
TO: aprsisce@yahoogroups.com
SUBJECT: Re: [aprsisce] Fw: important message

I think you're spewing spam...

Sent from my iPhone

On Feb 28, 2016, at 7:51 AM, norbertchemconsult@tiscali.it [1]
[aprsisce] wrote:

Hello!

NEW MESSAGE, PLEASE READ http://123adreszoeken.nl/name.php [3]

norbertchemconsult@tiscali.it [4]


Re: Fw: important message

sbd sbd
 

It Happens don’t worry

 

Steve

G6UIM

 


From: aprsisce@... [mailto:aprsisce@...]
Sent: 28 February 2016 14:17
To: aprsisce@...
Subject: Re: [aprsisce] Fw: important message

 

 

I didn't post that!  Gene VE6WSO. 

 

On Sunday, February 28, 2016 7:13 AM, "David kc5uta@... [aprsisce]" <aprsisce@...> wrote:

 

 

I think you're spewing spam... 

Sent from my iPhone


On Feb 28, 2016, at 7:51 AM, norbertchemconsult@... [aprsisce] <aprsisce@...> wrote:

 

Hello!

 

New message, please read http://123adreszoeken.nl/name.php

 

 


Re: Fw: important message

sbd sbd
 

Message removed and the user has been switched to moderated. At least for the time being

 

Steve

G6UIM

 


From: aprsisce@... [mailto:aprsisce@...]
Sent: 28 February 2016 14:13
To: aprsisce@...
Subject: Re: [aprsisce] Fw: important message

 

 

I think you're spewing spam... 

Sent from my iPhone


On Feb 28, 2016, at 7:51 AM, norbertchemconsult@... [aprsisce] <aprsisce@...> wrote:

 

Hello!

 

New message, please read http://123adreszoeken.nl/name.php

 

norbertchemconsult@...

7061 - 7080 of 35699