Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
POP is used for receiving messages & SMTP for sending messages. So what does 'use POP before SMTP' do?
In any case when the user logs into his mail, all mails are downloaded first & then sent. Can someone please differentiate the workflow with & without this option?
In a mail system using POP and SMTP servers, checking mail on the POP server first and then sending queued mail to the SMTP server is quite common. If properly set up you need to authenticate to send mail as well as receive it. Often a POP system is set up so that if you have already authenticated to the POP server, you don't have to re-authenticate to the SMTP server as long as you're logged into the POP server.
It isn't so much that checking POP before sending is required, but that when the SMTP server is configured to require authentication to send mail, if you have already accessed the POP server it usually uses that authentication as valid authorization to send.
If you ARE asked for a password/authentication by the SMTP server when you try sending mail without checking on the POP server first, but are NOT asked for a password to send if you check POP first then the system is using POP before SMTP to authenticate outgoing mail server access.
POP before SMTP is used primarily as a means to limit SMTP server use to network users and prevent spam relaying.
It isn't so much that checking POP before sending is required, but that when the SMTP server is configured to require authentication to send mail, if you have already accessed the POP server it usually uses that authentication as valid authorization to send.
If you ARE asked for a password/authentication by the SMTP server when you try sending mail without checking on the POP server first, but are NOT asked for a password to send if you check POP first then the system is using POP before SMTP to authenticate outgoing mail server access.
POP before SMTP is used primarily as a means to limit SMTP server use to network users and prevent spam relaying.
Thanks, for the reply. Consider the first scenario where there is no POP3 before SMTP
In this case, mail is directly sent to the recipient without any authentication
Second Scenario: POP3 before SMTP
It authenticates POP3 mail server using username & password & then sends a mail
How can this prevent spam?
Thanks
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.