Fetchmail, sendmail, postfix what to use

I just installed RT got it running so far… i am using Debian (sarge) and am having trouble getting the emailing to work… which is the best way to configure the mailing piece and what is the best mail program to use in linux for this task… What I would like to do is use another server for the SMTP traffic and another for the pop3 receipt. that is how our email system is currently set up.

Thanks

I just installed RT got it running so far… i am using Debian (sarge) and
am having trouble getting the emailing to work…

You don’t say what trouble you are having. What are you doing? What
happens? What did you expect to happen? What’s in the mail log files?

which is the best way to configure the mailing piece

The documentation is pretty clear on this.

and what is the best mail program to use in
linux for this task…

There are many to choose from: personally, I use Postfix. Which are you
trying to use?

What I would like to do is use another server for
the SMTP traffic and another for the pop3 receipt. that is how our email
system is currently set up.

Do you mean another server to receive SMTP or to send via? If the later,
you need to set your MTA’s “smarthost” to that server. If the former,
please explain exactly how this setup should work. I don’t understand your
POP3 comment - POP3 is a protocol for collecting email, and is not really
applicable to RT.

bob wrote:

I just installed RT got it running so far… i am using Debian (sarge)
and am having trouble getting the emailing to work… which is the best
way to configure the mailing piece and what is the best mail program to
use in linux for this task… What I would like to do is use another
server for the SMTP traffic and another for the pop3 receipt. that is
how our email system is currently set up.

Sorry Bob, I’ll have to agree with Susan’s comments - you’ll need to be
a bit more specific.

The “best” mail program is whatever one you’re comfortable with. If
you’re not using one today, you’ll be spending some time in the books on
just about any of them to get them doing what you want. Susan mentioned
she’s using postfix, and if I were building a brand new server today,
I’d probably consider going that route too, as I see benefits to it, but
I’d be on a big learning curve myself.

Currently on my RT system I’m using exim4 for the MTA on a Debian
system, and the only reason really is that it was upgraded from older
versions of Debian over the years and Debian used to use exim3 as a
default MTA, so I got used to it.

The “use another server” for the traffic part is not a problem or issue
related to RT in any way, it’s your MTA’s job to route mail. Most MTA’s
have the ability to deliver mail to a “smarthost”. That’ll be the key
word for finding out how to do that in your particular MTA’s documentation.

On the receipt part of e-mail, if you’re hoping to set up multiple mail
accounts on a remote machine to receive RT’s mail and then pull them to
the RT machine, you’ll end up using fetchmail, most likely.

If you’ve never set up Unix MTA’s and fetchmail, you’re in for quite a
long while at the keyboard… that is not the easiest setup for a
beginner… but if you must, you must… we all understand and have
probably been there.

Bite off one chunk of the elephant at a time… get your box working and
your MTA of choice sending and receiving mail for some test user
accounts. Once you have that going, you’ll be able to integrate RT into
the mix.

Nate Duehr, nate@natetech.com

hi,

request-Tracker3 has been installed and is looking great.

i have installed this on a debian sarge machine and will paste my notes
to the bottom of this posting. when i have got postfix to work i will
update/tidy up the notes and put them up for the wiki.

but…

first…

i just need to get basic email sending to work. i have changed from
exim to postfix, the ‘mail’ command works from the command line.

but when i add users to the cc line in RT nothing gets sent out - the
local email server logs show nothing.

could someone paste in some conf file settings which enable RT to send
mail using postfix.

thanks

kev bailey

Setting up Request-Tracker3
Edited the /etc/Request_tracker3/RT_SiteConfig.pm file.:

    # RT_SiteConfig.pm
    # These are the bits you absolutely *must* edit.
    # To find out how, please read
    #   /usr/share/doc/request-tracker3/INSTALL.Debian

    # THE BASICS:
    # 04/01/2004 - kbailey
    Set($rtname, 'freewayprojects.com');
    Set($Organization, 'freewayprojects.com');
    # 04/01/2004 - kbailey
    Set($CorrespondAddress , 'RT_CorrespondAddressNotSet');
    Set($CommentAddress , 'RT_CommentAddressNotSet');

    Set($Timezone , 'Europe/London'); # obviously choose what suits you

    # THE DATABASE:

    Set($DatabaseType, 'Pg'); # e.g. Pg or mysql

    # These are the settings we used above when creating the RT database,
    # you MUST set these to what you chose in the section above.
    # 04/01/2004 - kbailey
    Set($DatabaseUser , 'rtuser');
    Set($DatabasePassword , 'password');
    Set($DatabaseName , 'rtdb');

    # THE WEBSERVER:

    Set($WebPath , "/rt");
    # 04/01/2004 - kbailey
    Set($WebBaseURL , "http://rt.freewayprojects.com");

    1;

