Talk:Email processing - Revision history

Tsala: /* base64 encoding and MTA case-sensitivity */ reply

2006-02-19T18:32:58Z

base64 encoding and MTA case-sensitivity: reply

← Older revision		Revision as of 18:32, 19 February 2006
Line 11:		Line 11:

	I see that there are base32_encode/decode() functions in lib/base32.php, which should be usable for case-insensitive en/decoding.		I see that there are base32_encode/decode() functions in lib/base32.php, which should be usable for case-insensitive en/decoding.

			:Hi Brian, thanks for your comments. Please could you post details of your problem in the Using Moodle [http://moodle.org/mod/forum/view.php?f=33 General developer forum] to enable discussion about it. --[[User:Helen Foster\|Helen Foster]] 02:32, 20 February 2006 (WST)

Brianking: /* base64 encoding and MTA case-sensitivity */

2006-02-19T17:55:31Z

base64 encoding and MTA case-sensitivity

← Older revision		Revision as of 17:55, 19 February 2006
Line 10:		Line 10:
	Wouldn't it be easier to create email_pack_encode() and email_unpack_decode() functions that do basically the same thing as the base64 encoding/decoding and pack/unpack functions currently being used - with the difference that they don't use any uppercase letters, than to require people to reconfigure their mail servers (which is not always the easiest thing to do!)?		Wouldn't it be easier to create email_pack_encode() and email_unpack_decode() functions that do basically the same thing as the base64 encoding/decoding and pack/unpack functions currently being used - with the difference that they don't use any uppercase letters, than to require people to reconfigure their mail servers (which is not always the easiest thing to do!)?

	I see that there are base32_encode/decode() functions in lib/base32.php.		I see that there are base32_encode/decode() functions in lib/base32.php, which should be usable for case-insensitive en/decoding.

Brianking: /* base64 encoding and MTA case-sensitivity */

2006-02-19T17:53:51Z

base64 encoding and MTA case-sensitivity

← Older revision		Revision as of 17:53, 19 February 2006
Line 8:		Line 8:
	However, I'm running into a problem with it - the MTA (postfix) on our server downcases the username+extension part of the email address. From searching on the internet, I see that this is a pretty common, and even recommended practice for MTAs. This means that replys to emails that go out with a reply to address of, for example: mdl+Bgbk-146913874a6e0fa08c@moodle.domain.ch are received by process_email.php with an $address of mdl+bgbk-146913874a6e0fa08c@moodle.domain.ch. This change of Bg to bg means that the hash doesn't match, and that the module id can not be identified.		However, I'm running into a problem with it - the MTA (postfix) on our server downcases the username+extension part of the email address. From searching on the internet, I see that this is a pretty common, and even recommended practice for MTAs. This means that replys to emails that go out with a reply to address of, for example: mdl+Bgbk-146913874a6e0fa08c@moodle.domain.ch are received by process_email.php with an $address of mdl+bgbk-146913874a6e0fa08c@moodle.domain.ch. This change of Bg to bg means that the hash doesn't match, and that the module id can not be identified.

	Wouldn't it be easier to create email_pack_encode() and email_unpack_decode() functions that do basically the same thing as the base64 encoding/decoding and pack/unpack functions currently being used - with the difference that they don't use any uppercase letters, than to require people to reconfigure their mail servers (which is not always the easiest thing to do!)?		Wouldn't it be easier to create email_pack_encode() and email_unpack_decode() functions that do basically the same thing as the base64 encoding/decoding and pack/unpack functions currently being used - with the difference that they don't use any uppercase letters, than to require people to reconfigure their mail servers (which is not always the easiest thing to do!)?

			I see that there are base32_encode/decode() functions in lib/base32.php.

Brianking: base64 encoding and MTA case-sensitivity

2006-02-19T17:41:59Z

base64 encoding and MTA case-sensitivity

← Older revision		Revision as of 17:41, 19 February 2006
Line 1:		Line 1:
	== References ==		== References ==
	*[http://moodle.org/mod/wiki/view.php?id=2935&page=Email+Processing+setup Developer wiki: Email processing] -- [[User:Helen\|Helen]] 16 December 2005 20:50 (WST)		*[http://moodle.org/mod/wiki/view.php?id=2935&page=Email+Processing+setup Developer wiki: Email processing] -- [[User:Helen\|Helen]] 16 December 2005 20:50 (WST)

			== base64 encoding and MTA case-sensitivity ==

			This is a great feature!

			However, I'm running into a problem with it - the MTA (postfix) on our server downcases the username+extension part of the email address. From searching on the internet, I see that this is a pretty common, and even recommended practice for MTAs. This means that replys to emails that go out with a reply to address of, for example: mdl+Bgbk-146913874a6e0fa08c@moodle.domain.ch are received by process_email.php with an $address of mdl+bgbk-146913874a6e0fa08c@moodle.domain.ch. This change of Bg to bg means that the hash doesn't match, and that the module id can not be identified.

			Wouldn't it be easier to create email_pack_encode() and email_unpack_decode() functions that do basically the same thing as the base64 encoding/decoding and pack/unpack functions currently being used - with the difference that they don't use any uppercase letters, than to require people to reconfigure their mail servers (which is not always the easiest thing to do!)?

Helen: references

2005-12-16T20:50:15Z

references

New page

== References ==
*[http://moodle.org/mod/wiki/view.php?id=2935&page=Email+Processing+setup Developer wiki: Email processing] -- [[User:Helen|Helen]] 16 December 2005 20:50 (WST)