> On 24 Nov 2019, at 03:42, Gianni Angelozzi wrote:
>
> In my system I have 10 users. Each user has his own upstream account on the
> ISP.
If you mentioned that before, I missed it.
> When I authenticate the SMTP connection, my ISP will only allow that user to
> send the mail. Like, if I u
In my system I have 10 users. Each user has his own upstream account on
the ISP.
I use postfix + dovecot + fetchmail as a local mail server, but the real
sending is done by my ISP. I only forward local mails and the rest goes
out by the ISP.
When I authenticate the SMTP connection, my ISP wi
On 23 Nov 2019, at 10:13, Gianni Angelozzi wrote:
> Yes, I need smtp_sender_dependent_authentication because the upstream ISP
> will only accept incoming mails from the authenticated user.
That doesn’t imply a need for smtp_sender_dependent_authentication. That is
needed, AIUI, when you have mu
Thanks for the reply.
Yes, I need smtp_sender_dependent_authentication because the upstream
ISP will only accept incoming mails from the authenticated user.
The feature you suggest may not work on my scenario, because if I send
email from user1 but authenticating with user2 (the default user)
Gianni Angelozzi:
[ Charset ISO-8859-15 converted... ]
> Hi,
>
> I've set up sieve vacation reply but my postfix setup is using
> smtp_sasl_password_maps and smtp_sender_dependent_authentication.
>
> The problem is that Sieve will send the reply with "from=<>" to prevent
> bounces.
>
> This me
Hi,
I've set up sieve vacation reply but my postfix setup is using
smtp_sasl_password_maps and smtp_sender_dependent_authentication.
The problem is that Sieve will send the reply with "from=<>" to prevent
bounces.
This means that Postfix has no way to authenticate to my ISP because it
does
