Allow emails from selected domains to internal distribution groups

Hi RATHER 

Please refer to the articles.

https://community.sophos.com/kb/en-us/120802

http://sea.sophos.com/webhelp/sea/tasks/ConfigPolAllowBlockLists.html

That is not what i want.

I need to set a rule that will allow some 20 domains to send email to a distribution group inside the organization. Rest of the domains should not be allowed to send meails to this distribution group.

hope it is clear.

Thanks.

Z. Rather

Hi RATHER 

Could you please share some more details on your requirements?

20 domains are outside or inside?

Ok, I have couple of Local email Distribution Groups and need to restrict them So only some 20 Domains could send emails to these couple of local email distribution groups from outside. everyone else is discarded or blocked.

Can i have  such rule/policy on sophos mail appliance.

thanks.

Z. Rather

Hi RATHER 

If the communication takes place over POP/IMAP, we will not be able to achieve your requirements. I would suggest raising a request with technical support to explore the option which may help you further

With POP3 and IMAP protocols, as mail client initiates the mail transfer and is already aware of the number of emails to be received, Cyberoam cannot reject any mails.

Due to this limitation of POP3 implementation, Cyberoam cannot reject mails even if they are infected. As an alternative, to inform the user about spam and virus-infected emails, Cyberoam has a provision to tag the mail transferred via any of the Mail protocols and lets the user deal with the mail. 

Similar is the case with IMAP implementation, while with SMTP protocol this is not the case hence Cyberoam can reject the mail if required.

By tagging POP3 and IMAP spam mails, the user has the flexibility to move the tagged emails to a separate folder or automatically delete indicating in the scanning rule to check for the tagged text in the subject line of the mail.

POP3 RFC

As per the RFC 1939, The Post Office Protocol - Version 3 (POP3) is intended to permit a client/user/workstation to dynamically access a maildrop on a server.  This means that the POP3 is used to allow a workstation to retrieve mail that the server is holding for it.  

In other words, when the POP3 client sends a request for the mail transfer, the mail is already dropped in the mail server. Mail client simply “pops” or “polls” the mail from mail server.  

Again as per the RFC 1939, POP3 is not intended to provide extensive manipulation operations of mail on the server.

Hi RATHER 

If the communication takes place over POP/IMAP, we will not be able to achieve your requirements. I would suggest raising a request with technical support to explore the option which may help you further

With POP3 and IMAP protocols, as mail client initiates the mail transfer and is already aware of the number of emails to be received, Cyberoam cannot reject any mails.

Due to this limitation of POP3 implementation, Cyberoam cannot reject mails even if they are infected. As an alternative, to inform the user about spam and virus-infected emails, Cyberoam has a provision to tag the mail transferred via any of the Mail protocols and lets the user deal with the mail. 

Similar is the case with IMAP implementation, while with SMTP protocol this is not the case hence Cyberoam can reject the mail if required.

By tagging POP3 and IMAP spam mails, the user has the flexibility to move the tagged emails to a separate folder or automatically delete indicating in the scanning rule to check for the tagged text in the subject line of the mail.

POP3 RFC

As per the RFC 1939, The Post Office Protocol - Version 3 (POP3) is intended to permit a client/user/workstation to dynamically access a maildrop on a server.  This means that the POP3 is used to allow a workstation to retrieve mail that the server is holding for it.  

In other words, when the POP3 client sends a request for the mail transfer, the mail is already dropped in the mail server. Mail client simply “pops” or “polls” the mail from mail server.  

Again as per the RFC 1939, POP3 is not intended to provide extensive manipulation operations of mail on the server.

Hi,

It is SMTP - from Mail Appliance to our internal Exchange server.

Hi RATHER 

Could you please provide the exact packet flow of your requirements? it would help us to assist you better.

Thanks.

When ever an email hits mail Appliance from internet addressed to exampledistributiongroup@mydomain.com it should allow it to deliver only if the domain is in exception or in allowed list in the rule/policy , if in place.

Rest of the emails discard or quarantine. But rest of the emails should flow as normal.

This is to limit the distribution group  to receive emails fome some domains only.

Hope it is clear.

thanks.

Z. Rather