Created users and a DB on the new database.

First of all created a superuser on the DB called dba.:

    tinkerfour:~# su - postgres
    postgres@tinkerfour:~$ createuser -a -d -P dba
    Enter password for new user:
    Enter it again:
    CREATE USER
    postgres@tinkerfour:~$

Now create the user which RT will use to connect to the DB.:

    postgres@tinkerfour:~$ createuser -d -P rtuser
    Enter password for new user:
    Enter it again:
    Shall the new user be allowed to create more new users? (y/n) n
    CREATE USER
    postgres@tinkerfour:~$

Updated the /etc/postgresql/pg_hba.conf:

    # TYPE  DATABASE    USER        IP-ADDRESS        IP-MASK           METHOD
    # Database administrative login by UNIX sockets
    local   all         postgres                                        ident sameuser

    # 04/01/2004 - kbailey
    host    template1   rtuser    127.0.0.1    255.255.255.255   password
    local   template1   rtuser                                   password
    host    rtdb        rtuser    127.0.0.1    255.255.255.255   password
    local   rtdb        rtuser                                   password

And then restarted the PG database.

Then checked that the user could connect.:

    kbailey@tinkerfour:~$ psql -d template1 -U rtuser -W
    Password:
    Welcome to psql 7.4.6, the PostgreSQL interactive terminal.

    Type:  \copyright for distribution terms
           \h for help with SQL commands
           \? for help on internal slash commands
           \g or terminate with semicolon to execute query
           \q to quit

    template1=>
    template1=>
    template1=> \q
    kbailey@tinkerfour:~$

NB NB NB NB
These notes are from when i copied a DB across from an original install.

Next should copy the DB across from the old machine.

First of all we create a fresh DB from the supplied script.:

    tinkerfour:~# /usr/sbin/rt-setup-database --action init --dba rtuser --prompt-for-dba-password

Lets copy the DB in one go.

To prepare for this we are need to ensure that all local connections to
the DB authenticate using a password - either if from sockets or local
IP address (127.0.0.1)

Then we will store passwords into the ~/.pgpass file so that the command
to backup (and restore) the DB will run from a script.

Ensure /etc/postgresql/pg_hba.conf contains:

    # All other connections by UNIX sockets
    # 02/12/2004 - kbailey
    #local   all         all                                    ident sameuser
    local   all     all     password
    # All IPv4 connections from localhost
    # 02/12/2004 - kbailey
    #host    all         all         127.0.0.1         255.255.255.255   ident sameuser
    host    all         all         127.0.0.1         255.255.255.255   password

The format of the .pgpass file is:

    tinkerthree:~# cat .pgpass
    localhost:5432:*:dba:password

Also, needed to allow tinkerfour to send backup to tinkerthree - so line
was added to allow password authentication on tinkerhtree.:

        host    all         all         127.0.0.1         255.255.255.255   password

Command used to move DB over:

    pg_dump -c -U dba -h tinkerthree rtdb | psql -U dba rtdb

Now we needed to set up apache - so we edited /etc/apache/httpd.conf:

    # 28/12/2004 - kbailey
    NameVirtualHost 192.168.1.18

    <VirtualHost 192.168.1.18>
    #    ServerAdmin webmaster@host.some_domain.com
        DocumentRoot /var/www
        ServerName rt.freewayprojects.com
    #    ErrorLog logs/host.some_domain.com-error.log
    #    CustomLog logs/host.some_domain.com-access.log common

        Include "/etc/request-tracker3/apache-modperl.conf"

    </VirtualHost>

Restart the apache server.

We can now access the RT application at http://rt.freewayprojects.com/rt

Hi Kevin!

I also use sarge with postfix and i don’t alter the config. I
use the original line in
/etc/request-tracker3/RT_Config.pm
which is
Set($MailCommand , ‘sendmailpipe’);

