Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Things you’d like to miss in the future...
vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

recently I noticed that when I drag a email from Outlook365 to xyplorer 23.00.0300, the <from> field is not set. instead only <from> appears in filename. This behaviour is only for external senders. Xyplorer is able to extract the name of sender from my organization.
Attachments
Clipboard-20220520-01.png
Clipboard-20220520-01.png (83.88 KiB) Viewed 1824 times
Clipboard-20220520.png
Clipboard-20220520.png (7.69 KiB) Viewed 1825 times

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by admin »

I don't have Outlook365 here at the moment. What is an "external sender"?

vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

External Sender means someone who is not in my organization. XYplorer is able to extract <from> only for someone who is within same organization.
This was working fine some months back for all senders (internal or external) but now something seems to be changed.

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by admin »

Aha. Can you confirm the latter by trying an older version from the freezer?: https://www.xyplorer.com/freezer.php

vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

Same Issue till version 22 & 21, want me to check even older version?

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by admin »

You said "This was working fine some months back for all senders ..." so now it looks like it was Windows or Outlook365 that changed, not XYplorer.

I'll check that later with a machine that has Outlook365. Is that Windows 10?

vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

Yes this is windows 10

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by admin »

The next beta (v23.10.0004) will print the full header of the dropped message to the debug log. We can then see if the info we want is there and on which line.

Your steps:

1. download and run beta v23.10.0004 from this forum: viewtopic.php?p=199577#p199577
2. drop the message onto XYplorer
3. paste dlog; into the XYplorer address bar and press ENTER
4. copy & paste the return into this thread

vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

XYplorer 23.10.0004 - Windows 10 Enterprise, 64-bit, Release 2009, Build 19042.1706 - 2022-05-25 17:12:36
=============================================================================================================

