Differences between version 11 and previous revision of WlugMailNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 11 | Last edited on Wednesday, November 3, 2004 4:09:11 pm | by JohnMcPherson | Revert |
Older page: | version 8 | Last edited on Saturday, January 10, 2004 5:09:27 pm | by JohnMcPherson | Revert |
@@ -1,13 +1,23 @@
-Just
a few notes about using the
[WLUG
] mail server
.
+* You can create a file named <tt>.forward</tt> in your home directory (remember, everyone who has a mail account, also has
a [Shell
] account) to have [Email] automatically forwarded to another address. For example after logging in:
+ <verbatim>
+ $ echo my_other_address@verisign.com > ~/
.forward
+ </verbatim>
-* If you're using MozillaMail and [IMAP] to connect through the firewall
to the server you may need to add imap.wlug.org.nz to your "No Proxies for" list (under preferences
/ advanced
/ proxies
). This tells you mailer to connect directly to the server rather than through the proxy.
-* When you log into WebMail you may need to use ''
username''
rather than ''
username@wlug.org.nz''
(this differs from other SquirrelMail setups). The feedback when you make this error
is a little obscure (i.e. several lines of the [PHP] internal error messages and then "
Unknown user or password incorrect."
)
-* Sometimes [Reload
] gives gives an php
error messages. This appears to be related to session TimeOut. The solution is not to use [Reload] but
to check for new mail by clicking on you
inbox.
-* You can create a file named ".forward" in your home directory (remember, everyone who has a mail account, also has a shell account) to have email automatically forwarded to another address. For example after logging in:
- $ echo "my_other_address@verisign.com" > ~/.forward
-* Exim also supports specially formatted .forward files to do limited processing of incoming email, such as save to a certain file, or forward or drop. As currently set up on the WLUG mail server, such filtering is supported. See EximFilter.
-* There is a bug in the WebMail whereby it occasionally forgets who you are (maybe it looses
the cookie?). If this bug were only present in WebMail I'd blame it on WebMail, but it also happens to long-running wiki edits, which suggests that the problem may be something more deep
rooted. Whatever it is, since I
'm current accessing WebMail via systems that meter by the minute (mainly the public library here), __it
's getting very frustrating
to lose long and well writen emails__
. Part of the problem
is that unlike the wiki, WebMail doesn
't store
the text and ask you
to identify yourself
, once it
's forgotten who you are you have to start from the initial login, loosing the text in the process.
+* [Exim] also supports specially formatted <tt>.forward</tt> files to do limited processing of incoming [Email], such as save to a certain file, or forward or drop. As currently set up on the [WLUG] MailServer, such filtering is supported. See EximFilter for hints and examples.
+
+
* If you're using MozillaMail and [IMAP] to connect through the FireWall
to the server you may need to add <tt>
imap.wlug.org.nz</tt>
to your "No Proxies for" list (under Preferences
/Advanced
/Proxies
). This tells you mailer to connect directly to the server rather than through the proxy.
+
+* When you log into WebMail you may need to use <tt>
username</tt>
rather than <tt>
username@wlug.org.nz</tt>
(this differs from other SquirrelMail setups). The feedback when you make this mistake
is a little obscure (i.e. several lines of the [PHP] internal error messages and then <tt>
Unknown user or password incorrect</tt>
.)
+
+* Sometimes reloading produces
[PHP
] error messages. This appears to be related to session TimeOut. The solution is to check for new mail by clicking on your
inbox instead of reloading
.
+
+* There is a bug in the WebMail whereby it occasionally forgets who you are (maybe it loses
the cookie?). If this bug were only present in WebMail I'd blame it on WebMail, but it also happens to long-running wiki edits, which suggests that the problem may be something more deeply
rooted.
+ --
''This seems
to be resolved now..
. I think it
is php
's session handling stuff. We upped
the timeout
to 60 minutes
, and haven't seen problems since
'' -- JohnMcPherson
+
+See also:
+* HoihoDocuments
+* MozillaNotes
+* SquirrelMail
-See also: [HoihoDocuments] [MozillaNotes] and SquirrelMail
----
CategoryMailNotes