/build/static/layout/Breadcrumb_cap_w.png

K1000 Email Setup - Exchange 2007 & Barracuda Spam Filter

Please note that these are my own notes along with pertinent comments I copied from Kace's Exchange email setup KB. Credit where credit is due, as I didn't invent this wheel, I just documented the specifics of my setup.

http://www.kace.com/support/resources/kb/article/Setting-Up-Microsoft-Exchange-to-Send-Email

The guide below covers settings used on my Exchange 2007 server cluster (2 transport servers, 2 mailbox servers, one cluster entity) and a Barracuda spam filter. If you are running a single Exchange server, you can probably use the same IP address anywhere the mail server IP is needed, but I can’t verify this as it’s not my setup. The major issues I ran into while setting this up (using Kace’s setup guide) were the need for a rule on the Barracuda spam filter (step 8), and the fact that the same setup for my Helpdesk queue didn't work for my HR queue (step 5 - 7 Alternate). 

If you have your Exchange config as per Kace’s setup guide for Exchange 2007 and are still not getting mail flow to your KBOX, you may need to tweak your spam filter (regardless of make/model), similar to what I setup on the Barracuda.

I should also clarify that although guide below is correct for my Helpdesk@Company.Com address, the transport rule did not work for my second queue's HR@Company.Com address. As a workaround I used mail forwarding from the HR mailbox. A note on this approach - if I remember correctly, this didn’t work when I tried setting up forwarding for the Helpdesk address when I was testing and troubleshooting things. Go figure.

Therefore any mail flow troubleshooting needs to take into consideration that Helpdesk@Company.Com reaches the helpdesk@kbox.company.net address via a transport rule, and that HR@Company.Com reaches the hr@kbox.company.net address via forwarding setup on the HR mailbox. As always, take the time to document and it will save you countless moments of frustration.

__________________________________________________

1. Verify the KBOX 1100 Network Settings

The KBOX Exim server is always running in this mode by default. The only thing needed here is to configure the email addresses that will be accepted.

Setup a queue and each queue has an email address:

  • go to the Settings -> Control Panel -> Network Settings
  • verify Use SMTP Server is checked and the address is set to the Exchange cluster [192.168.1.200]

K1000 Network Settings

K1000 DNS Hostname (e.g. kbox):    kbox

K1000 Web Server Name:                  kbox

Static IP Address:                               192.168.1.50

Domain (e.g. kace.com):                    company.net

Subnet Mask:                                     255.255.255.0

Default Gateway:                               192.168.1.1

Primary DNS:                                    192.168.1.100

Secondary DNS:                                192.168.1.101

Network Speed:                                Auto-negotiate 

Network Server Options

Use SMTP Server                             x

SMTP Server:                                  [192.168.1.200]

Use Proxy Server                             <unchecked>

Enable Help Desk POP3 Server      <unchecked>

__________________________________________________

2. Configure the KBOX 1100 to Accept Mail

The KBOX Exim server is always running in this mode (accept email) by default. The only thing needed here is to configure the email addresses that will be accepted.

Setup a queue and each queue has an email address:

  • go to the Service Desk -> Configuration -> Queues
  • click on Company Helpdesk
  • confirm that the domain suffix for the email address column is correct (kbox.company.net)
  • type in the name of the Queue (Company Helpdesk)
  • type in the email address for the queue (helpdesk@kbox.company.net).
  • if desired type in an alternate email address which will modify the from of email sent from the KBOX (Helpdesk@Company.Com). This is the email address that your end users will use

NOTE: The e-mail prefixes must match (i.e. helpdesk).

Allow all users as submitters:                      x

Allow all users as approvers:                      <unchecked>

Ticket Owners By Label:                            it

Accept email from unknown users:            <unchecked>

Allow ticket deletion:                                 <unchecked>

Allow parent ticket to close child tickets:  <unchecked>

Grant read/edit permissions to users with an Admin role (admin portal only):      x

__________________________________________________

3. Create a mailbox that your employees can address via Active Directory

In the Exchange Management console create a mailbox with the address that you want your end users to address. (Helpdesk@Company.Com)

  • Exchange 2007 Console – Recipient Configuration – Mailbox - New Mailbox…
  • User Mailbox – New User
  • First Name (Helpdesk) - Name (Helpdesk) - User logon name (Helpdesk)
  • specify desired alias and mailbox database (storage group)
  • verify E-Mail Addreses shows the alternate email address (helpdesk@company.com)
  • default settings for everything else

__________________________________________________

4. Create a contact that represents the KBOX 1100

In the Exchange Management console create a contact (not a mailbox) with the address of your KBOX (helpdesk@kbox.company.net)

  • Exchange 2007 Console – Recipient Configuration – Mail Contact – New Mail Contact…
  • Name (kbox1100) – External e-mail address (helpdesk@kbox.company.net)
  • make sure that this user's primary address is as above. You may need to turn off automatic updates of recipient policy to accomplish this.
  • you will want to hide this user from address lists so choose the option Hide from Exchange address lists
  • default settings for everything else

__________________________________________________

5. Create a Transport Rule to redirect mail to the KBOX 1100

In the Exchange Management Console:

  • go to Organization Configuration -> Hub Transport
  • click on the Transport Rules tab
  • select New Transport Rule
  • on Introduction set it any name (KBOX_1100) and make sure it is enabled
  • on Conditions step choose sent to and follow the hyperlink and locate the user with the address Helpdesk@Company.Com
  • on Actions step choose redirect the message to and follow the hyperlink and locate the user with the address helpdesk@kbox.company.net
  • complete the rule

