From: oldrah@hotmail.com   
      
   On 10/11/2025 7:47 PM, Nuno Silva wrote:   
   > On 2025-10-12, DICK HOFFMAN wrote:   
   >   
   >> On 10/11/2025 7:15 PM, Nuno Silva wrote:   
   >>> On 2025-10-11, Adam H. Kerman wrote:   
   >>>   
   >>>> Barryedwin1  wrote:   
   >>>>   
   >>>>>> . . .   
   >>>>   
   >>>>> Yes, that was my problem too.   
   >>>>> DKIM on my ISP's email server, requires the email sender's 'From'   
   >>>>> address to agree with the email user's email identity for authentication   
   >>>>> (claims all other 'From' usage is 'spoofing', even though it is my real   
   >>>>> gmail address.   
   >>>>> If I want too, I can get the ISP to accept the gmail sender-address, by   
   >>>>> dancing through hoops with gmail to authenticate that usage for the   
   >>>>> local ISP, which involves some sort of permit-token for the local ISP's   
   >>>>> email server (presumably within DKIM), but as I can just switch to the   
   >>>>> SeaMonkey browser to send gmail messages, I haven't bothered. HTH   
   >>>>   
   >>>> It's not within DKIM. DKIM comes after From has been set.   
   >>>>   
   >>>> In my case, I authenticate, then can use any From address I like, even   
   >>>> from a foreign domain. That does not mean the message will be delivered.   
   >>>>   
   >>>> For instance, a friend I do business with will send me email via his   
   >>>> ISP's MX but with the domain he controls on From. My MX rejects it   
   >>>> because the TXT record associated with the domain he controls is set to   
   >>>> strict and not loose. That's an instruction to everyone else that if the   
   >>>> message with that domain on From isn't sent via the the domain's default   
   >>>> MX to reject the connection.   
   >>>   
   >>> The initial section of the English Wikipedia article on SPF [1]   
   >>> indicates that SPF validation would (should?) look at *Envelope* From,   
   >>> not the header "From:"?   
   >>>   
   >>> [1] https://enwp.org/Sender_Policy_Framework   
   >>>   
   >>> Or is this something servers often mishandle?   
   >>>   
   >>>> We don't even get to the point of validating DKIM.   
   >>>   
   >>>   
   >> So weeding out all the technical stuff that I don't really understand,   
   >> I think you are saying that I can't have two email ISP's in my   
   >> SeaMonkey setup. Right now I have Earthlink defined and I have Hotmail   
   >> defined but with the new authentication going on at Gmail and   
   >> Sbcglobal only one of them, Earthlink, will work.   
   >   
   > No, you can have several outgoing servers configured, but you need to   
   > associate the appropriate server to each "incoming"/POP/IMAP account.   
   >   
   > In Edit > "Mail & Newsgroups Account Settings", the top-level pane for   
   > each "incoming" e-mail account has a drop-down box for "Outgoing server   
   > (SMTP)" near the bottom. So select the Hotmail "incoming" account and   
   > choose the Microsoft outgoing server in the drop-down box. (This   
   > assuming you have all the outgoing servers already configured - if that   
   > is not the case, you have to first go to the end of the list to   
   > "Outgoing Server (SMTP)" and there add the ones that are not present   
   > yet.)   
   >   
   >   
   > (If you use multiple identities per account (see the "Manage Identities"   
   > button), you may need to check all identities.)   
   >   
   Many thanks for your replies, Nunu. Changing the outgoing server to   
   smtp.office365.com and the communication security to OAuth2 has solved   
   my problem of not being able to send out from Hotmail.   
   Dick Hoffman   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)