You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Sean McElroy <Se...@sita.aero> on 2021/12/09 09:33:04 UTC

apache/james:demo-3.6.0

Hello,

I am trying to use the apache/james:demo-3.6.0 docker image but I cannot send a message via SMTP.
This is the error I am getting:

javax.mail.SendFailedException: Invalid Addresses;  nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 530 5.7.1 Authentication Required

I have tried several of the available docker images but I get the same error.

Can you tell me what I am doing wrong?

I am using Spring Boot and I am using user01@james.local, which is one of the default users created by this docker image.

This is my mail configuration:

  mail:
    host: localhost
    port: 25
    properties.mail.smtp.auth: false
    properties.mail.smtp.starttls.enable: false
    properties.mail.imap.host: localhost
    properties.mail.imap.port: 143
    properties.mail.imap.starttls.enable: false



Many thanks,
Sean
Confidential Communication: The contents of this e-mail including any attachment are confidential and intended solely for the person(s) to whom they are addressed. Any reader of this email who is not the intended recipient is notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately and delete all copies from your computer system. Subsequent alterations to this email after its transmission will be disregarded.

Re: apache/james:demo-3.6.0

Posted by "btellier@apache.org" <bt...@apache.org>.
Hello David!

Thanks for pointing DMarc out!

That would be great if someone find a bit of time to have a quick write
up on how to setup DMarc with James. Also it could be great to have
integrations for James retrieving, understanding, and complying with
DMarc policies.

Best regards,

Benoit TELLIER

On 10/12/2021 16:22, David Matthews wrote:
>> Hello Sean,
>>
>> Email trust is definitely a complicated thing. Getting third party
>> accepting your emails is a complex task [1]. To send emails to (say)
>> Gmail, you would need to buy a domain, register you MXs, set up
>> scertificates, battle with DKIM and SPF, etc...
>>
>> [1] https://james.apache.org/howTo/spf.html
>> https://james.apache.org/howTo/dkim.html
> I'd add to that DMARC, which as far as I can make out is a pointless addition to the fight against spammers, unlike DKIM & SPF. I'd agree they are a bit of a pain to set up, especially DKIM, but at least I see the sense in them in addition to actually getting your email delivered to an inbox rather than junk.
>
> An alternative read at
>
> https://dmatthews.org/email_auth.html
>
> covers similar ground
>
> --
> David Matthews
> mail@dmatthews.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: apache/james:demo-3.6.0

Posted by Felix Ingram <f....@gmail.com>.
I saw this article  in my feeds the other day. With a read: https://ploum.net/the-monstrosity-email-has-become/

Felix
________________________________
From: David Matthews <ma...@dmatthews.org.INVALID>
Sent: Friday, December 10, 2021 3:16 pm
To: James Users List
Subject: Re: apache/james:demo-3.6.0

hi Benoit
>
>Thanks for pointing DMarc out!
>
>That would be great if someone find a bit of time to have a quick write
>up on how to setup DMarc with James. Also it could be great to have
>integrations for James retrieving, understanding, and complying with
>DMarc policies.

It's not really a James issue at least not in the sense that you're wanting to get your email into an inbox rather than a spam folder. Rather it's a DNS issue, as with SPF - you just need an appropriate text record. DKIM differs, in that it's a two part thing, you need a public key in your DNS, but also James must sign the email with the appropriate private key.

If you wanted to check the DMARC of incoming mail, then it would become a James issue, but I don't believe it's worth the pain as checking an online blocklist is straight forward and adequate on it's own - maybe with a bit of spamassassin as backup.

Didn't the write ups you linked originate from my own one? Months/a year ago someone from the James community asked me if they could base something on them. I said I was entirely happy for that and remain entirely happy if that was done and if you want to add a DMARC article based on what's  at dmatthews.org, just go ahead.

I should say that my James foo is out of date as after investigating it, I decided to stick with exim4 as the devil I know being better than the devil I don't. As I've already said though, for SPF and DMARC, it makes no difference if your fighting with James/exim4/postfix etc - these are DNS issues rather mail exchanger issues.

Incidentally, if anyone can explain to me why DMARC, which seems to just duplicate DKIM and SPF, is not a stupid technology, I'd be pleased to read that

--
David Matthews
mail@dmatthews.org


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: apache/james:demo-3.6.0

Posted by David Matthews <ma...@dmatthews.org.INVALID>.
>I saw this article  in my feeds the other day. With a read: https://ploum.net/the-monstrosity-email-has-become/
>

Interesting article, but I would forcible argue that despite having to contend with legacy tech (actually your mail exchanger does that for you) and various hoops to jump through, including DMARC, SPF & DKIM, running your own email server from an always on machine (ie not one behind a home broadband connection) remains eminently doable.

I've not found it anything like so trying to reduce unwanted email to close to nothing as that author describes. Non tech people I know with accounts at gmail, hotmail etc tell me they also get much less spam that they used to. 

However, I suspect the network remains awash with the rubbish; it's not delivered due to everyone being forced to implement SPF and DKIM and using online blocklists. It is still being sent though, by the unscrupulous spammers, who don't tell their unscrupulous customers that although they send out their crap as per contract, no one gets it in an inbox.

--
David Matthews
mail@dmatthews.org


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: apache/james:demo-3.6.0

Posted by David Matthews <ma...@dmatthews.org.INVALID>.
hi Benoit
>
>Thanks for pointing DMarc out!
>
>That would be great if someone find a bit of time to have a quick write
>up on how to setup DMarc with James. Also it could be great to have
>integrations for James retrieving, understanding, and complying with
>DMarc policies.

It's not really a James issue at least not in the sense that you're wanting to get your email into an inbox rather than a spam folder. Rather it's a DNS issue, as with SPF - you just need an appropriate text record. DKIM differs, in that it's a two part thing, you need a public key in your DNS, but also James must sign the email with the appropriate private key.

If you wanted to check the DMARC of incoming mail, then it would become a James issue, but I don't believe it's worth the pain as checking an online blocklist is straight forward and adequate on it's own - maybe with a bit of spamassassin as backup.

Didn't the write ups you linked originate from my own one? Months/a year ago someone from the James community asked me if they could base something on them. I said I was entirely happy for that and remain entirely happy if that was done and if you want to add a DMARC article based on what's  at dmatthews.org, just go ahead.

I should say that my James foo is out of date as after investigating it, I decided to stick with exim4 as the devil I know being better than the devil I don't. As I've already said though, for SPF and DMARC, it makes no difference if your fighting with James/exim4/postfix etc - these are DNS issues rather mail exchanger issues.

Incidentally, if anyone can explain to me why DMARC, which seems to just duplicate DKIM and SPF, is not a stupid technology, I'd be pleased to read that

--
David Matthews
mail@dmatthews.org


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


Re: apache/james:demo-3.6.0

Posted by David Matthews <ma...@dmatthews.org.INVALID>.
>Hello Sean,
>
>Email trust is definitely a complicated thing. Getting third party
>accepting your emails is a complex task [1]. To send emails to (say)
>Gmail, you would need to buy a domain, register you MXs, set up
>scertificates, battle with DKIM and SPF, etc...
>
>[1] https://james.apache.org/howTo/spf.html
>https://james.apache.org/howTo/dkim.html

I'd add to that DMARC, which as far as I can make out is a pointless addition to the fight against spammers, unlike DKIM & SPF. I'd agree they are a bit of a pain to set up, especially DKIM, but at least I see the sense in them in addition to actually getting your email delivered to an inbox rather than junk.

An alternative read at

https://dmatthews.org/email_auth.html

covers similar ground

--
David Matthews
mail@dmatthews.org


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org