Hi, Have you tried running a tcpdump on the session to see what's being sent to the mail server?
Cheers, Andy. On Thu, Dec 3, 2009 at 5:54 AM, Meeko <[email protected]> wrote: > I did what you said, wrapping in an eval, and no errors occured. However, > I think I have narrowed the problem down some. Here is what I have > discovered: > > I changed the configuration of Catalyst::Plugin::Email to use an > unauthenticated SMTP server which I own (I have relaying disabled, and only > have the IP address of my web server on the allow relay domains - so its not > an open relay). This is actually the SMTP server that my other non-Catalyst > Net::SMTP scripts use. Well, needless to say, once I changed that the > Catalyst app began happily sending e-mails with Catalyst::Plugin::Email I > could keep it this way if I had to, but would rather not because I don't > know how long I am going to keep this other mail server around. This was > part of the reason why I began moving my e-mail activity to Rackspace, I > don't want to have to deal with maintaining a mail server in the future. > > So anyway, back to Catalyst::Plugin::Email with authenticated SMTP... > > I think the issue I am having is actually with the username and passwords > being sent encrypted in Base64. I have verified that I am able to perform > an AUTH LOGIN on the Rackspace SMTP server from my web server by doing a > telnet my.smtp.server 25; HELO host; AUTH LOGIN; <Base64 encoded Username>; > <Base64 encoded Password>, and I get a 235 2.7.0 Authentication successful. > So I know this web server is capable of authenticating on the SMTP server. > > So now my thoughts turn to, why would the username and password not be > encoded properly with perl on my web server, but it does work on my Mac at > home? Just as a quickie, I updated my MIME::Base64 to the newest version, > and re-started. No such luck. > > Any other ideas on where to look next, now that I have been able to uncover > more information? > > On Wed, Dec 2, 2009 at 9:53 PM, Charlie Garrison <[email protected]>wrote: > >> Good afternoon, >> >> >> On 2/12/09 at 8:51 PM -0500, Meeko <[email protected]> wrote: >> >> SELinux is disabled (see below). Also, on the same machine I have several >>> other non-Catalyst perl apps that I use Net::SMTP to send e-mail with, >>> and >>> they work fine so I know that e-mail can get out on this machine. >>> There's >>> just something about Catalyst::Plugin::Email that is not sending them, >>> and >>> leaving no visible errors/warnings/logs that I can find to try to figure >>> out >>> why. >>> >> >> How about wrapping the $c->email() statement in eval {} and checking for >> errors? I don't know if that will help but easy enough to test. >> >> Charlie >> >> -- >> Ꮚ Charlie Garrison ♊ <[email protected]> >> 〠 PO Box 141, Windsor, NSW 2756, Australia >> >> O< ascii ribbon campaign - stop html mail - www.asciiribbon.org >> http://www.ietf.org/rfc/rfc1855.txt >> >> >> _______________________________________________ >> List: [email protected] >> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst >> Searchable archive: >> http://www.mail-archive.com/[email protected]/ >> Dev site: http://dev.catalyst.perl.org/ >> > > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > >
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
