]>
Commit | Line | Data |
---|---|---|
3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
2 | <HTML> | |
3 | <HEAD> | |
4 | <TITLE> [IRCServices Coding] suggestion for nickserv | |
5 | </TITLE> | |
6 | <LINK REL="Index" HREF="index.html" > | |
7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20suggestion%20for%20nickserv&In-Reply-To=20020710002516.FNPE29616.out017.verizon.net%40bofh"> | |
8 | <META NAME="robots" CONTENT="index,nofollow"> | |
9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
10 | <LINK REL="Previous" HREF="001067.html"> | |
11 | <LINK REL="Next" HREF="001100.html"> | |
12 | </HEAD> | |
13 | <BODY BGCOLOR="#ffffff"> | |
14 | <H1>[IRCServices Coding] suggestion for nickserv</H1> | |
15 | <B>Aragon Gouveia</B> | |
16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20suggestion%20for%20nickserv&In-Reply-To=20020710002516.FNPE29616.out017.verizon.net%40bofh" | |
17 | TITLE="[IRCServices Coding] suggestion for nickserv">aragon at phat.za.net | |
18 | </A><BR> | |
19 | <I>Tue Jul 9 23:20:21 PDT 2002</I> | |
20 | <P><UL> | |
21 | <LI>Previous message: <A HREF="001067.html">[IRCServices Coding] suggestion for nickserv | |
22 | </A></li> | |
23 | <LI>Next message: <A HREF="001100.html">[IRCServices Coding] suggestion for nickserv | |
24 | </A></li> | |
25 | <LI> <B>Messages sorted by:</B> | |
26 | <a href="date.html#1068">[ date ]</a> | |
27 | <a href="thread.html#1068">[ thread ]</a> | |
28 | <a href="subject.html#1068">[ subject ]</a> | |
29 | <a href="author.html#1068">[ author ]</a> | |
30 | </LI> | |
31 | </UL> | |
32 | <HR> | |
33 | <!--beginarticle--> | |
34 | <PRE>I would imagine that being very difficult to do. For starters, every MTA's | |
35 | error messages aren't the same. And most error messages are too long to | |
36 | simply forward as a memo to a user. Services would have to parse the error | |
37 | message and memo the relevant information to the user. | |
38 | ||
39 | It's the user's responsibility to ensure his email address works. And it's | |
40 | the admins' duty to follow-up on error messages. | |
41 | ||
42 | My opinion atleast :) | |
43 | ||
44 | ||
45 | Regards, | |
46 | Aragon | |
47 | ||
48 | ||
49 | ||
50 | |<i> By <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">RT.Mail at verizon.net</A> <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">RT.Mail at verizon.net</A>> | |
51 | </I>|<i> [ 2002-07-10 02:27 +0200 ] | |
52 | </I>><i> Idea. When nickserv receives a failure and is unable to deliver the | |
53 | </I>><i> auth code to an email address. Have it message that user with a | |
54 | </I>><i> failure notice and allow them to re register it using a valid email.. | |
55 | </I>><i> or something along those lines. Maybe if the get the error twice it | |
56 | </I>><i> could hold it for 24 hours so they could contact an admin to give | |
57 | </I>><i> them a code.... Well something like that... | |
58 | </I>><i> | |
59 | </I>><i> | |
60 | </I>><i> ------------------------------------------------------------------ | |
61 | </I>><i> To unsubscribe or change your subscription options, visit: | |
62 | </I>><i> <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding</A> | |
63 | </I> | |
64 | </PRE> | |
65 | ||
66 | <!--endarticle--> | |
67 | <HR> | |
68 | <P><UL> | |
69 | <!--threads--> | |
70 | <LI>Previous message: <A HREF="001067.html">[IRCServices Coding] suggestion for nickserv | |
71 | </A></li> | |
72 | <LI>Next message: <A HREF="001100.html">[IRCServices Coding] suggestion for nickserv | |
73 | </A></li> | |
74 | <LI> <B>Messages sorted by:</B> | |
75 | <a href="date.html#1068">[ date ]</a> | |
76 | <a href="thread.html#1068">[ thread ]</a> | |
77 | <a href="subject.html#1068">[ subject ]</a> | |
78 | <a href="author.html#1068">[ author ]</a> | |
79 | </LI> | |
80 | </UL> | |
81 | ||
82 | </body></html> |