Relay Host

Hello and thanks for taking the time to take a peek. Do you know how to set up a relay host? I checked docs.sun.com and all I got was #805-3480 Mail Administration Guide for Solaris 7 (close enought I think), but no info on making a relay host. The 805-3480 shows me the file for relay-domains for sendmail (/etc/mail/relay-domains), but not how to make a relay host. Any help would be appreciated and thank you in advance for helping out.

Many thanks Massimo for the info... especially that the "Optional Gateway
settings" are not applicable for the GWIA, since I didn't find that in the
docu.
Thanks,
Mirko
Massimo Rosen wrote:
> Mirko,
>
> On 24.01.2013 11:17, Mirko Guldner wrote:
>> Hi,
>>
>> our GWIA (2012 on SLES 11 SP2, dedicated for SMTP) is sending outgoing
>> mail to a relay (sendmail). In the logs I see several hundred "Send
>> Failure: 450 Host down" per day.
>
> Aka the tcp connection to port 25 of the sendmail box is unsuccesful,
> and never establishes at all.
>
>> I talked to the sendmail admin and he told me there is a setting
>> MaxDaemonChildren=15; I checked the GWIAs settings, which has SMTP send
>> threads=8.
>>
>> My first question: I think increasing MaxDaemonChildren would not help in
>> this case. Or does GWIA open more than one connection per thread?
>
> It *might* help, but if it would be a workaround for a different
> problem. GWIA certainly only opens one connection per send thread. So
> your GWIA should never have more than 8 parallel outgoing connections to
> the sendmail box open at the same time.
>
> However, the two might disagree as to when a connection is closed. A LAN
> Trace for a while when the issue occurs might possibly show that. Is
> there a firewall between the GWIA and the sendmail? If yes, that might
> really be the core problem.
>
>> My second question: I'm a bit confused about the different GWIAs
>> settings. There is "Intervals to retry a defered message"; but there are
>> also retry settings in the "Optional Gateway settings" - do the latter
>> play any role here?
>
> No. The latter is a general setting for all groupwise agents in the C1
> snapins, but plays no role for GWIA.
>
>
> CU,

Similar Messages

Multiple Relay Host question

In the GWIA settings under SMTP/MIME, the "Relay Host for outbound messages" we have the address for a Cisco Ironport c170 that filters our messages.
We want to add another Ironport for failover. If I add a second IP, can this be prioritized so the 2nd unit will only be used if the 1st is down?
What logic will/might be used when a second relay host is used?
Am I approaching this right or should I plan to let it send from either relay host?
Thank you for any help you can offer.

I Like that answer!!!
On the Public side we are going to have different priorities on the MX Records.
I would prefer that One Ironport get all the messages, but realize they both most likely will.
We Quarantine all messages with attachments and manually release them "if" the recipient calls us to let us know they were expecting the message or know he sender.
So I assume we will have to check both Ironports to see which did the quarantine.
We will be using the Ironport Centralized Management to keep the two Ironport configurations the same.
If you have any recommendations or tips, Please share.
Thank You
>>> laurabuckley<[email protected]> 4/30/2013 9:16 AM >>>
'Support | How to setup multiple relay hosts in GroupWise Internet Agent
(GWIA)' (http://www.novell.com/support/kb/doc.php?id=7000379)
We are also using a clustered IronPort solution. We have both IP's
specified in the Relay Host configuration. It is my understanding that
the first IP is always used until it fails.
Cheers,
Laura Buckley
Technical Consultant
IT Dynamics, South Africa
http://www.itdynamics.co.za
laurabuckley's Profile: http://forums.novell.com/member.php?userid=122
View this thread: http://forums.novell.com/showthread.php?t=466322

Question on - GWIA - Relay Host for outbound messages setting

