On Thu, Jul 06, 2006 at 01:52:23PM -0500, Karen J. Cravens wrote:
> I deleted the message where you mentioned it, but... is
> Email::LocalDelivery really still a going concern? Shouldn't it be (or
> isn't it already) rolled into Email::Send? Or am I completely
> misremembering (I stopped using
On Fri, Jul 07, 2006 at 03:01:39PM +0100, Simon Flack wrote:
> Can we make it easier for end-users by standardising the set of mailer
> args, at the cost of breaking backwards compatability & adding a little
> complexity to the mailers themselves?
I really like the idea of standardizing on mailer
On Wed, Feb 14, 2007 at 05:34:12PM -, Karen J. Cravens wrote:
> my $delivery_agent = Email::LocalDelivery->deliver($message->as_string,
> ("/blahblah/blah.mbx"));
>
> comes unglued [...]
>
> Is this just me, or should I throw a report at rt?
If you can be more specific than "comes unglued" a
On Wed, Feb 21, 2007 at 12:07:06AM -0500, Dave O'Neill wrote:
> On Tue, Feb 20, 2007 at 07:07:43PM -0500, Ricardo SIGNES wrote:
> > Because the return value of a successful delivery always has a known
> > interface
> > (currently I'm calling it Email::Sender::Success, but something more like
> > E
On Wed, Feb 21, 2007 at 10:08:50AM -0500, Ricardo SIGNES wrote:
> I'm not sure. I also don't like Email::Mailer, for the same reason.
> Email::Delivery::Agent would be okay, but is pretty long. Then again, if most
> people use the simplified interface (like I do, in effect, at work) it may not
>
On Wed, Feb 21, 2007 at 11:18:10AM -0500, Ricardo SIGNES wrote:
> I am not sure that this matters! Why is Email::LocalDelivery not implemented
> in terms of Email::Send? Lack of vision I say! :)
>
> You generate an email and send it to your MTA destined for me. You use
> Email::Delivery::Agent:
On Mon, Mar 12, 2007 at 10:29:40PM -0400, [EMAIL PROTECTED] wrote:
> Is the root cause the line
> $headers[-1] .= $headers[-1] ? " $_" : $_;
> in the code? Ideas?
Can you please provide a failing test? It's hard to tell what the root cause is
without at least the original message, and a complete
On Thu, Apr 19, 2007 at 10:42:46AM -0500, Karen Cravens wrote:
> If it's direct filesystem access, you can look at Email::Folder for other
> access methods. If it's IMAP, I don't know that PEP is the route to go.
> IMAP definitely gets beyond Simple - maybe someone will jump up to correct
> me,
We do a lot of manipulation of MIME stuff. I get tired of taking apart MIME
emails, especially if I have to later get at some sub-part of a message. I
wrote an ad hoc syntax for that which was terrible.
So today I replaced my terrible stuff with XPath[1]. Email-MIME-XPath pretends
that a MIME m
On Fri, May 11, 2007 at 03:25:57PM +0200, Matijs van Zuijlen wrote:
> I am the author of msgconvert.pl (http://www.matijs.net/software/msgconv/),
> a tool to convert Microsoft Outlook's .msg files into message/rfc822. I'm
> in the process of making this tool into a module.
This sounds really usefu
On Wed, Jul 18, 2007 at 03:52:55PM -0400, Ricardo SIGNES wrote:
> I mean, do we want to use Moose? It always comes up, half in jest. I don't
> know what its performance or maintenance impact are. I don't think it adds
> *that* many prerequisites, but I haven't looked up the whole tree.
Specifi
On Wed, Jul 18, 2007 at 03:09:21PM -0500, Smith Warren - wasmit wrote:
> Just remember, if you ever want your module to become part of the perl
> core distribution, it must rely solely upon other core modules.
I can't think of anything in Email:: that belongs in core, offhand:
http://use.perl.o
On Tue, Jul 24, 2007 at 12:13:53AM -0400, Ricardo SIGNES wrote:
> The moniker is either '::Foo' to get Email::Exception::Foo or 'Bar::Baz' to
> get
> just that. I don't think I like this, but it's where I started. The exact
> opposite might be better.
I have a mild preference for 'Foo' expandin
On Tue, Jul 24, 2007 at 12:22:57AM -0400, Ricardo SIGNES wrote:
> How many people are going to shoot themselves in the foot by re-sending to all
> recipients after a PartialFailure? How many would shoot themselves in the
> foot
> by not noticing failed destinations if partial failure was treated
On Tue, Jul 24, 2007 at 07:46:36AM -0400, Dave O'Neill wrote:
> On Tue, Jul 24, 2007 at 07:06:46AM -0400, Hans Dieter Pearcey wrote:
>
> > I have a mild preference for 'Foo' expanding to 'Email::Exception::Foo' and
> > '+Bar::Baz' having the
On Tue, Jul 24, 2007 at 10:19:35PM -0400, Ricardo SIGNES wrote:
> ->throw('Fully::Qualified::Name');
> ->throw('-Under::EE');
>
> (a) hypen means "tacked on to previous thing" like "hyper -active and
> -trophic"
> (b) it lets you skip quoting
> (c) which means less typing for the common case
On Wed, Sep 19, 2007 at 09:44:28AM -0500, Karen Cravens wrote:
> WY>But that's a totally different matter from how I understood the original
> WY>topic (let's create a perl based MLM just because).
>
> Yes. And perhaps a bit off-topic for this list.
Close enough, I think. It's a really interesti
On Sat, Sep 29, 2007 at 06:17:44PM +0200, Matijs van Zuijlen wrote:
> On Fri, Jun 15, 2007 at 12:06:27PM -0700, Robert G. Werner wrote:
> > Matijs van Zuijlen wrote:
> > [snip]
> >> Maybe Email::Outlook::Message, leaving open the option of adding
> >> Email::Outlook::Archive in the future, for acce
On Thu, Apr 17, 2008 at 09:25:31AM -0400, Ricardo SIGNES wrote:
> > - send an email requiring a reply
>
> The common practice these days is to send an email that has a link in it.
> Sending one that also accepts a reply is just bonus.
Make sure that you use the header From or Reply-To, though, no
On Wed, Jun 25, 2008 at 10:38:09AM -0400, Ricardo SIGNES wrote:
> You want something like:
>
> my $root = Email::MIME->new($message_text);
> my ($html_part) = grep { $_->content_type =~ m{^text/html} }
> $root->subparts;
Or:
use Email::MIME::XPath;
my $html_part = $root->xpath_findnode(
Excerpts from Justin Skazat's message of Tue Jan 05 17:32:25 -0500 2010:
> > But that can already easily be done, I can just put
> >
> > From: You
> >
> > in my email headers.
>
> OK - what should I do about that? What's the general wisdom to help thwart
> that? Use the Sender: header? Both? S
Excerpts from Karen Cravens's message of Wed Jan 06 11:29:15 -0500 2010:
> Depends on what you mean by access control.
I mean what the OP said he was using it for: running various commands when
messages are received.
> You'd still want E::A to parse it properly, if only so you can test for
> "If
Excerpts from Wedge Martin's message of Tue Jan 05 17:06:48 -0500 2010:
> I also ran into another weird issue, which turned out to be the
> MIME::Base64 encoding data into base64 with .. and this baffles me ..
> random carriage returns within the base64 data string...
MIME::Base64 wraps its output
23 matches
Mail list logo
