Email on Shell - Revision history

Jab at 21:52, 27 January 2014

2014-01-27T21:52:08Z

← Older revision		Revision as of 15:52, 27 January 2014
Line 109:		Line 109:
	Unfortunately, there is no way to directly access the mail spool used by our "new" mail system from shell, but if you prefer to use shell to access your mail, I hope you can find a method of accessing your mail here that fits your own preferences. If you use another imap-capable mail client on shell, you should be able to configure it in a manner similar to mutt and pine. You may also want to look into either using webmail, or switching to a mail client that runs on your own computer. Using IMAP (which is what webmail uses behind the scenes), you can access your mailbox from multiple email clients easily, all keeping your email in a consistent state, and avoiding the numerous problems that come with POP.		Unfortunately, there is no way to directly access the mail spool used by our "new" mail system from shell, but if you prefer to use shell to access your mail, I hope you can find a method of accessing your mail here that fits your own preferences. If you use another imap-capable mail client on shell, you should be able to configure it in a manner similar to mutt and pine. You may also want to look into either using webmail, or switching to a mail client that runs on your own computer. Using IMAP (which is what webmail uses behind the scenes), you can access your mailbox from multiple email clients easily, all keeping your email in a consistent state, and avoiding the numerous problems that come with POP.

	[[~~Categpru~~:XMission_Email]]		[[Category:XMission_Email]]

Jab at 21:51, 27 January 2014

2014-01-27T21:51:53Z

← Older revision		Revision as of 15:51, 27 January 2014
Line 108:		Line 108:

	Unfortunately, there is no way to directly access the mail spool used by our "new" mail system from shell, but if you prefer to use shell to access your mail, I hope you can find a method of accessing your mail here that fits your own preferences. If you use another imap-capable mail client on shell, you should be able to configure it in a manner similar to mutt and pine. You may also want to look into either using webmail, or switching to a mail client that runs on your own computer. Using IMAP (which is what webmail uses behind the scenes), you can access your mailbox from multiple email clients easily, all keeping your email in a consistent state, and avoiding the numerous problems that come with POP.		Unfortunately, there is no way to directly access the mail spool used by our "new" mail system from shell, but if you prefer to use shell to access your mail, I hope you can find a method of accessing your mail here that fits your own preferences. If you use another imap-capable mail client on shell, you should be able to configure it in a manner similar to mutt and pine. You may also want to look into either using webmail, or switching to a mail client that runs on your own computer. Using IMAP (which is what webmail uses behind the scenes), you can access your mailbox from multiple email clients easily, all keeping your email in a consistent state, and avoiding the numerous problems that come with POP.

			[[Categpru:XMission_Email]]

Secretions: /* Configuring IMAP */

2010-03-12T17:55:20Z

Configuring IMAP

← Older revision		Revision as of 11:55, 12 March 2010
Line 96:		Line 96:
	set imap_pass=your_password_here		set imap_pass=your_password_here
	</pre>		</pre>

			=== Offline IMAP ===

			Though we cannot provide any support for it, you may also be interested in Offline IMAP:

			http://software.complete.org/software/projects/show/offlineimap

			It is essentially a two-way synchronization between IMAP and a set of Maildirs. One could either cron offlineimap, or run it continually in a screen, and use a maildir-aware console client to read their mail with direct file access and such, without sacrificing the ability to use POP and IMAP. It would also be possible to forward to a shell account (without keeping a copy), process with procmail into the maildirs that are being synchronized with the IMAP server, creating a setup that essentially mimicks direct mail spool access to mailboxes that are still accessible via POP, IMAP and Webmail.

	== Other Options ==		== Other Options ==

	Unfortunately, there is no way to directly access the mail spool used by our "new" mail system from shell, but if you prefer to use shell to access your mail, I hope you can find a method of accessing your mail here that fits your own preferences. If you use another imap-capable mail client on shell, you should be able to configure it in a manner similar to mutt and pine. You may also want to look into either using webmail, or switching to a mail client that runs on your own computer. Using IMAP (which is what webmail uses behind the scenes), you can access your mailbox from multiple email clients easily, all keeping your email in a consistent state, and avoiding the numerous problems that come with POP.		Unfortunately, there is no way to directly access the mail spool used by our "new" mail system from shell, but if you prefer to use shell to access your mail, I hope you can find a method of accessing your mail here that fits your own preferences. If you use another imap-capable mail client on shell, you should be able to configure it in a manner similar to mutt and pine. You may also want to look into either using webmail, or switching to a mail client that runs on your own computer. Using IMAP (which is what webmail uses behind the scenes), you can access your mailbox from multiple email clients easily, all keeping your email in a consistent state, and avoiding the numerous problems that come with POP.

Secretions: /* Forwarding to Shell */

2010-02-04T21:22:19Z

Forwarding to Shell

