I have just gone around in circles with both my hosting provider (which provides the e-mail for my domain name) and MailChannels, which provides the spam monitoring for them.
I have been seeing an increase in my outbound SMTP mail being flagged by MailChannels as spam, which generates a bounce message which forces me to click on a link within same to unflag the message in question for them to review and release. This is a huge inconvenience when outbound business-related mails are delayed by the spam filters at MailChannels.
They are now trying (in vain) to convince me to abandon Eudora and either use a RFC5322-complaint mail client or webmail. I have told them in no uncertain terms that any such suggestion is a non-starter, because in addition to my own domain, I also check a personal legacy e-mail address (going back to the 1990s under Pacific Bell Internet!) as well as a GMail backup address that is used for accounts that have "hiccups" with the legacy address, plus an address at a non-profit that i do volunteer work for. Eudora has worked perfectly for handling all of the addresses all in one place ... and that's why I have been using it ever since the days when the Pacific Bell address was the only domain I got e-mail from.
What I have been able to discern from the various e-mail exchanges in which it is implied that this is all my fault for not using what they want me to use for mail is that the "Message-ID" field in the outgoing mail header is not compliant with the RFC 5322 standard, and that is what causes their filters to believe my messages are spam. They have -- in language bordering on threatening (even though, being an outsourced tech support organization, is populated by people with names like Raneesh and Sarath who "kindly" ask me to do what they tell me to -- said that my messages are going to be increasingly likely to be triggered if I don't either follow orders or do something about the header.
I've had Eudora long enough to know that Message-ID is not something in the user-configurable settings. They tell me that Eudora inserts something like "1rcgb1-0008Ol-1G" as the Message-ID but that a RFC 5322-compliant format for same is formatted more like "unique_string@domain.com".
It appears to me that since this is some increasingly enforced protocol, all Eudora users are going to come up against it if we can't somehow apply a patch that would take that existing ID string and add the domain name information to create a compliant header on outgoing mail.
This needs to be addressed fairly quickly or there's going to be little reason to keep Eudora alive.
Last edit: K.M. Richards 2024-02-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fixing up MessageIDs is something I have had on the to-do list for Aurora for a long time. Doing the task is not a big deal and I have let it linger only because there has appeared to be little demand for it. After your posting, I will make it a priority.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please download XXXXXXXX. This is the latest alpha-test version of Aurora. Please read the instructions and install as directed. And you will have a Message-ID header on every email you send.
(Confidential link removed. —Nick M.)
Last edit: Ted Matavka 2024-03-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Pete, I did not find any instructions in that zipfile ... no text files of ANY kind, in fact.
I'd also like to ask if there is a way to import my existing eudora.ini file into Aurora without having to look up every single entry in it for configuration. As I pointed out at the outset, I have multiple e-mail addresses and domains, and anything that simplifies the transition would be helpful.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are indeed no text files. What you should use is either Alpha.chm (which is a Windows help file) or Alpha_Help.exe (which is an e-book). The contents of the two are the same.
The first time you run it, Aurora will make a copy of you Eudora.ini as Aurora.ini which it will then use instead. So there is no configuring that you have to do at the transition.
You can move back and forth between Eudora and Aurora although with only one running at any time. If you make changes in your settings in one .ini they will not be automatically carried over so if you wish a change to affect both then you should make it in each. As long as you are using both clients it would be wise not to create any new Personas or delete any.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Fair enough, Pete. I misinterpreted your directions to "read the instructions and install as directed" to mean there was separate documentation in the zipfile for same. It honestly never occurred to me to look in the .chm file! (bangs head against wall)
I am going to presume, based on what you said about the .ini file, that Aurora will act the same as Eudora in terms of displaying any mailboxes if I copy the .mbx and .toc files over, including mailboxes nested in folders in the existing Eudora directory. Same goes for the nickname files (NNdbase.toc and .txt). If I'm wrong, please correct me.
I won't get to this until Wednesday anyway, as I want to make sure I have a window of time clear of other matters so as to concentrate on this 100%.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh dear, I have evidently not made things clear enough. Sorry. Eudora and Aurora will each have a private, independent .ini file but they will share everything else (.toc, .fld, .mbx and .pce files). There is no need for you to copy any part of your existing Eudora data.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have just gone around in circles with both my hosting provider (which provides the e-mail for my domain name) and MailChannels, which provides the spam monitoring for them.
I have been seeing an increase in my outbound SMTP mail being flagged by MailChannels as spam, which generates a bounce message which forces me to click on a link within same to unflag the message in question for them to review and release. This is a huge inconvenience when outbound business-related mails are delayed by the spam filters at MailChannels.
They are now trying (in vain) to convince me to abandon Eudora and either use a RFC5322-complaint mail client or webmail. I have told them in no uncertain terms that any such suggestion is a non-starter, because in addition to my own domain, I also check a personal legacy e-mail address (going back to the 1990s under Pacific Bell Internet!) as well as a GMail backup address that is used for accounts that have "hiccups" with the legacy address, plus an address at a non-profit that i do volunteer work for. Eudora has worked perfectly for handling all of the addresses all in one place ... and that's why I have been using it ever since the days when the Pacific Bell address was the only domain I got e-mail from.
What I have been able to discern from the various e-mail exchanges in which it is implied that this is all my fault for not using what they want me to use for mail is that the "Message-ID" field in the outgoing mail header is not compliant with the RFC 5322 standard, and that is what causes their filters to believe my messages are spam. They have -- in language bordering on threatening (even though, being an outsourced tech support organization, is populated by people with names like Raneesh and Sarath who "kindly" ask me to do what they tell me to -- said that my messages are going to be increasingly likely to be triggered if I don't either follow orders or do something about the header.
I've had Eudora long enough to know that Message-ID is not something in the user-configurable settings. They tell me that Eudora inserts something like "1rcgb1-0008Ol-1G" as the Message-ID but that a RFC 5322-compliant format for same is formatted more like "unique_string@domain.com".
It appears to me that since this is some increasingly enforced protocol, all Eudora users are going to come up against it if we can't somehow apply a patch that would take that existing ID string and add the domain name information to create a compliant header on outgoing mail.
This needs to be addressed fairly quickly or there's going to be little reason to keep Eudora alive.
Last edit: K.M. Richards 2024-02-26
Fixing up MessageIDs is something I have had on the to-do list for Aurora for a long time. Doing the task is not a big deal and I have let it linger only because there has appeared to be little demand for it. After your posting, I will make it a priority.
That would be very much appreciated and would earn you a decent donation for the project, Pete.
Please download XXXXXXXX. This is the latest alpha-test version of Aurora. Please read the instructions and install as directed. And you will have a Message-ID header on every email you send.
(Confidential link removed. —Nick M.)
Last edit: Ted Matavka 2024-03-04
Pete, I did not find any instructions in that zipfile ... no text files of ANY kind, in fact.
I'd also like to ask if there is a way to import my existing eudora.ini file into Aurora without having to look up every single entry in it for configuration. As I pointed out at the outset, I have multiple e-mail addresses and domains, and anything that simplifies the transition would be helpful.
There are indeed no text files. What you should use is either Alpha.chm (which is a Windows help file) or Alpha_Help.exe (which is an e-book). The contents of the two are the same.
The first time you run it, Aurora will make a copy of you Eudora.ini as Aurora.ini which it will then use instead. So there is no configuring that you have to do at the transition.
You can move back and forth between Eudora and Aurora although with only one running at any time. If you make changes in your settings in one .ini they will not be automatically carried over so if you wish a change to affect both then you should make it in each. As long as you are using both clients it would be wise not to create any new Personas or delete any.
Fair enough, Pete. I misinterpreted your directions to "read the instructions and install as directed" to mean there was separate documentation in the zipfile for same. It honestly never occurred to me to look in the .chm file! (bangs head against wall)
I am going to presume, based on what you said about the .ini file, that Aurora will act the same as Eudora in terms of displaying any mailboxes if I copy the .mbx and .toc files over, including mailboxes nested in folders in the existing Eudora directory. Same goes for the nickname files (NNdbase.toc and .txt). If I'm wrong, please correct me.
I won't get to this until Wednesday anyway, as I want to make sure I have a window of time clear of other matters so as to concentrate on this 100%.
Oh dear, I have evidently not made things clear enough. Sorry. Eudora and Aurora will each have a private, independent .ini file but they will share everything else (.toc, .fld, .mbx and .pce files). There is no need for you to copy any part of your existing Eudora data.
Even better (and a heckuva lot easier). Thanks.