0 - 2022-05-25 17:12:25.977 --- Header Line 0: Received: from .eurprd07.prod.outlook.com (::1) by
1 - 2022-05-25 17:12:25.978 --- Header Line 3: Received: from .eurprd07.prod.outlook.com () by
0 - 2022-05-25 17:12:25.978 --- Header Line 7: Received: from .eop-EUR03.prod.protection.outlook.com
0 - 2022-05-25 17:12:25.978 --- Header Line 12: Authentication-Results: spf=softfail (sender IP is )
0 - 2022-05-25 17:12:25.978 --- Header Line 13: smtp.mailfrom=*****.ae; dkim=none (message not signed)
0 - 2022-05-25 17:12:25.978 --- Header Line 14: header.d=none;dmarc=fail action=none header.from=*****.ae;compauth=softpass
0 - 2022-05-25 17:12:25.978 --- Header Line 15: reason=202
0 - 2022-05-25 17:12:25.978 --- Header Line 16: Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
0 - 2022-05-25 17:12:25.978 --- Header Line 17: *****.ae discourages use of as permitted sender)
0 - 2022-05-25 17:12:25.978 --- Header Line 18: Received: from esa3.hc1632-22.c3s2.iphmx.com () by
0 - 2022-05-25 17:12:25.978 --- Header Line 22: Received-SPF: Pass (esa3.hc1632-22.c3s2.iphmx.com: domain of
0 - 2022-05-25 17:12:25.978 --- Header Line 23: btv1==144a5641f6d==muzaffar@*****.ae designates 8
0 - 2022-05-25 17:12:25.978 --- Header Line 24: as permitted sender) identity=mailfrom;
0 - 2022-05-25 17:12:25.978 --- Header Line 25: client-ip=;
0 - 2022-05-25 17:12:25.978 --- Header Line 26: receiver=esa3.hc1632-22.c3s2.iphmx.com;
0 - 2022-05-25 17:12:25.978 --- Header Line 27: envelope-from="btv1==144a5641f6d==muzaffar@****.ae";
0 - 2022-05-25 17:12:25.978 --- Header Line 28: x-sender="btv1==144a5641f6d==muzaffar@****.ae";
0 - 2022-05-25 17:12:25.978 --- Header Line 29: x-conformance=spf_only; x-record-type="v=spf1";
0 - 2022-05-25 17:12:25.978 --- Header Line 30: x-record-text="v=spf1 mx a ip4: ~all"
0 - 2022-05-25 17:12:25.978 --- Header Line 31: Authentication-Results-Original: esa3.hc1632-22.c3s2.iphmx.com; dkim=none
0 - 2022-05-25 17:12:25.978 --- Header Line 32: (message not signed) header.i=none; spf=Pass
0 - 2022-05-25 17:12:25.978 --- Header Line 33: smtp.mailfrom=btv1==144a5641f6d==muzaffar@*****.ae; dmarc=pass (p=none
0 - 2022-05-25 17:12:25.978 --- Header Line 34: dis=none) d=****.ae
0 - 2022-05-25 17:12:25.978 --- Header Line 35: IronPort-SDR: KDJ9Juda81IuJG0cr94Dh9wJg2xPX4puVZ6MxLEuxHYtl+ykxzjcw02U/XZiF0L9rA68kromds
0 - 2022-05-25 17:12:25.978 --- Header Line 36: kYgCRrL6uJoLaJNB4jN7u0VMWyjQjIkuRvK7e9R+v2j+dJrs8m8dh2Pa1JRtZmubELJfkxWFuw
0 - 2022-05-25 17:12:25.978 --- Header Line 37: lRRjEGYmJ7iMPj830m2Zqq4g4aGnpqhgsTTbFxUopBeK8qvirVcdfmA/vzSeOi9bGzkjFpgoNa
0 - 2022-05-25 17:12:25.978 --- Header Line 38: axv4rjJurmdyb5VnU48ui95mEDO5+07ZwfA0AYvjvSTgTClGhhu4FDNZGtuJqRCzzrv6hiF/aj
0 - 2022-05-25 17:12:25.978 --- Header Line 39: usqVrVCTUXZgoIrXv47gRsOT
0 - 2022-05-25 17:12:25.978 --- Header Line 40: X-IronPort-RemoteIP:
0 - 2022-05-25 17:12:25.978 --- Header Line 41: X-IronPort-MID: 18231237
0 - 2022-05-25 17:12:25.978 --- Header Line 42: X-IronPort-Reputation: 5.2
0 - 2022-05-25 17:12:25.978 --- Header Line 43: X-IronPort-Listener: IncomingMail
0 - 2022-05-25 17:12:25.978 --- Header Line 44: X-IronPort-S
0 - 2022-05-25 17:12:25.978 --- Header Line 45: X-IronP
0 - 2022-05-25 17:12:25.978 --- Header Line 46: X-IronPort
0 - 2022-05-25 17:12:25.978 --- Header Line 47: X-IronPort-AV
0 - 2022-05-25 17:12:25.978 --- Header Line 48:
0 - 2022-05-25 17:12:25.978 --- Header Line 49: X-Amp-Result: UNKNOWN
0 - 2022-05-25 17:12:25.978 --- Header Line 50: X-Amp-Original-Verdict: FILE UNKNOWN
0 - 2022-05-25 17:12:25.978 --- Header Line 51: X-Amp-File-Uploaded: False
0 - 2022-05-25 17:12:25.978 --- Header Line 52: X-MGA-submission: MDEzJBkAfF0ySixOQmPAr8Ga//Ur6/BCoDOdqi
0 - 2022-05-25 17:12:25.978 --- Header Line 53: r9wZvU+zhx/Q+8zc7hbsJ4sGVKUMb8bH2SpUhHzR0imL37LYJVLWy6AtTwmE
0 - 2022-05-25 17:12:25.978 --- Header Line 54: wpYsNISNn0/vxS56Sq9uNLJtvEmKsg1MSwaP5H93a+RG0uWjw3I6tT8pU5vJ
0 - 2022-05-25 17:12:25.978 --- Header Line 55: Ajcbn2rFgvHHXcV1HCE8t92dFrDgRVxns+hkbqpnRd7f4h2m0nuEdqx0y5GS
0 - 2022-05-25 17:12:25.978 --- Header Line 56: bhS57QDbZBqasfSVkEq3jsDuuQF/la/Dkkucz2VCs0ezIXvihX7YMycw8C9w
0 - 2022-05-25 17:12:25.978 --- Header Line 57: Kj4AB23v4LvzGQWyc6SRRTo9IDHsgDbaOd6Sf9vzSo6fqHaWBMX5gQdU/etG
0 - 2022-05-25 17:12:25.978 --- Header Line 58: FKnuEkQS/AV6Yl/H8d+TrKkROgMbSpCTLlGD8k5PHomKvKPtjro8P466leX3
0 - 2022-05-25 17:12:25.978 --- Header Line 59: jI1PLsa6ciMQYXWVssnfkotSptMZ0y9fXr7N1plNe+6+nA1Q8rQsm4Dslnux
0 - 2022-05-25 17:12:25.978 --- Header Line 60: EzQlyuMy10nhStX/9vCpOzeo60tfzxgyZW5XakwjbmTVVhjluVDjgiaMTw40
0 - 2022-05-25 17:12:25.978 --- Header Line 61: DhGA9B6NuOTZtE+Np+hoW47Cm6TF1A5ngPeZ1VfSug599dDLH8mtZFeNQQvw
0 - 2022-05-25 17:12:25.978 --- Header Line 62: OZHXBA51oL8wVxDi5YKwZ6Mb0jLNVTUK795iIjnJsp6bYwC+SV3xVFheXAf7
0 - 2022-05-25 17:12:25.978 --- Header Line 63: T4lf7/T/0wmCMnqHYHpO7k1iHKzY3g3zTFYKMb0lS10SOvPqqEtZ5rXuA2IW
0 - 2022-05-25 17:12:25.978 --- Header Line 64: Au8zKv2gfpoBRsk/ZS9YIxBIvK8VscsdUqnOo178+IVnh0L9NX9C+Xdgu0+i
0 - 2022-05-25 17:12:25.978 --- Header Line 65: GrBu13PNT/Py2YoTbsQzgszpHvSoLPzp15dUKuUonTbfHNyJCb0MQUor5Qwl
0 - 2022-05-25 17:12:25.979 --- Header Line 66: kUh2ji0YT3dNLcid66oB8Ap/hnDoglrdR95xu1iIqr4crL3i1UXob9C+Zcmf
0 - 2022-05-25 17:12:25.979 --- Header Line 67: OOHNCYxJVEmHI6QSdFsp2bh5cNTP9SZy68w4t2R5Qe2eaIzFMTcvAROacL+K
0 - 2022-05-25 17:12:25.979 --- Header Line 68: 1iUFuPyaA0Ozmlkwak1hqpdhCTo/1fFouj4kxU2iq8otQ1H4KnsdIA0EHxVc
0 - 2022-05-25 17:12:25.979 --- Header Line 69: +bbyMWwW4tldO4cTicq0Yp/U0kV5VcVncqkJuOjhkkMrVW8A2IlJLP+civq6
0 - 2022-05-25 17:12:25.979 --- Header Line 70: +xhVE06c1RUBs1319SBNQgZZhk+XBoAFXP7dLRbJvoUZ0VX8aiT2DekJb7Zd
0 - 2022-05-25 17:12:25.979 --- Header Line 71: NbzVCh0+7FPsKyHn+XpuXpTHkjth8JHhc9EmO2MBfo/kNJuNP61vrFIlR8Lu
0 - 2022-05-25 17:12:25.979 --- Header Line 72: JyeIgPOcJDDR1me3+1B6yqTQirb6MYbmuWE/Rc4AQTbZhTNnBs5AH75FwpSu
0 - 2022-05-25 17:12:25.979 --- Header Line 73: j23QjORqkh4nlJ1jAx1ynBcikcCGQSaHYdPB5pDZpHonAe9RfNrK6APul1il
0 - 2022-05-25 17:12:25.979 --- Header Line 74: b5n183Yuk54fiSVHTtrp07oaa/g+5AR1AxpzSMI71KEe8o+gIZ7qNJcuHPxd
0 - 2022-05-25 17:12:25.979 --- Header Line 75: ac6f9+VKPSZsYeufBLjskMRPyZbeXnWTqYqdpuGT4cQFkuySVxPXuy4nd2V2
0 - 2022-05-25 17:12:25.979 --- Header Line 76: ptpZ29sHHTPRaB5ghYGDfuus16tFbJ5kdRe8uzNdkzbmEiAOCb2fGnsLhs/H
0 - 2022-05-25 17:12:25.979 --- Header Line 77: bcHPGbKYQJnLFcPZCsfh0y0/PioJdiILvWtDhstjizEhKNY82+K97HZL6Cl5
0 - 2022-05-25 17:12:25.979 --- Header Line 78: B/Gn+CwaL5qeYueDyg3T/udT9W7corwyIby4njCXC2MyWsAgk/TznKxTpMpq
0 - 2022-05-25 17:12:25.979 --- Header Line 79: FIIHDDH9MN3t1ep0kNwxeDoV5RRbmUEjDT6DaK4ufpeqCE6ab0hpyzvYpi5S
0 - 2022-05-25 17:12:25.979 --- Header Line 80: 1d0/VZnnmAFl59po0wzTguCXGY7OPQXW8yYnbjQUx86f2jA4kKJpH8112+x6
0 - 2022-05-25 17:12:25.979 --- Header Line 81: 7MaNRVOu2KuhR1exFmjtnY9P5Q+UwLRUgk5W//NISZE7QhRJO+Rxr2jgp5+u
0 - 2022-05-25 17:12:25.979 --- Header Line 82: aK/Gw7Xbt05Z0AMtG2wQ0T/VTZyqCRdAC9p+sVEymPVv8y+n4+YNtWXaMgcj
0 - 2022-05-25 17:12:25.979 --- Header Line 83: F/8lfP8ArdYFWcqu9mhqDBso+detlQjmu9POh8G7isW0DbKsbYl3V7V6HNoR
0 - 2022-05-25 17:12:25.979 --- Header Line 84: kdeMt5xG5+yAffrTFVFHBOfa5TYYlAW7Xz86rRzjxgdJLCTcmqhA9ZJVV7Te
0 - 2022-05-25 17:12:25.979 --- Header Line 85: Sexf
Last edited by vipin on 26 May 2022 08:37, edited 1 time in total.

vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

I have replaced the originating organization name with **** for privacy reasons.

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by admin »

Ok, do you see the sender outside organization somewhere in those lines?

vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

0 - 2022-05-25 17:12:25.978 --- Header Line 23: btv1==144a5641f6d==muzaffar@*****.ae designates 83.111.105.4

vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

0 - 2022-05-25 17:12:25.978 --- Header Line 28: x-sender="btv1==144a5641f6d==muzaffar@****.ae";

admin
Site Admin
Posts: 60357
Joined: 22 May 2004 16:48
Location: Win8.1 @100%, Win10 @100%
Contact:

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by admin »

So you want that email address to fill the <from> field, right?

The data looks as if this is the only email address in it. Is it present already in this line?:
[code]0 - 2022-05-25 17:12:25.978 --- Header Line 13: smtp.mailfrom=*****.ae; dkim=none (message not signed)[/code]
Here it would be easy to parse: smtp.mailfrom=here;

UPDATE: well, probably not. I would probably rather take this line with x-sender=:

Code: Select all

0 - 2022-05-25 17:12:25.978 --- Header Line 28: x-sender="btv1==144a5641f6d==muzaffar@****.ae";
So you want the <from> field to be filled with btv1==144a5641f6d==muzaffar@****.ae?

vipin
Posts: 13
Joined: 21 Mar 2018 14:36

Re: Outlook 365 mail drag-drop name <from> field not working for sender outside organization

Post by vipin »

Yes, <from> field should have "muzaffar"

Post Reply