Mail - Revision history

S23adhik: /* Technical Details */

2025-08-11T07:26:01Z

Technical Details

← Older revision		Revision as of 02:26, 11 August 2025
Line 216:		Line 216:

	== Technical Details ==		== Technical Details ==

			=== Relay Server ===
			At some point IST started enforcing that everyone use their Relay server so we did, info on how we configured it can be found here; [https://uwaterloo.atlassian.net/wiki/spaces/FAST/pages/5212014152/Bulk+Automatic+Email+Configuration]

	=== Mail Transfer (Incoming) ===		=== Mail Transfer (Incoming) ===

Y266shen: add instructions on sieve/managesieve

2024-10-21T19:31:53Z

add instructions on sieve/managesieve

@@ Line 24: / Line 24: @@
 ** SSL encryption and authentication required
 ** Port: 25, 465, or 587
 == Mail User Agents ==
@@ Line 191: / Line 214: @@
 Gnus has a plethora of useful and complex features, and one cat get very fancy with it.  But that is left as an exercise for the [https://www.gnu.org/software/emacs/manual/gnus.html interested reader]. :-)
 == Technical Details ==
@@ Line 252: / Line 243: @@
 If you are out of quota or another error occurs writing to your home directory, dovecot will deliver your message to /var/mail/$USER on the mail server. If that too fails, the server is probably on fire. The message will be returned to the queue where it will eventually bounce.
 ==== Forwarding ====

Y266shen: mail refresh on 2024-10

2024-10-21T19:21:42Z

mail refresh on 2024-10

← Older revision		Revision as of 14:21, 21 October 2024
Line 234:		Line 234:

	* zen.spamhaus.org RBL		* zen.spamhaus.org RBL
	* Greylisting with ~~postgrey~~		* Greylisting with rspamd (see below)

	These filters reject truckloads of spam, preventing them from reaching your inbox. Greylisting adds a delay to mail delivery from unknown servers, but after a small number of successes they will be auto-whitelisted. If that isn't good enough, ask systems-committee@csclub.uwaterloo.ca to whitelist all mail to your address.		These filters reject truckloads of spam, preventing them from reaching your inbox. Greylisting adds a delay to mail delivery from unknown servers, but after a small number of successes they will be auto-whitelisted. If that isn't good enough, ask systems-committee@csclub.uwaterloo.ca to whitelist all mail to your address.

			=== Spam filtering ===
			Before mail is delivered, it is sent to rspamd for spam checking. rspamd might greylist and/or add headers to the mail. rspamd WON'T reject the mail on its own. It is up to the user's filter to decide what to do based on the spam headers (usually put mails tagged as spam into a folder like Junk).

	=== Mail Delivery ===		=== Mail Delivery ===

	User mail is delivered, by ~~default,~~ to ~~procmail~~. This is configurable by adding a comma-separated list of destinations in $HOME/.forward. See aliases(5) for more details.		User mail is delivered by LMTP to dovecot. This is configurable by adding a comma-separated list of destinations in $HOME/.forward. See aliases(5) for more details.

			Dovecot, in turn, runs the mail through user's sieve filter script (in $HOME/.maildir/sieve/ with the active filer symlink-ed to $HOME/.maildir/.dovecot.sieve). If no sieve script is found, Dovecot defaults to an internal sieve script, which pipes the mail though procmail to maintain compatibility with existing $HOME/.procmailrc scripts. You can write sieve scripts by hand, or use the graphical editor provided by https://mail.csclub.uwaterloo.ca, under Settings/Filters.
	Procmail, in turn, writes mail to $HOME/.maildir unless instructed otherwise. You can customize procmail by editing $HOME/.procmailrc. See procmailrc(5) for more details.

			Note that procmail compatibility might be removed in the future.

	==== Failures ====		==== Failures ====

	If you are out of quota or another error occurs writing to your home directory, ~~procmail~~ will deliver your message to /var/mail/$USER on the mail server. If that too fails, the server is probably on fire. The message will be returned to the queue where it will eventually bounce.		If you are out of quota or another error occurs writing to your home directory, dovecot will deliver your message to /var/mail/$USER on the mail server. If that too fails, the server is probably on fire. The message will be returned to the queue where it will eventually bounce.

	==== Forwarding ====		==== Forwarding ====
Line 263:		Line 268:

	On the mail container, outgoing mail is submitted directly to Postfix via the sendmail(1) wrapper or on submission/587. Submitted mail is then queued for delivery to its destination. The other systems have no MTA and instead run sSMTP, which relays mail through the mail container immediately without any queue or daemon.		On the mail container, outgoing mail is submitted directly to Postfix via the sendmail(1) wrapper or on submission/587. Submitted mail is then queued for delivery to its destination. The other systems have no MTA and instead run sSMTP, which relays mail through the mail container immediately without any queue or daemon.

	=== Syscom ===

	Postgrey whitelists are in `/etc/postgrey` on mail.

	[[Category:Software]]		[[Category:Software]]

Merenber at 13:12, 21 July 2022

2022-07-21T13:12:42Z

← Older revision		Revision as of 08:12, 21 July 2022
Line 1:		Line 1:
	Mail services are currently handled by [[Machine_List#mail\|the mail container]] on [[Machine_List#~~glomag~~\|~~glomag~~]].		Mail services are currently handled by [[Machine_List#mail\|the mail container]] on [[Machine_List#xylitol\|xylitol]].

	== Reading your mail ==		== Reading your mail ==

R389li at 01:59, 6 January 2022

2022-01-06T01:59:58Z

← Older revision		Revision as of 20:59, 5 January 2022
Line 263:		Line 263:

	On the mail container, outgoing mail is submitted directly to Postfix via the sendmail(1) wrapper or on submission/587. Submitted mail is then queued for delivery to its destination. The other systems have no MTA and instead run sSMTP, which relays mail through the mail container immediately without any queue or daemon.		On the mail container, outgoing mail is submitted directly to Postfix via the sendmail(1) wrapper or on submission/587. Submitted mail is then queued for delivery to its destination. The other systems have no MTA and instead run sSMTP, which relays mail through the mail container immediately without any queue or daemon.

			=== Syscom ===

			Postgrey whitelists are in `/etc/postgrey` on mail.

	[[Category:Software]]		[[Category:Software]]

Merenber: /* Gmail (SMTP Relay) */

2021-07-24T00:21:06Z

Gmail (SMTP Relay)

← Older revision		Revision as of 19:21, 23 July 2021
Line 106:		Line 106:
	[[File:Gmail_choose_sender.png\|600px]]		[[File:Gmail_choose_sender.png\|600px]]

	If you want to receive your CSC messages via Gmail, just append your Gmail address to the end of the <code>.forward</code> file in your home directory on the CSC servers (it needs to be on a new line). However, if you have a custom procmailrc file, then the procmailrc will be ignored, because .forward files have higher precedence. If you really wanted to, you could write a custom Python script which is called by procmail and which would forward each message to your Gmail account (this is outside of the scope of this article, however).		If you want to receive your CSC messages via Gmail, just append your Gmail address to the end of the <code>.forward</code> file in your home directory on the CSC servers (it needs to be on a new line).

	=== Outlook Desktop ===		=== Outlook Desktop ===

R389li: /* Mail User Agents */ Add Outlook Desktop

2021-05-15T21:49:18Z

Mail User Agents: Add Outlook Desktop

← Older revision		Revision as of 16:49, 15 May 2021
Line 107:		Line 107:

	If you want to receive your CSC messages via Gmail, just append your Gmail address to the end of the <code>.forward</code> file in your home directory on the CSC servers (it needs to be on a new line). However, if you have a custom procmailrc file, then the procmailrc will be ignored, because .forward files have higher precedence. If you really wanted to, you could write a custom Python script which is called by procmail and which would forward each message to your Gmail account (this is outside of the scope of this article, however).		If you want to receive your CSC messages via Gmail, just append your Gmail address to the end of the <code>.forward</code> file in your home directory on the CSC servers (it needs to be on a new line). However, if you have a custom procmailrc file, then the procmailrc will be ignored, because .forward files have higher precedence. If you really wanted to, you could write a custom Python script which is called by procmail and which would forward each message to your Gmail account (this is outside of the scope of this article, however).

			=== Outlook Desktop ===

			This is probably the world's most powerful email client, but you need to jump through a lot of hoops to setup your CSC email with it. Luckily I've done those for you so just follow these steps:

			[[File:Ol1.png\|600px]]

			Open Outlook and click File at the top left.

			[[File:Ol2.png\|600px]]

			Click Account Settings and then Manage Profiles.

			[[File:Ol3.png\|600px]]

			Click Email accounts...

			[[File:Ol4.png\|600px]]

			Click New...

			[[File:Ol5.png\|600px]]

			Enter your name, CSC email and password. If you have an email alias, don't use your alias, use your QuestID@csclub.uwaterloo.ca email. Click Next >

			[[File:Ol6.png\|600px]]

			It will start searching for your account, this can take a minute or two.

			[[File:Ol7.png\|600px]]

			Once it finishes configuring it you'll get a test email.

			[[File:Ol8.png\|600px]]

			Uncheck Set up Outlook Mobile on my phone (unless you want to), and check Change account settings. Then click Next >

			[[File:Ol9.png\|600px]]

			If you have an email alias, you can now change your email to that in the Email Address field. Don't change your logon info. You can click More Settings to change your mailbox name, or click Finish (setup is complete).

			[[File:Ol10.png\|600px]]

			You can change the name here. That's it. I've provided the other two tabs' configs below just in case anyone (including future me) needs it.

			[[File:Ol11.png\|600px]]
			[[File:Ol12.png\|600px]]

	=== Gnus ===		=== Gnus ===

Abandali: add Gnus

2021-04-24T02:24:58Z

add Gnus

← Older revision		Revision as of 21:24, 23 April 2021
Line 107:		Line 107:

	If you want to receive your CSC messages via Gmail, just append your Gmail address to the end of the <code>.forward</code> file in your home directory on the CSC servers (it needs to be on a new line). However, if you have a custom procmailrc file, then the procmailrc will be ignored, because .forward files have higher precedence. If you really wanted to, you could write a custom Python script which is called by procmail and which would forward each message to your Gmail account (this is outside of the scope of this article, however).		If you want to receive your CSC messages via Gmail, just append your Gmail address to the end of the <code>.forward</code> file in your home directory on the CSC servers (it needs to be on a new line). However, if you have a custom procmailrc file, then the procmailrc will be ignored, because .forward files have higher precedence. If you really wanted to, you could write a custom Python script which is called by procmail and which would forward each message to your Gmail account (this is outside of the scope of this article, however).

			=== Gnus ===

			Gnus is one of the MUAs built into GNU Emacs. Gnus is very powerful and flexible, and comes with several "backend"s out of the box for reading newsgroups, email, RSS feeds, and more. Over the years people have written many other backends for it as well.

			To get started using Gnus for reading your CSC mail over IMAPS, you can start with the following simple configuration based on Gnus's <code>nnimap</code> backend:

			<nowiki>
			(setq mail-user-agent 'gnus-user-agent
			read-mail-command 'gnus
			gnus-select-method '(nnnil "")
			gnus-secondary-select-methods
			'((nnimap "csc"
			(nnimap-stream tls)
			(nnimap-address "mail.csclub.uwaterloo.ca")
			(nnimap-user "abandali"))))</nowiki>

			The <code>gnus-secondary-select-methods</code> variable set above is the most important bit.

			For reference sake, here's how we can do client-side mail splitting in Gnus: say we want to move all messages with a <code>X-Spam-Flag</code> header of <code>YES</code> to the Junk folder; here's how we tell Gnus to do that:

			<nowiki>
			(setq gnus-secondary-select-methods
			'((nnimap "csc"
			(nnimap-stream tls)
			(nnimap-address "mail.csclub.uwaterloo.ca")
			(nnimap-user "abandali")
			(nnimap-inbox "INBOX")
			(nnimap-split-methods 'nnimap-split-fancy)
			(nnimap-split-fancy
			(\|
			;; move spam to Junk
			("X-Spam-Flag" "YES" "Junk")
			;; catch-all; leave everything else in inbox
			"INBOX")))))</nowiki>

			Gnus has a plethora of useful and complex features, and one cat get very fancy with it. But that is left as an exercise for the [https://www.gnu.org/software/emacs/manual/gnus.html interested reader]. :-)

	== Spamfiltering ==		== Spamfiltering ==

Merenber: /* Mail User Agents */

2021-04-23T23:43:28Z

Mail User Agents

@@ Line 53: / Line 53: @@
 If you had an existing Mail account, you will need to click on the 'Mailboxes' button to see your CSC account. There will be a dropdown
 button beside 'Inboxes' on the left hand side where you can toggle between different inboxes.
 === Gmail (SMTP Relay) ===

Merenber: /* Gmail (SMTP Relay) */

2021-04-23T23:02:59Z

Gmail (SMTP Relay)

← Older revision		Revision as of 18:02, 23 April 2021
Line 63:		Line 63:
	Fill in your real name and CSC email address (should be watiam_id@csclub.uwaterloo.ca). I would suggest unchecking the 'Treat as an alias'		Fill in your real name and CSC email address (should be watiam_id@csclub.uwaterloo.ca). I would suggest unchecking the 'Treat as an alias'
	box unless you want your CSC and Gmail addresses to be treated the same. See more info [https://support.google.com/a/answer/1710338 here].		box unless you want your CSC and Gmail addresses to be treated the same. See more info [https://support.google.com/a/answer/1710338 here].
	Note that it is still possible to receive CSC messages in your Gmail inbox even if this box is unchecked (see notes below).

	[[File:Gmail_add_another_email_address_you_own.png\|600px]]		[[File:Gmail_add_another_email_address_you_own.png\|600px]]