List <"List"> is not a valid e-mail address because it is not of the form user@host.
This problem showed up again recently. I'm on OpenSuSE and when I upgraded to 38.1 or 38.2, this problem occurs. Backing off to the previous version available (31.7) and I'm able to send fine.
This is at least the third time I've encountered this problem over several years. Could this be added somehow as a regression test before releasing a new version? And fix the problem in 38.2? I see that 38.3 has been released, but it's not yet available as an OpenSuSE package. I'll install it when it becomes available in the next couple days.
All Replies (8)
re :List <"List">
can you confirm that the name of your Mailing list is:- List
If the name of your mailing list is contructed using two words eg: My List then the space may be causing the issue, so instead rename it to either: MyList (no spaces) or My_List (using underscore).
If it is called just:- List Please make sure there is no hidden spaces either at the start or at the end of the name.
Please report back on results or additional info.
I sanitized my question. In actuality, the names of almost all of my lists DO include spaces. They are automatically generated (I create ldif files from a central data location) and they do not have special characters in them.
I will have investigate more and see if I can provide any additional information.
I am having a similar problem. It looks like TB is picking up entries in the description field as e-mail names. The description is any thing but valid e-mail addresses. I have screen shots of the error and of the address list
Hi vhradice could you perform three separate tests for me ?
First test: I notice that the Mailing list name is: ExtendedCoregroup
Could you test this: change the name so that the only capital letter is at the start. Thus: Extendedcoregroup
Do not change the description, as this test is specifically seeing if the issue is only with the Mailing List name. I have seen a recent report that an all one word name was rejected because it had a capital letter (other than first) in the name. So, I would appreciate some feedback to see if this is causing the issue in your case.
If this still fails then perform this test: Second test: Change name back to original : 'ExtendedCoregroup; (with capital letter) Please remove the description.
This test will see if the original Mailing list name is ok but the Description is causing an issue.
If this fails to work then perform the final test: Third test: Change name again - no capitals : 'Extendedcoregroup' Keep description empty.
This test will see if the Mailing list name without capitals is ok, but the Description was also causing an issue.
Please report back on the test results, so we can identify what is going on.
Gewysig op deur Toad-Hall
I have removed the description and it works. The list name still had the capital letter in the middle.
As a further test, I created a new list with several names in it. This worked. I then added a description and that also worked.
One thing I did notice was that the first name in the Description was Barb. In the error message it changed it to <Bar>. Does this help?
Many thanks for your feedback. Info very useful. Good to hear that all is now working ok.
It is not working right. If I put the description back (helps to know what the list is for), it fails again with the same error. Why is TB trying to use the description field when the list is used?
I've tested the description options and can agree with you. Something is definately not correct. Using a 'comma' seems to trigger the bug. I tested with a colon and it sent ok.
I've posted a bug on this and would be grateful if you could add your vote and comments, such as what OS you use, version of TB and also exactly what you are using in the Description field. You will need to register if not posted anything before. But, it helps if there is more than just me saying it is a bug.