We are being forced to use a "centralized" message relay host due to
State mandates. So . . . most everything is working except messages
sent to comcast.net. For some reason the GWIA is trying to communicate
directly with comcast.net (76.96.62.116). Here is my configuration
(all my GW systems are GW 7.0.3 lastest service patch, NW6.5SP8 server):
PO - on its own server
PO MTA - on its own server
GWIA MTA and GWIA - on their own server
GWIA is configured to use "Relay Host for outbound messages:" -
domain.com
The following is from my GWIA Log showing where I sent a message to my
comcast and hotmail e-mail accounts. For some reason, the GWIA is
trying to send my comcast.net addressed message directly to comcast
server instead of relaying thourgh my relay host. Is there some
setting or config file I need to look at to see how this is
happening?????
14:24:21 3EA MSG 626 File:
GWIA/VOL1:\MBCWEB\WPGATE\GWIA\wpcsout\gwi2e63\4\4C2DF69 5.000 Message
Id: (4C2DF68F.1FC:166:8140) Size: 0
14:24:21 3EA MSG 626 Sender: [email protected]
14:24:21 3EA MSG 626 Converting message to MIME:
MEDBD06/VOL1:\MBCWEB\WPGATE\GWIA\send\xc2df695.141
14:24:21 3EA MSG 626 Recipient: [email protected]
14:24:21 3EA MSG 626 Queuing message to daemon:
GWIA/VOL1:\MBCWEB\WPGATE\GWIA\send\sc2df695.141
14:24:21 3EA MSG 626 Converting message to MIME:
GWIA/VOL1:\MBCWEB\WPGATE\GWIA\send\xc2df695.142
14:24:21 3EA MSG 626 Recipient: [email protected]
14:24:21 3EA MSG 626 Queuing message to daemon:
GWIA/VOL1:\MBCWEB\WPGATE\GWIA\send\sc2df695.142
14:24:21 3E0 DMN: MSG 627 Sending file:
GWIA/VOL1:\MBCWEB\WPGATE\GWIA\send\pc2df695.141
14:24:21 3E0 DMN: MSG 627 Attempting to connect to 76.96.62.116
14:24:22 3FC DMN: MSG 628 Sending file:
GWIA/VOL1:\MBCWEB\WPGATE\GWIA\send\pc2df695.142
14:24:22 3FC DMN: MSG 628 Attempting to connect to domain.com
14:24:22 3FC DMN: MSG 628 Connected to XXX.XX.XXX.XX
14:24:22 3FC DMN: MSG 628 Transferred
14:24:22 3FC DMN: MSG 628 SMTP session ended: [XXX.XX.XXX.XX]
(domain.com)

Chris,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Relay Host for Outbound Messages not being used...

I have a new v7 GWIA on a new domain that is using the relay settings from the original GWIA (on a separate domain) despite its own settings.
Anyone seen this before?
Regards

Check your GWIA.CFG file as anything in there will override settings from eDirectory. I think the switch is /mh which is your Mail relay Host.
If that isn't it, when you say it's a new GWIA, is this a new GWIA installation? Is it a whole new object? Or is it a new server that is running against the existing GWIA object?
Aaron

GWIA is not authenticating to relay host.

Hi,
Since GW7 through to 2012 our gwia has worked without a problem to our relay host authenticating using a gwauth.cfg file. However, now that we have upgraded to GW2014 from GW2012, the relay no longer works using the same gwia.cfg and gwauth.cfg files. We keep getting this error: MSG xxxxxx Response: 550 You must authenticate to use XXXX Standard SMTP.
The agents run on SLES11SP3 (OES11SP2), and the gwauth.cfg file is correct.
Any thoughts?
Thanks,
Brent

In article <[email protected]>, Rbalcorn wrote:
> Since GW7 through to 2012 our gwia has worked without a problem to our
> relay host authenticating using a gwauth.cfg file. However, now that we
> have upgraded to GW2014 from GW2012, the relay no longer works using the
> same gwia.cfg and gwauth.cfg files. We keep getting this error: MSG
> xxxxxx Response: 550 You must authenticate to use XXXX Standard SMTP.
>
> The agents run on SLES11SP3 (OES11SP2), and the gwauth.cfg file is
> correct.
>
Just in case there has been a drift in how it is handled, have you run
through the relevant docs ? The mechanism looks just like it was in 2012.
https://www.novell.com/documentation...ide_admin/data
/adm_gwia_switches_smtp_mime.html
I'd be tempted to do some packet captures to ensure the right data is
going out to where it is supposed to go. If it is hitting the correct
host, then part of the process is working correctly. Perhaps recreate the
gwauth.cfg file incase something funny has happened to it. Also confirm
that there wasn't a password reset at the other end at the same time as
Murphy could have struck while you were upgrading.
Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

