Quantcast

Force SASL-auth when sending mail

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Force SASL-auth when sending mail

Nikolaos Milas
Hi,

I am using v1.4.22 on CentOS 5.8 (x86_64).

Currently, when sending mail from SM, it uses the following setup
(config/config.php):

    $useSendmail            = true;
    $smtpServerAddress = 'localhost';
    $smtpPort = 587;
    $sendmail_path = '/usr/sbin/sendmail';
    $sendmail_args = '-i -t';
    $pop_before_smtp = false;
    $pop_before_smtp_host = '';

Here is a typical session, as logged by Postfix:

Nov  4 21:43:11 mailserver postfix/pickup[17587]: C58DC6D6771: uid=48
from=<[hidden email]>
Nov  4 21:43:11 mailserver postfix/cleanup[18472]: C58DC6D6771:
message-id=<[hidden email]>
Nov  4 21:43:11 mailserver opendkim[5402]: C58DC6D6771: DKIM-Signature
header added (s=default, d=example.com)
Nov  4 21:43:13 mailserver postfix/qmgr[25488]: C58DC6D6771:
from=<[hidden email]>, size=799, nrcpt=1 (queue active)
Nov  4 21:43:21 mailserver postfix/pipe[18491]: C58DC6D6771:
to=<[hidden email]>, relay=dovecot, delay=16, delays=8.9/0.017/0/7.3,
dsn=2.0.0, status=sent (delivered via dovecot service)
Nov  4 21:43:21 mailserver postfix/qmgr[25488]: C58DC6D6771: removed

So, in essence, SM directly feeds Postfix (through "pickup").

Can we configure SM to explicitly use SMTP SASL-auth (using
username/password of the logged-in user) when sending each and every
email message?

Doing so, we would be able to distinguish between sending users (since
they will be SASL-authenticated)and enforcevarious limitations based on
their identity at the SMTP level (e.g. using postfwd). Currently, there
is no way to tell who was the user who submitted a mail, since the
senderaddress should not be the definitive criterion (while the client
is always 127.0.0.1).

I am aware of "Restrict Senders" plugin, which provides a solution, but
-as mentioned in the plugin description- it is not the suggested one.

Any advice regarding the issue will be appreciated.

Thanks and regards,
Nick

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: [hidden email]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Force SASL-auth when sending mail

Tomas Kuliavas
Nikolaos Milas wrote
Hi,

I am using v1.4.22 on CentOS 5.8 (x86_64).

Currently, when sending mail from SM, it uses the following setup
(config/config.php):

    $useSendmail            = true;
    $smtpServerAddress = 'localhost';
    $smtpPort = 587;
    $sendmail_path = '/usr/sbin/sendmail';
    $sendmail_args = '-i -t';
    $pop_before_smtp = false;
    $pop_before_smtp_host = '';

Here is a typical session, as logged by Postfix:

....

So, in essence, SM directly feeds Postfix (through "pickup").

Can we configure SM to explicitly use SMTP SASL-auth (using
username/password of the logged-in user) when sending each and every
email message?
....
Any advice regarding the issue will be appreciated.
Could you check Server configuration section in conf.pl utility or check all configuration options documented in config_default.php, if you insist on not using recommended configuration tools.

SquirrelMail has other configuration setting for smtp auth.
--
Tomas
Loading...