User Tools

Site Tools

Trace:
email_at_sdf

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
email_at_sdf [2024/06/21 18:01] – updated pop3 server to "pop3.sdf.org" peteyboyemail_at_sdf [2025/03/27 17:14] (current) – [Webmail (Memberships: Validated User or ARPA or MetaARPA)] added note about shell auth steps for webmail peteyboy
Line 1: Line 1:
 ======= Accessing your SDF Email ======= ======= Accessing your SDF Email =======
 +
 //There are several ways to get and send email at SDF, but the different options depend on your membership(s) here. This guide is intended to describe the options simply and clearly, by membership level// //There are several ways to get and send email at SDF, but the different options depend on your membership(s) here. This guide is intended to describe the options simply and clearly, by membership level//
  
Line 7: Line 8:
  
   * User   * User
-  * Pre-validated User: This is before you are "validated" by either sending a nominal amount of money to SDF(enter ''%%validate%%'' at shell) or by finding a MetaARPA member to validate you+  * Pre-validated User: This is before you are “validated” by either sending a nominal amount of money to SDF(enter ''%%validate%%'' at shell) or by finding a MetaARPA member to validate you
   * Validated User/ARPA   * Validated User/ARPA
   * [[https://sdf.org/?faq?VHOST |VPM/VHOST*]]   * [[https://sdf.org/?faq?VHOST |VPM/VHOST*]]
Line 15: Line 16:
  
 The differences of the above accounts, besides the cost, is that VPM, VHOST and MetaARPA are annual memberships, so require continuing support of SDF, while User and ARPA are lifetime memberships, and only require payment once. The differences of the above accounts, besides the cost, is that VPM, VHOST and MetaARPA are annual memberships, so require continuing support of SDF, while User and ARPA are lifetime memberships, and only require payment once.
- 
  
 ====== Ways to Get and Send Email at SDF ====== ====== Ways to Get and Send Email at SDF ======
Line 21: Line 21:
 By default your E-mail Address is your SDF username, which by default works with a couple of domain names (you can also choose the domain you would like to use from the list of SDF domain names). By default your E-mail Address is your SDF username, which by default works with a couple of domain names (you can also choose the domain you would like to use from the list of SDF domain names).
  
-So if your username is "coffee" you can try sending yourself a mail with your existing E-mail account to:+So if your username is “coffee” you can try sending yourself a mail with your existing E-mail account to:
  
 //coffee@sdf.org// or //coffee@freeshell.org//.  //coffee@sdf.org// or //coffee@freeshell.org//. 
Line 31: Line 31:
 ===== Email Programs from Shell (Memberships: User or ARPA or MetaARPA) ===== ===== Email Programs from Shell (Memberships: User or ARPA or MetaARPA) =====
  
-You can always access your SDF mail account through any of several email programs installed on the server. All of these emails access your "mail spool", where your email is put by the mail server.+You can always access your SDF mail account through any of several email programs installed on the server. All of these emails access your “mail spool”, where your email is put by the mail server.
  
 //mutt// is available even to **Pre-validated Users**. Just type ''%%mutt%%'' at the command prompt. Here's [[How to Use mutt]] //mutt// is available even to **Pre-validated Users**. Just type ''%%mutt%%'' at the command prompt. Here's [[How to Use mutt]]
Line 44: Line 44:
  
   * The old SquirrelMail, accessible for Validated Users or above, accessible from the ''%%webmail%%'' link at the top of the [[http://sdf.org|SDF home page]] (current direct link: [[https://mx.sdf.org/sm/src/login.php]])   * The old SquirrelMail, accessible for Validated Users or above, accessible from the ''%%webmail%%'' link at the top of the [[http://sdf.org|SDF home page]] (current direct link: [[https://mx.sdf.org/sm/src/login.php]])
 +  * As of March 2025, to combat malicious actors, a shell auth requirement was added to use webmail:
 +    * Message from //membership// on bboard: "We're going back to have webpage auth enabled for SquirrelMail which will reset once a week.  To get the current auth to load the page, please run 'webmail' at the shell.  Once you have that, authenticate to load the page and then login to your account to bring up SquirrelMail webmail."
   * Roundcube, a slicker experience, accessible by MetaARPA users from the link on the [[http://ma.sdf.org|metaarray home page]]   * Roundcube, a slicker experience, accessible by MetaARPA users from the link on the [[http://ma.sdf.org|metaarray home page]]
- 
  
 ===== Local Client Email  (Memberships: User or ARPA or MetaARPA) ===== ===== Local Client Email  (Memberships: User or ARPA or MetaARPA) =====
-If you want to use an email program running on your computer or phone or tablet or other device to access your SDF mail, things get a little more complicated. At different membership levels, you have a different set of options for both getting ("fetching") or sending your mail.+If you want to use an email program running on your computer or phone or tablet or other device to access your SDF mail, things get a little more complicated. At different membership levels, you have a different set of options for both getting (“fetching”) or sending your mail.
  
 Basically, While **User or ARPA can read mail on their own machines or devices**, the SDF mail server does not offer outgoing SMTP to users at these membership levels. **You can still compose messages on your own machine**, however, leaving the final delivery to be handled by //either//: Basically, While **User or ARPA can read mail on their own machines or devices**, the SDF mail server does not offer outgoing SMTP to users at these membership levels. **You can still compose messages on your own machine**, however, leaving the final delivery to be handled by //either//:
Line 55: Line 56:
   * an SSH session to SDF that initiates ''sendmail -t'' instead of the usual interactive shell.   * an SSH session to SDF that initiates ''sendmail -t'' instead of the usual interactive shell.
  
-With the first option (local ISP), setting the "Envelope-from" address to //you@sdf.org// might result in the message getting blocked by your recipient's email provider, since your local ISP is not likely to be recognized as a valid origin for an address like //you@sdf.org// (i.e, the message fails SPF/DKIM verification). The second option (sendmail in an SSH session) will present no such discrepancy between "Envelope-from" and originating host, so the message is more likely to be delivered successfully.+With the first option (local ISP), setting the “Envelope-from” address to //you@sdf.org// might result in the message getting blocked by your recipient's email provider, since your local ISP is not likely to be recognized as a valid origin for an address like //you@sdf.org// (i.e, the message fails SPF/DKIM verification). The second option (sendmail in an SSH session) will present no such discrepancy between “Envelope-from” and originating host, so the message is more likely to be delivered successfully.
  
 ==== Local Client Email: Receiving Mail (Memberships: Validated User or ARPA or VPM or VHOST or MetaARPA) ==== ==== Local Client Email: Receiving Mail (Memberships: Validated User or ARPA or VPM or VHOST or MetaARPA) ====
Line 86: Line 87:
  
 ==== Local Client Email: Sending Email Via SMTP (Memberships: User or ARPA or VPM or VHOST or MetaARPA) ==== ==== Local Client Email: Sending Email Via SMTP (Memberships: User or ARPA or VPM or VHOST or MetaARPA) ====
 +
 As mentioned above, there are different paths for sending SDF mail from an email client on your computer or other device, depending on your membership level. As mentioned above, there are different paths for sending SDF mail from an email client on your computer or other device, depending on your membership level.
  
Line 96: Line 98:
 After you've set up your email client to receive mail (see above), the next thing you need to do is figure out the outgoing mail server that your computer or device's ISP provides. After you've set up your email client to receive mail (see above), the next thing you need to do is figure out the outgoing mail server that your computer or device's ISP provides.
  
-For example, if you are with Comcast on your computer at home, you can set up POP3 or IMAP in your favorite mail client as described above to read your SDF mail, and use your Comcast mail SMTP server (outgoing mail server) to send mail "from" your SDF account. On your phone, you can do the same, except you would use Verizon/AT&T/T-mobile's SMTP server (you may have to look up how if you don't know it) for sending messages "from" your SDF account. +For example, if you are with Comcast on your computer at home, you can set up POP3 or IMAP in your favorite mail client as described above to read your SDF mail, and use your Comcast mail SMTP server (outgoing mail server) to send mail “from” your SDF account. On your phone, you can do the same, except you would use Verizon/AT&T/T-mobile's SMTP server (you may have to look up how if you don't know it) for sending messages “from” your SDF account. 
  
 Next, you can follow the directions in [[setting up mail clients]], but you'll have to replace the values for the settings with those of your ISP's outgoing SMTP server. Next, you can follow the directions in [[setting up mail clients]], but you'll have to replace the values for the settings with those of your ISP's outgoing SMTP server.
Line 113: Line 115:
  
 //For VHOST memberships:// if you are using email addresses on your VHOST using '''[[https://sdf.org/?faq?VHOST?06|mkvpm]]'', you need to add a SPF record to your VHOST's ''.dns'' file so other mail services (Google, Yahoo!, AOL) won't reject your emails as spam. See [[Add SPF Record for your VPM mail]] //For VHOST memberships:// if you are using email addresses on your VHOST using '''[[https://sdf.org/?faq?VHOST?06|mkvpm]]'', you need to add a SPF record to your VHOST's ''.dns'' file so other mail services (Google, Yahoo!, AOL) won't reject your emails as spam. See [[Add SPF Record for your VPM mail]]
 +
email_at_sdf.1718992890.txt.gz · Last modified: 2024/06/21 18:01 by peteyboy