Sorry to be unhelpful in describing the issue. The password and username
credentials are all correct. I am using BuildBot MailNotifier to send an
email each time a build has taken place:
from buildbot.status import mail
c['status'].append(mail.MailNotifier(
fromaddr="bu...@companyname.co.uk",
extraRecipients=[exam...@companyname.com",],
sendToInterestedUsers=False,
mode='all',
relayhost="smtp.companyname.lan",
useTls=False,
smtpUser="username",
smtpPassword="password"))
I am a new user to twisted and am unsure of what it would be helpful to
show. The traceback I have shown is from the twistd.log. If I can't expect
it to work with some other authentication method then how can the problem
be resolved?
On 24 July 2012 14:31, Itamar Turner-Trauring <ita...@futurefoundries.com>wrote:
>
>
> On Tue, Jul 24, 2012 at 6:54 AM, Phil Mayers <p.may...@imperial.ac.uk>wrote:
>
>> IIRC the Twisted SMTP stuff has support for handling auth errors and
>> trying other methods; it should "just work".
>>
>
> The code is a bit convoluted, so I can't be sure without more time than I
> want to spend on it, but I wouldn't expect it to try more than one auth
> method. If you send your username and password with CRAM-MD5 and got an
> error, why would you expect it to work with some other authentication
> method? It's still the same credentials.
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>
>
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
