Re: LuaSockets - smtp header problems

[Graham Henstridge <graham@...>]

Hi

As usual - self-induced problems!

Yes, the smtp.lua module is case sensitive on *content-type:* which
if not assigned, is loaded with an inappropriate default.  
*Content_Type:*
is treated as a separate user added header. Problem was easily
solved, thank you.

Problem 2. was less obvious. We supplied a value to *from*
in smtp.send call as per manual example. However it is also required
as a separately defined header (which is in the multipart example on
closer inspection). No doubt there are good reasons for this.

Thank you for the speedy assistance.

Graham Henstridge
Email: graham@capgo.com, Web: www.capgo.com


On 10/03/2007, at 3:38 AM, Diego Nehab wrote:


> Hi,
>
>
> > While not show stoppers, any help resolving problems greatly
> > appreciated.
>
> Can you send a tiny sample that causes the problem? I can
> debug it. These problems should not happen by design. :) So
> one of us is doing something wrong.
>
> Regards,
> Diego.


On 10/03/2007, at 1:02 AM, David Burgess wrote:

> smtp.lua provides some defaults and keeps a case senitive table of
> headers.
>
> This is why you get two content-types.
>
> No idea about the from:
>
> check the smtp.lua code.
>
> On 3/10/07, Graham Henstridge <graham@capgo.com> wrote:
> > Hi all
> >
> > For us LuaSocket 2.0.1 is working really well except for two smtp
> > header issues:
> >
> > 1. When including attachments in an email, LuaSockets inserts the
> > follow headers into the attachment part:
> >         Content-Transfer-Encoding: base64
> >         Content-Disposition: attachment; filename="vibration.png"
> >         Content-Type: image/png; name="vibration.png"
> >         content-type: text/plain; charset="iso-8859-1"
> > The doubling up of the Content-Type (with different cases)
> > cause problems with MIME types on some email clients because
> > the second occurrence is incorrect. Any ideas why this might happen?
> >
> > 2. The original "From:" header as we defined it (same as Reply-To:)
> > it is
> > missing in received email (but Reply-To is there). The ISP has
> > inserted a "From:" header, very different to ours. Emails sent via
> > standard program do not experience the substitution. Where are we
> > likely to be going wrong?
> >
> > While not show stoppers, any help resolving problems greatly
> > appreciated.
> >
> > Graham Henstridge
> > Email: graham@capgo.com