To confirm, should there be an "=" between SMTP_WELCOME_NAME and
"banner.xyz.com" in the .ini file? Should this line replace the normal
vdomain address="1.2.3.4" name="xyz.com" line in the .ini?
Thanks.
On 2011/01/27, at 6:59, SurgeMail Support wrote:
> I would not expect the banner to be related to delivery problems as
> it's only seen on incoming mail not outgoing., But you can set it
> for each domain using:
>
> vdomain name="xyz.com" ip="1.2.3.4"
> SMTP_WELCOME_NAME "banner.xyz.com"
>
> This only works for vdomains that have a specific ip address
> association.
>
> ChrisP
>
> On 20/01/2011 5:42 p.m., Admin wrote:
>>
>> I am running version 5.0e3 on Linux servers.
>>
>> The PTR, SPF, A name, and MX records are all correct.
>>
>> For the g_recieved_name setting, I have the FQDN.
>> The telnet banner still lists the vdomain name which is the MX domain
>> rather than the FQDN for the mail servers. The telnet banner lists
>> the
>> first vdomain name in the surgemail.ini file.
>>
>> I need to set the telnet banner to the FQDN for each mail server in
>> order to have mail delivered to many University mail servers.
>>
>> Thank you for your suggestions.
>>
>>
>> On 2011/01/20, at 11:21, Lyle Giese wrote:
>>
>>> What version of Surgemail are you running? And on what platform?
>>> That
>>> might be useful info.
>>>
>>> For all domains hosted here, outgoing email for them is sent from
>>> mail3.lcrcomputer.net(and I have well over 100 domains here). I am
>>> running mirrored servers here with this set:
>>>
>>> g_received_name "mail3.lcrcomputer.net"
>>>
>>> The host names are mail3a.lcrcomputer.net and mail3b.lcrcomputer.net
>>> and are behind a nat box. However the all banners are tagged
>>> mail3.lcrcomputer.net because of the above setting. The forward on
>>> the
>>> public IP address for this is mail3.lcrcomputer.net on ip address
>>> 209.172.152.5 and the reverse points back to mail3.lcrcomputer.net.
>>>
>>> What you are calling the telnet header is properly called the
>>> banner.
>>> The FQDN announced does not have to relate directly to the domain in
>>> the From address field. However the ip address reverse lookup
>>> needs to
>>> match the FQDN and the FQDN needs to have an A record that matches
>>> the
>>> IP address connecting to the other mail server and the FQDN needs to
>>> match the name announced in the banner.
>>>
>>> Again, the banner or FQDN does not have to relate directly to the
>>> domain in the From field in the email. However SPF records for the
>>> domain should list the IP address or FQDN of the sending mail server
>>> which should match the name announced in the banner.
>>>
>>> Lyle Giese
>>> LCR Computer Services, Inc.
>>>
>>> Admin wrote:
>>>> Hi Stephen,
>>>>
>>>> Yes, both domains have proper PTR records, reverse DNS and SPF
>>>> entries. Many universities, particularly in Europe, are checking
>>>> that
>>>> the telnet header matches the FQDN and rejecting if it does not.
>>>>
>>>> I seem to remember that in earlier versions of Surgemail that there
>>>> was a config setting that would allow admins to pre-set the webmail
>>>> log-in domain. Is that still a possibility? Any other ideas?
>>>>
>>>> Thanks,
>>>> Jamus
>>>>
>>>>
>>>>
>>>> On 2011/01/19, at 22:29, Stephen D. Goff wrote:
>>>>
>>>>> I run many virtuals and have never experienced this issue you are
>>>>> describing. Does your FQDN.org have a proper reverse entry in DNS
>>>>> (you didn’t provide the real name, so I couldn’t check it myself)?
>>>>> And do you have a proper SPF entry for both your domains that
>>>>> include the FQDN.org?
>>>>> *From:*Admin [mailtoHIDDEN@iodp-mi-sapporo.org]
>>>>> *Sent:*Wednesday, January 19, 2011 12:59 AM
>>>>> *To:*surgemailHIDDEN@etwinsite.com
>>>>> <mailto:surgemailHIDDEN@etwinsite.com>
>>>>> *Subject:*[SurgeMail List] telnet header domain, surgeweb domain
>>>>> and
>>>>> surgemail.ini configuration
>>>>>
>>>>> Hello,
>>>>>
>>>>> I have mirrored mail servers hosting 2 domains. I am having
>>>>> trouble
>>>>> with mail rejections from many recipients based on the telnet
>>>>> header
>>>>> not matching the FQDN for the mail servers. When I change the
>>>>> surgemail.ini file so that the vdomain name matches the FQDN for
>>>>> the
>>>>> server, the FQDN becomes the domain listed for Surgeweb login and
>>>>> users cannot login to Surgeweb.
>>>>>
>>>>> My surgemail.ini has the following lines:
>>>>> vdomain address="1xx.xxx.xxx.xx1" name="MXdomain.org" ---This
>>>>> works
>>>>> for Surgeweb but the Telnet banner is the MXdomain.org and the
>>>>> mail
>>>>> servers reject our mail.
>>>>>
>>>>> My surgemail.ini has the following lines:
>>>>> vdomain address="1xx.xxx.xxx.xx1" name="FQDN.org" ---This makes
>>>>> the
>>>>> Telnet banner match the FQDN, but users cannot log into Surgeweb
>>>>> because their login becomesHIDDEN@QDN.org <mailto:user@FQDN.org>
>>>>> ratherHIDDEN@er@MXdomain.org <mailto:user@MXdomain.org>.
>>>>>
>>>>>
>>>>> Any advice on how to correct this problem is greatly appreciated.
>>>>>
>>>>> Thank you.
>>>>
>>>
>>
>
>
|
