• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

What if I set Mail Relay off ?

K

kadoudal

Regular Pleskian
Currently we have the standard Mail Relay with authentication... , when Mail Relay is Off , Still anyone from the company with our domain addresses will be able to send email via the SMTP ? or does it suppress it ?
I did not pick it up right in my mind ....

thanks for some enlightments ..
 
In control panel under Settings -> Mail Server Settings -> Relaying - you have:
Code: 
Relaying	
 (*) closed
 ( ) authorization is required:
    [ ] POP3 before SMTP  lock time    Min
    [ ] SMTP

If people with a mail account at your server needs to be able to relay through your server - you need to choose the "authorization is required:" setting and the choose the two ways to open up the relay - by creating a POP3 auth or a SMTP auth (or both).

The POP3 auth method will create a record for (lock time minutes) where the IP the mail account user used a POP3 login from will be allowed to relay (send) mails through your server.

The SMTP will not require the mail account user to first login using POP3 (if in example its a IMAP user) but require the mail account user to setup SMTP AUTH in his/her mail client. (with login credentials the same as the mail account).

This way will enable your legitimate mail account users to still relay (send) mail through your server.

EDIT:
If set to Closed - no one will be able to relay through your server - except mails coming locally from the server itself.

(ie. local webmail on server, local scripts, system mails from the server it self etc.)


Hope this helps?

--
Kind regards
Geert Lund,
www.GLD.dk
 
Last edited:
Thanks a lot ... very helpful
you stated :

If set to Closed - no one will be able to relay through your server - except mails coming locally from the server itself.

This way will enable your legitimate mail account users to still relay (send) mail through your server.

Do you mean that even "if set to closed" , our user will be able to send email from their client mail app (Outlook, Mac mail app, ..) configured mailbox ?
 
No, Im so sorry - the two sentenses was switched around when I posted ... I just reedited my post.

If set to Closed - no one will be able to use your server to relay mails through SMTP (but a local application/PHP script/ webmail etc. running on the server might still send mail).

And server still accepts mail for local users.

--
Kind regards
Geert Lund,
www.GLD.dk
 
OK thanks .. it's clear now I keep it open..
Now, to avoid the following issue, should I install SpamAssassin ?
--
a spammer ( rdlau@buckeye-express.com ) sent an email to one of our generic addresses ( info@ourdomain.co.uk)
qmail-queue-handlers is then relaying the spam to our employees ( john.doe@ourdomain.co.uk )..

