Hi,
         We have prepared the PS on shifting from PEAR to SwiftMailer.
Please go through and review the PS here (
https://gerrit.wikimedia.org/r/#/c/135290/ ). As the commit message says -
there are some compatibility issues like :-

* Couldn't find an alternative for the 'IDHost' in SwiftMailer SMTP
  parameters
* Safemode check when $wgSMTP is unset is removed. Dont think that is
  necessary when using SwiftMailer
* $wgAdditionalMailParams is not sent to SwiftMailer when $wgSMTP is unset,
  which doesn't sound needed according to
  http://swiftmailer.org/docs/sending.html#the-mail-transport

Anyway, I could test the code successfully with Gmail SMTP settings and no
SMTP settings.


Thanks,
Tony Thomas <http://tttwrites.in>
FOSS@Amrita <http://foss.amrita.ac.in>

*"where there is a wifi, there is a way"*


On Fri, May 2, 2014 at 7:20 PM, Tony Thomas <01tonytho...@gmail.com> wrote:

> Hello Andre,
>             I was indeed in search of more input whether it's a good idea
> or bad one. Nemo tells me it will be a nice move to shift from the
> conventional usermailer [1]. Since its an additional task in my proposal, I
> am ready to take up the shifting job, as it needs to be done first, should
> it be done. If anyone would like to take up the job, I would be happy to
> pair with them too.
> Some discussions:-
> [1] :
> https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Third-party_components
>  [2] :
> https://www.mediawiki.org/wiki/Talk:VERP#Swift_Mailer_and_VERP__40928
>
>
>
>
> Thanks,
> Tony Thomas <http://tttwrites.in>
> FOSS@Amrita <http://foss.amrita.ac.in>
>
> *"where there is a wifi,there is a way"*
>
>
> On Fri, May 2, 2014 at 2:34 AM, Andre Klapper <aklap...@wikimedia.org>wrote:
>
>> Hi Tony,
>>
>> could you clarify your intention for this email?
>> Are you seeking for more input whether it's a good idea, or if this
>> actually needed? Or are you searching for agreement as you plan to work
>> on a patch yourself? Or are you looking for somebody to work on this?
>>
>> It's not entirely clear to me from your email.
>>
>> Thanks,
>> andre
>>
>>
>> On Tue, 2014-04-29 at 21:28 +0530, Tony Thomas wrote:
>> > Hi,
>> >           Looks like there isn't any more reply about this proposal on
>> > shifting from UserMailer to Swift-Mailer. Since, we have already started
>> > with implementing VERP, it's high time this enhancement needs to be
>> > applied, if it needs to be. If Swift-Mailer is to be done, VERP needs
>> to be
>> > implemented as a plugin to it, or else as an additional script in the
>> > UserMailer code.
>> >
>> > Bugzilla ticket:- https://bugzilla.wikimedia.org/show_bug.cgi?id=63483
>> >
>> > Thanks,
>> > Tony Thomas <http://tttwrites.in>
>> > FOSS@Amrita <http://foss.amrita.ac.in>
>> >
>> > *"where there is a wifi,there is a way"*
>> >
>> >
>> > On Fri, Apr 4, 2014 at 10:45 PM, Tony Thomas <01tonytho...@gmail.com>
>> wrote:
>> >
>> > > Hi,
>> > >           While working on implementing VERP for Mediawiki[1], Nemo
>> > > pointed to me, Tyler' recommendation[2] on shifting from PHP mailer to
>> > > Swift Mailer[3]. Quoting Tyler's words :
>> > > "PHPMailer has everything packed into a few classes, whereas
>> Swift_Mailer
>> > > actually has a separation of concerns, with classes for attachments,
>> > > transport types, etc. A result of this is that PHPMailer has two
>> different
>> > > functions for embedding multimedia: addEmbeddedImage() for files and
>> > > addStringEmbeddedImage() for strings. Another example is that
>> PHPMailer
>> > > supports only two bodies for multipart messages, whereas Swift_Mailer
>> will
>> > > add in as many bodies as you tell it to since a body is wrapped in
>> its own
>> > > object. In addition, PHPMailer only really supports SMTP, whereas
>> > > Swift_Mailer has an extensible transport architecture, and multiple
>> > > transport providers. (And there's also plugins, and monolog
>> integration,
>> > > etc".
>> > >
>> > >           My mentors too think about it to be a nice idea, and Nemo
>> > > recommended adding it to my GSoC project deliverable here (
>> > > https://www.mediawiki.org/wiki/VERP#Deliverables ). But, we need more
>> > > community-consensus on the same as this needs to be done first, and
>> VERP as
>> > > a plugin to it, if Swift mailer needs to be done. I have opened a BZ
>> ticket
>> > > for the same ( https://bugzilla.wikimedia.org/show_bug.cgi?id=63483).
>> > > Please comment to this thread or in the BZ regarding the shift as it
>> needs
>> > > to be done for a start. The discussions we had on this till date is
>> here:
>> > > https://www.mediawiki.org/wiki/Talk:VERP#Swift_Mailer_and_VERP__40928
>> .
>> > >
>> > > [1]: https://www.mediawiki.org/wiki/VERP
>> > > [2]:
>> > >
>> https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Third-party_components
>> > > [3]: http://swiftmailer.org/
>> > >
>> > >
>> > > Thanks,
>> > > Tony Thomas <http://tttwrites.in>
>> > > FOSS@Amrita <http://foss.amrita.ac.in>
>> > >
>> > > *"where there is a wifi,there is a way"*
>> > >
>> > _______________________________________________
>> > Wikitech-l mailing list
>> > Wikitech-l@lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
>> --
>> Andre Klapper | Wikimedia Bugwrangler
>> http://blogs.gnome.org/aklapper/
>>
>>
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to