[drats_users] Sending Email and Form

[Jann Traschewski]

> Your email is masqueraded behind the gateway station's email address. 
> So, lets say you compose an email to "foo at bar.com" and send 
> it to my station for gatewaying to the internet.  My station 
> sends the following:
> 
>    From: "DG8NGN <kk7ds at arrl.net>"
>    To: foo at bar.com
>    Subject: $subject
> 
>    $message
> 
> Most MUAs will then only show "DG8NGN" as the source of the 
> message in the listing.  When they hit reply, it will go back 
> to kk7ds at arrl.net, where my station will fetch, see that 
> there is a callsign in the To: 
> field and queue the result in my outbox to go back to you.
> 
> It's not transparent email delivery, nor is it designed to 
> be.  It's intended to facilitate communication with an email 
> recipient through another station without a lot of setup and 
> prior knowledge about who has what setup and how.

Thank you for clarification.
 
>> I'd like to choose my full e-mail adress rather than using 
>> the "Source Callsign" in it.
> 
> Well, that would be a bit of a problem.  First, if you put 
> your station on the air and allow people to send from any 
> address through your station, then I can start sending spam 
> through your machine "from" anyone I want.
> 
> Second, lets say I use GMail as my SMTP server (as many do).  
> That service, like many others, will not allow me to 
> originate a message from an address that I have not already 
> pre-verified as my own.  Thus, my station *cannot* 
> arbitrarily allow you to send email from your own email 
> address in a generic way, even if it wasn't a security issue.

Maybe you can add the option to additional add the "reply-to" information.
Then the users can decide theirself to let it look like:

   From: "DG8NGN <kk7ds at arrl.net>"
   To: foo at bar.com
   Reply-to: "DG8NGN <jann at gmx.de>"
   Subject: $subject

   $message
 
>> Winlink is fine ;)
> 
> Great, then you might be better off using that.  Because 
> Winlink is a fixed service with some predefined variables, it 
> allows more of a transparent experience.  In this example, 
> assume you send an email form to my station, addressed to 
> "WL2K:foo at bar.com".  In this example, my station composes the 
> following Winlink message and injects it into the
> system:
> 
>    From: DG8NGN at winlink.org
>    To: foo at bar.com
>    Subject: $subject
> 
>    $message
> 
> You can also right-click on my station in your stations list 
> on the right side of the screen and "request mail check" from 
> the WL2K service. 
>   Since my station knows how to log in to Winlink as your 
> callsign, it will go fetch any mail waiting there and queue 
> it up in the outbox.  As you can see, the WL2K support in 
> D-RATS allows you to be a more transparent email user, if 
> that's what you want to do.

Yes, nothing to complain about the winlink support :D
Thank you,
73,
Jann