SPF record: not found for host

2023-06-21 Thread Günter Paul
Hi,

I'm using the spf-mailet now and test it. I found this warning in the log file:
"No SPF record found for host: googlemail.com"

So I checked "googlemail.com" by mxtoolbox.com
DNS-Record: v=spf1 redirect=_spf.google.com

The Tool found not any problems. Somebody know about such problems or a 
solution?

Best wishes

Günter

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



Re: SPF record: not found for host

2023-06-21 Thread David Matthews
>I'm using the spf-mailet now and test it. I found this warning in the log file:
>"No SPF record found for host: googlemail.com"
>
>So I checked "googlemail.com" by mxtoolbox.com
>DNS-Record: v=spf1 redirect=_spf.google.com

Obvious things first - does your setup deal with SPF records for other domains 
without problem?

If so join the gmail sucks club.

I use gmail as a test sender/recipient for my mail server. I go back a couple 
of years now - I noticed that gmail was failing my SPF record, despite it 
definitely being correct. Since it was still delivering my test mails to Inbox 
rather than junk, I just left it. 

Then it started to put mail in junk folders - good job I noticed.

It did not like my SPFv6 record, despite it being correct, despite mxtoolbox 
saying it was correct, despite the authoritative DNS server saying it was 
correct and every other DNS server I thought to check. Even the gmail DNS 
servers thought it was correct. Go figure that one :-)

Since I have a /64, I pragmatically brought up the v6 address gmail thought I 
should have and adjusted my records - just to make gmail happy and stop binning 
test mails and email to friends unfortunate enough to be relying on gmail.

It has solved the problem, but you seem to have a different one. To complete my 
story, it's likely that the record gmail wanted to see (and now does) had been 
in use before. For most people DNS changes update in lets say 24 hours, but for 
gmail it seems to take a couple of years :-)

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


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



Re: SPF record: not found for host

2023-06-21 Thread Günter Paul
Hi David,

That's ironic: because of a hint from my provider to set up SPF to be on the 
safe side (because of Google!), I dealt with the topic. 

And now, of all people, should Google not be configured properly? It would be 
possible.

The warning isn't really a problem, I can receive and send emails from Google. 
But I have to evaluateare this warnings. 

And yes, by other domains all works fine.

Best wishes

Günter

> Obvious things first - does your setup deal with SPF records for other 
> domains without problem?
> 
> If so join the gmail sucks club.
> 
> I use gmail as a test sender/recipient for my mail server. I go back a couple 
> of years now - I noticed that gmail was failing my SPF record, despite it 
> definitely being correct. Since it was still delivering my test mails to 
> Inbox rather than junk, I just left it. 
> 
> Then it started to put mail in junk folders - good job I noticed.
> 
> It did not like my SPFv6 record, despite it being correct, despite mxtoolbox 
> saying it was correct, despite the authoritative DNS server saying it was 
> correct and every other DNS server I thought to check. Even the gmail DNS 
> servers thought it was correct. Go figure that one :-)
> 
> Since I have a /64, I pragmatically brought up the v6 address gmail thought I 
> should have and adjusted my records - just to make gmail happy and stop 
> binning test mails and email to friends unfortunate enough to be relying on 
> gmail.
> 
> It has solved the problem, but you seem to have a different one. To complete 
> my story, it's likely that the record gmail wanted to see (and now does) had 
> been in use before. For most people DNS changes update in lets say 24 hours, 
> but for gmail it seems to take a couple of years :-)
> 
> --
> David Matthews
> m...@dmatthews.org
> 
> 
> -
> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
> For additional commands, e-mail: server-user-h...@james.apache.org

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



Re: SPF record: not found for host

2023-06-21 Thread Günter Paul
Hi David,

That's ironic: because of a hint from my provider to set up SPF to be on the 
safe side (because of Google!), I dealt with the topic. 

And now, of all people, should Google not be configured properly? It would be 
possible.

