Talk:Email processing: Difference between revisions
Brian King (talk | contribs) (base64 encoding and MTA case-sensitivity) |
Helen Foster (talk | contribs) |
||
(2 intermediate revisions by one other user not shown) | |||
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, 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) |
Latest revision as of 18:32, 19 February 2006
References
- Developer wiki: Email processing -- Helen Foster 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!)?
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 General developer forum to enable discussion about it. --Helen Foster 02:32, 20 February 2006 (WST)