Email encoding problem with attachments
| Project: | Job Posting |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
trludewig posted this is an incorrect issue but I think it deserves its own. I this deployed on a few different servers, one of them being a server with Japanese as its primary language. It is the only one with this error, so I am guessing it has something to do with it. When sending an application I get a mail message similar to:
--1dfb80b7955437366c14836eddef94d4
Content-Type: text/plain; charset=UTF-8; format=flowed;
aadefsd
--1dfb80b7955437366c14836eddef94d4
Content-Type: text/plain;
name="mailOutFile.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="mailOutFile.txt"
SW4gZHJ1cGFsX21haWxfd3JhcHBlcgpJbiBkcnVwYWxfbWFpbF93cmFwcGVyCkluIGRydXBhbF9t
YWlsX3dyYXBwZXIKSW4gZHJ1cGFsX21haWxfd3JhcHBlcgo=
--1dfb80b7955437366c14836eddef94d4--
Any ideas?
#1
Actually I solved my own problem. Emails are sent out using the current user's language, even if the poster of the job is using a different language. Can I suggest the confirmation email be sent out in the language of the job poster's owner, not the current user's?
#2
Interesting. Having not worked much in a multi-lingual setting I hadn't noticed this before and assumed it would make most sense to use the sender's language on the basic principle of not messing with user data unless absolutely necessary. Also, the user object is readily available at the time of submission, whereas the poster's is not so changing this is a little more involved than it might seem at first but something we should probably look at changing in the near future. Thanks for reporting back on this.
#3