Mailing List Archive

I am sure there is, however, AFAIK, this would break the RFC compliance
qmail has. You might just want to try changing the address to
food_bev@remote.com or food_and_deb@remote.com or something similar.

-----Original Message-----
From: Roger Walker [mailto:roger@rope.net]
Sent: Thursday, February 09, 2012 10:11 AM
To: qmail ML
Subject: ampersand "&" in email address

I'm seeing the following problem in the log files (minor changes
to protect the innocent and guilty):

info msg 1966555: bytes 468716 from <Food&Bev@remote.com> qp 27994 uid
220

info msg 1968033: bytes 223 from <food\@local.emailserver.com> qp 28003
uid 730

delivery 934057: deferral:
sh:_bev@remote.com:_command_not_found/Aack,_child_crashed._(#4.3.0)/

So, qmail is separating the message delivery into being from
"food" at the host/domain name of the local qmail server, AND from "bev"
at the actual sender's host/domain name.

It is, essentially, splitting the sender address at the
ampersand "&" and trying to send to the resulting two addresses.

Is there a fix for this so qmail can handle it like any other
email?

Thanks.

Hi Roger,




Am 09.02.2012 um 16:10 schrieb Roger Walker:

> I'm seeing the following problem in the log files (minor changes
> to protect the innocent and guilty):
>
> info msg 1966555: bytes 468716 from <Food&Bev@remote.com> qp 27994
> uid 220
>
> info msg 1968033: bytes 223 from <food\@local.emailserver.com> qp 28003
> uid 730
>
> delivery 934057: deferral:
> sh:_bev@remote.com:_command_not_found/Aack,_child_crashed._(#4.3.0)/
>
> So, qmail is separating the message delivery into being from
> "food" at the host/domain name of the local qmail server, AND from "bev"
> at the actual sender's host/domain name.
>
> It is, essentially, splitting the sender address at the ampersand
> "&" and trying to send to the resulting two addresses.
>

Hm. This is strange.


> Is there a fix for this so qmail can handle it like any other
> email?


I'm not aware, that qmail actually has a problem with '&' in the local part or behaves erratically as you mentioned.

man addresses:


Be wary of the following characters:

$&!#~`'^*|{}

Some users will not know how to feed these characters safely to their mail programs.

Thus, what you see at the final end:


> delivery 934057: deferral:
> sh:_bev@remote.com:_command_not_found/Aack,_child_crashed._(#4.3.0)/

seems to be due to a problem of your mail delivery instruction (.qmail). An '&' here defines a forwarding rule.

I need to investigate this in more detail. Again. you can use qmFind out of my Newanalyse package to check the qmail-send logs.

regards.
--eh.


>
> Thanks.

--
Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: 7E4034BE

On 9 Feb 2012, at 16:56, Robert Wolfe wrote:

> I am sure there is, however, AFAIK, this would break the RFC compliance
> qmail has.

Which RFC? All of 822, 2822 and 5322 say that & is allowed in a local-part. It's true that many servers don't allow it, but that's not the RFC talking.

Marcus
--
Marcus Bointon
Synchromedia Limited: Creators of http://www.smartmessages.net/
UK info@hand CRM solutions
marcus@synchromedia.co.uk | http://www.synchromedia.co.uk/