Hello,

To be honest I was not expecting it to need anything else besides a MX Record.

The java exception on the other hand states the following :
jvm 1 | 30-Jun-2021 10:20:30.654 ERROR [RemoteDelivery-2] 
org.apache.james.dnsservice.library.MXHostAddressIterator.<init>:79 - Couldn't 
resolve IP address for discovered host smtpxxx.xxxx.com. Seems to me that the 
RemoteDelivery class is looking for an ip address for smtpxxx.xxxx.com and 
treat it as an A Record. Where as all it is the following

$host smtpxxx.xxxx.com
smtpxxx.xxxx.com mail is handled by 10 sinxxx.xxx.com.
smtpxxx.xxxx.com mail is handled by 10 sinyyy.yyy.com.
smtpxxx.xxxx.com mail is handled by 10 frayyy.yyy.com.
smtpxxx.xxxx.com mail is handled by 10 fraxxx.xxx.com.

All my usecase is

Application running in a container ---> ApacheJames Running in a separated 
container ( MTA ) ------> SMTP gateway (exposed through MX Records)

Amlan



On 30/06/2021, 16:43, "David Matthews" <m...@dmatthews.org.INVALID> wrote:

    hi Amlan

    Why do you think any SMTP server needs anything other than an MX record?

    OK Some TXT records for dkim, spf and dmarc, but why an A record?

    I doubt that I properly understand your use case and since James itself 
does SMTP, I don't follow why you talk about connecting to an smtp provider 
with your own James instance.

    I'm out of date with James now, but did do a write up with config changes, 
as much as for my own future reference as for anyone else. I'm not sure if it 
will help you, but it's at

    https://dmatthews.org/java_email.html

    if you care to look.

    best wishes

    --
    David Matthews
    m...@dmatthews.org






---
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and delete this e-mail. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and 
regulatory disclosures and to 
http://www.db.com/unitedkingdom/content/privacy.htm for information about 
privacy.

Reply via email to