GWIA Relay Host for outbound messages

Hi,
In GW2012 I had two relay hosts configured for outbound messages. The IP addresses were separated by a space. Since the upgrade to GW2014, I can no longer add two relay hosts in the GWIA SMTP/MIME tab. When I add the second one, separated by a space, the admin console throws an error. The error says: "Internet address provided is invalid". According to the admin guide, it should still be possible.
How can I resolve this?
Iwan

Originally Posted by laurabuckley
Hi Iwan,
As a work around perhaps try to add the -mh switch to your gwia.cfg:
http://www.novell.com/documentation/...mtp_relay_host
Let us know how it goes.
Cheers,
Hi,
This morning I did just that. However I don't see the switch being used. I checked the GWIA log and the GWIA web console and don't see any mention of it.
Iwan

Server Admin relay host field bug?

I noticed something curious when attempting to specify a relay host via Server Admin 10.4.3 (157.5) application.
If I specify xxx.com in "Relay outgoing mail through host" field, the value will appear as entered in MailServicesOther.plist. However, it will NOT appear in main.cf, there is only a line 'relay='.
When I manually edited main.cf to add 'relay=xxx.com' then relaying started working...however, if I use Server Admin after that to edit the value, it reverts back to an empty value again. Rather annoying, really.
Is this a known bug?

Honestly, I've had trouble with ServerAdmin and Postfix's main.cf from the beginning of 10.3.x I've given up on using SA for anything to do with the mail. I've tried everything from having someone send me a default main.cf and reseting everything in SA.
I can't get it back into sync, and since my backup MX server is running Postfix on FC3 I learned the CLI and got over the SA. I still use SA for looking at Account Quotas under the Maintenance tab, everything else is dorked anyway now.
Xserve G4 1ghz Mac OS X (10.4.3) OSXS 10.4.3

Configuring two smtp relay hosts

Hello all,
I am running Iplanet Messaging Server 5.2 P1.I would like to know if it is possible to add one more smtp relay to the existing setup so that there is a automatic failover from one smtp host to the other.Thanks in advance.
Regards

Not sure exactly what you're trying to do, but. . .
Adding another MX record to your DNS is likely to be the correct route to go. Why create a new software mechanism, when an already well-proven one exists.

How do I install stunnel on Yosemite server 4 so my mail relay works on port 465?

My ISP blocks outbound smtp mail and insists I point to their relay server on port 465. After I set up mail relaying in the server config app I get SMTP log errors saying it's unimplemented. After some research it looks like I need to install a SSL tunnel package called stunnel. Has anyone had an success getting stunnel installed? Or, has anyone had any luck using Yosemite Server 4 to mail relay through verizon.net (port 465)? Any suggestions are much appreciated.

I'll assume that you have to authenticate to the mail relay with a name and password. The Server GUI doesn't provide for this use case.
Take the following steps to configure Postfix to relay mail to a remote SMTP server with password authentication over SSL. Substitute as required for strings in italics below. Address is the fully-qualified domain name of the relay host. The value of port is usually either 25, 465, or 587. Username and password refer to your credentials on the relay host.
In the current version of OS X Server (but not necessarily in older versions), Steps 1 and 3 should be done for you when you enable relaying and relay authentication in the Server application.
1. If necessary, create or update the relayhost directive in
     /Library/Server/Mail/Config/postfix/main.cf
It should look like this:
     relayhost = [address]:port
2. Add these lines, above the section at the end that begins with the comment "# Mac OS X Server":
     smtp_sasl_security_options =
     smtp_tls_CAfile = /etc/certificates/relayhost.pem
     smtp_tls_session_cache_database = btree:$data_directory/smtp_tls_session_cache
     smtp_use_tls = yes
3. If it doesn't already exist, create the password file
     /Library/Server/Mail/Config/postfix/sasl/passwd
with this content:
     [address]:port
     username:password
Here address must match $relayhost.
Then create the password database:
sudo postmap /Library/Server/Mail/Config/postfix/sasl/passwd
This action creates the file
     /Library/Server/Mail/Config/postfix/sasl/passwd.db
