[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [linrad] For W3SZ
- Subject: Re: [linrad] For W3SZ
- From: "John Harrison, NI1B" <jmh6@xxxxxxxxxxxxxx
- Date: Wed, 28 Jan 2004 06:52:22 -0500 (EST)
Hi Leif,
The message you received means that the destination refused your mail
because it 'thinks' your site is a 'open relay'.
<rant>
I have NO kind words for sysadmins who set their systems up to refuse
incoming mail. I have had this problem myself sending PCB files to
companies!!
The basic problem is that W3SZ's e-mail ISP is braindead.. NO clue..
It's like saying, someone once said you MIGHT send junk mail, so just
to be sure I won't accept ANY mail from you EVER. Furthermore if you try
to send mail to the SYSOP pointing this out, this mail TOO will be
refused.
Like I said. A REALLY clueless sysop.
</rant>
I hope the above helps. Simple solution, change e-mail providers.
Problem solved.
regards to all,
john, ni1b
On Wed, 28 Jan 2004, [iso-8859-1] Leif Åsbrink wrote:
> Hi Roger,
>
> I have tried to send mails to you several times in the past (comments
> to things on MOON-NET) but I have got the following message from
> MAILER-DAEMON:
>
> This Message was undeliverable due to the following reason:
> Your message was not delivered because the return address was refused.
> The return address was 'xxxxxxxxxxxxxx' (my address)
>
>
>
> This time my message was an answer to your question so I send it
> via the Linrad mailing list.
>
> 73
>
> Leif
>
>
>
>
> ********************************************************************
>
>
> Hi Roger,
>
> > Will the hardware interface bug affect the 3 units I already have
> > [RX2500, RX10700,
> > RX70]?
> Maybe. Depends on many things.
>
> If you see the message NO RESPONSE FROM HARDWARE it is probably
> the bug, but it could also be incorrect connections.
> The next version has a function for testing the serial communication to
> the hardware so it will be easy to troubleshoot.
>
> The bug is that i forgot to update a variable against which time
> is compared before the clock is toggled. This means that the clock
> may become too fast on a fast computer..........
>
> I am waiting to see if there will be some response to the swap issue.
> It is necessary to issue the command:
>
> swapoff -a
>
> Then verify that Linrad runs with the parameters you have selected.
> If it does, just issue
>
> swapon -a
>
> to turn swap on again.
>
> This will be the recommendation unless someone has a better suggestion.
>
>
> 73
>
> Leif
>
>
LINRADDARNIL