maybe this is not a configuration problem, it is more a
general issue.

but when i add users to the cc line in RT nothing gets sent out - the
local email server logs show nothing.

where do you see the CC line?

For example the “new ticket” page there is a line under the cc field

->(Sends a carbon-copy of this update to a comma-delimited list of email
addresses. These people will receive future updates.)

this means only future updates will be send, because normaly you only
have the scrip:
On Correspond Notify Requestors and Ccs with template Correspondence

if you want the new ticket to be send to the cc you need a new scrip:On Create Notify Requestors and Ccs with template Correspondence okay hope it helps! regards sven Kevin Bailey wrote:

hi,

request-Tracker3 has been installed and is looking great.

i have installed this on a debian sarge machine and will paste my notes
to the bottom of this posting. when i have got postfix to work i will
update/tidy up the notes and put them up for the wiki.

but…

first…

i just need to get basic email sending to work. i have changed from
exim to postfix, the ‘mail’ command works from the command line.

could someone paste in some conf file settings which enable RT to send
mail using postfix.

Hi Kevin!

I also use sarge with postfix and i don’t alter the config. I
use the original line in
/etc/request-tracker3/RT_Config.pm
which is
Set($MailCommand , ‘sendmailpipe’);

ok - so i leave that to be the same.

maybe this is not a configuration problem, it is more a
general issue.

but when i add users to the cc line in RT nothing gets sent out - the
local email server logs show nothing.

where do you see the CC line?

This is when i add a comment to a ticket. it says

(Sends a carbon-copy of this update to a comma-delimited list of email
addresses. Does not change who will receive future updates.)

For example the “new ticket” page there is a line under the cc field

->(Sends a carbon-copy of this update to a comma-delimited list of email
addresses. These people will receive future updates.)

this means only future updates will be send, because normaly you only
have the scrip:
On Correspond Notify Requestors and Ccs with template Correspondence

these are the scrips which are installed

Modify scrips for queue fpoffice
Scrips which apply to all queues

On Correspond Open Tickets with template Blank
On Create Autoreply To Requestors with template Autoreply
On Create Notify AdminCcs with template Transaction
On Correspond Notify AdminCcs with template Admin Correspondence
On Correspond Notify Requestors and Ccs with template Correspondence
On Correspond Notify Other Recipients with template Correspondence
On Comment Notify AdminCcs as Comment with template Admin Comment
On Comment Notify Other Recipients as Comment with template
Correspondence
On Resolve Notify Requestors with template Resolved

so it looks like i’ve got the correct (standard) scrips in place.

as mentioned before - the ‘mail’ and ‘sendmail’ commands work from the
command line.

should the
Set($MailCommand , ‘sendmailpipe’);
line work if set in
/etc/request-tracker3/RT_SiteConfig.pm

BTW isn’t it true i should use
/etc/request-tracker3/RT_SiteConfig.pm

and leave
/etc/request-tracker3/RT_Config.pm

untouched.

is there any way i can test the email sending function of request
tracker?

is there any way i can see what’s going wrong?

thanks - kev

if you want the new ticket to be send to the cc you need a new scrip:

hi,

request-Tracker3 has been installed and is looking great.

i have installed this on a debian sarge machine and will paste my notes
to the bottom of this posting. when i have got postfix to work i will
update/tidy up the notes and put them up for the wiki.

but…

first…

i just need to get basic email sending to work. i have changed from
exim to postfix, the ‘mail’ command works from the command line.

could someone paste in some conf file settings which enable RT to send
mail using postfix.

Kevin Bailey kbailey@freewayprojects.com

i have found some stuff in the log…