here is the log -
qmail-queue-handlers[30755]: Handlers Filter before-queue for qmail started ...
qmail-queue-handlers[30755]: from=qmail-queue-handlers[30755]: Handlers Filter before-queue for qmail started ...
qmail-queue-handlers[30755]: from=rdlau@buckeye-express.com
qmail-queue-handlers[30755]: to=info@ourdomain.co.uk
qmail: 1302831436.714827 new msg 6603912
qmail: 1302831436.714857 info msg 6603912: bytes 2723 from <rdlau@buckeye-express.com> qp 30756 uid 2020
qmail: 1302831436.717172 starting delivery 169: msg 6603912 to local 1-info@ourdomain.co.uk
qmail: 1302831436.717195 status: local 1/10 remote 0/20
qmail-local-handlers[30757]: Handlers Filter before-local for qmail started ...
qmail-local-handlers[30757]: from=rdlau@buckeye-express.com
qmail-local-handlers[30757]: to=info@ourdomain.co.uk
qmail-local-handlers[30757]: mailbox: /var/qmail/mailnames/ourdomain.co.uk/info
qmail-queue-handlers[30760]: Handlers Filter before-queue for qmail started ...
qmail-queue-handlers[30760]: from=rdlau@buckeye-express.com
qmail-queue-handlers[30760]: to=john.doe@ourdomain.co.uk
qmail: 1302831436.737236 new msg 6603925
qmail: 1302831436.737266 info msg 6603925: bytes 2837 from <rdlau@buckeye-express.com> qp 30761 uid 110
qmail: 1302831436.743625 starting delivery 170: msg 6603925 to local 1-john.doe@ourdomain.co.uk
qmail: 1302831436.743649 status: local 2/10 remote 0/20
qmail: 1302831436.743664 delivery 169: success: did_0+1+2/qp_30760/
qmail: 1302831436.743750 status: local 1/10 remote 0/20
qmail: 1302831436.743771 end msg 6603912
qmail-local-handlers[30762]: Handlers Filter before-local for qmail started ...
qmail-local-handlers[30762]: from=rdlau@buckeye-express.com
qmail-local-handlers[30762]: to=john.doe@ourdomain.co.uk
qmail-local-handlers[30762]: mailbox: /var/qmail/mailnames/ourdomain.co.uk/john.doe
qmail: 1302831436.749384 delivery 170: success: did_0+0+2/
qmail: 1302831436.749524 status: local 0/10 remote 0/20
qmail: 1302831436.749541 end msg 6603925
qmail-queue-handlers[30755]: to=info@ourdomain.co.uk
qmail: 1302831436.714827 new msg 6603912
qmail: 1302831436.714857 info msg 6603912: bytes 2723 from <rdlau@buckeye-express.com> qp 30756 uid 2020
qmail: 1302831436.717172 starting delivery 169: msg 6603912 to local 1-info@ourdomain.co.uk
qmail: 1302831436.717195 status: local 1/10 remote 0/20
qmail-local-handlers[30757]: Handlers Filter before-local for qmail started ...
qmail-local-handlers[30757]: from=rdlau@buckeye-express.com
qmail-local-handlers[30757]: to=info@ourdomain.co.uk
qmail-local-handlers[30757]: mailbox: /var/qmail/mailnames/ourdomain.co.uk/info
qmail-queue-handlers[30760]: Handlers Filter before-queue for qmail started ...
qmail-queue-handlers[30760]: from=rdlau@buckeye-express.com
qmail-queue-handlers[30760]: to=john.doe@ourdomain.co.uk
qmail: 1302831436.737236 new msg 6603925
qmail: 1302831436.737266 info msg 6603925: bytes 2837 from <rdlau@buckeye-express.com> qp 30761 uid 110
qmail: 1302831436.743625 starting delivery 170: msg 6603925 to local 1-john.doe@ourdomain.co.uk
qmail: 1302831436.743649 status: local 2/10 remote 0/20
qmail: 1302831436.743664 delivery 169: success: did_0+1+2/qp_30760/
qmail: 1302831436.743750 status: local 1/10 remote 0/20
qmail: 1302831436.743771 end msg 6603912
qmail-local-handlers[30762]: Handlers Filter before-local for qmail started ...
qmail-local-handlers[30762]: from=rdlau@buckeye-express.com
qmail-local-handlers[30762]: to=john.doe@ourdomain.co.uk
qmail-local-handlers[30762]: mailbox: /var/qmail/mailnames/ourdomain.co.uk/john.doe
qmail: 1302831436.749384 delivery 170: success: did_0+0+2/
qmail: 1302831436.749524 status: local 0/10 remote 0/20
qmail: 1302831436.749541 end msg 6603925
 
You must log in or register to reply here.

Similar threads

V
Issue Smarthost + SRS = relay?
Replies
2
Views
10K
vanlier
V
F
Issue SOGo - emails sent from webmail, both manually created and autoresponder/vacation/out-of-office, are rejected. They miss spf, dkim, dmarc, everything
Replies
1
Views
411
Farfalk
F
I
Issue Mail delivery deferred (4.4.2 delivery temporarily suspended)
Replies
1
Views
229
iainh
I
F
Issue Relay access denied for root mails
Replies
3
Views
724
fliegerhermi
F
A
Question Alternative ways to forward emails
Replies
2
Views
824
Aslanj
A
Back
Top