Re: [SOLVED] Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-11 Thread Paul Kudla
Happy Saturday !!! Thanks - paul Paul Kudla Scom.ca Internet Services 004-1009 Byron Street South Whitby, Ontario - Canada L1N 4S3 Toronto 416.642.7266 Main 1.866.411.7266 Fax 1.888.892.7266 Email p...@scom.ca On 2/11/2023 8:12 AM, Dr. Rolf Jansen wrote: Spare

[SOLVED] Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-11 Thread Dr. Rolf Jansen
Spare your breath. I have solved my issue AWS-SES, and it behaves well now with Pigeonhole Sieve Vacation (s. patch attached) Many thanks for all your thoughts. I will leave the list now. Best regards Rolf pigeonhole-vacation-sender-fix.patch Description: Binary data > Am 11.02.2023 um

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-11 Thread Paul Kudla
Ok again just trying to help ___ The question on why I use AWS-SES as my outbound mail relays can be simply answered with the attribute „superior reputation“. ___ that being said, again an experience thing that most people do not know about ! opensrs (i use them for my domain

RE: [OFF TOPIC] Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-11 Thread Marc
> > >> The actual problem is that Pigeonhole responds to to=<010301863b0211fe- > 9416f5b2-7e18-4c03-a5e5-2204dd7946f8-000...@sa-east-1.amazonses.com> instead > of to=. > Yes indeed, why are companies misusing the envelope for something different than it should be. The worst thing is even that

Re: [OFF TOPIC] Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-11 Thread Stuart Henderson
On 2023-02-10, Michael Peddemors wrote: > TOP POSTING for clarity > > I think this is getting off topic for the dovecot list. Vacation > messaging is a complex topic, and for the record it does seem that the > way they are doing vacation messages could use improvement. > > This should NOT be

[OFF TOPIC] Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-10 Thread Michael Peddemors
TOP POSTING for clarity I think this is getting off topic for the dovecot list. Vacation messaging is a complex topic, and for the record it does seem that the way they are doing vacation messages could use improvement. This should NOT be sent as a BOUNCE <>, and it should NOT come from

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-10 Thread Dr. Rolf Jansen
As stated elsewhere, the severe problem of incomprehensible OoO notice comes not because I relay MY outbound mails via Amazon’s SES but because some of MY PEERS (senders of the original messages and receivers of OoO notices) do or perhaps other relays which do funny manipulations of envelope

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-10 Thread Paul Kudla
Good morning, I have been following this post for a bit and would like to share experience please and thanks. This is not meant to give a solution but save some massive frustration with other system as i have gone through the same issues overall. In general I found found over the past few

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-10 Thread Dr. Rolf Jansen
> Am 08.02.2023 um 20:03 schrieb Michael Peddemors : > > Dovecot vacation message issues.. > Tough for any system to do correctly. > >> The problem here is that inbound mails from third parties utilizing AWS-SES >> come in with an unpersonalized envelope address and SES takes returns to >>

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-08 Thread Dr. Rolf Jansen
> Am 08.02.2023 um 09:27 schrieb Stephan Bosch : >> On 8-2-2023 13:10, Dr. Rolf Jansen wrote: >>> Am 08.02.2023 um 08:37 schrieb Stephan Bosch : >>> >>> https://doc.dovecot.org/settings/pigeonhole-ext/vacation/#pigeonhole_setting-sieve_vacation_send_from_recipient >>> >>> On 7-2-2023 15:01, Dr.

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-08 Thread Stephan Bosch
On 8-2-2023 13:10, Dr. Rolf Jansen wrote: Am 08.02.2023 um 08:37 schrieb Stephan Bosch : https://doc.dovecot.org/settings/pigeonhole-ext/vacation/#pigeonhole_setting-sieve_vacation_send_from_recipient On 7-2-2023 15:01, Dr. Rolf Jansen wrote: To begin with, usage of Amazons Simple Email

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-08 Thread Dr. Rolf Jansen
> Am 08.02.2023 um 08:37 schrieb Stephan Bosch : > > https://doc.dovecot.org/settings/pigeonhole-ext/vacation/#pigeonhole_setting-sieve_vacation_send_from_recipient > > On 7-2-2023 15:01, Dr. Rolf Jansen wrote: >> To begin with, usage of Amazons Simple Email Service (SES) is mandatory for >>

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-08 Thread Stephan Bosch
https://doc.dovecot.org/settings/pigeonhole-ext/vacation/#pigeonhole_setting-sieve_vacation_send_from_recipient On 7-2-2023 15:01, Dr. Rolf Jansen wrote: To begin with, usage of Amazons Simple Email Service (SES) is mandatory for outgoing mails from AWS-EC2 instances. The Pro is, it does work

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-07 Thread Dr. Rolf Jansen
> Am 07.02.2023 um 17:54 schrieb jeremy ardley : > > On 7/2/23 22:01, Dr. Rolf Jansen wrote: >> To begin with, usage of Amazons Simple Email Service (SES) is mandatory for >> outgoing mails from AWS-EC2 instances. > > I run AWS-EC2 instances using postfix to send a receive mail. They can send

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-07 Thread Plutocrat
On 2/8/23 05:33, jeremy ardley wrote: - AWS throttles but does not block traffic to a *destination* port 25. I set one up last week and can confirm that port 25 outbound was definitely blocked rather than throttled. However there's a form you can fill in to get it unblocked, and it only

[OFF TOPIC] Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-07 Thread Michael Peddemors
On 2023-02-07 13:33, jeremy ardley wrote: On 8/2/23 05:08, Dr. Rolf Jansen wrote: Am 07.02.2023 um 17:54 schrieb jeremy ardley: On 7/2/23 22:01, Dr. Rolf Jansen wrote: To begin with, usage of Amazons Simple Email Service (SES) is mandatory for outgoing mails from AWS-EC2 instances. I run

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-07 Thread jeremy ardley
On 8/2/23 05:08, Dr. Rolf Jansen wrote: Am 07.02.2023 um 17:54 schrieb jeremy ardley: On 7/2/23 22:01, Dr. Rolf Jansen wrote: To begin with, usage of Amazons Simple Email Service (SES) is mandatory for outgoing mails from AWS-EC2 instances. I run AWS-EC2 instances using postfix to send a

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-07 Thread Dr. Rolf Jansen
> Am 07.02.2023 um 17:54 schrieb jeremy ardley : > > On 7/2/23 22:01, Dr. Rolf Jansen wrote: >> To begin with, usage of Amazons Simple Email Service (SES) is mandatory for >> outgoing mails from AWS-EC2 instances. > > I run AWS-EC2 instances using postfix to send a receive mail. They can send

Re: Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-07 Thread jeremy ardley
On 7/2/23 22:01, Dr. Rolf Jansen wrote: To begin with, usage of Amazons Simple Email Service (SES) is mandatory for outgoing mails from AWS-EC2 instances. I run AWS-EC2 instances using postfix to send a receive mail. They can send direct assuming I set up suitable SPF, but they typically

Pigeonhole Sieve Vacation Reply-To peculiarity with inbound AWS-SES

2023-02-07 Thread Dr. Rolf Jansen
To begin with, usage of Amazons Simple Email Service (SES) is mandatory for outgoing mails from AWS-EC2 instances. The Pro is, it does work and we may utilize email relays with high reputation for our outgoing mails at no additional costs. The Con's are that (A) SES does not relay mails with