16 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Setting up SSL re...
FromSent OnAttachments
Peter William LountJan 19, 2003 3:22 am 
Peter William LountJan 19, 2003 3:47 am 
Anand BuddhdevJan 19, 2003 4:33 am 
Peter William LountJan 19, 2003 6:02 am 
Peter William LountJan 19, 2003 6:35 am 
PaeddyJan 19, 2003 4:14 pm 
Brian CandlerJan 20, 2003 1:45 am 
Peter William LountJan 20, 2003 2:11 am 
Brian CandlerJan 20, 2003 3:19 am 
Michael LeoneJan 20, 2003 6:32 am 
Brian CandlerJan 20, 2003 9:16 am 
Peter William LountJan 20, 2003 9:18 am 
Sam VarshavchikJan 20, 2003 10:02 am 
Michael LeoneJan 20, 2003 11:11 am 
Brian CandlerJan 20, 2003 11:31 am 
Peter William LountJan 24, 2003 10:07 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Setting up SSL relaying?Actions...
From:Peter William Lount (pet@sensei.zoku.net)
Date:Jan 19, 2003 6:35:40 am
List:net.sourceforge.lists.courier-users

Hi Anand,

I've got courier preventing relaying unless a user authenticates. I Still have
to setup the SSL to allow authorized remote users to send their mail (and
password) securely. Is there a standard way to do this or is this a custom setup
(such as the one you suggested below)?

With your suggestion of using a second esmtpd (and config file) running on a
different port, won't the global security settings affect the other non-ssl
users?

All the best,

Peter

p.s. starting to get the hang of this courier gizmo... ;--)

> AUTH_REQUIRED > ESMTPD_TLS_REQUIRED > > This causes those clients to use TLS *and* authenticate before they can > relay. These 2 settings can also be enabled globally in the esmtpd config > file, but keep in mind that it will force TLS and AUTH for *all* incoming > connections, which you don't want, otherwise you will not receive any > email > form the outside world. You could run 2 separate instances of smtpd, a > normal one with any TLS and AUTH requirements, and another solely for your > clients, with stricter requirements. Is this the only (or standard) way to allow relaying for authenticaed users
while still receiving email from other servers for local domains? What
alternatives are there?