[imp] RFC822/PEAR problem ?

[Bjorn Swift]

I have had the same problem with PEAR's Mail.php and RFC822.php and
submitted a bug report on the 17th of February
(http://bugs.php.net/bug.php?id=15590&edit=1). At that time noone seemed to
mind and the report is still marked as "Open". I'm glad someone is running
into similar problems, maybe it will lead to a solution. If you have
anything to add to the bug report, please do.

The problem I've had is that my users tend to put special characters into
the email addresses (ie. ýúíó). The address gets rewritten to <@> and sent
to the local postmaster (using postfix like Lars) without notifying the
sender.

I would like to see this dealt with within IMP. Unfortunately I'm not
familiar enough with IMP's way of dealing with things to write a patch for
this, sorry Chuck ;).

Comments?

Björn Swift

----- Original Message -----
From: "Lars Anderson" <lsa@business.auc.dk>
To: <imp@lists.horde.org>
Sent: Monday, April 22, 2002 2:54 PM
Subject: Re: [imp] RFC822/PEAR problem ?


> On Mon, Apr 22, 2002 at 16:43:06, Marc Villegas wrote:
>
>
> Hi,
>
> I have also seen this problem with postfix, and I found out the following:
>
> If I send email to an invalid adresse, eg.
>
>   example@example.com.
>
> Ie. with a trailing dot.
>
> IMP (via Mail.php and RFC822.php from PEAR) shortens this adress to <@>
>
> This may lead to unwanted actions, For example in postfix, if you do not
> specify  reject_non_fqdn_recipient postfix will accept the mail but see
> it as an empty adress and forward the mail to postmaster.
>
> Maybe it would be better to catch the bad address in IMP.
>
> Regards
> Lars
>