On Jul 18, 2008, at 4:28 PM, Will Scheidegger wrote:

After digging through the code for an hour I'm able to answer my questions myself:

- No, it's not broken... and I guess it never was.
- No, it's not the username, which causes the trouble
=> One simply needs to add a content node "smtpAuth" to the smtp settings and set it to true.

It would have been sooooo much easier, if this nodedata would be there in the first place (set to false).

You know how patches are easy to apply for us when they're provided in a nifty little jira report ;)

-g



will

On 18.07.2008, at 15:56, Will Scheidegger wrote:

So far STMP with authentication has never worked for us -> We ended up sending mails over a local mail server which did not require authentication or using our own mail sending mechanism.

Now I wanted to try the PUR module, but this module of course is also sending mails, except that this time, we _need_ to send over an SMTP server which requires authentication. I was hoping that by now (Mag 3.6 RC3) this would work when we configure the user and password under config:/modules/mail/smtp. Unfortunately we still get blocked by the mail server (yes, we did test the account).

- Is this still broken?
- Could it be that the stmpUser is causing the trouble because it contains an "@"?

Any help warmly appreciated!

Regards,
will

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to