Jan 18 20:09:53 localhost RT: RT::Scrip=HASH(0x9d8deac): Couldn’t
prepare Open Tickets
(/usr/share/request-tracker3/lib/RT/Scrip_Overlay.pm:346)
Jan 18 20:09:53 localhost RT:
rt-3.0.12-19-109.0.0331767004733763@freewayprojects.com #19/109 -
Scrip 4 (/usr/share/request-tracker3/lib/RT/Action/SendEmail.pm:92)
Jan 18 20:09:53 localhost RT:
rt-3.0.12-19-109.0.0331767004733763@freewayprojects.com No recipients
found. Not sending.
(/usr/share/request-tracker3/lib/RT/Action/SendEmail.pm:257)
Jan 18 20:09:53 localhost RT:
rt-3.0.12-19-109.14.7192714687555@freewayprojects.com #19/109 - Scrip
5 (/usr/share/request-tracker3/lib/RT/Action/SendEmail.pm:92)
Jan 18 20:09:53 localhost RT:
rt-3.0.12-19-109.14.7192714687555@freewayprojects.com No recipients
found. Not sending.
(/usr/share/request-tracker3/lib/RT/Action/SendEmail.pm:257)
Jan 18 20:09:54 localhost RT:
rt-3.0.12-19-109.12.909606347107@freewayprojects.com #19/109 - Scrip 6
(/usr/share/request-tracker3/lib/RT/Action/SendEmail.pm:92)
Jan 18 20:09:54 localhost RT:
rt-3.0.12-19-109.12.909606347107@freewayprojects.com No recipients
found. Notsending.
(/usr/share/request-tracker3/lib/RT/Action/SendEmail.pm:257)

Have checked it out but (currently) can’t figure it out - any help
gratefully received!

kevOn Tue, 2005-01-18 at 19:50 +0000, Kevin Bailey wrote:

On Tue, 2005-01-18 at 17:35 +0100, Sven Sternberger wrote:

Hi Kevin!

I also use sarge with postfix and i don’t alter the config. I
use the original line in
/etc/request-tracker3/RT_Config.pm
which is
Set($MailCommand , ‘sendmailpipe’);

ok - so i leave that to be the same.

maybe this is not a configuration problem, it is more a
general issue.

but when i add users to the cc line in RT nothing gets sent out - the
local email server logs show nothing.

where do you see the CC line?

This is when i add a comment to a ticket. it says

(Sends a carbon-copy of this update to a comma-delimited list of email
addresses. Does not change who will receive future updates.)

For example the “new ticket” page there is a line under the cc field

->(Sends a carbon-copy of this update to a comma-delimited list of email
addresses. These people will receive future updates.)

this means only future updates will be send, because normaly you only
have the scrip:
On Correspond Notify Requestors and Ccs with template Correspondence

these are the scrips which are installed

Modify scrips for queue fpoffice
Scrips which apply to all queues

On Correspond Open Tickets with template Blank
On Create Autoreply To Requestors with template Autoreply
On Create Notify AdminCcs with template Transaction
On Correspond Notify AdminCcs with template Admin Correspondence
On Correspond Notify Requestors and Ccs with template Correspondence
On Correspond Notify Other Recipients with template Correspondence
On Comment Notify AdminCcs as Comment with template Admin Comment
On Comment Notify Other Recipients as Comment with template
Correspondence
On Resolve Notify Requestors with template Resolved

so it looks like i’ve got the correct (standard) scrips in place.

as mentioned before - the ‘mail’ and ‘sendmail’ commands work from the
command line.

should the
Set($MailCommand , ‘sendmailpipe’);
line work if set in
/etc/request-tracker3/RT_SiteConfig.pm

BTW isn’t it true i should use
/etc/request-tracker3/RT_SiteConfig.pm

and leave
/etc/request-tracker3/RT_Config.pm

untouched.

is there any way i can test the email sending function of request
tracker?

is there any way i can see what’s going wrong?

thanks - kev

if you want the new ticket to be send to the cc you need a new scrip:
On Create Notify Requestors and Ccs with template Correspondence okay hope it helps! regards sven Kevin Bailey wrote:

hi,

request-Tracker3 has been installed and is looking great.

i have installed this on a debian sarge machine and will paste my notes
to the bottom of this posting. when i have got postfix to work i will
update/tidy up the notes and put them up for the wiki.

but…

first…

i just need to get basic email sending to work. i have changed from
exim to postfix, the ‘mail’ command works from the command line.

could someone paste in some conf file settings which enable RT to send
mail using postfix.

Kevin Bailey kbailey@freewayprojects.com

i seem to have noticed that certain changes only take effect after i
have logged out and logged back in again.

are there any pointers to say when i need to logout/login for
configuration changes to take effect.

thanks - kev

does the mail sending command try to do something different if the
domain name of the email address is the same as the domain of the RT
instance?

kev