The two password files should be readable by root only.
4. Create the file
     /etc/certificates/relayhost.pem
with the CA certificate(s) to be trusted for authentication of the remote host. You get those certificates from the service provider. If you can't find a link to download them, try this:
openssl s_client -connect address:port -showcerts < /dev/null | sed -n '/-BEGIN /,/-END /p' | sudo sh -c 'cat > /etc/certificates/relayhost.pem'
The command may produce an error message that isn't necessarily significant. For servers that use the older STARTTLS protocol, rather than straight TLS or SSL, this command may need to be modified.
5. Restart the Mail service.

Smtp relay on osx 10.9.5 and server 3.2.2

What we have
We have a mac mini setup using 10.9.5 and server 3.2.2.    The mail server is OFF but we have a Relay Outgoing Mail through ISP checked (and the proper credentials for the outgoing relay (FQDN) and the authorization credentials.
What we are trying to do
Our mac mini runs a php script to generate an email that needs to be sent to users.   The mail has to use a smtp relay and we are trying to use the smtp relay provided by our email vendor.
Settings required by our email vendor
Instructions for configuring an email client can be found here
https://www.namecheap.com/support/knowledgebase/article.aspx/1179/2175/general-c onfiguration-for-mail-clients-and-mobile-devices
We set up the relay in Mail on the Server 3.2.2 to use SSL and port 465. In our particular case the relay is configured as shown below. Obviously the [email protected] is the proper username for our authorization.
When we try to send mail (we test this function by sending mail from terminal by using the following command (sending mail to myself from myself)
printf "Subject: TestnHello" | sendmail -f [email protected] [email protected]
and then watch the mail logs the smtp server rejects our mail due to authorization issues. The mail log text is shown below (email addresses replaced with [email protected] and IP addresses modified)
Dec 22 11:57:03 109-218-164-81.lightspeed.austtx.sbcglobal.net postfix/pickup[16825]: 5545383231: uid=501 from=<[email protected]>
Dec 22 11:57:03 109-218-164-81.lightspeed.austtx.sbcglobal.net postfix/cleanup[16827]: 5545383231: message-id=<[email protected]bal.net>
Dec 22 11:57:03 109-218-164-81.lightspeed.austtx.sbcglobal.net postfix/qmgr[16826]: 5545383231: from=<[email protected]>, size=340, nrcpt=1 (queue active)
Dec 22 11:57:03 109-218-164-81.lightspeed.austtx.sbcglobal.net postfix/error[16838]: 5545383231: to=<[email protected]>, relay=none, delay=0.04, delays=0.02/0/0/0.02, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to eforwardct3.name-services.com[216.163.176.39]:465: Connection refused)
Dec 22 11:57:05 109-218-164-81.lightspeed.austtx.sbcglobal.net postfix/master[16824]: master exit time has arrived
We find many self help pages on the internet that talk about modifying the main.cf file located at /Library/Server/Mail/Config/postfix.   Some even talk about modifying settings in the master.cf file in /ect/postfix. I have tried several and none seem to work.
Can anyone provide some guidance?
Regards!

The Server GUI doesn't provide for this use case.
Take the following steps to configure Postfix to relay mail to a remote SMTP server with password authentication over SSL. Substitute as required for strings in italics below. Address is the fully-qualified domain name of the relay host. The value of port is usually either 25, 465, or 587. Username and password refer to your credentials on the relay host.
In the current version of OS X Server (but not necessarily in older versions), Steps 1 and 3 should be done for you when you enable relaying and relay authentication in the Server application.
1. If necessary, create or update the relayhost directive in
     /Library/Server/Mail/Config/postfix/main.cf
It should look like this:
     relayhost = [address]:port
2. Add these lines, above the section at the end that begins with the comment "# Mac OS X Server":
     smtp_sasl_security_options =
     smtp_tls_CAfile = /etc/certificates/relayhost.pem
     smtp_tls_session_cache_database = btree:$data_directory/smtp_tls_session_cache
     smtp_use_tls = yes
3. If it doesn't already exist, create the password file
     /Library/Server/Mail/Config/postfix/sasl/passwd
with this content:
     [address]:port
     username:password
Here address must match $relayhost.
Then create the password database:
sudo postmap /Library/Server/Mail/Config/postfix/sasl/passwd
This action creates the file
     /Library/Server/Mail/Config/postfix/sasl/passwd.db
The two password files should be readable by root only.
4. Create the file
     /etc/certificates/relayhost.pem
with the CA certificate(s) to be trusted for authentication of the remote host. You get those certificates from the service provider. If you can't find a link to download them, try this:
openssl s_client -connect address:port -showcerts < /dev/null | sed -n '/-BEGIN /,/-END /p' | sudo sh -c 'cat > /etc/certificates/relayhost.pem'
The command may produce an error message that isn't necessarily significant. For servers that use the older STARTTLS protocol, rather than straight TLS or SSL, this command may need to be modified.
5. Restart the Mail service.

Hello, relay access denied error

Hello, can someone help me with such thing: need to configure c170 as mail gateway for postfix. the thing is, i've done all the initial setup, set RAT to accept all emails for my domain and for other domains, as i use one interface deployment solution. I've put my postfix as relay host in HAT. Also i've put my host in smtp routes as for my domain and for all other domains too, so c170 must redirect outgoing messages to my postfix, but postfix tells Relay access denied. Did i miss something? or i just don't understand something? it would be great if postfix will send outgoing messages, rather than c170. Need advise. Thanks in advance.

HERE IS WHAT MY ESA SAYS:
Received Time:           17 Dec 2013 09:28:42 (GMT +02:00)
MID:           74842, 74841
Message Size:           856 (Bytes)
Subject:           123
Envelope Sender:           [email protected]
Envelope Recipients:           [email protected]
Message ID Header:           <[email protected]>
SMTP Auth User ID:           N/A
Attachment Attachments:           N/A
Sending Host Summary
Reverse DNS Hostname:           (unverified)
IP Address:           xx.xxx.xx.146
SBRS Score:           not enabled
Processing Details
           MAIL POLICY "OutgoingMail" MATCHED THESE RECIPIENTS: [email protected]
17 Dec 2013 09:28:42 (GMT +02:00)           Protocol SMTP interface Data 2 (IP xx.xxx.xx.147) on incoming connection (ICID 363238) from sender IP xx.xxx.xx.146. Reverse DNS host None verified no.
17 Dec 2013 09:28:42 (GMT +02:00)           (ICID 363238) RELAY sender group Incoming Relay match xx.xxx.xx.146 SBRS not enabled
17 Dec 2013 09:28:42 (GMT +02:00)           Start message 74841 on incoming connection (ICID 363238).
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 enqueued on incoming connection (ICID 363238) from [email protected].
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 on incoming connection (ICID 363238) added recipient ([email protected]).
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 on incoming relay (Postfix) missing header Received.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 contains message ID header '<[email protected]>'.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 original subject on injection: 123
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 (856 bytes) from [email protected] ready.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 matched per-recipient policy OutgoingMail for outbound mail policies.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74841 queued for delivery.
17 Dec 2013 09:28:42 (GMT +02:00)           SMTP delivery connection (DCID 41909) opened from Cisco IronPort interface xx.xxx.xx.147 to IP address xx.xxx.xx.146. on port 25.
17 Dec 2013 09:28:42 (GMT +02:00)           (DCID 41909) Delivery started for message 74841 to [email protected].
17 Dec 2013 09:28:42 (GMT +02:00)           (DCID 41909) Message 74841 bounce verification rewriting sender [email protected] to [email protected].
17 Dec 2013 09:28:42 (GMT +02:00)           (DCID 41909) Message 74841 to [email protected] bounced by destination server. Reason: 5.1.0 - Unknown address error ('554', ['5.7.1 <[email protected]>: Relay access denied'])
17 Dec 2013 09:28:42 (GMT +02:00)           Start message 74842 on incoming connection (ICID 0).
17 Dec 2013 09:28:42 (GMT +02:00)           A new message 74842 was generated to handle bounce of message 74841.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74842 enqueued on incoming connection (ICID 0) from .
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74842 on incoming connection (ICID 0) added recipient ([email protected]).
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74842 (1971 bytes) from ready.
17 Dec 2013 09:28:42 (GMT +02:00)           Message 74842 queued for delivery.
17 Dec 2013 09:28:42 (GMT +02:00)           SMTP delivery connection (DCID 41910) opened from Cisco IronPort interface xx.xxx.xx.147 to IP address xx.xxx.xx.146 on port 25.
17 Dec 2013 09:28:42 (GMT +02:00)           (DCID 41910) Delivery started for message 74842 to [email protected].
17 Dec 2013 09:28:43 (GMT +02:00)           (DCID 41910) Delivery details: Message 74842 sent to [email protected]
17 Dec 2013 09:28:43 (GMT +02:00)          Message 74842 to [email protected] received remote SMTP response '2.0.0 Ok: queued as E39B43807DF'.
HERE IS WHAT MY POSTFIX SAYS:
Dec 17 09:06:51 mail postfix/smtpd[18564]: connect from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:06:51 mail postfix/smtpd[18564]: NOQUEUE: reject: RCPT from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]: 554 5.7.1 <[email protected]>: Relay access denied; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=
Dec 17 09:06:51 mail postfix/smtpd[18568]: connect from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:06:51 mail postfix/smtpd[18568]: 8A90D3807E5: client=smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:06:51 mail postfix/cleanup[18569]: 8A90D3807E5: message-id=<[email protected]>
Dec 17 09:06:51 mail postfix/qmgr[2383]: 8A90D3807E5: from=<>, size=2553, nrcpt=1 (queue active)
Dec 17 09:06:51 mail postfix/local[18570]: 8A90D3807E5: to=<[email protected]>, relay=local, delay=0.08, delays=0.05/0.01/0/0.02, dsn=2.0.0, status=sent (delivered to mailbox)
Dec 17 09:06:51 mail postfix/qmgr[2383]: 8A90D3807E5: removed
Dec 17 09:06:56 mail postfix/smtpd[18564]: disconnect from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:06:56 mail postfix/smtpd[18568]: disconnect from smtp.xxxx.xxx.xx[xxx.xxx.xxx.147]
Dec 17 09:07:01 mail dovecot: pop3-login: Login: user=, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.146, mpid=18578, TLS
Dec 17 09:07:01 mail dovecot: pop3(test): Disconnected: Logged out top=0/0, retr=1/2651, del=0/17, size=34346
xx.xxx.xx.146 is ip of my postfix server. it is listed in relaylist. also it is listed in smtp routes for All other domains.

