Using different Incoming Mail Server

RT Users
1

Hello,

I need to configure my RT server to receive the emails but from another mail
server.

RT ticket gets created within the RT Interface -> RT server sends email with
new created ticket to users via its local sendmail -> Users receive email
with ticket number and the reply address -> A user replies back to the reply
address which is hosted on a different mail server -> Mail server receives
the email and forwards email to the RT server which is running sendmail ->
RT receives the reply and post the reply in the ticket and sends the reply
information to the users via email

RT Server Name and Outgoing Mail Server: rt.domain.tld 10.0.0.5

Incoming Mail server which forwards email to the RT MTA: mail.domain.tld
192.168.0.5

Any inputs?

Thanks.

2

Richard Solid wrote:

Hello,

I need to configure my RT server to receive the emails but from another
mail server.

RT ticket gets created within the RT Interface → RT server sends email
with new created ticket to users via its local sendmail → Users receive
email with ticket number and the reply address → A user replies back to
the reply address which is hosted on a different mail server → Mail
server receives the email and forwards email to the RT server which is
running sendmail → RT receives the reply and post the reply in the
ticket and sends the reply information to the users via email

RT Server Name and Outgoing Mail Server: rt.domain.tld 10.0.0.5
http://10.0.0.5

Incoming Mail server which forwards email to the RT MTA:
mail.domain.tld 192.168.0.5 http://192.168.0.5

Any inputs?

Thanks.

You need to configure your receiving mail server with virtual support or
relaying maps – depending on your MTA… is.
rt.example.com. IN MX 10 mailgw.example.com

mailgw.example.com
virtualhost rt.expample.com

For outbound mail simply set a smarthost in your Rt server’s sendmail.cf
file – make sure the smarthost allows relaying from the Rt server.

3

Hello,

I need to configure my RT server to receive the emails but from
another mail
server.

We just use fetchmail on the RT server. Then I run things from
fetchmail through procmail so that I can filter out spam and such. The
formail command allows me to keep the Queues seperate, but still only
have one RT user on the RT server. (all \ mean long wrapped line. take
out if you copy/paste and move all to one line)

rtuser@trouble:~$ cat .fetchmailrc
set logfile /home/rtuser/logs/fetchmail.log
poll smtp.example.com protocol pop3 and port 995

Queue 1

username rt@example.com password xxxxxx
mda ‘/usr/bin/formail -f
-A “X-Original-Account: rt@example.com” |
/usr/bin/procmail -d rtuser’

username rt-comment@example.com password xxxxxx
mda ‘/usr/bin/formail -f \
-A “X-Original-Account: rt-comment@example.com” |
/usr/bin/procmail -d rtuser’

Queue 2

username rt2@example.com password yyyyyyy
mda ‘/usr/bin/formail -f
-A “X-Original-Account: rt2@example.com” |
/usr/bin/procmail -d rtuser’

username rt2-comments@example.com password yyyyyyyy
mda ‘/usr/bin/formail -f \
-A “X-Original-Account: rt2-comments@example.com” |
/usr/bin/procmail -d rtuser’

rtuser@trouble:~$ cat .procmailrc

Standard Procmail variable declared here

The condition line ensures that only messages smaller than 250 kB

(250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam

isn’t bigger than a few k and working with big messages can bring

SpamAssassin to its knees.

:0fw

  • < 256000
    | /usr/bin/spamc -d 192.168.74.3 -p 783

If the message was actually skipped, we want to know

:0Ef
| formail -A “X-Spam-Skipped: Yes =Message not tested by SpamAssassin=”

Get Spam out of the way

:0:

  • ^X-Spam-Status: Yes
    $DEFAULT

I have a few other procmail recipes here

Helpdesk emails

:0

  • ^X-Original-Account:.*rt@example.com
    | /usr/bin/rt-mailgate --url http://your.url.here \
    –queue helpdesk --action correspond

:0

  • ^X-Original-Account:.*rt-comment@example.com
    | /usr/bin/rt-mailgate --url http://your.url.here
    –queue helpdesk --action comment

Recuitment emails

:0

  • ^X-Original-Account:.*rt2@example.com
    | /usr/bin/rt-mailgate --url http://your.url.here
    –queue Recruitment --action correspond

:0

  • ^X-Original-Account:.*rt2-comment@example.com
    | /usr/bin/rt-mailgate --url http://your.url.here
    –queue Recruitment --action comment

This drops any Unsorted mail into the INBOX

:0:
$DEFAULT

http://gentgeen.homelinux.org

Associate yourself with men of good quality if you esteem
your own reputation; for 'tis better to be alone then in bad
company. - George Washington, Rules of Civility

4

We have a user sending us tickets in the Simplified Chinese charset
(gb2312).

The body renders fine in RT 3.4.5 (as viewed through Firefox), but the
Subject seems to get munged, all we see is question marks.

Is this a known bug, a feature, or do I have some parameter switched off
somewhere?

Thomas

5

Ugh, sorry about replying to an already-existing message, I usually blow
away the original message-id before I do that…

Thomas