Piping on seperate server

[msteudel]

Whats the new file to point mail aliases at with the v3?

In the old v2 you set your /etc/aliases file like:

email: "/etc/smrsh/pop3pipe.php"

Or something like that ...

[msteudel]

Anyone know how to setup mail parsing on a seperate server from the main installation?

[w00d]

Originally Posted by msteudel

Anyone know how to setup mail parsing on a seperate server from the main installation?

I was able to get "piping" to work by using a combination of SSH and sudo. I can give details to help you set it up between your servers if you'd like, provided your servers are not running Windows.

[msteudel]

That'd be great, yah I'm running RHAS boxes and have full root. I tried piping to the parse.php but I don't think was the right file ...

* The two boxes can already talk to each other via MySQL so thats all good.

* I've just copied the upload directory up, but haven't run the setup.php as I we didn't have to do that with the older version.

* I know how to setup the alias file and pipe an alias to a script

Mark

[w00d]

I'll give you specific instructions for how I have piping set up between two of our servers. Since your configuration may not match our configuration exactly, you'll have to make some modifications to get this working on your set up.

The first thing you will need is a shell account on both your mail and web servers. For this discussion, we'll call the user "maint." Set up public/private key encryption between the maint account on both the web server and the mail server so the maint user can SSH from the mail server to the web server without needing a password. Search google for "passwordless SSH login" for instructions on how to do this.

Our mail server uses vpopmail and qmail for mail delivery so all email is owned by the vpopmail user. I use sudo to allow the vpopmail user to execute a command on behalf of the maint user. To do this, I have the following line in my /etc/sudoers file:

vpopmail ALL= NOPASSWD: /bin/su maint [-c]*

Now that I have that set up, I needed some way to let eSupport know when a new email is delivered to the support@??? email account. Since we are using qmail, I have the following commands in the .qmail file for the support@??? email account:

| /usr/local/bin/maildrop /usr/local/etc/mail/mailfilter
| /usr/bin/sudo /bin/su maint -c "/usr/bin/ssh our.web.server.address '/usr/bin/wget -q --delete-after http://our.web.server.address/esupport/cron/index.php?_t=parser'"

The first line of the .qmail file sends the message through our mail filters, which handle delivery of the message to the inbox. The second line executes a SSH command on behalf of the maint user on the web server that will trigger eSupport v3 to check for new messages in inboxes of the email accounts it monitors.

So to summarize:

1. Create an account on the web and mail servers using passwordless SSH logins
2. Configure sudo to allow the mail user access to execute a command on behalf of the account you just created
3. Configure your mail system to deliver the message and then trigger eSupport to check for the new message

This has been working well for us because incoming messages to our mail server are immediately read into eSupport. There is no need to make eSupport check for new messages through a cron job. The message isn't exactly piped from one server to the next in this example but the web server is certainly triggered to check for new mail dynamically so the effect is the same.

[msteudel]

Wow did you come up with this or did Kayako come up with this? I'll try it out and let you know how it goes.

[w00d]

Originally Posted by msteudel

Wow did you come up with this or did Kayako come up with this? I'll try it out and let you know how it goes.

No I came up with this when I wanted more response out of eSupport and I didn't want to wait for the cron job to execute every few minutes to check for new messages.

[Skeptical]

While this method works, wouldn't it be better if there were a separate set of scripts that you can install on the mail server which will auto-insert emails into the mysql database? Deskpro already does this.

[Varun Shoor]

Originally Posted by Skeptical

While this method works, wouldn't it be better if there were a separate set of scripts that you can install on the mail server which will auto-insert emails into the mysql database? Deskpro already does this.

Interesting Idea and not tough to do, I will see what I can do to implement this. I would recommend using POP3 for now.

Regards,

Varun Shoor

[dpezzo]

Originally Posted by Varun [K]

Interesting Idea and not tough to do, I will see what I can do to implement this. I would recommend using POP3 for now.

Regards,

Varun Shoor

Any update on this, as in has this been added? I have the same issue with mail server separate from web server. Did not even think about that going into this, and really need to get this going with piping.

Thanks for any assistance.

Regards,
Darren

[qpsupport]

I am also interested in this. Any updates?