Relaying denied,on a multiple domain server

For legacy reason, we set up our Groupwsie with 2 domain, the old one and the new one. Groupwise accept email from both old and new adresses. The "default" domain is the new one, and outgoing emails are sent using the new domain.
When we try to use an internal multifonction printer that allow send-to-email, when we use the new addresses as destination, it says "Relaying denied", but it works using the old addresses.
It's not going thru any anti-spam, which only protect from the internet.
On the internal DNS, both domains are configured and point to the same server. Ex: groupwise.cegepgim.ca and groupwise.cgaspesie.qc.ca
Both domains have entries on the DNS as MX, with different priorities
Any idea why?

On 13.10.2011 11:36, crioux wrote:
>
> For legacy reason, we set up our Groupwsie with 2 domain, the old one
> and the new one. Groupwise accept email from both old and new adresses.
> When we try to use an internal multifonction printer that allow
> send-to-email, when we use the new addresses as destination, it says
> "Relaying denied", but it works using the old addresses.
That makes no sense I'm afraid. Either your GWIA accepts mails to the
new domain, or it doesn't. There is *zero* difference between every
other internet mail (which you say works), and mail coming from your
printer. It's indistinguishible for the GWIA.
That said, and considering you *do* have another frontend server
forwarding internet mail to your GWIA, whereas for the printer, GWIA
receives directly, the only explanation I can come up with is that your
GWIA does *not* know the new domain, but your relay host in front of it
modifies all incoming mail and sent it to the old domain in reality in
the SMTP "rcpt to" command.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

