htmlpurifier - Webmail: HTML headers -

-

html e-mails complex beast. deciding send (as sender) , display (as recipient) tricky , potentially dangerous.

on recipient side of things, have webmail , have regular e-mail clients. purposes, consider 'webmail' displays html e-mail part of in html, , regular e-mail clients displays html e-mail in different context (e.g. os- , program-specific gui).

what should webmail html headers (<head>, <title>, <meta>, ...) in e-mail?
there spec somewhere, actual standard or de-facto-standard?

my motivation asking use html purifier sanitise our html , if core.collecterrors feature reports changes, they're reported. 'reported' both necessary... , frustrating. strip out of reported errors insignificant our purposes, html headers mark massive hurdle:

someone potentially use <link> in e-mail, strip out. (html purifier intended html fragments, not full documents)

the desire use things <link> in html e-mails seems exist, , there plenty of e-mail clients send <meta>-tags in html header (e.g. outlook), how things handled in wild? safe strip them out silently (which our purposes denotes 'non-breaking change') , lay proverbial blame on sending party if does break? reasonable? has ever decided in 1 or other way? google-fu weak. :(

i doubt there spec anywhere specifies how html emails should embedded webmail clients. it's question of achieving parity existing webmail providers provide ability view html email. suspect stylesheets notable exception, suspect html mailers support heavy styling constrained in can , cannot do, given how webmail things may handle them. i'd suggest doing experiments, , consulting source code of open-source webmail systems squirrelmail.

if worried information loss, 1 thing many clients allow download original html, offline viewing. of course, tends pretty atrocious, don't know why that.


Comments

Post a Comment

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

-
what’s difference between $_server['path_info'] , $_server['orig_path_info'] ? how use them? when run print_r($_server) , path_info , orig_path_info not present in array. why not? how can enable them? i have read php manual on them, still don’t understand them. the path_info variable present if invoke php script this: http://www.example.com/phpinfo.php/hello_there it's /hello_there part after .php script. if don't invoke url that, there won't $_server["path_info"] environment variable. the porig_ prefix uncommon. path_info standard cgi-environment variable, , should never prefixed. did read that? (there issues around php3/php4 if invoked php interpreter via cgi-bin/ - hardly has such setups today.) for reference: http://www.ietf.org/rfc/rfc3875
Read more

fortran - Function return type mismatch -

-
i'm attempting recode old c++ program in fortran make use of lapack (i'm aware c++ have lapack++, i'm having lot of trouble installing it, gave up). i didn't have problems compilation, when had variables declared real . when started coding section of program required lapack, found parameters passed dsyev need double precision . tried change double precision (including changing hard coded numbers double precision counterparts, i.e. 0.0 -> 0.0d0) when try compile, following error of functions , subroutines i've written: error: return type mismatch of function <function> @ (1) (real(4)/real(8)) i'm not sure coming from, in program has been changed double precision. for example, i've declared following: double precision :: alpha(3),d(3),zeta1,zeta2 double precision :: a1(3),a2(3),d1(3),d2(3) double precision :: pi pi = 3.14159265359d0 alpha = (/0.109818d0, 0.405771d0, 2.22766d0/) d = (/0.444635d0, 0.535328d0, 0.154329d0 /) 10 i=1,3 ...
Read more

queue - mq_receive: message too long -

-
i implementing communication between 2 processes using queue. problem when call function mq_receive, error: message long. i have done following: struct mq_attr attr; long size = attr.mq_msgsize; .... // initializing queue "/gateway" int rc = mq_receive(gateway, buffer, size, &prio); if print size value, size=1, while when print same size program (got same mechanism), not long integer ( -1217186280 )... how can solve error?....so while size = 1, believe it's right "message long" why 1? p.s. have tried put : int rc = mq_receive(gateway, buffer, sizeof(buffer), &prio); but no result. it seems need read docs more carefully. when call mq_receive should pass size of destination buffer. this size must greater mq_msgsize attribute of queue . in addition, seems have error in queue attributes initialisation makes proper mq_receive call impossible. here standard message queue session: fill mq_attr struct ( doc ): struct mq_a...
Read more