#28038 [Com]: Sent incorrect RCPT TO commands to SMTP server

ID: 28038 Comment by: business at ziu dot de Reported By: jordi at jcanals dot net Status: Open Bug Type: Mail related Operating System: win32 PHP Version: 5CVS, 4CVS (2006-01-06) (cvs) New Comment: This bug is now open since THREE YEARS. And still the version of today (5.2.1) can not talk to SMTP servers as it should do. This can not be so complicated to fix. Previous Comments: ------------------------------------------------------------------------ [2006-04-14 11:55:21] sniper@php.net See also bug #37073 ------------------------------------------------------------------------ [2006-01-06 03:17:07] sniper@php.net The case reported in bug #35013 should be fixed now in CVS. (the others are NOT!) ------------------------------------------------------------------------ [2005-11-10 15:57:04] Ruben at e-builds dot com The sames happens when using mail() with the 'From' part of the extra headers. php uses this Header From part (and others for RPath etc..) for the "MAIL FROM" address in the SMTP protocol, at least if you didn't specify the sendmail_from setting in php.ini. But for one reason or another, php (I thínk it's php) wraps this part in "<" and ">" again! The workaround is not to use the special format -User <xxx@yy.zzz>-, but just the e-mail address "xxx@yyy.zzz". Of course then php scripters who like a professional approach and want to use this special format, ..well..they can't, at least not per php script. I use a Domino SMTP server on Win32. P.S. I saw several bugs of the same kind allover. Some are even wrongly closed, I presume. ------------------------------------------------------------------------ [2005-11-02 00:05:27] php-louis at steelbytes dot com can we at least just implement stripping of leading and trailing white space on what is extracted from the headers? (as that'll fix 35013). ------------------------------------------------------------------------ [2005-11-01 11:37:04] sniper@php.net See also bug #35013, one more way how headers are parsed wrong. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/28038 -- Edit this bug report at http://bugs.php.net/?id=28038&edit=1