Evil Net::SMTP Hack with SMTP Authentication

For some reason my hosting provider doesn't like Perl's Net::SMTP SMTP authentication of PLAIN. Everytime, it gives an error.

Unfortunately, there is not way to tell Net::SMTP::auth method to only use a predefined mechanism from Authen::SASL. It will tries the first one every time.... This happens to be the ever failing PLAIN not the working LOGIN flavor.

I tried to pass in a Authen::SASL to the auth method but it will just be smart and override the mechanism list :(

Well, here is my evil to turn the mechanism method into a read only method, put in the top of my script:

package Authen::SASL;
no warnings 'redefine'; # suppress sub refine warning
sub mechanism { return 'LOGIN'; }
package main;


Awful hack but right now I can't find a better way around this problem without completely overriding the the auth method, which seems much worse.



now to figure out how to open a good bug for Net::SMTP.































Comments











Post a Comment



















Popular posts from this blog









Template Toolkit Debugging inside of Perl Dancer





















 The other day someone was asking how to enable Template Toolkit  debugging inside of Perl Dancer  in the #dancer  IRC channel, it seemed like a good time for a write up.   The template engine configuration directive supports passing through various options like start_tag  and stop_tag  as explained in Dancer::Template::TemplateToolkit  POD. And alludes to being able to pass other options.   How   To pass TT options like those found in Template::Constants , there must be a DEBUG  section in engines -> template_toolkit , usually found in config.yml .   Example Snippet    Here is an example:   A few notes     Remove leading DEBUG_  from TT constants. The option DEBUG_PLUGINS  becomes plugins .    Multiple options can be separated with a comma. Example: DEBUG: "provider,plugins" .   Be warned, some of these options can lead to tons of information :)    __END__     








Read more










BootstrapX clickover





















Birth  The last few weeks, i've been pushing Bootstrap  in various directions. Most of the time, its being hacking around Popovers. Our current design uses Popovers with forms. It provides a very nice balance between in page action and more subtle interruption to viewing the page than a modal.   Over the last few weeks, I've found a few quirks with using Popover's  trigger action of 'focus'. This works fine with forms but on Chrome and Safari 'focus' events are supported incompletely . In addition to that varied support we have a few other needs that inspired a new Bootstrap  extension. BootstrapX - Clickover .   Our requirements are:     Click button/link/icon to toggle display of popover content     Option to click 'away' from popover to close     Ability to have 'popover' autoclose after some amount of time     Option to have element inside of popover hide it   I suspect, in the future, it will need to only auto close when user's mouse








Read more










Changing Dancer::Plugin::Ajax's content type





















 Dancer does lots of great things. It has a nice clean way to define routes to handle AJAX routes using the plugin Dancer::Plugin::Ajax .    ajax routes are defined in a clear way:  ajax '/stuff' => sub {   # do work and return };    This plugin technique allows for clear way to separate between ajax and other types of actions for the same route.  ajax '/stuff' => sub {    # do ajax-y stuff here };  get '/stuff' => sub {    # handle html response };    Unfortunately, the one negative with Dancer::Plugin::Ajax  is that is assumes all responses will be XML.     A quick fix is to manually set the content type  in each ajax handler.   ajax '/stuff' => sub {    content_type('application/json');        # do work };   or add set it as a general option in your main before hook or in each prefix route handler like:  package WebApp;  hook before => sub {    if ( request->is_ajax ) {       content_type('application/json');    } }; 








Read more