A problem has plagued me for a long time in Eudora. I'm able to download my Inbox, but not the separate "Junk Email" folder in Outlook.com using Eudora. Setting up filters on Outlook.com to move "Junk Email" to Inbox or moving mail manually is futile. I want a solution in Eudora to download mail straight from Outlook.com's "Junk Email" folder. How is this done? I'd be willing to implement something around this.
Thanks.
Last edit: Test 2019-11-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Doing what you want is easy in principle using IMAP. Eudora's implementation of IMAP is poor though and one of my own biggest wishes for Hermes is to improve it. Setting up filters to download specific folders might be a useful feature but I am not sure that we would want to go that far. A better approach may be to equip Hermes with an API that allows messages to be imported and exported (and this is, again, something I want to do anyway). Then independent tools could be developed to do such fancy and clever things without overloading Hermes itself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Doing what you want is easy in principle using IMAP. Eudora's
implementation of IMAP is poor though and one of my own biggest wishes for
Hermes is to improve it. Setting up filters to download specific folders
might be a useful feature but I am not sure that we would want to go that
far. A better approach may be to equip Hermes with an API that allows
messages to be imported and exported (and this is, again, something I want
to do anyway). Then independent tools could be developed to do such fancy
and clever things without overloading Hermes itself.
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
Short answer is I can't do this using POP3. Exchange Server support would be fun, but that may go beyond the scope of this project. Other third party e-mail clients include Exchange Server support.
From elsewhere:
The POP3 protocol works only with the main Inbox. POP3 is designed with the intention that email only resides on the server (in the Inbox) as a temporary holding place until download. The intent is that your email is stored on your local computer and organized by your email client (Outlook, Thunderbird, etc.) in some client-side database (file-based, relational database, or whatever).
To access other folders on the server, you would need to use the IMAP protocol. The intent of that protocol is the opposite -- that email is managed and stored long-term on the server. You would need to use the Chilkat IMAP API to select the Junk/SPAM folder and then read emails from it. Also, the specific name of the Junk/SPAM folder could be anything -- it depends on the IMAP mail server implementation. You may need to list mailboxes and then surmise which is the Junk folder based on the name. Also, mailboxes can have flags, and you can find the mailbox that has the "\Junk" flag.
For example, in RFC6154:
The new attributes defined here are as follows:
\All
This mailbox presents all messages in the user's message store.
Implementations MAY omit some messages, such as, perhaps, those
in \Trash and \Junk. When this special use is supported, it is
almost certain to represent a virtual mailbox.
\Archive
This mailbox is used to archive messages. The meaning of an
"archival" mailbox is server-dependent; typically, it will be
used to get messages out of the inbox, or otherwise keep them
out of the user's way, while still making them accessible.
\Drafts
This mailbox is used to hold draft messages -- typically,
messages that are being composed but have not yet been sent. In
some server implementations, this might be a virtual mailbox,
containing messages from other mailboxes that are marked with
the "\Draft" message flag. Alternatively, this might just be
advice that a client put drafts here.
\Flagged
This mailbox presents all messages marked in some way as
"important". When this special use is supported, it is likely
to represent a virtual mailbox collecting messages (from other
mailboxes) that are marked with the "\Flagged" message flag.
\Junk
This mailbox is where messages deemed to be junk mail are held.
Some server implementations might put messages here
automatically. Alternatively, this might just be advice to a
client-side spam filter.
\Sent
This mailbox is used to hold copies of messages that have been
sent. Some server implementations might put messages here
automatically. Alternatively, this might just be advice that a
client save sent messages here.
\Trash
This mailbox is used to hold messages that have been deleted or
marked for deletion. In some server implementations, this might
be a virtual mailbox, containing messages from other mailboxes
that are marked with the "\Deleted" message flag.
Alternatively, this might just be advice that a client that
chooses not to use the IMAP "\Deleted" model should use this as
its trash location. In server implementations that strictly
expect the IMAP "\Deleted" model, this special use is likely not
to be supported.
All of the above attributes are OPTIONAL, and any given server or
message store may support any combination of the attributes, or none
at all. In most cases, there will likely be at most one mailbox with
a given attribute for a given user, but in some server or message
store implementations it might be possible for multiple mailboxes to
have the same special-use attribute.
Last edit: Test 2019-11-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm only looking for a POP3 solution. Exchange Push e-mail would be great,
but well beyond scope of Eudora. I guess with the source code, I could
implement my solution, but don't want to commit time if others plan to
address. Also good to wait for a VS2015+ compatible solution.
There is WAY too much in there for us to address. If it's in any way
possible, please join the project, and contribute. This app has brought
experienced programmers to their knees when we had a human resource
shortage (i.e. in the early months). Many hands make light work.
Hi. Great work!
A problem has plagued me for a long time in Eudora. I'm able to download my Inbox, but not the separate "Junk Email" folder in Outlook.com using Eudora. Setting up filters on Outlook.com to move "Junk Email" to Inbox or moving mail manually is futile. I want a solution in Eudora to download mail straight from Outlook.com's "Junk Email" folder. How is this done? I'd be willing to implement something around this.
Thanks.
Last edit: Test 2019-11-23
Doing what you want is easy in principle using IMAP. Eudora's implementation of IMAP is poor though and one of my own biggest wishes for Hermes is to improve it. Setting up filters to download specific folders might be a useful feature but I am not sure that we would want to go that far. A better approach may be to equip Hermes with an API that allows messages to be imported and exported (and this is, again, something I want to do anyway). Then independent tools could be developed to do such fancy and clever things without overloading Hermes itself.
Perhaps one could crib the IMAP api from Trojita? That's a specialist,
IMAP-only e-mail client, so their IMAP implementation had better be good!
On Fri, 22 Nov 2019 at 09:42, Pete Maclean petemaclean@users.sourceforge.net wrote:
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
Short answer is I can't do this using POP3. Exchange Server support would be fun, but that may go beyond the scope of this project. Other third party e-mail clients include Exchange Server support.
From elsewhere:
The POP3 protocol works only with the main Inbox. POP3 is designed with the intention that email only resides on the server (in the Inbox) as a temporary holding place until download. The intent is that your email is stored on your local computer and organized by your email client (Outlook, Thunderbird, etc.) in some client-side database (file-based, relational database, or whatever).
To access other folders on the server, you would need to use the IMAP protocol. The intent of that protocol is the opposite -- that email is managed and stored long-term on the server. You would need to use the Chilkat IMAP API to select the Junk/SPAM folder and then read emails from it. Also, the specific name of the Junk/SPAM folder could be anything -- it depends on the IMAP mail server implementation. You may need to list mailboxes and then surmise which is the Junk folder based on the name. Also, mailboxes can have flags, and you can find the mailbox that has the "\Junk" flag.
For example, in RFC6154:
The new attributes defined here are as follows:
\All
This mailbox presents all messages in the user's message store.
Implementations MAY omit some messages, such as, perhaps, those
in \Trash and \Junk. When this special use is supported, it is
almost certain to represent a virtual mailbox.
\Archive
This mailbox is used to archive messages. The meaning of an
"archival" mailbox is server-dependent; typically, it will be
used to get messages out of the inbox, or otherwise keep them
out of the user's way, while still making them accessible.
\Drafts
This mailbox is used to hold draft messages -- typically,
messages that are being composed but have not yet been sent. In
some server implementations, this might be a virtual mailbox,
containing messages from other mailboxes that are marked with
the "\Draft" message flag. Alternatively, this might just be
advice that a client put drafts here.
\Flagged
This mailbox presents all messages marked in some way as
"important". When this special use is supported, it is likely
to represent a virtual mailbox collecting messages (from other
mailboxes) that are marked with the "\Flagged" message flag.
\Junk
This mailbox is where messages deemed to be junk mail are held.
Some server implementations might put messages here
automatically. Alternatively, this might just be advice to a
client-side spam filter.
\Sent
This mailbox is used to hold copies of messages that have been
sent. Some server implementations might put messages here
automatically. Alternatively, this might just be advice that a
client save sent messages here.
\Trash
This mailbox is used to hold messages that have been deleted or
marked for deletion. In some server implementations, this might
be a virtual mailbox, containing messages from other mailboxes
that are marked with the "\Deleted" message flag.
Alternatively, this might just be advice that a client that
chooses not to use the IMAP "\Deleted" model should use this as
its trash location. In server implementations that strictly
expect the IMAP "\Deleted" model, this special use is likely not
to be supported.
All of the above attributes are OPTIONAL, and any given server or
message store may support any combination of the attributes, or none
at all. In most cases, there will likely be at most one mailbox with
a given attribute for a given user, but in some server or message
store implementations it might be possible for multiple mailboxes to
have the same special-use attribute.
Last edit: Test 2019-11-23
On Sat, 23 Nov 2019 at 09:59, Test ttesty@users.sourceforge.net wrote:
There is WAY too much in there for us to address. If it's in any way
possible, please join the project, and contribute. This app has brought
experienced programmers to their knees when we had a human resource
shortage (i.e. in the early months). Many hands make light work.
It should be possible to interact with Junk Mail using Outlook MAPI (or more prefably, the Exchange API). Plenty of resources/sample code:
https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/how-to-create-a-simple-mail-item
https://docs.microsoft.com/en-us/office/client-developer/outlook/mapi/mapi-samples
https://www.nylas.com/blog/the-developers-guide-to-the-microsoft-exchange-apis-eas-ews-and-graph/
https://docs.microsoft.com/en-us/outlook/rest/get-started
https://knowledge.domo.com/Connect/Connecting_to_Data_with_Connectors/Configuring_Each_Connector/Connectors_for_File_Retrieval/Microsoft_Exchange_Mailbox_REST_Connector
Probably best to wait for the VS2015+ upgrade first for compatibility reasons.
Maybe easier for me to write a tool to periodically move Junk Email to the Inbox. Then it'll download in Eudora/Hermes.