Scrollout F1 is setup as a SPAM inbound gateway to an Exchange server.  We have some senders whos emails won't deliver to the Exchange server.  Thus far the emails have not kicked back.  The remote Exchange server is stating the message delivery has been delayed.  I am assuming Scrollout is terminating the connection from the remote mail server.  I did notice that the remote domain doesn't have an SPF record.  Would that be enough to cause this issue?  What can I do i Scrollout to mitigate the issue so we can receive their emails?  I don't see anything in the logs of the web interface that report any activity for the remote server domain.  Are there other logs on the Scrollout file system that I should be looking at?

Any help would be appreciated

This message is sent to me, from me and on behalf of me. Upon clicking the reply key I see the real sender. I have tried to options and add to the blocked list and also open the blocked content and unsubscribe them (meggannsmith6) to hopefully get them blocked by the actual company with the unsubscribe link.
This person is sending me multiple messages each day in two accounts and I changed the passwords and no luck.
What is the solution?

We will soon be starting a relationship with a company where we will be allowing them to send emails to our customers on our behalf from their mail provider using our domain name. They are using Amazon Ses, and they have asked us to add the amazonses.com domain as an allowed sender in our SPF record. We are going to do this, but I am a little uncomfortable with the risk of any potential Amazon cloud customer having the ability to spoof our domain and pass SPF. Because of this, I am looking into implementing DKIM and having the third party sign their messages with a private key.

I want to implement DKIM for our own domain's email messages as well. I have been reading up on DKIM, but it gets a little confusing when third party senders become involved. I am looking to see if anyone can provide me with a best practice for this situation.  If I create a private/public key pair for our domain, I am guessing that it is not recommended practice to provide that key to the third party and tell them to use the selector name I make up. I have come across different articles describing the use of multiple selectors, but I admit I am finding them confusing. Can I have two different private keys for the same domain? Then I could give them one private key for their emails and have a separate key for our emails? Do I use the same private key, but create two selectors for my domain? Then provide the third party with the private key and tell them to sign using the alternate selector? At that …

You have a secure Document from . Open message below

 click here.

Note; Your email and your password is required for authentication.

Can you please let me know how to block this message in o365 and what are the  preventive steps? Thanks.

Regards,


Note- please help me how to block - we have o365

This question is for the Exchange Admins out there who have experience in dealing with phishing campaigns or malicious emails in general.

When a phishing campaign with malicious links and/or attachments hits your mail servers what are doing to figure out who clicked the links or attachments in said phishing email?

We are using Exchange 2013 CU19 On-Premise , Outlook 2013

Thank you for your time and knowledge!

i am a google adwords customer and have a number of ads setup, each of which directs the "clicker" to one of my website pages. I was testing one of the ads yesterday and found that when I click on it, I am directed to a page that is not remotely associated with my website. It takes me to a page that sells viagra. This happens on all of my computers and all browsers on all of those computers. It even happens on my cell phone. It does not appear to happen to anyone else. I just got off of the phone with Google support and they could not replicate the problem. When anyone there clicked on the ad, the correct page opened. I've had others test it as well and they all get connected to the right page. It appears that it is just me who is having the problem. I downloaded malwarebytes and ran a scan on one of my pcs but nothing was detected.

Any ideas out there about what could be causing this and how I can fix it?

If you google for "Maximo Training" my add should be very near the top of the list. It's "Maximo Training | Training by Maximo Experts | mmgts.com. When I click on that add, a page with the correct URL opens but it shows a page for Viagra sales. When I right click the link and choose "open link in an incognito window", the correct page shows up.

I have 2 windows 7 pro PCs and one windows 10 pro PC. As i mentioned, I get the same results on each. Also have the problem on my cell phone.

AV software best compatible with O365. Any suggestion? Local outlook emails? Thanks

I have a client that sends invoices through Netsuite. The clients domain uses SPF, DKIM, and DMARC. Their DMARC policy is: (v=DMARC1;p=reject;aspf=r;rua=mailto:admin@domain.com)

When emailing certain customers they get bouncebacks and after contacting Rackspace who hosts most of the customers they can't reach. Rackspace is saying it's because of domain alignment under the DMARC standard even though SPF and DKIM match fine. (After I finally reached someone who understood what DMARC was and didn't want me to add Rackspace to our SPF...)

The headers on the netsuite include the following bits which some or all are apparently the cause because they specify netsuite instead of my client's domain so they aren't aligned:

smtp.mailfrom=bounces.na3.netsuite.com
helo=nmail001.na3.netsuite.com
Reply-To: User <transactions#_msg_#@transactions.na3.netsuite.com>
Return-Path: b.#.user_domain_pcom.#@bounces.na3.netsuite.com

Spoke with someone at Netsuite who says that Netsuite can't change this behavior at all, but Netsuite also claims they can send DMARC-compliant mail. Is anyone else able to get DMARC working completely with Netsuite?

When the client sends to me on O365 it passes SPF/DKIM/DMARC just fine, but I also see the above bits in the headers. It looks to me like it's doing SPF checks against the netsuite.com domain instead of my client's domain...which seems like Netsuite actually is tagging these wrong...

This is what O365 says in my headers for DKIM/SPF/DMARC …

Hi everyone,

I have a simple questions that's been bothering me for a while now. I have a 3rd party Spam Filter connected to my Office 365 Tenant. When an external sender sends me a legit email it is being tagged as a SPAM. My question is when the email passes through the 3rd party spam filter, is the email still going to be scanned by Office 365 EOP once it reaches Microsoft server or will it bypass EOP?