__________________________________________________

6. Create a Send Connector so Exchange can reach the KBOX 1100

In the Exchange Management Console:

  • go to Organization Configuration ->Hub Transport
  • click on the Send Connectors tab
  • select New Send Connector
  • configure as follows:
    • Name (KBOX_1100)
    • General tab (maximum message size - 10240 KB)
    • Address Space tab (Type - SMTP, Address - 192.168.1.50, Cost - 1)
    • Network tab (Route mail through the following smart hosts: (192.168.1.50)
    • Source Server tab (TRANSPORT1, TRANSPORT2)

__________________________________________________

7. Create a Receive Connector so the KBOX 1100 can reach Exchange

In the Exchange Management Console:

  • go to Server Configuration -> Hub Transport
  • select New Receive Connector
  • configure as follows:
    • Name (KBOX_1100)
    • General tab (Specify the FQDN... - TRANSPORT1.Company.Net) (maximum message size - 10240 KB)
    • Network tab (Local IP - 192.168.1.200 - Port 25) (Remote IP - 192.168.1.50)
    • Authentication tab (clear all - nothing should be checked)
    • Permission Groups tab (Anonymous users)

__________________________________________________

5-7 Alternate. Use the Forwarding Address Rule Instead of Transport Rules

This is how I handle mail flow to the KBOX for my HR queue, as the transport rules don't work for some reason

In the Exchange Management Console:

  • open the Properties screen for the mailbox (HR)
  • select the Mail Flow Settings tab - Delivery Options properties
  • for the Forwarding address, check the Forward to: box and specify the corresponding mail contact (hr1100)

__________________________________________________

8. Configure Barracuda 300 so e-mail can reach KBOX 1100

In the Barracuda Networks Spam & Virus Firewall 300 admin console (https://192.168.1.25):

  • go to Domains - Domain Manager tab
  • Advanced Domain Confiiguration- New Domain Name - type kbox.company.net - click Add Domain
  • click on Manage Domain for kbox.company.net
  • go to IP Configuration tab
  • Destination Server - 192.168.1.50
  • Destination Port - 25
  • Valid Test Email Address - mailbox@kbox.company.net - click on Test SMTP Connection
    • this should create a new ticket in the KBOX 1100 (Service Desk - Tickets)
    • if this fails, check the outbound queue on the Barracuda (Manage System - Advanced - Queue Management)
    • can also delete stuck messages from here (select and CTRL+click for multiple, Tools - Message Actions - Delete Selected)

__________________________________________________

9. Troubleshooting incoming mail to KBOX 1100 SMTP Server

For a complete test, make sure that you run this test from your mail server. Remember, the KBOX does not have a POP server. You route the mail to the KBOX SMTP server and it does the rest. So, you can try to telnet to the KBOX SMTP server and send a test mail. Make sure when you do this test that the address used (user@company.com) is a valid user that can submit tickets to the helpdesk queue you are testing (also so you can test receiving the reply message the KBOX 1100 generates).

Also note that if you make any typos while doing this, you will have to start over - so type carefully.

E.g.

>telnet kbox.company.net 25

>EHLO company.net

>MAIL FROM:<jverbosk@company.com>

>RCPT TO:<helpdesk@kbox.company.net>

>DATA

To: <helpdesk@kbox.company.net>

From: <jverbosk@company.com>

Subject: <Test>

Test

.

Every step should work. Note that on some kbox configurations there must be a user with the email address of admin@company.com that is allowed to be a submitter of tickets

__________________________________________________

If you get the following error, try again on a mail server (not your own PC):

554 SMTP synchronization error

Connection to host lost.


Comments

  • The formatting didn't apply correctly in places, hopefully you can still follow. Hope this helps somebody.

    John - jverbosk 12 years ago
  • Just a note that setting up mail flow for all of my subsequent queues has just involved setting up mail forwarding from the mailbox to the mail contact. It appears the single transport rule handles everything.

    John - jverbosk 11 years ago
  • Hi John! Awesome post. We are still currently on Exchange 2003 and I am having trouble figuring out how to translate transport rule step #5 into Exchange 2003 world. Since there is no option to create transport rules I did the forward option instead. When I try to forward to the kbox I get this mailer delivery system notice:

    This is the mail system at host gwo5.mbox.net.

    I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.

    For further assistance, please send mail to postmaster.

    If you do so, please include this problem report. You can delete your own text from the attached returned message.

    The mail system

    <helpdesk@k1000.company.com>: Host or domain name not found. Name service
    error for name=k1000.company.com type=AAAA: Host not found

    I'm pretty new to Exchange administration and especially new to Exchange 2003, so it's quite possible I'm missing something obvious. Any ideas?

    Thank you,
    Alicia - awingren 9 years ago
    • Alicia,

      See if this one will help:

      http://www.itninja.com.tw/blog/view/kace-configuring-exchange-2003-and-kbox-communication

      Hope that helps!

      John - jverbosk 9 years ago
      • John,
        I can't believe I missed that! >_<

        Thank you!
        Alicia - awingren 9 years ago
  • Thank you! Great research! I was able to complete the service desk module. - Miggy 9 years ago
This post is locked
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