; >> I'm certainly interested in maintaining and developing Email Perl modules.
> >>
> >> I'll also talk about "Email with Perl" at the French Perl Workshop (slides
> >> in progress:
> >> https://www.linuxia.de/talks/fpw2019/perlmail-en-b
On Thursday 16 May 2019 10:15:27 Stefan Hornburg (Racke) wrote:
> On 5/16/19 10:03 AM, p...@cpan.org wrote:
> > On Wednesday 15 May 2019 15:19:10 Marc Chantreux wrote:
> >> hello people,
> >>
> >>> I think now it is good time for starting process of takeover of Email
> >>> modules until those peopl
On Wednesday 15 May 2019 15:19:10 Marc Chantreux wrote:
> hello people,
>
> > I think now it is good time for starting process of takeover of Email
> > modules until those people who were interested in development would not
> > loose they interested just because of silence and inactivity of
> > ma
On Thursday 17 January 2019 12:25:04 p...@cpan.org wrote:
> Hi Ricardo!
>
> On Monday 25 June 2018 08:31:08 Ricardo Signes wrote:
> > So: you can wait for me to have more time, or people with some vested
> > interest can agree to step up to do more in general.
>
> I'm really disappointed as you
Hi Ricardo!
On Monday 25 June 2018 08:31:08 Ricardo Signes wrote:
> So: you can wait for me to have more time, or people with some vested
> interest can agree to step up to do more in general.
I'm really disappointed as you have not wrote anything about this topic
as people are already there...
On Monday 25 June 2018 08:31:08 Ricardo Signes wrote:
> * p...@cpan.org [2018-06-25T05:08:32]
> > So what is status of Email::* modules? Does silence now mean that
> > modules are abandoned / unmaintained? I guess so.
>
> You are mistaken.
>
> The answer is the same as every other time you have a
On Thursday 09 August 2018 15:34:27 p...@cpan.org wrote:
> On Thursday 28 June 2018 13:03:58 p...@cpan.org wrote:
> > On Monday 25 June 2018 08:31:08 Ricardo Signes wrote:
> > > * p...@cpan.org [2018-06-25T05:08:32]
> > > > So what is status of Email::* modules? Does silence now mean that
> > > > m
On Monday 25 June 2018 08:31:08 Ricardo Signes wrote:
> If we had three or four people who committed to create a better sense of group
> responsibility, maybe we'd see more progress.
...
> So: you can wait for me to have more time, or people with some vested
> interest can agree to step up to do m
On Thursday 28 June 2018 13:03:58 p...@cpan.org wrote:
> On Monday 25 June 2018 08:31:08 Ricardo Signes wrote:
> > * p...@cpan.org [2018-06-25T05:08:32]
> > > So what is status of Email::* modules? Does silence now mean that
> > > modules are abandoned / unmaintained? I guess so.
> >
> > You are m
On Monday 25 June 2018 08:31:08 Ricardo Signes wrote:
> * p...@cpan.org [2018-06-25T05:08:32]
> > So what is status of Email::* modules? Does silence now mean that
> > modules are abandoned / unmaintained? I guess so.
>
> You are mistaken.
>
> The answer is the same as every other time you have a
Hi! I would like to ask: What is the state of the perl Email::* modules?
Currently there are lot of open pull request without review, some of
there more then year. Who is the maintainer or supporter of Email::*
modules? Currently, rjbs as primary person does not respond to emails.
For Email::MIME
Hi! Following trivial input can be used to DoS Email::Address module
when is used by server application to parse From or To email headers:
$ perl -MEmail::Address -E 'Email::Address->parse("\f" x 30)'
Yes, it is just 30 form-fields characters.
Because Ricardo as Email::Address maintainer had not
ub
> > > https://github.com/pali/Email-Address-XS (branch master).
> > >
> > > Can you test if everything is OK now in master branch?
> >
> > Yep, tested commit b4bec06cbccd0a7e16ed55e3c34076112228a4ea
> > and my original script behaves as expected. Th
On Thursday 24 May 2018 05:28:27 Eric Wong wrote:
> p...@cpan.org wrote:
> > Anyway, Now I pushed more changes related to formatting and parsing
> > email addresses into Email::Address::XS git repository at github
> > https://github.com/pali/Email-Address-XS (branch master).
problems, please let me know.
> >
> > Thanks for report!
>
> Will do, thanks for catching this. I guess this list covers
> everything in Email::*, anyways?
E.g. Email::Stuffer uses Email::MIME. So transitively - yes.
Anyway, Now I pushed more changes related to formatting and parsing
email addresses into Email::Address::XS git repository at github
https://github.com/pali/Email-Address-XS (branch master).
Can you test if everything is OK now in master branch?
Hi!
On Friday 11 May 2018 18:52:13 Eric Wong wrote:
> Hello, I noticed a behavior change somewhere in the Email::MIME
> stack when header_str_set is passed a string with a single-quote
> (') character in it.
So you mean that input header
"Quoted N'Ame"
is changed to
"Quoted N\'Ame"
On Thursday 08 February 2018 15:02:28 p...@cpan.org wrote:
> On Friday 02 February 2018 11:55:28 p...@cpan.org wrote:
> > On Wednesday 29 November 2017 10:46:46 p...@cpan.org wrote:
> > > On Monday 27 November 2017 10:24:51 Ricardo Signes wrote:
> > > > * p...@cpan.org [2017-11-24T08:08:28]
> > > >
On Friday 02 February 2018 11:55:28 p...@cpan.org wrote:
> On Wednesday 29 November 2017 10:46:46 p...@cpan.org wrote:
> > On Monday 27 November 2017 10:24:51 Ricardo Signes wrote:
> > > * p...@cpan.org [2017-11-24T08:08:28]
> > > > There is a big silence so I do not know if Email::* modules are go
On Wednesday 29 November 2017 10:46:46 p...@cpan.org wrote:
> On Monday 27 November 2017 10:24:51 Ricardo Signes wrote:
> > * p...@cpan.org [2017-11-24T08:08:28]
> > > There is a big silence so I do not know if Email::* modules are going to
> > > be
> > > unmaintained or if there is planned some a
On Monday 27 November 2017 10:24:51 Ricardo Signes wrote:
> * p...@cpan.org [2017-11-24T08:08:28]
> > There is a big silence so I do not know if Email::* modules are going to be
> > unmaintained or if there is planned some activity. Thanks!
>
> I do plan to work through these. The situation rough
Hi! There are opened lot of pull requests for perl Email::* modules,
some of them fixes reported bugs. Can somebody look & review my opened
pull requests? I would like to know if there are some problems with them
and they needs to be reworked or if they can be merged and released a
new version of E
On Tuesday 14 February 2017 21:26:34 p...@cpan.org wrote:
> On Saturday 28 January 2017 21:48:55 Ricardo Signes wrote:
> > * p...@cpan.org [2017-01-14T15:32:57]
> >
> > > So lets move. This is implemented in my pull request:
> > > https://github.com/rjbs/Email-MIME/pull/35
> >
> > Done!
>
> I ha
On Monday 23 May 2016 19:05:39 p...@cpan.org wrote:
> Hello!
>
> I created new perl module Email::Address::XS for parsing and formatting
> email groups or addresses. Parser is borrowed from dovecot and that part
> implemented in C/XS.
>
> Source code is currently at:
>
On Saturday 28 January 2017 21:48:55 Ricardo Signes wrote:
> * p...@cpan.org [2017-01-14T15:32:57]
>
> > So lets move. This is implemented in my pull request:
> > https://github.com/rjbs/Email-MIME/pull/35
>
> Done!
I have there open question about header_to_class_map. Can you look at it?
On Saturday 14 January 2017 21:32:57 p...@cpan.org wrote:
> On Sunday 04 September 2016 00:24:56 Ricardo Signes wrote:
> > If we never *store* objects, but only produce them as requested, then
> > I think the total needed changes are -- but I'm sure I'll miss
> > things -- as follows:
> >
> > * al
On Sunday 04 September 2016 00:24:56 Ricardo Signes wrote:
> If we never *store* objects, but only produce them as requested, then
> I think the total needed changes are -- but I'm sure I'll miss
> things -- as follows:
>
> * allow header_str and header args to Email::MIME->create to include
> o
On Sunday 04 September 2016 00:24:56 Ricardo Signes wrote:
> If we never *store* objects, but only produce them as requested, then
> I think the total needed changes are -- but I'm sure I'll miss
> things -- as follows:
>
> * allow header_str and header args to Email::MIME->create to include
> o
On Monday 05 September 2016 10:25:11 p...@cpan.org wrote:
> On Saturday 03 September 2016 18:24:56 Ricardo Signes wrote:
> > The Email::MIME changes look like they could be broken up into
> > several PRs, some of which would be obviously good to apply
> > immediately, like removals of dead code and
On Wednesday 28 September 2016 15:29:28 Ricardo Signes wrote:
> * p...@cpan.org [2016-09-18T11:40:53]
>
> > Currently passing string values of From/To/Cc/Bcc/... headers into
> > header_str() method is broken in Email::MIME. That is because
> > Email::MIME currently uses Email::Address for generat
On Sunday 18 September 2016 17:26:11 Ricardo Signes wrote:
> * p...@cpan.org [2016-09-17T19:05:51]
>
> > $class->from_mime_string() will take raw MIME encoded string and
> > returns new object of $class (which will have decoded string
> > parts) $object->as_mime_string() will convert (Unicode) $ob
On Saturday 17 September 2016 00:37:40 Ricardo Signes wrote:
> * p...@cpan.org [2016-09-12T03:26:52]
>
> > And as I wrote if Email::MIME is not good place, then what about
> > other modules like Email::MIME::Header::Address (or invent other
> > name) which will use Address parse/format functions a
On Sunday 11 September 2016 18:58:42 Ricardo Signes wrote:
> * p...@cpan.org [2016-09-05T04:25:11]
> > I do not want to add ->as_mime_header (or other function) which will do
> > MIME encoding/decoding into Email::Address::XS. That module is for
> > formating and parsing email addresses headers, no
On Saturday 03 September 2016 18:24:56 Ricardo Signes wrote:
> > Look at my proposal just for first version and lets change parts which
> > are not OK for you. I do not believe that everything is totally wrong.
>
> Okay!
>
> First, I think we should just leave Email::Simple alone. In general, I
On Wednesday 24 August 2016 22:55:05 Ricardo Signes wrote:
> * p...@cpan.org [2016-08-23T03:56:24]
> > > > Also it must be possible to get either named groups from Original-Cc
> > > > header or only list of addresses. And I think with your proposal API it
> > > > is not possible. You would need t
On Monday 22 August 2016 22:34:39 Ricardo Signes wrote:
> * p...@cpan.org [2016-08-20T06:01:16]
> > Email::MIME is module which automatically do any MIME encoding/decoding
> > without user interaction, so that decoding must be done automatically
> > and without such "upgrade" function.
>
> So do
On Monday 22 August 2016 22:26:09 Ricardo Signes wrote:
> Here's a verbose form:
>
> # Get an email.
> my $email = get_some_email_mime();
>
> # Get the header -- the (unfolded) raw bytes.
> my $cc_hdr = $email->header_raw('Original-CC');
>
> # parse it into an object
> my $cc_obj
object
representation of list of Email::Address::XS objects with parse() and
format() methods.
Next I added support for Email::Address::List::XS objects into
Email::Simple and Email::MIME modules.
All source code is available at:
https://github.com/pali/Email-Address-XS/tree/list
https
On Thursday 18 August 2016 23:35:10 p...@cpan.org wrote:
> On Thursday 18 August 2016 23:21:28 Ricardo Signes wrote:
> > > If I create Email::MIME object from input string, I would like to
> > > get:
> > >
> > > 1) Raw (ASCII) string representation of To: field
> > >
> > > 2) Unicode string repre
On Thursday 18 August 2016 23:21:28 Ricardo Signes wrote:
> > If I create Email::MIME object from input string, I would like to
> > get:
> >
> > 1) Raw (ASCII) string representation of To: field
> >
> > 2) Unicode string representation of To: field
> >
> > 3) List of Email::Address::XS objects w
On Wednesday 03 August 2016 00:36:11 Ricardo Signes wrote:
> * p...@cpan.org [2016-08-02T17:03:07]
>
> > I can imagine, that people could be confused about header_str
> > meaning. It has suffix _str and I would expect it needs (Unicode)
> > string, not object... Name "header" is better as it does
On Tuesday 02 August 2016 01:00:02 Ricardo Signes wrote:
> * p...@cpan.org [2016-07-12T11:43:02]
>
> > On Monday 04 July 2016 01:52:41 Ricardo Signes wrote:
> > > I'd stick to header_str, I think, but I'm not sure. At any rate:
> > > yes.
> >
> > And this is what I do not like... to pass objects
On Monday 04 July 2016 01:52:41 Ricardo Signes wrote:
> * p...@cpan.org [2016-07-03T08:39:22]
>
> > On Friday 01 July 2016 02:51:31 Ricardo Signes wrote:
> > > What if we defined a role (here, just a well-known name) called
> > > Email::MIME::Header::Value, which is used to signal that a
> > > par
On Friday 01 July 2016 02:51:31 Ricardo Signes wrote:
> My coworkers have returned to the other side of the world! I
> attended YAPC! i had a vacation! I am back.
>
> * p...@cpan.org [2016-06-01T12:44:01]
>
> > On Tuesday 31 May 2016 02:42:48 Ricardo Signes wrote:
> > > * p...@cpan.org [2016-0
On Tuesday 31 May 2016 02:42:48 Ricardo Signes wrote:
> * p...@cpan.org [2016-05-28T16:48:40]
>
> > Basically yes. From caller perspective I want to pass email address
> > object and let Email::MIME to do MIME encoding correctly. Something
> > like this:
> >
> > my $email = Email::MIME->create(
>
On Saturday 28 May 2016 22:33:02 Ricardo Signes wrote:
> > Thanks to named group support I would like to extend Email::MIME
> > module to allow passing directly Email::Address::XS objects, not
> > only string headers to make MIME encoding and decoding from
> > applications easier.
> >
> > What do
Hello!
I created new perl module Email::Address::XS for parsing and formatting
email groups or addresses. Parser is borrowed from dovecot and that part
implemented in C/XS.
Source code is currently at:
https://github.com/pali/Email-Address-XS
Email::Address::XS has backward compatible API with
46 matches
Mail list logo
