can't send to addresses w/ in them.
One of our customers is upset because he can't email his brother at his bigfoot address. The address has an ampersand in the username portion eg; DNB[EMAIL PROTECTED] which qmail (1.03) apparently translates to "dnb^[EMAIL PROTECTED]" and the message is returned as undeliverable. Of course this customer has to point out that the sister with the MSN account can send to it, with no problems. DOH! I'm not necessarily trying to correct or work around the problem, but I wish I had an RFC I could quote that explains why this isn't working, and why MSN shouldn't deliver it either, except it is their nature to ignore/bend/break established protocols and procedures. Any insight would be greatly apreciated. TIA Duane L - [EMAIL PROTECTED] -
Re: can't send to addresses w/ in them.
On Thu, Sep 21, 2000 at 09:43:57AM -0700, Duane L. wrote: One of our customers is upset because he can't email his brother at his bigfoot address. The address has an ampersand in the username portion eg; DNB[EMAIL PROTECTED] which qmail (1.03) apparently translates to "dnb^[EMAIL PROTECTED]" and I see no evidence of that. Can you show us the log entries? Try: qmail-inject 'DNB[EMAIL PROTECTED]' and show us your logs as a consequence. Regards. the message is returned as undeliverable. Of course this customer has to point out that the sister with the MSN account can send to it, with no problems. DOH! I'm not necessarily trying to correct or work around the problem, but I wish I had an RFC I could quote that explains why this isn't working, and why MSN shouldn't deliver it either, except it is their nature to ignore/bend/break established protocols and procedures. Any insight would be greatly apreciated. TIA Duane L - [EMAIL PROTECTED] -
Re: can't send to addresses w/ in them.
On Thu, Sep 21, 2000 at 09:43:57AM -0700, Duane L. wrote: One of our customers is upset because he can't email his brother at his bigfoot address. The address has an ampersand in the username portion eg; DNB[EMAIL PROTECTED] which qmail (1.03) apparently translates to "dnb^[EMAIL PROTECTED]" and the message is returned as undeliverable. Of course this customer has to point out that the sister with the MSN account can send to it, with no problems. DOH! I know for a fact that qmail can send to addresses with a in them because I once had a mailing list that sent them unquoted, backgrounded itself, resent them because it did not complete, ad infinitem until I caught it and fixed the quoting. In a nutshell the **shell** was the issue, not qmail. cfm I'm not necessarily trying to correct or work around the problem, but I wish I had an RFC I could quote that explains why this isn't working, and why MSN shouldn't deliver it either, except it is their nature to ignore/bend/break established protocols and procedures. Any insight would be greatly apreciated. TIA Duane L - [EMAIL PROTECTED] - -- Christopher F. Miller, Publisher [EMAIL PROTECTED] MaineStreet Communications, Inc 208 Portland Road, Gray, ME 04039 1.207.657.5078 http://www.maine.com/ Database publishing, e-commerce, office/internet integration, Debian linux.
Re: can't send to addresses w/ in them.
On Thu, 21 Sep 2000, Duane L. wrote: One of our customers is upset because he can't email his brother at his bigfoot address. The address has an ampersand in the username portion eg; DNB[EMAIL PROTECTED] which qmail (1.03) apparently translates to "dnb^[EMAIL PROTECTED]" and This looks like it is passing through the Obtuse smtpd program. That will escape strange characters (it's own definition of strange) with the hex code. As to where the obtuse smtpd is in the chain of mail from your customer to his brother remains to be seen. -- Regards Peter -- Peter Samuel[EMAIL PROTECTED] http://www.e-smith.org (development)http://www.e-smith.com (corporate) Phone: +1 613 368 4398 Fax: +1 613 564 7739 e-smith, inc. 1500-150 Metcalfe St, Ottawa, ON K2P 1P1 Canada "If you kill all your unhappy customers, you'll only have happy ones left"
Re: can't send to addresses w/ in them.
Well apparently the problem is with Outlook Express (surprise surprise) Using Elm or Pine delivers the message just fine. My apoligies for not trying a different mail client before posting my question. Thanks though, Duane On Thu, 21 Sep 2000 [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2000 at 09:43:57AM -0700, Duane L. wrote: One of our customers is upset because he can't email his brother at his bigfoot address. The address has an ampersand in the username portion eg; DNB[EMAIL PROTECTED] which qmail (1.03) apparently translates to "dnb^[EMAIL PROTECTED]" and I see no evidence of that. Can you show us the log entries? Try: qmail-inject 'DNB[EMAIL PROTECTED]' and show us your logs as a consequence. Regards. the message is returned as undeliverable. Of course this customer has to point out that the sister with the MSN account can send to it, with no problems. DOH! I'm not necessarily trying to correct or work around the problem, but I wish I had an RFC I could quote that explains why this isn't working, and why MSN shouldn't deliver it either, except it is their nature to ignore/bend/break established protocols and procedures. Any insight would be greatly apreciated. TIA Duane L - [EMAIL PROTECTED] - Duane L - [EMAIL PROTECTED] -