RAID Connection Causing Mail Relay Start??

Greetings,
I have an interesting problem, and I'm cross-posting it to the Mail forum as well as the RAID forum. I have a client with an XServe running OS X 10.5.5 with a Fibre Channel and XSAN. The issue is whenever there's a fibre disconnect error on the RAID, for some reason, the "Relay outgoing mail through host" section of SMTP checks on, and, since there's no setting in there, e-mail doesn't go out. If anyone can assist in ideas on where to start, that would be awesome. Thank you.

I guess I should clarify a bit.
When the RAID disconnects, there's a brief period of time where the mail server fails to actively send mail out and it adds the relay outgoing mail to host option in the mail server configuration/main.cf. We've removed the setting through the GUI, and also directly through the main.cf file to attempt to resolve the issue. However, every time the RAID errors out, the mail server adds the setting back in.
What is happening is that the mail server cannot send the mail from localhost/hostname and adds the default outgoing mail server name to the main.cf file as a relay host. In turn, this attempts to relay mail back through the localhost which is identified by the name added as the relay host. This creates an endless loop and there's not way to get notification of this except that mail isn't being received by those to whom we are trying to send messages. So, essentially, our mail server is timing out, adding a relay host that loops back to itself, and is stopping all mail delivery services for outgoing messages. This is only affecting SMTP. There are no duplicate configuration files, and this is a fresh install of 10.5.5 Server.
Any help would be awesome.

