New answers tagged

0

I have done a test in my exchange online lab, you could open admin center, go to the Users then go to Active users page.Select the user's name, and then on the Account tab select Manage contact information.In the Display name box, type a new name for the person, and then select Save. Here are some testing screenshots for you: For more details: Change a user'...


1

In my situation, for two distinct Ubuntu and Debian servers, the problem was a broken systemd service file for opendkim. The config files were absolutely ok but the service file was probably generated by an old version. To regenerate the service file and reslove the problem, just run this command: sudo /lib/opendkim/opendkim.service.generate Then reload ...


0

Problem was solved by deleting the mydestination parameter on /etc/postfix/main.cf This is because the /etc/aliases was being ignored as postfix thinks the email is not a local delivery so it will not apply the local aliases. after removing the parameter, root mail was forwarded to my e-mail address.


0

Agree with what Mike L'Angelo has said above, each rule has a priority, and the one with the highest priority will be selected first. Could create one rule for these 2 purpose?


2

465/587 are client submission ports, they are usually protected with authentication and transport layer security. Email clients, i.e. MUAs, use port 587 and 465, while mail servers, i.e. MTAs, use port 25. Opportunistic TLS (Wikipedia) "At least for the email related protocols, RFC 8314 favors separate SSL ports instead of STARTTLS." The ...


0

Blacklisting by rbl The reject_rbl_client directive is used to leverage existing DNSBL services, for instance to check spam against Spamhaus and Spamcop Example for reject_rbl_client main.cf smtpd_recipient_restrictions = reject_rbl_client zen.spamhaus.org, reject_rbl_client bl.spamcop.net, permit Blacklisting by domain/ip To ...


0

From the relevant microsoft documentation All messages that flow through your organization are evaluated against the enabled mail flow rules in your organization. Rules are processed in the order listed on the Mail flow > Rules page in EAC, or based on the corresponding Priority parameter value in the PowerShell. Each rule also offers the option of ...


4

Port 25 is the standard server-side email port. This includes server-to-server relaying, etc. It is the standard. You can set postfix to use a different port, but it's unlikely you'd be able to talk to anyone else. Port 587 is typically what a mail client would use to send mail to a server. In this case, by client, I mean something like an iPhone, or ...


0

There are many reasons why email could end up in someone's spam folder. In your case, however, the first thing I would look into is correctly setting up the SPF records From Wikipedia: SPF allows the receiving mail server to check during mail delivery that a mail claiming to come from a specific domain is submitted by an IP address authorized by that domain'...


0

The issue is the way Outlook and Spark work. Since they are offering push notifications, then this is why their IP ranges are showing up and not your IP address. Standard IMAP connection in a normal email app, connects every X minutes to check to see if new email is available or not. Which would be a bit wasteful on your battery usage. So, these new apps ...


0

My problem was from a parameter in main.cf of postfix : smtpd_client_restrictions = check_client_access hash:/etc/postfix/amavis_bypass, reject_rbl_client apple.sgcloud2u.com, reject_rbl_client sanko.sg, reject_rbl_client goutama.biz, reject_rbl_client bs010-003.domainserver.ne.jp, reject_rbl_client webmail.inocnews.com, ...


0

If there is no smtp server install on localhost, you don't need to install one, just point to the one that you use as an smtp server to send mails. yum install -y mailx mail -S smtp={email_host} -s {subject} -r {email_from} {email_to}


0

See below to resolve the following error: postdrop: warning: unable to look up public/pickup: No such file or directory Run the following command as root: mkfifo /var/spool/postfix/public/pickup And then, restart the service : service postfix restart


1

Its very easy to send from any domain within your network if you allow SMTP relay to O365 from your Corp IP range. It a common security misconfiguration that I look for. login to your O365 Exchange admin center Browse to Mail flow > Connectors Check the connector rules set up, this will show which Public IPs/networks are allowed Based on the IP(s) you ...


3

Perform your own message trace from the Security and Compliance center and verify that the email originated from your Office 365 tenant. Look at the sign-ins logs in Azure AD for suspicious sign-ins. Look at the Risky users, Risky sign-ins, and Risk detection logs in Azure AD and look for suspicious activity. Create a Display Name Spoofing transport rule ...


0

Yes. What you are describing is possible from resources on the VNET connecting to a server on the other side of the VPN via port 25. Be advised that not all services that are connected to the VNET will be able to do this (App Service with VNET integration won’t be able to as all outbound traffic other than to Service Endpoints/Private Link will be via the ...


0

Based on my research, Remote Mailbox is a new feature in Exchange 2010 SP1. More details about it: Support for Hybrid Deployments with Exchange Online


0

The following works if envelope :user :matches "to" "*" { set :lower "user" "${1}"; if envelope :domain :matches "to" "*" { set :lower "domain" "${1}"; set "my_recipient" "${user}@${domain}"; filter ".." "${...


0

In case you happen to have set up destination domain filtering in /etc/postfix/transport then you need to add the subdomain of your machine to the allowed domains list. For example, if you had: mydomain.com : anotherdomain.com : * discard: Update it to: linux1.mylinux.mydomain.com : mydomain.com ...


Top 50 recent answers are included