As an extra note, at least with the ARRL, if you don't get a confirmation
e-mail right away there is no liability in sending your log again. You can
submit your log several times and only the most recent will be used.
I think the ARRL 10 GHz contest is one of the few that does not require a
Cabrillo log. I believe I got confirmations from the ARRL on sending logs
for this but they took a while to be sent and did not include captured log
info for verification like other contests do.
73, Zack W9SZ
On Thu, Jun 13, 2013 at 7:07 AM, Bob Naumann <W5OV@w5ov.com> wrote:
> None of these technical speculations really solve this problem do they?
>
> Q: What is the answer?
>
> A: The answer is that the sender has *total responsibility* to send the
> email to the right address. When he does, the robot will respond with a
> confirmation - usually within minutes if not sooner.
>
> So, if the sender does not get a confirmation that his log was received in
> good order, *he alone has the responsibility* to follow up on it.
>
> The contest sponsor has absolutely no responsibility until the log is
> correctly received by their "robot" system.
>
> So - what should you do?
>
> 1) Check that you're sending to the right address
> 2) Send your properly formatted log
> 3) Watch for a confirmation from the robot
> 4)
> a) If you don't get a confirmation in a reasonable time:
> 1) Check YOUR SPAM folder/system to see if it's there
> 2) If not, then go back to step #1
> b) If you do get a confirmation, you're all set.
>
> de W5OV
>
> -----Original Message-----
> From: CQ-Contest [mailto:cq-contest-bounces@contesting.com] On Behalf Of
> Sean Cavanaugh
> Sent: Wednesday, June 12, 2013 10:07 PM
> To: Katsuhiro Kondou
> Cc: cq-contest@contesting.com
> Subject: Re: [CQ-Contest] Logs - Upload don't email
>
> I suppose I was a bit lax in terminology.
>
> It technically doesn't violate the SMTP spec to not send a DSN, but from
> the
> RFC 5321 (SMTP) and RFC 821 (Old SMTP) standards, both state that if a
> message is not able to be forwarded or delivered, "the message MUST be
> returned as undeliverable." (RFC 5321) There is exceptions for things like
> harmful or invalid return addresses, but I'd presume a log sent from a
> properly formatted email address is neither of those.
>
> It breaks a lot of things, including user expectations, to just have a
> message disappear into the ether.
>
> 73,
>
> Sean - VA5LF
>
> On 2013-06-12, at 6:21 PM, Katsuhiro Kondou <kondou@voyackey.net> wrote:
>
> > In article <D1B4A9A8-E416-4CF4-97D3-DB349FD24DBE@unixgeeks.ca>,
> > Sean Cavanaugh <seanc@unixgeeks.ca> wrote,
> > on "Wed, 12 Jun 2013 12:26:38 -0600";
> >
> >> Most servers send back a Delivery Status Notification (DSN) saying the
> mail was undeliverable. I'm rather surprised the ARRL server doesn't, as it
> is very useful for both informing someone they sent the message to the
> wrong
> address, and for diagnosing any mail delivery problems that occur. It also
> violates the applicable standards (RFC 5321), but it seems a lot of people
> are willing to throw the baby out with the bathwater when it comes to
> fighting spam.
> >
> > I don't think it violate, since DSN is RFC3461, which is
> > just an SMTP extention.
> > --
> > Katsuhiro "Don" Kondou, JH5GHM
> > _______________________________________________
> > CQ-Contest mailing list
> > CQ-Contest@contesting.com
> > http://lists.contesting.com/mailman/listinfo/cq-contest
>
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|