Mail relay server specifying a port...

Hi,
The advanced server guide says you should be anle to specify a port .. ie.. myserver:587 in the dialog box.
Dialog box says Formatting error invalid value.
I use the Dyn mailforwarding service .. or i did till the latest upgrade broke it.
Does anyone know of a fix? .. I assume it will mean editing the postfix files .. that no doubt the next upgrade will break again.
Thanks in advance.

You have to edit the configuration using the command line; Server.app lost the ability to handle the outbound SMTP relay otherwise.
sudo serveradmin settings mail
You're after the relayhost setting (the following is from a generic setup, you'll want to set the host name via the GUI then check the output here, and add the port to the relayhost specification:
$ sudo serveradmin settings mail | grep -i relay
mail:postfix:smtp_auth_relay_dict:smtp_auth_relay_userid = ""
mail:postfix:smtp_auth_relay_dict:smtp_auth_relay_pwd = ""
mail:postfix:smtp_auth_relay_dict:smtp_auth_relay_host = ""
mail:postfix:luser_relay_enabled = no
mail:postfix:relayhost = ""
mail:postfix:relayhost_enabled = no
mail:imap:lmtp_luser_relay_enabled = no
mail:imap:lmtp_luser_relay = ""
$
Once edited, you'll end up with something like this:
mail:postfix:relayhost = "mail.example.com:587"
Where you've entered your relay host and port. See this thread (for the Postfix-level path to this data and for some background, I'd generally use serveradmin here and not the Postfix-level access) and see this Krypted article for some more details on the setup and commands available here.
You can use postconf -n /Library/Server/Mail/Config/postfix to verify that the changes have been implemented, and here's a similar discussion of the lower-level path into this same general area.

Sonicwall DHCP relay not working

I recently set up a new vlan and am trying to get the dhcp server on the existing vlan to issue IPs. I have no trouble getting dhcp working with the sonicwall as the server, but I can't get it to pass it along to the actual server. I've set up the IP of the server as a trusted DHCP relay host but I don't see anything in the logs for the relay for the test host on the vlan. I tagged the port the server is connected to for the new vlan so I'm lost as to why it isn't working. DNS also isn't working using that server for the lookup. I am able to ping it by IP though. I'm sure it's something simple I'm missing but vlans are new to me so I'm still learning.
This topic first appeared in the Spiceworks Community

I recently set up a new vlan and am trying to get the dhcp server on the existing vlan to issue IPs. I have no trouble getting dhcp working with the sonicwall as the server, but I can't get it to pass it along to the actual server. I've set up the IP of the server as a trusted DHCP relay host but I don't see anything in the logs for the relay for the test host on the vlan. I tagged the port the server is connected to for the new vlan so I'm lost as to why it isn't working. DNS also isn't working using that server for the lookup. I am able to ping it by IP though. I'm sure it's something simple I'm missing but vlans are new to me so I'm still learning.
This topic first appeared in the Spiceworks Community

Relay Host

Similar Messages

Maybe you are looking for