The warning isn't really a problem, I can receive and send emails from Google. 
But I have to evaluateare this warnings. 

And yes, by other domains all works fine.

Best wishes

Günter

> Obvious things first - does your setup deal with SPF records for other 
> domains without problem?
> 
> If so join the gmail sucks club.
> 
> I use gmail as a test sender/recipient for my mail server. I go back a couple 
> of years now - I noticed that gmail was failing my SPF record, despite it 
> definitely being correct. Since it was still delivering my test mails to 
> Inbox rather than junk, I just left it. 
> 
> Then it started to put mail in junk folders - good job I noticed.
> 
> It did not like my SPFv6 record, despite it being correct, despite mxtoolbox 
> saying it was correct, despite the authoritative DNS server saying it was 
> correct and every other DNS server I thought to check. Even the gmail DNS 
> servers thought it was correct. Go figure that one :-)
> 
> Since I have a /64, I pragmatically brought up the v6 address gmail thought I 
> should have and adjusted my records - just to make gmail happy and stop 
> binning test mails and email to friends unfortunate enough to be relying on 
> gmail.
> 
> It has solved the problem, but you seem to have a different one. To complete 
> my story, it's likely that the record gmail wanted to see (and now does) had 
> been in use before. For most people DNS changes update in lets say 24 hours, 
> but for gmail it seems to take a couple of years :-)
> 
> --
> David Matthews
> m...@dmatthews.org
> 
> 
> -
> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
> For additional commands, e-mail: server-user-h...@james.apache.org

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



Re: SPF record: not found for host

2023-06-21 Thread Günter Paul
Hi,

> And yes, by other domains all works fine.

sorry, after wrote, the next problem with "myfritz.net":

DNS: v=spf1 ip4:212.42.244.0/24 ip6:2001:bf0:244::/48  -all

I think it's a james-problem.

The problems is with incoming mails, I recieve the mails an can read it without 
problems.

Best wishes

Günter

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



Re: SPF record: not found for host

2023-06-21 Thread David Matthews
hi Gunter

>And yes, by other domains all works fine.

Google sucks :-)

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


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



It's not possible to create folder which name starts with hash-sign (#)

2023-06-21 Thread Wojtek

Hi,
I ran into an issue when importing mails from other servers - it seems that it's not possible to 
create folder which name starts with hash-sign, e.g.: "#testfolder".


I tested other mail servers (gmail, mailu [postfix?], fastmail [cyrrus?], mailbox.org, infomaniak 
[no idea what they use]) and all of them allowed folder names starting with "#".



```
A4 CREATE #hashtest
A4 NO CREATE You can not access a mailbox that does not belong to you
```

Looking at the spec (https://datatracker.ietf.org/doc/html/rfc3501#section-5.1) it seems that `#` 
can have special meaning and could be used to denote namespaces.


Is it a configurable option (i.e. is it possible to disable namespaces/shared mailboxes or some 
such) that would result in James allowing mailboxes starting with `#`?


--
Wojtek

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



Re: It's not possible to create folder which name starts with hash-sign (#)

2023-06-21 Thread Benoit TELLIER
Hello Wojtek,

That is because James employs a folder hierarchy where '#' is used to denote a 
namespace.

#private:wojtek:INBOX denotes your inbox on which I would have a shared access.
#shared:marketting:INBOX denotes a shared mailbox for the marketting team.

I bet you could do: #private:wojtek:#hashtest ?

That being said, james have no support for accessing shared mailboxes in IMAP 
just quite yet. The usefulness of that addressing scheme is thus limited.

IMO we could:
 - Drop the #namespace:user:mailbox addressing sheme in IMAP as it is not 
currently in use...
 - Or (lighter) if we can't parse a mailbox path (no : after #) then keep the 
name as is, IE support #hashtest
 - Review and adopt another addressing sheme that matches those of eg cyrus.

--


Best regards,



Benoit TELLIER



General manager of Linagora VIETNAM.

Product owner for Team-Mail product.

Chairman of the Apache James project.



Mail: btell...@linagora.com

Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)