← Older revision		Revision as of 15:22, 4 February 2010
Line 8:		Line 8:

	One option is to forward all your email to your shell account.		One option is to forward all your email to your shell account.

			Your account MUST be on the new mail system for this to work. If you have received an email informing you of a pending migration to the new mail system, please wait until AFTER the migration has occurred to set this option up. You may also email support@xmission.com and request that forwarding be setup along with the migration of your email account.

	You can do this by logging into [https://webmail.xmission.com webmail], expanding the "mail" section on the left, and clicking "Filters". On the right, in the main pane of webmail, click on "Show Detailed Filter Rules".		You can do this by logging into [https://webmail.xmission.com webmail], expanding the "mail" section on the left, and clicking "Filters". On the right, in the main pane of webmail, click on "Show Detailed Filter Rules".

Secretions at 23:49, 3 February 2010

2010-02-03T23:49:30Z

← Older revision		Revision as of 17:49, 3 February 2010
Line 27:		Line 27:
	Here are some sample .fetchamilrc files...		Here are some sample .fetchamilrc files...

	Standard fetchmail, ~~writes directly~~ to the ~~mail spool~~:		Standard fetchmail, sends to the mta:

	<pre>poll mail.xmission.com		<pre>poll mail.xmission.com

Secretions at 22:15, 3 February 2010

2010-02-03T22:15:15Z

← Older revision		Revision as of 16:15, 3 February 2010
Line 27:		Line 27:
	Here are some sample .fetchamilrc files...		Here are some sample .fetchamilrc files...

	Standard fetchmail, ~~sends~~ to ~~local mta~~:		Standard fetchmail, writes directly to the mail spool:

	<pre>poll mail.xmission.com		<pre>poll mail.xmission.com

Bob: /* Using Fetchmail / Maildrop */

2009-12-22T20:28:57Z

Using Fetchmail / Maildrop

← Older revision		Revision as of 14:28, 22 December 2009
Line 21:		Line 21:
	== Using Fetchmail / Maildrop ==		== Using Fetchmail / Maildrop ==

	You can set up fetchmail on ~~it's~~ own, in which case it will send mail to the local mail transport agent (Exim on shell.xmission.com), or using Maildrop. Fetchmail uses the configuration ".fetchmailrc" in your home directory. Once you have it configured, you can just run the command "fetchmail" on shell.xmission.com, and it will retreive your mail. You can cron this, or set up a shell script that runs in right before running your mail client, and have delivery to your shell account become automated.		You can set up fetchmail on its own, in which case it will send mail to the local mail transport agent (Exim on shell.xmission.com), or using Maildrop. Fetchmail uses the configuration ".fetchmailrc" in your home directory. Once you have it configured, you can just run the command "fetchmail" on shell.xmission.com, and it will retreive your mail. You can cron this, or set up a shell script that runs in right before running your mail client, and have delivery to your shell account become automated.

	If you choose the latter option (shell script running both), this has the advantage that you can check your mail via webmail.xmission.com (or pop, leaving on server, or imap) from locations where you don't have shell access, seeing all the mail that's queued up, but still have the mail automatically delivered to shell once you're ready to read it there, avoiding the quota maintenance problems present with simple forwarding / keep on server.		If you choose the latter option (shell script running both), this has the advantage that you can check your mail via webmail.xmission.com (or pop, leaving on server, or imap) from locations where you don't have shell access, seeing all the mail that's queued up, but still have the mail automatically delivered to shell once you're ready to read it there, avoiding the quota maintenance problems present with simple forwarding / keep on server.

Secretions at 20:14, 8 December 2009

2009-12-08T20:14:03Z

← Older revision		Revision as of 14:14, 8 December 2009
Line 13:		Line 13:
	You will now see your webmail filters, including the built-in forwarding filter. Make sure that the forwarding filter is enabled. There should be a green checkbox on the same line indicating that it's enabled. If there is a red "X" on the same line as the forwarding filter, click on the "X", and it should become a green checkbox. Now click on "Forward".		You will now see your webmail filters, including the built-in forwarding filter. Make sure that the forwarding filter is enabled. There should be a green checkbox on the same line indicating that it's enabled. If there is a red "X" on the same line as the forwarding filter, click on the "X", and it should become a green checkbox. Now click on "Forward".

	Enter your shell username in the text box labeled "Address(es) to forward to", and click save.		Enter your shell username@shell.xmission.com in the text box labeled "Address(es) to forward to", and click save.

	Your email will now be forwarded to shell.xmission.com.		Your email will now be forwarded to shell.xmission.com.

Secretions at 18:50, 8 December 2009

2009-12-08T18:50:28Z

← Older revision		Revision as of 12:50, 8 December 2009
Line 76:		Line 76:
	Quite pine and restart.		Quite pine and restart.

	We do not have passwordfile support in our copy of pine, so you will need to type your ~~username~~ in every time you start pine.		We do not have passwordfile support in our copy of pine, so you will need to type your password in every time you start pine.

	=== Mutt Instructions ===		=== Mutt Instructions ===

Secretions at 18:49, 8 December 2009

2009-12-08T18:49:36Z

← Older revision		Revision as of 12:49, 8 December 2009
Line 58:		Line 58:
	mda "/usr/bin/procmail -f %F"</pre>		mda "/usr/bin/procmail -f %F"</pre>

	Note that the "no keep" and "flush" are optional. Remove "no keep", and fetchmail will leave messages it downloads on the server. Remove flush, and fetchmail will ~~delete~~ all already-downloaded messages ~~off~~ the server.		Note that the "no keep" and "flush" are optional. Remove "no keep", and fetchmail will leave messages it downloads on the server. Remove flush, and fetchmail will leave all already-downloaded messages on the server.

	== Configuring IMAP ==		== Configuring IMAP ==