#haraka

nedry_: I flicked through JS The Good Parts, but ignore all the crap about objects. Crockford gets that basically wrong IMHO.

Thanks Matt!

morning

Hi does anyone know what the message_stream of the transaction is? Is it rfc822 email?

BigOrangeSU: yes - it's a stream of the message in rfc822 format.

_smf_: Sweetness, also where is the documentation about how multiple messages can be within a single transaction?

BigOrangeSU: incorrect; you can't have multiple messages in a transaction.

multiple messages per-connection yes.

multiple recipients per-transaction yes also.

_smf_: the multiple messages per connection, is the queue_outbound called per transaction or per connection?

per transaction

_smf_: So are there any loops that you need to worry about when handling queue_outbound?

I'm not sure I understand the question.

You obviously want to make sure that you don't loop back around to yourself.

Maybe if you explained what you're trying to do?

_smf_: Ya that was a bad question. I was having issues with smtp_forward, specifically with smtp_client not handling TLS properly, so I am using a new library nodemailer/smtp-connection to send the email via the queue_outbound, however I jut wanted to make sure I wasn't missing anything.

So i am building my own smtp_forward plugin that uses a different smtp-client

and the code is overly simple

compared to the smtp_forward plugin included in haraka so I was just double checking to see if I was missing anyhting

No - you should be fine I think.

I looked at smtp_forward to see what the issue was with TLS and the problem is that smtp_forward defines it's own SMTP AUTH callbacks which run before the smtp_client.js functions that do the TLS start-up.

(I think)

_smf_: yea TBH I am a newbie on this TLS and auth stuff so I am really struggling here

this was my original thread: https://github.com/haraka/Haraka/issues/1387

ok I just updated my nickname so im more easier to identify :)

_smf_: I actually wonder if its work replacing smtp_client with nodemailer/smtp-connection, I hate dependencies but the code of smtp-connection seems much simpler.

brad_r: I've never looked at smtp-connection so I don't know.

What don't you just use the in-build outbound module instead?

smtp_forward was specifically designed to forward all mail to a *single* server for onward delivery.

_smf_ I dont like the outbound.js because its not neccessarily synchronous. I am doing an smtp_relay and I would prefer to pass the upstream failures back down

Ok - fair enough.

_smf_: In addition its a little hack-ish to swap the upstream provider in the get_mx hook

hack-ish?

That's kinda what get_mx was designed for.

yea i get it but it just seems weird because get_mx only has access to the hmail, not the connection when in reality my usecase is more of a "per connection" basis

It doesn't have a connection because outbound becomes independent of the connection/transaction once the message is queued to disk (spooled).

You can pass connection level attributes across to it by putting notes into the transaction.

They'll then appear in hmail.todo.notes

_smf_: Thats what I was doing initially. But also why I said a little "hack-ish" to flip the mx.

Ok

_smf_ does haraka have a bunyan compatible logger built in besides the logger documented?

Ultimately we need to fix smtp_forward - I just haven't had time to start hacking on it as I don't use it any more.

Nope

You can create your own bunyan logger easily though by creating a log plugin for it.

_smf_ Yea I am going to, I actually think the core Haraka team should firm up the smtp_client or outbound and deprecate the smtp_forward plugin. If the users want to implement it, they can easily as long as their is a well done client

It's not quite that simple.

smtp_forward is *very* different to outbound.

_smf_ what do you mean? smtp_forward fowards for delivery while holding the connection open, while outbound accepts the message and sends it.

e.g. outbound queues mail to disk like an MTA and does periodic retries, handles bounces and deferrals, splits messages etc.

smtp_forward delivers the message to the 'next-hop' in real time before proxying the response back to the client.

_smf_: gotcha, ya in that case smtp_forward is definitely what I want since I dont want to handle bounces or anything.

So not sure about outbound, but I just rather the smarter people (like you) handle the hard stuff like the smtp-client, tls, etc, etc, et,c and let the less experienced handle the easy part of using that library for smtp_forward, proxy, etc