[pfx] sasl_passwd hash

2023-12-16 Thread saunders.nicholas--- via Postfix-users
I'm using Alpine for e-mail and have the "app" password stored in a file 
so that the client can login to Gmail.  It's stored as an alphanumeric 
with whitespace:  xxx yyy zzz



How and where is this password stored on Ubuntu?


/etc/postfix/sasl/sasl_passwd  is where I have it.  The example is:

[smtp.gmail.com]:587 jane@gmail.com:doeadeer

but let's put some whitespace in there:

doe 123 adee 456 r78


so the file would like as:

[smtp.gmail.com]:587 jane@gmail.com:doe 123 adee 456 r78



is that correct?


see also:

https://askubuntu.com/q/1497269/847449
https://help.ubuntu.com/community/GmailPostfixFetchmail



thanks,

Nick


___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] Re: sasl_passwd hash

2023-12-17 Thread saunders.nicholas--- via Postfix-users

Would you be able to point me to anyone there, or a contact?

I'm not seeing any contact information.

thanks,

Nick


On Sun, 17 Dec 2023, Wietse Venema via Postfix-users wrote:


saunders.nicholas--- via Postfix-users:

/etc/postfix/sasl/sasl_passwd  is where I have it.  The example is:


That file is mainained by Cyrus SASL. Questions about implementation
details are bettere asked there.

Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] omitting the X-Google-Original-From header

2023-12-17 Thread saunders.nicholas--- via Postfix-users

How is this header populated?

X-Google-Original-From: nicho...@mordor.saundersconsulting.tech


What's interesting about this value is that the user name on localhost is 
nicholas.  The FQDN is as above.  There's no such e-mail address.  Well, I 
suppose mail on localhost to that e-mail will make its way to the user 
mail.


Can this value be explicitly set?  Or, preferably, even configured so that 
gmail doesn't generate and populate this header.


Is there a work-around to this header, so that it's never generated?




thanks,

Nick
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org


[pfx] TLS config for gmail relay

2023-12-23 Thread saunders.nicholas--- via Postfix-users
I think that I have the SASL figured out, and probably it's a similar 
process to get the tls_policy compliant and functional.  The log:



Dec 23 13:11:32 mordor postfix/smtp[287549]: error: open database 
/etc/postfix/tls_policy.db: No such file or directory
Dec 23 13:11:32 mordor postfix/smtp[287549]: warning: 
hash:/etc/postfix/tls_policy is unavailable. open database 
/etc/postfix/tls_policy.db: No such file or directory
Dec 23 13:11:32 mordor postfix/smtp[287549]: warning: 
hash:/etc/postfix/tls_policy lookup error for "[smtp.gmail.com]:587"




root@mordor:~#
root@mordor:~# postconf -n | grep tls
smtp_sasl_tls_security_options = noanonymous
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
smtp_tls_CApath = /etc/ssl/certs
smtp_tls_policy_maps = hash:/etc/postfix/tls_policy
smtp_tls_security_level = may
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtp_use_tls = yes
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_security_level = may
root@mordor:~#



I seem to recall needing generate a hash for this .db file, but can't seem 
to recall the details.  Is that about right?



thanks,

Nick
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org