On Jun 22, 2023 9:10 AM, from Wojtek Hi,
I ran into an issue when importing mails from other servers - it seems that 
it's not possible to
create folder which name starts with hash-sign, e.g.: "#testfolder".

I tested other mail servers (gmail, mailu [postfix?], fastmail [cyrrus?], 
mailbox.org, infomaniak
[no idea what they use]) and all of them allowed folder names starting with "#".


```
A4 CREATE #hashtest
A4 NO CREATE You can not access a mailbox that does not belong to you
```

Looking at the spec (https://datatracker.ietf.org/doc/html/rfc3501#section-5.1) 
it seems that `#`
can have special meaning and could be used to denote namespaces.

Is it a configurable option (i.e. is it possible to disable namespaces/shared 
mailboxes or some
such) that would result in James allowing mailboxes starting with `#`?

--
Wojtek

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




Re: It's not possible to create folder which name starts with hash-sign (#)

2023-06-21 Thread Benoit TELLIER
By the way https://www.rfc-editor.org/rfc/rfc3501#section-5.1

   5)Two characters, "#" and "&", have meanings by convention, and
 should be avoided except when used in that convention.--


Best regards,



Benoit TELLIER



General manager of Linagora VIETNAM.

Product owner for Team-Mail product.

Chairman of the Apache James project.



Mail: btell...@linagora.com

Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)

On Jun 22, 2023 12:32 PM, from Benoit Tellier Hello Wojtek,

That is because James employs a folder hierarchy where '#' is used to denote a 
namespace.

#private:wojtek:INBOX denotes your inbox on which I would have a shared access.
#shared:marketting:INBOX denotes a shared mailbox for the marketting team.

I bet you could do: #private:wojtek:#hashtest ?

That being said, james have no support for accessing shared mailboxes in IMAP 
just quite yet. The usefulness of that addressing scheme is thus limited.

IMO we could:
 - Drop the #namespace:user:mailbox addressing sheme in IMAP as it is not 
currently in use...
 - Or (lighter) if we can't parse a mailbox path (no : after #) then keep the 
name as is, IE support #hashtest
 - Review and adopt another addressing sheme that matches those of eg cyrus.

--


Best regards,



Benoit TELLIER



General manager of Linagora VIETNAM.

Product owner for Team-Mail product.

Chairman of the Apache James project.



Mail: btell...@linagora.com

Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)

On Jun 22, 2023 9:10 AM, from Wojtek Hi,
I ran into an issue when importing mails from other servers - it seems that 
it's not possible to
create folder which name starts with hash-sign, e.g.: "#testfolder".

I tested other mail servers (gmail, mailu [postfix?], fastmail [cyrrus?], 
mailbox.org, infomaniak
[no idea what they use]) and all of them allowed folder names starting with "#".


```
A4 CREATE #hashtest
A4 NO CREATE You can not access a mailbox that does not belong to you
```

Looking at the spec (https://datatracker.ietf.org/doc/html/rfc3501#section-5.1) 
it seems that `#`
can have special meaning and could be used to denote namespaces.

Is it a configurable option (i.e. is it possible to disable namespaces/shared 
mailboxes or some
such) that would result in James allowing mailboxes starting with `#`?

--
Wojtek

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




Re: TLS protocol versions - defaults for all listeners/mail protocols?

2023-06-21 Thread Benoit TELLIER

Hello Wojtek,

On 21/06/2023 10:44, Wojtek wrote:

Hi,
Is there a way to configure list of default TLS protocols for all 
enabled listeners instead of modifying configuration file for each one 
(i.e. ``)?

I think we have no such things like default value accross all protocols.

Maybe we as a project can come up with better defaults here? EG TLSV2 + 
V3 so that users are less in need to configure this?


sslcontext-kickstart does seem to have support for `https.protocols` 
property, but it looks like it's not used in James?



May I ask for a link?

Best regards,

Benoit

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