SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: Connection refused' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-12-21 23:35 MST

Project: All Projects ClearCenter ClearOS

Main | My View | View Issues | Change Log | Roadmap | Repositories

View Issue Details [ Jump to Notes ]				[ Issue History ] [ Print ]
ID	Project	Category	View Status	Date Submitted	Last Update
0000185	ClearOS	app-smtp - SMTP Server	public	2010-10-13 12:12	2018-03-07 10:19
Reporter	user2
Assigned To	user2
Priority	normal	Severity	feature	Reproducibility	N/A
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version
Target Version		Fixed in Version
Summary	0000185: Allow for minimalist mail server configurations
Description	Sometimes, a user may not need a full-fledged mail server installed. Two common scenarios: 1) An outbound only mail server for handling web applications (e.g. a SugarCRM install) 2) A mail gateway configuration The web interface in ClearOS should be modified to handle these scenarios in an intuitive way (hmmmm). This will also remove the dependency on app-users since mailboxes are not required in these two modes.
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0007201) user2 2018-03-07 10:19	The app-mail-routing app handles this. By default, Postfix only listens on localhost. When an app requires Postfix on network interfaces, the app-mail-routing-core app can be used to handle this change.

Notes

Issue History
Date Modified	Username	Field	Change
2010-10-13 12:12	user2	New Issue
2010-10-13 14:15	user2	Status	new => confirmed
2013-02-02 09:25	user2	Target Version	Future => 6.4.0 Updates
2013-07-29 13:58	user2	Target Version	6.4.0 Updates => 6 Future
2014-04-22 13:28	user2	Target Version	6 Future => Future
2015-05-25 05:10	user2	Target Version	Future =>
2018-03-07 10:19	user2	Note Added: 0007201
2018-03-07 10:19	user2	Status	confirmed => resolved
2018-03-07 10:19	user2	Resolution	open => fixed
2018-03-07 10:19	user2	Assigned To	=> user2
2018-03-07 10:19	user2	Status	resolved => closed

Issue History