#haraka

Can you please tell how to receive mail in haraka

Kaustubh: set-up MX or A record for the label (e.g. domain or hostname) that you wish to receive mail for that points to your Haraka installation. Add the label (e.g. domain or hostname) to your config/rcpt_to.in_host_list. Then set-up smtp_forward to point to a mailbox host that will deliver the mail for that label to a mailbox (Haraka can't do this itself, unless you get it to deliver to an LMTP server like procmail or dovecot).

_smf_ No file rcpt_to.in_host_list in config

Kaustubh: sorry config/host_list

I don't use that particular plugin so I'd forgotten the name.

morning

morning baudehlo

Good weekend?

Not bad. Went to see Ant Man. Enjoyed that (except for it being in 3d - I'm so sick of 3d movies)

Yeah - 3D sucks. Headache inducing.

And the cinema we were in doesn't have a proper 3d projector, so it's half brightness.

Plus as a glasses wearer - putting those fucking 3d glasses over the top is really uncomfortable.

I bet

Hi

How do you require outbound from a subfolder?

Spathon: for plugins; you just do a: var outbound = require('./outbound'); and Haraka will find it automatically.

Regardless as to whether they are in a sub-folder of plugins or not.

I have a plugin that are calling another module that are in a sub-folder. I can require outbound from the plugin but not from the module

Weird; I'd have thought that should have worked the same, given the 'require' is actually a custom_require function that is provided via the plugin vm.

s/given the/given that/

I solved it for now by require it in the plugin and pass it in to the module

_smf_: yeah but if you require() something from a plugin, it's not in the same sandbox.

it uses the system require()

Ok - I didn't realise that as I haven't done that in a module before. I guess a relative path is then required?

yeah

it's the same as if you did a require() for something in node_modules - it couldn't do require('./outbound') either.

baudehlo: I always presumed the loading stuff in a plugin (and hence inside the vm) meant that require => custom_require.

It is. But it ultimately calls core require() rather than loading the code in a sandbox.

Ok - but I thought that './' in the front of the filename always caused custom_require to attempt to load HARAKA_DIR + '/' + plugin instead.

could it not be useful to have a custom require function for haraka specific files to call from plugins/modules? require_haraka('outbound') than it's also easier to see where the file is from