[qmailtoaster] Re: Qmailadmin weirdness

[Chris]

Found it.  When setting the domain defaults using
/home/vpopmail/bin/vmoddomlimits I had used NOQUOTA on the parameters
regarding the number of accounts, aliases, forwarders, etc.  While it
looked like it worked, this was the source of the missing menu items in
qmailadmin.  Once I re-ran the vmoddomlimits command against my domains
qmailadmin started behaving as expected.

-Chris

On Sun, Jun 9, 2024 at 4:04 PM Chris Knight  wrote:

> I’m still puttering along on my new toaster build, and I’ve hit a spot of
> the weird with qmailadmin.  After adding my home IP to the allow list in
> /etc/httpd/conf/toaster.conf and restarting httpd, I can access
> qmailadmin.  When I log in using the postmaster account of a test domain
> that I had manually added using /home/vpopmail/bin/vadddomain, I am only
> given a dashboard page of stats.  It lacks the links for adding accounts,
> aliases, and mailing lists.
>
> Has anyone else seen qmailadmin behave this way for a postmaster account?
> If so, did you find a fix?
>
> -Chris

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Gary Bowling]

  
  


You just have to have certbot installed (dnf install cerbot) and
  then have the timer active. That takes care of running it on a
  schedule and then you just configure it in all the directories
  under /etc/letsencrypt/
Here's what mine looks like.


[root@mail ~]# systemctl list-unit-files | grep certbot
certbot-renew.service
  static  -
certbot-renew.timer  
  enabled enabled

[root@mail ~]# systemctl list-timers certbot-renew.timer
  NEXT    LEFT  
  LAST   PASSED
  UNIT ACTIVATES
  Tue 2024-04-16 21:54:51 EDT 7h left Tue 2024-04-16 07:02:57 EDT 6h
  ago certbot-renew.timer certbot-renew.service
  

Once you get that done, Then you just need to set up apache with
  the virtualhosts and run certbot and it will prompt you for the
  virtualhost you want to set up a cert for. As long as you have
  apache and DNS configure correctly, it will challenge verify your
  site and install the cert. Once you get the cert set up, if you
  have the certbot-renew.timer enabled, it will take care of
  renewing that cert and execute the thing you put in the
  pre,post,deploy directories. 



Gary





On 4/16/2024 1:52 PM, Gary Bowling
  wrote:


  
  
  
  Yes, the script can go in those directories not in a cron. I
don't believe you have to call --deploy-hook on the command line
if the script is in those directories. Actually you don't call
anything in the command line, it's all done as part of the
certbot-renew.service and the certbot-renew.timer in systemd.
  That timer runs every day, but the cert won't renew unless it's
within 30 days of expiring. Whenever it renews it will run
whatever scripts are in those directories. Or at least that's my
understanding, I haven't had my script in the "post" directory
long enough yet to verify that it runs it, but that's my
understanding. I just moved my script to there from a cron based
on William's note. 
  
  
  
  Gary
  
  
  
  
  
  On 4/16/2024 10:34 AM, Eric Broch
wrote:
  
  

I thought William S. had mentioned something
  about a Let's Encrypt hook instead of a cron job. From what
  I've been reading, one's script simply goes in
  /etc/letsencrypt/renewal-hooks/{pre,post,deploy] or something
  like that, true? Then I suppose one calls certbot renew
  --deploy-hook or something like that. The documentation seemed
  sparse, anyway...
  
  
  Pipe in William if you have something.




  



  On Tue, Apr 16, 2024 at
6:33 AM Gary Bowling 
wrote:
  
  

  
  
  I'll help edit it if someone else that is currently
going through it wants to start it.  Maybe set up a
google doc and give some people edit access. Or give
read only access and we can drop comments/suggestions
back here for someone to edit. It's been a long time
since I set it up from scratch, so I'm a bit rusty on
that.
  
  
  
  It shouldn't be too hard to come up with something. I
like to do everything "standard" via the RH/Rocky way of
doing it. That way dnf updates work and I don't have as
much maintenance. So I don't compile, customize anything
unless I'm forced to.
  
  
  The only special part on my install is the script to
"cat" the certs and create a servercert.pem. Especially
with your new updates, if it works with ECDSA certs,
then no need for that custom rsa 2048 config part.
  
  
  With that, it should just be installing httpd, certbot,
and doing a standard config for the server name. The
only complication being if you use different names..
e.g. webmail.domain.com
and mail.domain.com or
something. It's much simpler if you use the same name
for both since letsencrypt queries back to the dns name
you set up on apache to validate. If you don't use the
same name, you either have to set up a dummy virtualhost
in apache to do the chal

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Gary Bowling]

  
  


Yes, the script can go in those directories not in a cron. I
  don't believe you have to call --deploy-hook on the command line
  if the script is in those directories. Actually you don't call
  anything in the command line, it's all done as part of the
  certbot-renew.service and the certbot-renew.timer in systemd.
That timer runs every day, but the cert won't renew unless it's
  within 30 days of expiring. Whenever it renews it will run
  whatever scripts are in those directories. Or at least that's my
  understanding, I haven't had my script in the "post" directory
  long enough yet to verify that it runs it, but that's my
  understanding. I just moved my script to there from a cron based
  on William's note. 



Gary





On 4/16/2024 10:34 AM, Eric Broch
  wrote:


  
  I thought William S. had mentioned something about
a Let's Encrypt hook instead of a cron job. From what I've been
reading, one's script simply goes in
/etc/letsencrypt/renewal-hooks/{pre,post,deploy] or something
like that, true? Then I suppose one calls certbot renew
--deploy-hook or something like that. The documentation seemed
sparse, anyway...


Pipe in William if you have something.
  
  
  
  

  
  
  
On Tue, Apr 16, 2024 at
  6:33 AM Gary Bowling 
  wrote:


  


I'll help edit it if someone else that is currently going
  through it wants to start it.  Maybe set up a google doc
  and give some people edit access. Or give read only access
  and we can drop comments/suggestions back here for someone
  to edit. It's been a long time since I set it up from
  scratch, so I'm a bit rusty on that.



It shouldn't be too hard to come up with something. I
  like to do everything "standard" via the RH/Rocky way of
  doing it. That way dnf updates work and I don't have as
  much maintenance. So I don't compile, customize anything
  unless I'm forced to.


The only special part on my install is the script to
  "cat" the certs and create a servercert.pem. Especially
  with your new updates, if it works with ECDSA certs, then
  no need for that custom rsa 2048 config part.


With that, it should just be installing httpd, certbot,
  and doing a standard config for the server name. The only
  complication being if you use different names.. e.g. webmail.domain.com and mail.domain.com or something.
  It's much simpler if you use the same name for both since
  letsencrypt queries back to the dns name you set up on
  apache to validate. If you don't use the same name, you
  either have to set up a dummy virtualhost in apache to do
  the challenge validation on that name, or you have to use
  another challenge method like DNS-01 to update your certs.
  Toaster doc should probably have examples of both.



Here's a generic letsencrypt setup for Rocky 8/9 and
  apache. Needs some tweaks to do the challenge verification
  back to your roundcube apache virtualhost instead of the
  default /var/www/html/ query. Or if you have separate
  names you can use the /var/www/html/ for the dummy
  virtualhost to get your mail server certs, but you'll
  still need another one for the roundcube virtualhost. 



https://www.cyberciti.biz/faq/how-to-secure-apache-with-lets-encrypt-certificates-on-rhel-8/


Hope this helps.. Gary



On 4/15/2024 1:33 PM, Eric Broch wrote:

Anyone feel like doing a write-up
  and I'll put it on the wiki? 
  
  On 4/15/2024 11:18 AM, Gary Bowling wrote: 
   

Ah, right. Actually it looks like I can just place my
script that I currently run in my cron job in the
/etc/letsencrypt/renewal-hooks/post/ directory and it
will run as a "post renew" script. 


Thanks for that. 

Gary 


On 4/15/2024 1:04 PM, William Silverstein wrote: 
I would not use a cron script. I
  use --deploy-

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[William Silverstein]

I suspect that it could be done either way.  I have been using
--deploy-hook since I started using letsencrypt. I'll look at the
/etc/letsencrypt/renewal-hooks when I build my new server (soon, I hope).

On Tue, April 16, 2024 7:34 am, Eric Broch wrote:
> I thought William S. had mentioned something about a Let's Encrypt hook
> instead of a cron job. From what I've been reading, one's script simply
> goes in /etc/letsencrypt/renewal-hooks/{pre,post,deploy] or something like
> that, true? Then I suppose one calls certbot renew --deploy-hook or
> something like that. The documentation seemed sparse, anyway...
>
> Pipe in William if you have something.
>
>
>
> On Tue, Apr 16, 2024 at 6:33 AM Gary Bowling  wrote:
>
>>
>> I'll help edit it if someone else that is currently going through it
>> wants
>> to start it.  Maybe set up a google doc and give some people edit
>> access.
>> Or give read only access and we can drop comments/suggestions back here
>> for
>> someone to edit. It's been a long time since I set it up from scratch,
>> so
>> I'm a bit rusty on that.
>>
>>
>> It shouldn't be too hard to come up with something. I like to do
>> everything "standard" via the RH/Rocky way of doing it. That way dnf
>> updates work and I don't have as much maintenance. So I don't compile,
>> customize anything unless I'm forced to.
>>
>>
>> The only special part on my install is the script to "cat" the certs and
>> create a servercert.pem. Especially with your new updates, if it works
>> with
>> ECDSA certs, then no need for that custom rsa 2048 config part.
>>
>>
>> With that, it should just be installing httpd, certbot, and doing a
>> standard config for the server name. The only complication being if you
>> use
>> different names.. e.g. webmail.domain.com and mail.domain.com or
>> something. It's much simpler if you use the same name for both since
>> letsencrypt queries back to the dns name you set up on apache to
>> validate.
>> If you don't use the same name, you either have to set up a dummy
>> virtualhost in apache to do the challenge validation on that name, or
>> you
>> have to use another challenge method like DNS-01 to update your certs.
>> Toaster doc should probably have examples of both.
>>
>>
>> Here's a generic letsencrypt setup for Rocky 8/9 and apache. Needs some
>> tweaks to do the challenge verification back to your roundcube apache
>> virtualhost instead of the default /var/www/html/ query. Or if you have
>> separate names you can use the /var/www/html/ for the dummy virtualhost
>> to
>> get your mail server certs, but you'll still need another one for the
>> roundcube virtualhost.
>>
>>
>>
>> https://www.cyberciti.biz/faq/how-to-secure-apache-with-lets-encrypt-certificates-on-rhel-8/
>>
>>
>> Hope this helps.. Gary
>>
>>
>> On 4/15/2024 1:33 PM, Eric Broch wrote:
>>
>> Anyone feel like doing a write-up and I'll put it on the wiki?
>>
>> On 4/15/2024 11:18 AM, Gary Bowling wrote:
>>
>>
>>
>> Ah, right. Actually it looks like I can just place my script that I
>> currently run in my cron job in the /etc/letsencrypt/renewal-hooks/post/
>> directory and it will run as a "post renew" script.
>>
>>
>> Thanks for that.
>>
>> Gary
>>
>>
>> On 4/15/2024 1:04 PM, William Silverstein wrote:
>>
>> I would not use a cron script. I use --deploy-hook option on the
>> certbot-auto to handle it.
>>
>>
>> On Mon, April 15, 2024 9:59 am, Gary Bowling wrote:
>>
>> Great. One question. Seems like everything on my server uses
>> /var/qmail/control/servercert.pem for the cert. Dovecot and qmail
>> all use that file. And I have a cron job that runs once a month to
>> check for a new letsencrypt cert and if there is one it copies it
>> over to servercert.pem to update my mail server.
>>
>>
>>
>>
>>
>> Is that the correct way to handle that? Or is that something that
>> is
>> left over from my old server that I moved over?
>>
>>
>>
>>
>> Thanks, Gary
>>
>>
>>
>>
>>   On 4/15/2024 12:44 PM, Eric Broch   wrote:
>>
>>
>> Neither,
>>
>> /var/qmail/control/dh2048.pem
>>   /var/qmail/control/rsa2048.pem
>>
>>
>> On 4/15/2024 10:33 AM, Gary Bowling wrote:
>>
>>
>>
>>
>>
>> Thanks, will still require rsa?
>>
>>
>>
>>   On 4/15/2024 10:47 AM, Eric Broch   wrote:
>>
>>
>> My next iteration on EL9 will remove keysize it's
>> deprecated,
>> has been for a while. Should have the new code out within
>> the
>> week.
>>
>> SSL_CTX_set_tmp_rsa_callback ·   openssl/openssl ·
>> Discussion #23769 (github.com)
>>
>>
>>
>> On 4/15/2024 6:25 AM, Gary Bowling wrote:
>>
>>
>>
>>
>>
>> Hey Jeff, glad you're making progress. Be aware that when
>> you get a new cert from Letsencrypt that the default now
>> retrieves an ECDSA cert. Which is fine for apache, but
>> doesn't work on qmail, or at least it didn't for me. To
>> fix
>> that you'll need to configure letsencrypt to give you   an
>> RSA
>> 2048 cert.
>>
>>
>>
>>
>>
>> There are two

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Eric Broch]

I thought William S. had mentioned something about a Let's Encrypt hook
instead of a cron job. From what I've been reading, one's script simply
goes in /etc/letsencrypt/renewal-hooks/{pre,post,deploy] or something like
that, true? Then I suppose one calls certbot renew --deploy-hook or
something like that. The documentation seemed sparse, anyway...

Pipe in William if you have something.



On Tue, Apr 16, 2024 at 6:33 AM Gary Bowling  wrote:

>
> I'll help edit it if someone else that is currently going through it wants
> to start it.  Maybe set up a google doc and give some people edit access.
> Or give read only access and we can drop comments/suggestions back here for
> someone to edit. It's been a long time since I set it up from scratch, so
> I'm a bit rusty on that.
>
>
> It shouldn't be too hard to come up with something. I like to do
> everything "standard" via the RH/Rocky way of doing it. That way dnf
> updates work and I don't have as much maintenance. So I don't compile,
> customize anything unless I'm forced to.
>
>
> The only special part on my install is the script to "cat" the certs and
> create a servercert.pem. Especially with your new updates, if it works with
> ECDSA certs, then no need for that custom rsa 2048 config part.
>
>
> With that, it should just be installing httpd, certbot, and doing a
> standard config for the server name. The only complication being if you use
> different names.. e.g. webmail.domain.com and mail.domain.com or
> something. It's much simpler if you use the same name for both since
> letsencrypt queries back to the dns name you set up on apache to validate.
> If you don't use the same name, you either have to set up a dummy
> virtualhost in apache to do the challenge validation on that name, or you
> have to use another challenge method like DNS-01 to update your certs.
> Toaster doc should probably have examples of both.
>
>
> Here's a generic letsencrypt setup for Rocky 8/9 and apache. Needs some
> tweaks to do the challenge verification back to your roundcube apache
> virtualhost instead of the default /var/www/html/ query. Or if you have
> separate names you can use the /var/www/html/ for the dummy virtualhost to
> get your mail server certs, but you'll still need another one for the
> roundcube virtualhost.
>
>
>
> https://www.cyberciti.biz/faq/how-to-secure-apache-with-lets-encrypt-certificates-on-rhel-8/
>
>
> Hope this helps.. Gary
>
>
> On 4/15/2024 1:33 PM, Eric Broch wrote:
>
> Anyone feel like doing a write-up and I'll put it on the wiki?
>
> On 4/15/2024 11:18 AM, Gary Bowling wrote:
>
>
>
> Ah, right. Actually it looks like I can just place my script that I
> currently run in my cron job in the /etc/letsencrypt/renewal-hooks/post/
> directory and it will run as a "post renew" script.
>
>
> Thanks for that.
>
> Gary
>
>
> On 4/15/2024 1:04 PM, William Silverstein wrote:
>
> I would not use a cron script. I use --deploy-hook option on the
> certbot-auto to handle it.
>
>
> On Mon, April 15, 2024 9:59 am, Gary Bowling wrote:
>
> Great. One question. Seems like everything on my server uses
> /var/qmail/control/servercert.pem for the cert. Dovecot and qmail
> all use that file. And I have a cron job that runs once a month to
> check for a new letsencrypt cert and if there is one it copies it
> over to servercert.pem to update my mail server.
>
>
>
>
>
> Is that the correct way to handle that? Or is that something that   is
> left over from my old server that I moved over?
>
>
>
>
> Thanks, Gary
>
>
>
>
>   On 4/15/2024 12:44 PM, Eric Broch   wrote:
>
>
> Neither,
>
> /var/qmail/control/dh2048.pem
>   /var/qmail/control/rsa2048.pem
>
>
> On 4/15/2024 10:33 AM, Gary Bowling wrote:
>
>
>
>
>
> Thanks, will still require rsa?
>
>
>
>   On 4/15/2024 10:47 AM, Eric Broch   wrote:
>
>
> My next iteration on EL9 will remove keysize it's deprecated,
> has been for a while. Should have the new code out within the
> week.
>
> SSL_CTX_set_tmp_rsa_callback ·   openssl/openssl ·
> Discussion #23769 (github.com)
>
>
>
> On 4/15/2024 6:25 AM, Gary Bowling wrote:
>
>
>
>
>
> Hey Jeff, glad you're making progress. Be aware that when
> you get a new cert from Letsencrypt that the default now
> retrieves an ECDSA cert. Which is fine for apache, but
> doesn't work on qmail, or at least it didn't for me. To   fix
> that you'll need to configure letsencrypt to give you   an RSA
> 2048 cert.
>
>
>
>
>
> There are two ways to do that. If you want all your certs   to
> be RSA 2048, you can add this to the
> /etc/letsencrypt/cli.ini file.
>
> key-type = rsa
> rsa-key-size = 2048
>
>
>
>
> If you just want to do that for your keys you use in   qmail,
> then you can put the above in the
> /etc/letsencrypt/renewal/domain.conf file. Where "domain"   is
> the name of the cert you're renewing. Ce

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Gary Bowling]

  
  


I'll help edit it if someone else that is currently going through
  it wants to start it.  Maybe set up a google doc and give some
  people edit access. Or give read only access and we can drop
  comments/suggestions back here for someone to edit. It's been a
  long time since I set it up from scratch, so I'm a bit rusty on
  that.



It shouldn't be too hard to come up with something. I like to do
  everything "standard" via the RH/Rocky way of doing it. That way
  dnf updates work and I don't have as much maintenance. So I don't
  compile, customize anything unless I'm forced to.


The only special part on my install is the script to "cat" the
  certs and create a servercert.pem. Especially with your new
  updates, if it works with ECDSA certs, then no need for that
  custom rsa 2048 config part.


With that, it should just be installing httpd, certbot, and doing
  a standard config for the server name. The only complication being
  if you use different names.. e.g. webmail.domain.com and
  mail.domain.com or something. It's much simpler if you use the
  same name for both since letsencrypt queries back to the dns name
  you set up on apache to validate. If you don't use the same name,
  you either have to set up a dummy virtualhost in apache to do the
  challenge validation on that name, or you have to use another
  challenge method like DNS-01 to update your certs. Toaster doc
  should probably have examples of both.



Here's a generic letsencrypt setup for Rocky 8/9 and apache.
  Needs some tweaks to do the challenge verification back to your
  roundcube apache virtualhost instead of the default /var/www/html/
  query. Or if you have separate names you can use the
  /var/www/html/ for the dummy virtualhost to get your mail server
  certs, but you'll still need another one for the roundcube
  virtualhost. 



https://www.cyberciti.biz/faq/how-to-secure-apache-with-lets-encrypt-certificates-on-rhel-8/


Hope this helps.. Gary



On 4/15/2024 1:33 PM, Eric Broch wrote:

Anyone
  feel like doing a write-up and I'll put it on the wiki? 
  
  On 4/15/2024 11:18 AM, Gary Bowling wrote: 
   

Ah, right. Actually it looks like I can just place my script
that I currently run in my cron job in the
/etc/letsencrypt/renewal-hooks/post/ directory and it will run
as a "post renew" script. 


Thanks for that. 

Gary 


On 4/15/2024 1:04 PM, William Silverstein wrote: 
I would not use a cron script. I use
  --deploy-hook option on the 
  certbot-auto to handle it. 
  
  
  On Mon, April 15, 2024 9:59 am, Gary Bowling wrote: 
  Great. One question. Seems like
everything on my server uses 
/var/qmail/control/servercert.pem for the cert. Dovecot and
qmail 
all use that file. And I have a cron job that runs once a
month to 
check for a new letsencrypt cert and if there is one it
copies it 
over to servercert.pem to update my mail server. 





Is that the correct way to handle that? Or is that something
that   is 
left over from my old server that I moved over? 




Thanks, Gary 




  On 4/15/2024 12:44 PM, Eric Broch   wrote: 


Neither, 

/var/qmail/control/dh2048.pem 
  /var/qmail/control/rsa2048.pem 


    On 4/15/2024 10:33 AM, Gary Bowling wrote: 





Thanks, will still require rsa? 



  On 4/15/2024 10:47 AM, Eric Broch   wrote:



My next iteration on EL9 will remove keysize
it's deprecated, 
has been for a while. Should have the new code
out within the 
week. 

SSL_CTX_set_tmp_rsa_callback ·  
openssl/openssl · 
Discussion #23769 (github.com) 



    On 4/15/2024 6:25 AM, Gary Bowling
wrote: 





Hey Jeff, glad you're making progress. Be aware that when 
you get a new cert from Letsencrypt 

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Eric Broch]

I'm not sure how many are using EL8, but I'll have that ready in a couple
days

On Mon, Apr 15, 2024 at 8:47 PM Eric Broch  wrote:

> qmail-1.03-3.3.9
>
> It has eliminated the need for dh and rsa keys
>
> Eric
>
> On Mon, Apr 15, 2024 at 10:44 AM Eric Broch 
> wrote:
>
>> Neither,
>>
>> /var/qmail/control/dh2048.pem
>> /var/qmail/control/rsa2048.pem
>>
>> On 4/15/2024 10:33 AM, Gary Bowling wrote:
>>
>>
>> Thanks, will still require rsa?
>>
>>
>> On 4/15/2024 10:47 AM, Eric Broch wrote:
>>
>> My next iteration on EL9 will remove keysize it's deprecated, has been
>> for a while. Should have the new code out within the week.
>>
>> SSL_CTX_set_tmp_rsa_callback · openssl/openssl · Discussion #23769
>> (github.com) 
>>
>>
>> On 4/15/2024 6:25 AM, Gary Bowling wrote:
>>
>>
>> Hey Jeff, glad you're making progress. Be aware that when you get a new
>> cert from Letsencrypt that the default now retrieves an ECDSA cert. Which
>> is fine for apache, but doesn't work on qmail, or at least it didn't for
>> me. To fix that you'll need to configure letsencrypt to give you an RSA
>> 2048 cert.
>>
>>
>> There are two ways to do that. If you want all your certs to be RSA 2048,
>> you can add this to the /etc/letsencrypt/cli.ini file.
>>
>> key-type = rsa
>> rsa-key-size = 2048
>>
>>
>> If you just want to do that for your keys you use in qmail, then you can
>> put the above in the /etc/letsencrypt/renewal/domain.conf file. Where
>> "domain" is the name of the cert you're renewing. Certbot creates the file
>> so it should already be there.
>>
>>
>> Gary
>>
>>
>> On 4/14/2024 10:39 PM, Jeff Koch wrote:
>>
>> I may have resolved this. I did the Rocy9 distro install of apache and
>> copied the mod_http2.so file over to our install of apache. Seems to work
>> (no errors) but I won't know for sure until we setup Lets Encrypt SSL
>> certbot tomorrow
>>
>> Jeff
>>
>> On 4/14/2024 3:11 PM, Jeff Koch wrote:
>>
>>
>> Hi - we're setting up a new mailserver with Rocky 9 and the learning
>> curve is slow as is usual with the first time with a new distro.
>>
>> Anyway because our various scripts look for apache at /usr/local/apache/
>> we've decided to compile our own binary with the latest apache and have run
>> into trouble / errors related to 'nghttp2'.
>>
>> We did download, compile and install the latest nghttp2-1.61.0 from
>> github. The configure and make went well and http1.1 works but apache
>> generates the following error when we activate  mod_http2
>>
>>  (Cannot load modules/mod_http2.so into server:
>> /usr/local/apache2/modules/mod_http2.so: undefined symbol:
>> nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)
>>
>> If anyone on the list has compiled their own httpd 2.4.59 with Rocky 9
>> would you mind sharing the details ?
>>
>> Thanks, Jeff Koch
>>
>>
>>
>> - To
>> unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For
>> additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>
>> - To
>> unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For
>> additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>
>>

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Eric Broch]

qmail-1.03-3.3.9

It has eliminated the need for dh and rsa keys

Eric

On Mon, Apr 15, 2024 at 10:44 AM Eric Broch  wrote:

> Neither,
>
> /var/qmail/control/dh2048.pem
> /var/qmail/control/rsa2048.pem
>
> On 4/15/2024 10:33 AM, Gary Bowling wrote:
>
>
> Thanks, will still require rsa?
>
>
> On 4/15/2024 10:47 AM, Eric Broch wrote:
>
> My next iteration on EL9 will remove keysize it's deprecated, has been for
> a while. Should have the new code out within the week.
>
> SSL_CTX_set_tmp_rsa_callback · openssl/openssl · Discussion #23769
> (github.com) 
>
>
> On 4/15/2024 6:25 AM, Gary Bowling wrote:
>
>
> Hey Jeff, glad you're making progress. Be aware that when you get a new
> cert from Letsencrypt that the default now retrieves an ECDSA cert. Which
> is fine for apache, but doesn't work on qmail, or at least it didn't for
> me. To fix that you'll need to configure letsencrypt to give you an RSA
> 2048 cert.
>
>
> There are two ways to do that. If you want all your certs to be RSA 2048,
> you can add this to the /etc/letsencrypt/cli.ini file.
>
> key-type = rsa
> rsa-key-size = 2048
>
>
> If you just want to do that for your keys you use in qmail, then you can
> put the above in the /etc/letsencrypt/renewal/domain.conf file. Where
> "domain" is the name of the cert you're renewing. Certbot creates the file
> so it should already be there.
>
>
> Gary
>
>
> On 4/14/2024 10:39 PM, Jeff Koch wrote:
>
> I may have resolved this. I did the Rocy9 distro install of apache and
> copied the mod_http2.so file over to our install of apache. Seems to work
> (no errors) but I won't know for sure until we setup Lets Encrypt SSL
> certbot tomorrow
>
> Jeff
>
> On 4/14/2024 3:11 PM, Jeff Koch wrote:
>
>
> Hi - we're setting up a new mailserver with Rocky 9 and the learning curve
> is slow as is usual with the first time with a new distro.
>
> Anyway because our various scripts look for apache at /usr/local/apache/
> we've decided to compile our own binary with the latest apache and have run
> into trouble / errors related to 'nghttp2'.
>
> We did download, compile and install the latest nghttp2-1.61.0 from
> github. The configure and make went well and http1.1 works but apache
> generates the following error when we activate  mod_http2
>
>  (Cannot load modules/mod_http2.so into server:
> /usr/local/apache2/modules/mod_http2.so: undefined symbol:
> nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)
>
> If anyone on the list has compiled their own httpd 2.4.59 with Rocky 9
> would you mind sharing the details ?
>
> Thanks, Jeff Koch
>
>
>
> - To
> unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For
> additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
> - To
> unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For
> additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Eric Broch]

Anyone feel like doing a write-up and I'll put it on the wiki?

On 4/15/2024 11:18 AM, Gary Bowling wrote:



Ah, right. Actually it looks like I can just place my script that I 
currently run in my cron job in the 
/etc/letsencrypt/renewal-hooks/post/ directory and it will run as a 
"post renew" script.



Thanks for that.

Gary


On 4/15/2024 1:04 PM, William Silverstein wrote:

I would not use a cron script. I use --deploy-hook option on the
certbot-auto to handle it.


On Mon, April 15, 2024 9:59 am, Gary Bowling wrote:

Great. One question. Seems like everything on my server uses
/var/qmail/control/servercert.pem for the cert. Dovecot and qmail
all use that file. And I have a cron job that runs once a month to
check for a new letsencrypt cert and if there is one it copies it
over to servercert.pem to update my mail server.





Is that the correct way to handle that? Or is that something that   is
left over from my old server that I moved over?




Thanks, Gary




  On 4/15/2024 12:44 PM, Eric Broch   wrote:


Neither,

/var/qmail/control/dh2048.pem
  /var/qmail/control/rsa2048.pem


On 4/15/2024 10:33 AM, Gary Bowling wrote:





Thanks, will still require rsa?



  On 4/15/2024 10:47 AM, Eric Broch   wrote:


My next iteration on EL9 will remove keysize it's deprecated,
has been for a while. Should have the new code out within the
week.

SSL_CTX_set_tmp_rsa_callback ·   openssl/openssl ·
Discussion #23769 (github.com)



On 4/15/2024 6:25 AM, Gary Bowling wrote:





Hey Jeff, glad you're making progress. Be aware that when
you get a new cert from Letsencrypt that the default now
retrieves an ECDSA cert. Which is fine for apache, but
doesn't work on qmail, or at least it didn't for me. To   fix
that you'll need to configure letsencrypt to give you   an RSA
2048 cert.





There are two ways to do that. If you want all your certs   to
be RSA 2048, you can add this to the
/etc/letsencrypt/cli.ini file.

key-type = rsa
rsa-key-size = 2048




If you just want to do that for your keys you use in   qmail,
then you can put the above in the
/etc/letsencrypt/renewal/domain.conf file. Where "domain"   is
the name of the cert you're renewing. Certbot creates   the
file so it should already be there.




Gary




  On 4/14/2024 10:39 PM, Jeff   Koch wrote:

I may have resolved this. I did
the Rocy9
distro install of apache and
copied the
mod_http2.so file over to our
install of apache. Seems
  to work (no errors)
but I won't know for sure until
we setup Lets
Encrypt SSL certbot tomorrow

  Jeff

On 4/14/2024 3:11 PM, Jeff Koch wrote:


  Hi - we're setting up a new mailserver with Rocky 9 and
   the learning curve is slow as is usual with
the first time with a new distro.

  Anyway because our various scripts look for apache at
 /usr/local/apache/ we've decided to compile
our own binary with the latest apache and
have run into trouble / errors related to
'nghttp2'.

  We did download, compile and install the latest
   nghttp2-1.61.0 from github. The configure and make
went well and http1.1 works but apache
generates the following error when we
activate  mod_http2

   (Cannot load modules/mod_http2.so into server:
/usr/local/apache2/modules/mod_http2.so: undefined
 symbol:
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)

  If anyone on the list has compiled their own httpd
  2.4.59 with Rocky 9 would you mind sharing the
details ?

  Thanks, Jeff Koch



   
-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com  For
additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com  For
additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
- 
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Gary Bowling]

  
  


Ah, right. Actually it looks like I can just place my script that
  I currently run in my cron job in the
  /etc/letsencrypt/renewal-hooks/post/ directory and it will run as
  a "post renew" script. 



Thanks for that. 

Gary



On 4/15/2024 1:04 PM, William
  Silverstein wrote:


  I would not use a cron script. I use --deploy-hook option on the
certbot-auto to handle it.


On Mon, April 15, 2024 9:59 am, Gary Bowling wrote:

  




Great. One question. Seems like everything on my server uses
/var/qmail/control/servercert.pem for the cert. Dovecot and qmail
all use that file. And I have a cron job that runs once a month to
check for a new letsencrypt cert and if there is one it copies it
over to servercert.pem to update my mail server.





Is that the correct way to handle that? Or is that something that   is
left over from my old server that I moved over?




Thanks, Gary




 On 4/15/2024 12:44 PM, Eric Broch   wrote:


Neither,

/var/qmail/control/dh2048.pem
 /var/qmail/control/rsa2048.pem


   On 4/15/2024 10:33 AM, Gary Bowling wrote:





Thanks, will still require rsa?



 On 4/15/2024 10:47 AM, Eric Broch   wrote:


My next iteration on EL9 will remove keysize it's deprecated,
has been for a while. Should have the new code out within the
week.

SSL_CTX_set_tmp_rsa_callback ·   openssl/openssl ·
Discussion #23769 (github.com)



   On 4/15/2024 6:25 AM, Gary Bowling wrote:





Hey Jeff, glad you're making progress. Be aware that when
you get a new cert from Letsencrypt that the default now
retrieves an ECDSA cert. Which is fine for apache, but
doesn't work on qmail, or at least it didn't for me. To   fix
that you'll need to configure letsencrypt to give you   an RSA
2048 cert.





There are two ways to do that. If you want all your certs   to
be RSA 2048, you can add this to the
/etc/letsencrypt/cli.ini file.

key-type = rsa
   rsa-key-size = 2048




If you just want to do that for your keys you use in   qmail,
then you can put the above in the
/etc/letsencrypt/renewal/domain.conf file. Where "domain"   is
the name of the cert you're renewing. Certbot creates   the
file so it should already be there.




Gary




 On 4/14/2024 10:39 PM, Jeff   Koch wrote:

   I may have resolved this. I did
the Rocy9
distro install of apache and
copied the
mod_http2.so file over to our
install of apache. Seems
 to work (no errors)
but I won't know for sure until
we setup Lets
Encrypt SSL certbot tomorrow

 Jeff

   On 4/14/2024 3:11 PM, Jeff Koch wrote:


 Hi - we're setting up a new mailserver with Rocky 9 and
  the learning curve is slow as is usual with
the first time with a new distro.

 Anyway because our various scripts look for apache at
/usr/local/apache/ we've decided to compile
our own binary with the latest apache and
have run into trouble / errors related to
'nghttp2'.

 We did download, compile and install the latest
  nghttp2-1.61.0 from github. The configure and make
went well and http1.1 works but apache
generates the following error when we
activate  mod_http2

  (Cannot load modules/mod_http2.so into server:
   /usr/local/apache2/modules/mod_http2.so: undefined
symbol:
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)

 If anyone on the list has compiled their own httpd
 2.4.59 with Rocky 9 would you mind sharing the
details ?

 Thanks, Jeff Koch



  -
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com For
additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com For
additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com

  
  



  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[William Silverstein]

I would not use a cron script. I use --deploy-hook option on the
certbot-auto to handle it.


On Mon, April 15, 2024 9:59 am, Gary Bowling wrote:
>
>
>
>
> Great. One question. Seems like everything on my server uses
> /var/qmail/control/servercert.pem for the cert. Dovecot and qmail
> all use that file. And I have a cron job that runs once a month to
> check for a new letsencrypt cert and if there is one it copies it
> over to servercert.pem to update my mail server.
>
>
>
>
>
> Is that the correct way to handle that? Or is that something that   is
> left over from my old server that I moved over?
>
>
>
>
> Thanks, Gary
>
>
>
>
>  On 4/15/2024 12:44 PM, Eric Broch   wrote:
>
>
> Neither,
>
> /var/qmail/control/dh2048.pem
>  /var/qmail/control/rsa2048.pem
>
>
>On 4/15/2024 10:33 AM, Gary Bowling wrote:
>
>
>
>
>
> Thanks, will still require rsa?
>
>
>
>  On 4/15/2024 10:47 AM, Eric Broch   wrote:
>
>
> My next iteration on EL9 will remove keysize it's deprecated,
> has been for a while. Should have the new code out within the
> week.
>
> SSL_CTX_set_tmp_rsa_callback ·   openssl/openssl ·
> Discussion #23769 (github.com)
>
>
>
>On 4/15/2024 6:25 AM, Gary Bowling wrote:
>
>
>
>
>
> Hey Jeff, glad you're making progress. Be aware that when
> you get a new cert from Letsencrypt that the default now
> retrieves an ECDSA cert. Which is fine for apache, but
> doesn't work on qmail, or at least it didn't for me. To   fix
> that you'll need to configure letsencrypt to give you   an RSA
> 2048 cert.
>
>
>
>
>
> There are two ways to do that. If you want all your certs   to
> be RSA 2048, you can add this to the
> /etc/letsencrypt/cli.ini file.
>
> key-type = rsa
>rsa-key-size = 2048
>
>
>
>
> If you just want to do that for your keys you use in   qmail,
> then you can put the above in the
> /etc/letsencrypt/renewal/domain.conf file. Where "domain"   is
> the name of the cert you're renewing. Certbot creates   the
> file so it should already be there.
>
>
>
>
> Gary
>
>
>
>
>  On 4/14/2024 10:39 PM, Jeff   Koch wrote:
>
>I may have resolved this. I did
> the Rocy9
> distro install of apache and
> copied the
> mod_http2.so file over to our
> install of apache. Seems
>  to work (no errors)
> but I won't know for sure until
> we setup Lets
> Encrypt SSL certbot tomorrow
>
>  Jeff
>
>On 4/14/2024 3:11 PM, Jeff Koch wrote:
>
>
>  Hi - we're setting up a new mailserver with Rocky 9 and
>   the learning curve is slow as is usual with
> the first time with a new distro.
>
>  Anyway because our various scripts look for apache at
> /usr/local/apache/ we've decided to compile
> our own binary with the latest apache and
> have run into trouble / errors related to
> 'nghttp2'.
>
>  We did download, compile and install the latest
>   nghttp2-1.61.0 from github. The configure and make
> went well and http1.1 works but apache
> generates the following error when we
> activate  mod_http2
>
>   (Cannot load modules/mod_http2.so into server:
>/usr/local/apache2/modules/mod_http2.so: undefined
> symbol:
> nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)
>
>  If anyone on the list has compiled their own httpd
>  2.4.59 with Rocky 9 would you mind sharing the
> details ?
>
>  Thanks, Jeff Koch
>
>
>
>   
> -
> To unsubscribe, e-mail:
> qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail:
> qmailtoaster-list-h...@qmailtoaster.com
> -
> To unsubscribe, e-mail:
> qmailtoaster-list-unsubscr...@qmailtoaster.com For
> additional commands, e-mail:
> qmailtoaster-list-h...@qmailtoaster.com
> -
> To unsubscribe, e-mail:
> qmailtoaster-list-unsubscr...@qmailtoaster.com For
> additional commands, e-mail:
> qmailtoaster-list-h...@qmailtoaster.com


-- 
William G. Silverstein, Esq.
Litigation Counsel
Licensed in California.




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Gary Bowling]

  
  


Great. One question. Seems like everything on my server uses
  /var/qmail/control/servercert.pem for the cert. Dovecot and qmail
  all use that file. And I have a cron job that runs once a month to
  check for a new letsencrypt cert and if there is one it copies it
  over to servercert.pem to update my mail server.



Is that the correct way to handle that? Or is that something that
  is left over from my old server that I moved over?


Thanks, Gary



On 4/15/2024 12:44 PM, Eric Broch
  wrote:


  
  Neither,
  /var/qmail/control/dh2048.pem
/var/qmail/control/rsa2048.pem

  
  On 4/15/2024 10:33 AM, Gary Bowling
wrote:
  
  



Thanks, will still require rsa?


On 4/15/2024 10:47 AM, Eric Broch
  wrote:


  
  My next iteration on EL9 will remove keysize it's
deprecated, has been for a while. Should have the new code
out within the week.
  SSL_CTX_set_tmp_rsa_callback ·
  openssl/openssl · Discussion #23769 (github.com)
  
  
  On 4/15/2024 6:25 AM, Gary
Bowling wrote:
  
  



Hey Jeff, glad you're making progress. Be aware that when
  you get a new cert from Letsencrypt that the default now
  retrieves an ECDSA cert. Which is fine for apache, but
  doesn't work on qmail, or at least it didn't for me. To
  fix that you'll need to configure letsencrypt to give you
  an RSA 2048 cert. 



There are two ways to do that. If you want all your certs
  to be RSA 2048, you can add this to the
  /etc/letsencrypt/cli.ini file.
key-type = rsa
  rsa-key-size = 2048


If you just want to do that for your keys you use in
  qmail, then you can put the above in the
  /etc/letsencrypt/renewal/domain.conf file. Where "domain"
  is the name of the cert you're renewing. Certbot creates
  the file so it should already be there.


Gary



On 4/14/2024 10:39 PM, Jeff
  Koch wrote:


  
  I may have resolved this. I did the
Rocy9 distro install of apache and copied the
mod_http2.so file over to our install of apache. Seems
to work (no errors) but I won't know for sure until we
setup Lets Encrypt SSL certbot tomorrow

Jeff
  
  On 4/14/2024 3:11 PM, Jeff
Koch wrote:
  
   
Hi - we're setting up a new mailserver with Rocky 9 and
the learning curve is slow as is usual with the first
time with a new distro. 

Anyway because our various scripts look for apache at
/usr/local/apache/ we've decided to compile our own
binary with the latest apache and have run into trouble
/ errors related to 'nghttp2'. 

We did download, compile and install the latest
nghttp2-1.61.0 from github. The configure and make went
well and http1.1 works but apache generates the
following error when we activate  mod_http2 

 (Cannot load modules/mod_http2.so into server:
/usr/local/apache2/modules/mod_http2.so: undefined
symbol:
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation) 

If anyone on the list has compiled their own httpd
2.4.59 with Rocky 9 would you mind sharing the details ?


Thanks, Jeff Koch 


  
  

- To
unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
  

- To
unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
  

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h..

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Eric Broch]

Neither,

/var/qmail/control/dh2048.pem
/var/qmail/control/rsa2048.pem

On 4/15/2024 10:33 AM, Gary Bowling wrote:



Thanks, will still require rsa?


On 4/15/2024 10:47 AM, Eric Broch wrote:


My next iteration on EL9 will remove keysize it's deprecated, has 
been for a while. Should have the new code out within the week.


SSL_CTX_set_tmp_rsa_callback · openssl/openssl · Discussion #23769 
(github.com) 



On 4/15/2024 6:25 AM, Gary Bowling wrote:



Hey Jeff, glad you're making progress. Be aware that when you get a 
new cert from Letsencrypt that the default now retrieves an ECDSA 
cert. Which is fine for apache, but doesn't work on qmail, or at 
least it didn't for me. To fix that you'll need to configure 
letsencrypt to give you an RSA 2048 cert.



There are two ways to do that. If you want all your certs to be RSA 
2048, you can add this to the /etc/letsencrypt/cli.ini file.


key-type = rsa
rsa-key-size = 2048


If you just want to do that for your keys you use in qmail, then you 
can put the above in the /etc/letsencrypt/renewal/domain.conf file. 
Where "domain" is the name of the cert you're renewing. Certbot 
creates the file so it should already be there.



Gary


On 4/14/2024 10:39 PM, Jeff Koch wrote:
I may have resolved this. I did the Rocy9 distro install of apache 
and copied the mod_http2.so file over to our install of apache. 
Seems to work (no errors) but I won't know for sure until we setup 
Lets Encrypt SSL certbot tomorrow


Jeff

On 4/14/2024 3:11 PM, Jeff Koch wrote:


Hi - we're setting up a new mailserver with Rocky 9 and the 
learning curve is slow as is usual with the first time with a new 
distro.


Anyway because our various scripts look for apache at 
/usr/local/apache/ we've decided to compile our own binary with 
the latest apache and have run into trouble / errors related to 
'nghttp2'.


We did download, compile and install the latest nghttp2-1.61.0 
from github. The configure and make went well and http1.1 works 
but apache generates the following error when we activate  mod_http2


 (Cannot load modules/mod_http2.so into server: 
/usr/local/apache2/modules/mod_http2.so: undefined symbol: 
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)


If anyone on the list has compiled their own httpd 2.4.59 with 
Rocky 9 would you mind sharing the details ?


Thanks, Jeff Koch




- 
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com For additional 
commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
- 
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Gary Bowling]

  
  


Thanks, will still require rsa?


On 4/15/2024 10:47 AM, Eric Broch
  wrote:


  
  My next iteration on EL9 will remove keysize it's deprecated,
has been for a while. Should have the new code out within the
week.
  SSL_CTX_set_tmp_rsa_callback ·
  openssl/openssl · Discussion #23769 (github.com)
  
  
  On 4/15/2024 6:25 AM, Gary Bowling
wrote:
  
  



Hey Jeff, glad you're making progress. Be aware that when you
  get a new cert from Letsencrypt that the default now retrieves
  an ECDSA cert. Which is fine for apache, but doesn't work on
  qmail, or at least it didn't for me. To fix that you'll need
  to configure letsencrypt to give you an RSA 2048 cert. 



There are two ways to do that. If you want all your certs to
  be RSA 2048, you can add this to the /etc/letsencrypt/cli.ini
  file.
key-type = rsa
  rsa-key-size = 2048


If you just want to do that for your keys you use in qmail,
  then you can put the above in the
  /etc/letsencrypt/renewal/domain.conf file. Where "domain" is
  the name of the cert you're renewing. Certbot creates the file
  so it should already be there.


Gary



On 4/14/2024 10:39 PM, Jeff Koch
  wrote:


  
  I may have resolved this. I did the Rocy9
distro install of apache and copied the mod_http2.so file
over to our install of apache. Seems to work (no errors) but
I won't know for sure until we setup Lets Encrypt SSL
certbot tomorrow

Jeff
  
  On 4/14/2024 3:11 PM, Jeff Koch
wrote:
  
   
Hi - we're setting up a new mailserver with Rocky 9 and the
learning curve is slow as is usual with the first time with
a new distro. 

Anyway because our various scripts look for apache at
/usr/local/apache/ we've decided to compile our own binary
with the latest apache and have run into trouble / errors
related to 'nghttp2'. 

We did download, compile and install the latest
nghttp2-1.61.0 from github. The configure and make went well
and http1.1 works but apache generates the following error
when we activate  mod_http2 

 (Cannot load modules/mod_http2.so into server:
/usr/local/apache2/modules/mod_http2.so: undefined symbol:
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)


If anyone on the list has compiled their own httpd 2.4.59
with Rocky 9 would you mind sharing the details ? 

Thanks, Jeff Koch 


  
  

- To
unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
  

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Eric Broch]

My next iteration on EL9 will remove keysize it's deprecated, has been 
for a while. Should have the new code out within the week.


SSL_CTX_set_tmp_rsa_callback · openssl/openssl · Discussion #23769 
(github.com) 



On 4/15/2024 6:25 AM, Gary Bowling wrote:



Hey Jeff, glad you're making progress. Be aware that when you get a 
new cert from Letsencrypt that the default now retrieves an ECDSA 
cert. Which is fine for apache, but doesn't work on qmail, or at least 
it didn't for me. To fix that you'll need to configure letsencrypt to 
give you an RSA 2048 cert.



There are two ways to do that. If you want all your certs to be RSA 
2048, you can add this to the /etc/letsencrypt/cli.ini file.


key-type = rsa
rsa-key-size = 2048


If you just want to do that for your keys you use in qmail, then you 
can put the above in the /etc/letsencrypt/renewal/domain.conf file. 
Where "domain" is the name of the cert you're renewing. Certbot 
creates the file so it should already be there.



Gary


On 4/14/2024 10:39 PM, Jeff Koch wrote:
I may have resolved this. I did the Rocy9 distro install of apache 
and copied the mod_http2.so file over to our install of apache. Seems 
to work (no errors) but I won't know for sure until we setup Lets 
Encrypt SSL certbot tomorrow


Jeff

On 4/14/2024 3:11 PM, Jeff Koch wrote:


Hi - we're setting up a new mailserver with Rocky 9 and the learning 
curve is slow as is usual with the first time with a new distro.


Anyway because our various scripts look for apache at 
/usr/local/apache/ we've decided to compile our own binary with the 
latest apache and have run into trouble / errors related to 'nghttp2'.


We did download, compile and install the latest nghttp2-1.61.0 from 
github. The configure and make went well and http1.1 works but 
apache generates the following error when we activate  mod_http2


 (Cannot load modules/mod_http2.so into server: 
/usr/local/apache2/modules/mod_http2.so: undefined symbol: 
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)


If anyone on the list has compiled their own httpd 2.4.59 with Rocky 
9 would you mind sharing the details ?


Thanks, Jeff Koch




- 
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Eric Broch]

Will fix on EL8, soon...removing this function:

SSL_set_tmp_rsa_callback(myssl, tmp_rsa_cb);

.

.

.

RSA *tmp_rsa_cb(SSL *ssl, int export, int keylen)
{
  RSA *rsa;

  if (!export) keylen = 2048;
  if (keylen == 2048) {
    FILE *in = fopen("control/rsa2048.pem", "r");
    if (in) {
  rsa = PEM_read_RSAPrivateKey(in, NULL, NULL, NULL);
  fclose(in);
  if (rsa) return rsa;
    }
  }

On 4/15/2024 8:47 AM, Eric Broch wrote:


My next iteration on EL9 will remove keysize it's deprecated, has been 
for a while. Should have the new code out within the week.


SSL_CTX_set_tmp_rsa_callback · openssl/openssl · Discussion #23769 
(github.com) 



On 4/15/2024 6:25 AM, Gary Bowling wrote:



Hey Jeff, glad you're making progress. Be aware that when you get a 
new cert from Letsencrypt that the default now retrieves an ECDSA 
cert. Which is fine for apache, but doesn't work on qmail, or at 
least it didn't for me. To fix that you'll need to configure 
letsencrypt to give you an RSA 2048 cert.



There are two ways to do that. If you want all your certs to be RSA 
2048, you can add this to the /etc/letsencrypt/cli.ini file.


key-type = rsa
rsa-key-size = 2048


If you just want to do that for your keys you use in qmail, then you 
can put the above in the /etc/letsencrypt/renewal/domain.conf file. 
Where "domain" is the name of the cert you're renewing. Certbot 
creates the file so it should already be there.



Gary


On 4/14/2024 10:39 PM, Jeff Koch wrote:
I may have resolved this. I did the Rocy9 distro install of apache 
and copied the mod_http2.so file over to our install of apache. 
Seems to work (no errors) but I won't know for sure until we setup 
Lets Encrypt SSL certbot tomorrow


Jeff

On 4/14/2024 3:11 PM, Jeff Koch wrote:


Hi - we're setting up a new mailserver with Rocky 9 and the 
learning curve is slow as is usual with the first time with a new 
distro.


Anyway because our various scripts look for apache at 
/usr/local/apache/ we've decided to compile our own binary with the 
latest apache and have run into trouble / errors related to 'nghttp2'.


We did download, compile and install the latest nghttp2-1.61.0 from 
github. The configure and make went well and http1.1 works but 
apache generates the following error when we activate  mod_http2


 (Cannot load modules/mod_http2.so into server: 
/usr/local/apache2/modules/mod_http2.so: undefined symbol: 
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)


If anyone on the list has compiled their own httpd 2.4.59 with 
Rocky 9 would you mind sharing the details ?


Thanks, Jeff Koch




- 
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com For additional 
commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Jeff Koch]

Gary - thanks for this info - I'll add it to our setup notes.

Jeff

On 4/15/2024 8:25 AM, Gary Bowling wrote:



Hey Jeff, glad you're making progress. Be aware that when you get a 
new cert from Letsencrypt that the default now retrieves an ECDSA 
cert. Which is fine for apache, but doesn't work on qmail, or at least 
it didn't for me. To fix that you'll need to configure letsencrypt to 
give you an RSA 2048 cert.



There are two ways to do that. If you want all your certs to be RSA 
2048, you can add this to the /etc/letsencrypt/cli.ini file.


key-type = rsa
rsa-key-size = 2048


If you just want to do that for your keys you use in qmail, then you 
can put the above in the /etc/letsencrypt/renewal/domain.conf file. 
Where "domain" is the name of the cert you're renewing. Certbot 
creates the file so it should already be there.



Gary


On 4/14/2024 10:39 PM, Jeff Koch wrote:
I may have resolved this. I did the Rocy9 distro install of apache 
and copied the mod_http2.so file over to our install of apache. Seems 
to work (no errors) but I won't know for sure until we setup Lets 
Encrypt SSL certbot tomorrow


Jeff

On 4/14/2024 3:11 PM, Jeff Koch wrote:


Hi - we're setting up a new mailserver with Rocky 9 and the learning 
curve is slow as is usual with the first time with a new distro.


Anyway because our various scripts look for apache at 
/usr/local/apache/ we've decided to compile our own binary with the 
latest apache and have run into trouble / errors related to 'nghttp2'.


We did download, compile and install the latest nghttp2-1.61.0 from 
github. The configure and make went well and http1.1 works but 
apache generates the following error when we activate  mod_http2


 (Cannot load modules/mod_http2.so into server: 
/usr/local/apache2/modules/mod_http2.so: undefined symbol: 
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)


If anyone on the list has compiled their own httpd 2.4.59 with Rocky 
9 would you mind sharing the details ?


Thanks, Jeff Koch




- 
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Gary Bowling]

  
  


Hey Jeff, glad you're making progress. Be aware that when you get
  a new cert from Letsencrypt that the default now retrieves an
  ECDSA cert. Which is fine for apache, but doesn't work on qmail,
  or at least it didn't for me. To fix that you'll need to configure
  letsencrypt to give you an RSA 2048 cert. 



There are two ways to do that. If you want all your certs to be
  RSA 2048, you can add this to the /etc/letsencrypt/cli.ini file.
key-type = rsa
  rsa-key-size = 2048


If you just want to do that for your keys you use in qmail, then
  you can put the above in the /etc/letsencrypt/renewal/domain.conf
  file. Where "domain" is the name of the cert you're renewing.
  Certbot creates the file so it should already be there.


Gary



On 4/14/2024 10:39 PM, Jeff Koch wrote:


  
  I may have resolved this. I did the Rocy9
distro install of apache and copied the mod_http2.so file over
to our install of apache. Seems to work (no errors) but I won't
know for sure until we setup Lets Encrypt SSL certbot tomorrow

Jeff
  
  On 4/14/2024 3:11 PM, Jeff Koch
wrote:
  
   
Hi - we're setting up a new mailserver with Rocky 9 and the
learning curve is slow as is usual with the first time with a
new distro. 

Anyway because our various scripts look for apache at
/usr/local/apache/ we've decided to compile our own binary with
the latest apache and have run into trouble / errors related to
'nghttp2'. 

We did download, compile and install the latest nghttp2-1.61.0
from github. The configure and make went well and http1.1 works
but apache generates the following error when we activate 
mod_http2 

 (Cannot load modules/mod_http2.so into server:
/usr/local/apache2/modules/mod_http2.so: undefined symbol:
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)


If anyone on the list has compiled their own httpd 2.4.59 with
Rocky 9 would you mind sharing the details ? 

Thanks, Jeff Koch 


  
  

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Remo Mattei]

For the longest time I used sources but was always too painful when there are 
dependencies and when bugs are discovered not enough time to babysit it. 

My 2 cents on that. 
Inviato da iPhone

> Il giorno 14 apr 2024, alle ore 20:41, Jeff Koch  
> ha scritto:
> 
>  I may have resolved this. I did the Rocy9 distro install of apache and 
> copied the mod_http2.so file over to our install of apache. Seems to work (no 
> errors) but I won't know for sure until we setup Lets Encrypt SSL certbot 
> tomorrow
> 
> Jeff
> 
>> On 4/14/2024 3:11 PM, Jeff Koch wrote:
>> 
>> Hi - we're setting up a new mailserver with Rocky 9 and the learning curve 
>> is slow as is usual with the first time with a new distro.
>> 
>> Anyway because our various scripts look for apache at /usr/local/apache/ 
>> we've decided to compile our own binary with the latest apache and have run 
>> into trouble / errors related to 'nghttp2'.
>> 
>> We did download, compile and install the latest nghttp2-1.61.0 from github. 
>> The configure and make went well and http1.1 works but apache generates the 
>> following error when we activate  mod_http2
>> 
>>  (Cannot load modules/mod_http2.so into server: 
>> /usr/local/apache2/modules/mod_http2.so: undefined symbol: 
>> nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)
>> 
>> If anyone on the list has compiled their own httpd 2.4.59 with Rocky 9 would 
>> you mind sharing the details ?
>> 
>> Thanks, Jeff Koch
>> 
>> 
> 

[qmailtoaster] Re: Rocky9 - new mailserver setup - off topic

[Jeff Koch]

I may have resolved this. I did the Rocy9 distro install of apache and 
copied the mod_http2.so file over to our install of apache. Seems to 
work (no errors) but I won't know for sure until we setup Lets Encrypt 
SSL certbot tomorrow


Jeff

On 4/14/2024 3:11 PM, Jeff Koch wrote:


Hi - we're setting up a new mailserver with Rocky 9 and the learning 
curve is slow as is usual with the first time with a new distro.


Anyway because our various scripts look for apache at 
/usr/local/apache/ we've decided to compile our own binary with the 
latest apache and have run into trouble / errors related to 'nghttp2'.


We did download, compile and install the latest nghttp2-1.61.0 from 
github. The configure and make went well and http1.1 works but apache 
generates the following error when we activate mod_http2


 (Cannot load modules/mod_http2.so into server: 
/usr/local/apache2/modules/mod_http2.so: undefined symbol: 
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation)


If anyone on the list has compiled their own httpd 2.4.59 with Rocky 9 
would you mind sharing the details ?


Thanks, Jeff Koch

Re: [qmailtoaster] Re: I messed up DKIM setup

[Qmail]

Hi

Wonder where Qmail would be without people like Eric ?

Excellent support - respect

/Finn


Den 08-04-2024 kl. 06:21 skrev Eric Broch:

Good
On Apr 7, 2024, at 10:19 PM, Biju Jose <mailto:bijuko...@outlook.com>> wrote:


renamed assign.rpmsave to assign
renamed cdb.rpmsave to cdb

Now it seems working shall revert soon after checking

Thank you Eric for the support

Best regards
Biju Jose.




*From:* Eric Broch 
*Sent:* 08 April 2024 09:44
*To:* qmailtoaster-list@qmailtoaster.com

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
Here are what entries in the assign file look like, below. You'll
need to check the domains in /home/vpopmail/domains and add them in
the assign file then run qmailctl cdb. Then you'll need to add
domains to the rcpthosts file.


+ qmailtoaster.org
<http://qmailtoaster.org>-:qmailtoaster.org:89:89:/home/vpopmail/domains/ 
qmailtoaster.org <http://qmailtoaster.org>:-::
.


On Apr 7, 2024, at 9:57 PM, Eric Broch < ebr...@whitehorsetc.com
<mailto:ebr...@whitehorsetc.com>> wrote:

# cat /var/qmail/users/assign

If there is nothing in it it's going to have to be rebuilt.

On Apr 7, 2024, at 9:48 PM, Biju Jose < bijuko...@outlook.com
<mailto:bijuko...@outlook.com>> wrote:

doveadm auth test postmas...@xx.in '*7YOBpkeE3ybN'
passdb: postmaster@ xx .in auth succeeded
extra fields:
   user=postmaster@ xx .in

# conntest
Enter a valid remote email account to which QMT will send
mail via Submission & SMTPS: bijuko...@outlook.com

Error. Domain domain1.co.in was not found in the assign file
Error. Domain domain2.co.in was not found in the assign file

IMAPS: postmas...@domain1.co.in [failed]
Submission: postmas...@domain1.co.in -->
bijuko...@outlook.com [failed]
SMTPS: postmas...@domain1.co.in --> bijuko...@outlook.com
[failed]




*From:* Eric Broch 
*Sent:* 08 April 2024 07:57
*To:* qmailtoaster-list@qmailtoaster.com

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Biju,


The first thing to do is to check dovecot.


doveadm auth test usern...@somedomain.com
<mailto:usern...@somedomain.com> 'password'


To check


Submission & SMTPS


download conntest





# wget -P /usr/local/bin

https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest 
<https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest> # conntest Enter a valid remote 
email account to which QMT will send mail: 'your outlook account' IMAPS: postmas...@domain.tld 
<mailto:postmas...@domain.tld> --> success Submission: postmas...@domain.tld 
<mailto:postmas...@domain.tld> --> success SMTPS: postmas...@domain.tld 
<mailto:postmas...@domain.tld> --> success

If Dovecot does not work, check the log file
/var/log/dovecot.log. You may need to put advanced logging
in the config file. Does that log file presently give you
any errors?


Eric



On 4/7/2024 8:12 PM, Eric Broch wrote:

The *ONLY* thing that should have changed for a DKIM
upgrade is qmail-remote. This has absolutely *NOTHING*
to do with logging in.


What else changed on your system besides qmail-remote?
The *ONLY* thing needed to restore the system (outgoing
mail) was to cp qmail-remote.orig back to qmail-remote.


Again, what else changed!




On 4/7/2024 7:55 PM, Biju Jose wrote:

No, I can login to newly created domain, but not to
the existing domains.
How can I fix  this?


*From:* Eric Broch 
<mailto:ebr...@whitehorsetc.com>
*Sent:* 08 April 2024 07:23
*To:* qmailtoaster-list@qmailtoaster.com
<mailto:qmailtoaster-list@qmailtoaster.com>

<mailto:qmailtoaster-list@qmailtoaster.com>
*Subject:* Re: [qmailtoaster] Re: I messed up DKIM
setup

Does it work 

Re: Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

Good

On Apr 7, 2024, 10:19 PM, at 10:19 PM, Biju Jose  wrote:
>renamed assign.rpmsave to assign
>renamed cdb.rpmsave to cdb
>
>Now it seems working shall revert soon after checking
>
>Thank you Eric for the support
>
>Best regards
>Biju Jose.
>
>
>
>
>From: Eric Broch 
>Sent: 08 April 2024 09:44
>To: qmailtoaster-list@qmailtoaster.com
>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>Here are what entries in the assign file look like, below. You'll need
>to check the domains in /home/vpopmail/domains and add them in the
>assign file then run qmailctl cdb. Then you'll need to add domains to
>the rcpthosts file.
>
>
>+qmailtoaster.org<http://qmailtoaster.org>-:qmailtoaster.org:89:89:/home/vpopmail/domains/qmailtoaster.org<http://qmailtoaster.org>:-::
>.
>
>
>On Apr 7, 2024, at 9:57 PM, Eric Broch
>mailto:ebr...@whitehorsetc.com>> wrote:
># cat /var/qmail/users/assign
>
>If there is nothing in it it's going to have to be rebuilt.
>
>On Apr 7, 2024, at 9:48 PM, Biju Jose <
>bijuko...@outlook.com<mailto:bijuko...@outlook.com>> wrote:
>doveadm auth test postmas...@xx.in '*7YOBpkeE3ybN'
>passdb: postmaster@ xx .in auth succeeded
>extra fields:
>  user=postmaster@ xx .in
>
># conntest
>Enter a valid remote email account to which QMT will send mail via
>Submission & SMTPS: bijuko...@outlook.com
>
>Error. Domain domain1.co.in was not found in the assign file
>Error. Domain domain2.co.in was not found in the assign file
>
>IMAPS: postmas...@domain1.co.in [failed]
>Submission: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
>SMTPS: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
>
>
>
>From: Eric Broch 
>Sent: 08 April 2024 07:57
>To: qmailtoaster-list@qmailtoaster.com
>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>
>Biju,
>
>
>The first thing to do is to check dovecot.
>
>
>doveadm auth test
>usern...@somedomain.com<mailto:usern...@somedomain.com> 'password'
>
>
>To check
>
>
>Submission & SMTPS
>
>
>download conntest
>
>
>
>
>
>
># wget -P /usr/local/bin
>https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest #
>conntest Enter a valid remote email account to which QMT will send
>mail: 'your outlook account' IMAPS:
>postmas...@domain.tld<mailto:postmas...@domain.tld> -->
>
>success
>
>Submission: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
>
>success
>
> SMTPS: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
>
>success
>
>
>
>
>
>If Dovecot does not work, check the log file /var/log/dovecot.log. You
>may need to put advanced logging in the config file. Does that log file
>presently give you any errors?
>
>
>Eric
>
>
>
>On 4/7/2024 8:12 PM, Eric Broch wrote:
>
>The *ONLY* thing that should have changed for a DKIM upgrade is
>qmail-remote. This has absolutely *NOTHING* to do with logging in.
>
>
>What else changed on your system besides qmail-remote? The *ONLY* thing
>needed to restore the system (outgoing mail) was to cp
>qmail-remote.orig back to qmail-remote.
>
>
>Again, what else changed!
>
>
>
>
>On 4/7/2024 7:55 PM, Biju Jose wrote:
>No, I can login to newly created domain, but not to the existing
>domains.
>How can I fix  this?
>
>From: Eric Broch
><mailto:ebr...@whitehorsetc.com>
>Sent: 08 April 2024 07:23
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>
>Does it work now?
>
>
>On 4/7/2024 6:57 PM, Biju Jose wrote:
># qmailctl stat
>send: up (pid 1761) 126 seconds
>smtp: up (pid 1760) 126 seconds
>submission: up (pid 1774) 126 seconds
>send/log: up (pid 1770) 126 seconds
>smtp/log: up (pid 1762) 126 seconds
>submission/log: up (pid 1759) 126 seconds
>
>From: Biju Jose <mailto:bijuko...@outlook.com>
>Sent: 08 April 2024 00:15
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
># qmailctl stat
>send: up (pid 44308) 13 seconds
>smtp: up (pid 44504) 0 seconds
>submission: up (pid 44505) 0 seconds
>send/log: up (pid 44309) 13 seconds
>smtp/lo

Re: Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

# cat /var/qmail/users/assign.rpmsave

Make sure it has what you want and copy and past contents to assign file above 
the ending period and run qmailctl cdb

On Apr 7, 2024, 10:10 PM, at 10:10 PM, Biju Jose  wrote:
> cat /var/qmail/users/assign
>+domain1.in-:domain1.in:89:89:/home/vpopmail/domains/domain1.in:-::
>+domain2.in-:domain2.in:89:89:/home/vpopmail/domains/domain2.in:-::
>
>I have /var/qmail/assign.rpmsave , how do I add the domains therin to
>assign  file and rebuild it?
>
>
>
>From: Eric Broch 
>Sent: 08 April 2024 09:27
>To: qmailtoaster-list@qmailtoaster.com
>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
># cat /var/qmail/users/assign
>
>If there is nothing in it it's going to have to be rebuilt.
>
>On Apr 7, 2024, at 9:48 PM, Biju Jose
>mailto:bijuko...@outlook.com>> wrote:
>doveadm auth test postmas...@xx.in '*7YOBpkeE3ybN'
>passdb: postmaster@ xx .in auth succeeded
>extra fields:
>  user=postmaster@ xx .in
>
># conntest
>Enter a valid remote email account to which QMT will send mail via
>Submission & SMTPS: bijuko...@outlook.com
>
>Error. Domain domain1.co.in was not found in the assign file
>Error. Domain domain2.co.in was not found in the assign file
>
>IMAPS: postmas...@domain1.co.in [failed]
>Submission: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
>SMTPS: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
>
>
>____
>From: Eric Broch 
>Sent: 08 April 2024 07:57
>To: qmailtoaster-list@qmailtoaster.com
>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>
>Biju,
>
>
>The first thing to do is to check dovecot.
>
>
>doveadm auth test
>usern...@somedomain.com<mailto:usern...@somedomain.com> 'password'
>
>
>To check
>
>
>Submission & SMTPS
>
>
>download conntest
>
>
>
>
># wget -P /usr/local/bin
>https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest #
>conntest Enter a valid remote email account to which QMT will send
>mail: 'your outlook account' IMAPS:
>postmas...@domain.tld<mailto:postmas...@domain.tld> -->
>  success
>   Submission: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
>  success
>   SMTPS: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
>  success
>
>
>
>If Dovecot does not work, check the log file /var/log/dovecot.log. You
>may need to put advanced logging in the config file. Does that log file
>presently give you any errors?
>
>
>Eric
>
>
>
>On 4/7/2024 8:12 PM, Eric Broch wrote:
>
>The *ONLY* thing that should have changed for a DKIM upgrade is
>qmail-remote. This has absolutely *NOTHING* to do with logging in.
>
>
>What else changed on your system besides qmail-remote? The *ONLY* thing
>needed to restore the system (outgoing mail) was to cp
>qmail-remote.orig back to qmail-remote.
>
>
>Again, what else changed!
>
>
>
>
>On 4/7/2024 7:55 PM, Biju Jose wrote:
>No, I can login to newly created domain, but not to the existing
>domains.
>How can I fix  this?
>
>From: Eric Broch
><mailto:ebr...@whitehorsetc.com>
>Sent: 08 April 2024 07:23
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>
>Does it work now?
>
>
>On 4/7/2024 6:57 PM, Biju Jose wrote:
># qmailctl stat
>send: up (pid 1761) 126 seconds
>smtp: up (pid 1760) 126 seconds
>submission: up (pid 1774) 126 seconds
>send/log: up (pid 1770) 126 seconds
>smtp/log: up (pid 1762) 126 seconds
>submission/log: up (pid 1759) 126 seconds
>
>From: Biju Jose <mailto:bijuko...@outlook.com>
>Sent: 08 April 2024 00:15
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
># qmailctl stat
>send: up (pid 44308) 13 seconds
>smtp: up (pid 44504) 0 seconds
>submission: up (pid 44505) 0 seconds
>send/log: up (pid 44309) 13 seconds
>smtp/log: up (pid 44310) 13 seconds
>submission/log: up (pid 44312) 13 seconds
>
>From: Biju Jose <mailto:bijuko...@outlook.com>
>Sent: 08 April 2024 00:01
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re:

Re: Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

renamed assign.rpmsave to assign
renamed cdb.rpmsave to cdb

Now it seems working shall revert soon after checking

Thank you Eric for the support

Best regards
Biju Jose.




From: Eric Broch 
Sent: 08 April 2024 09:44
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

Here are what entries in the assign file look like, below. You'll need to check 
the domains in /home/vpopmail/domains and add them in the assign file then run 
qmailctl cdb. Then you'll need to add domains to the rcpthosts file.


+qmailtoaster.org<http://qmailtoaster.org>-:qmailtoaster.org:89:89:/home/vpopmail/domains/qmailtoaster.org<http://qmailtoaster.org>:-::
.


On Apr 7, 2024, at 9:57 PM, Eric Broch 
mailto:ebr...@whitehorsetc.com>> wrote:
# cat /var/qmail/users/assign

If there is nothing in it it's going to have to be rebuilt.

On Apr 7, 2024, at 9:48 PM, Biju Jose < 
bijuko...@outlook.com<mailto:bijuko...@outlook.com>> wrote:
doveadm auth test postmas...@xx.in '*7YOBpkeE3ybN'
passdb: postmaster@ xx .in auth succeeded
extra fields:
  user=postmaster@ xx .in

# conntest
Enter a valid remote email account to which QMT will send mail via Submission & 
SMTPS: bijuko...@outlook.com

Error. Domain domain1.co.in was not found in the assign file
Error. Domain domain2.co.in was not found in the assign file

IMAPS: postmas...@domain1.co.in [failed]
Submission: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
SMTPS: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]



From: Eric Broch 
Sent: 08 April 2024 07:57
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Biju,


The first thing to do is to check dovecot.


doveadm auth test usern...@somedomain.com<mailto:usern...@somedomain.com> 
'password'


To check


Submission & SMTPS


download conntest






# wget -P /usr/local/bin 
https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest # conntest 
Enter a valid remote email account to which QMT will send mail: 'your outlook 
account' IMAPS: postmas...@domain.tld<mailto:postmas...@domain.tld> -->

success

 Submission: postmas...@domain.tld<mailto:postmas...@domain.tld> -->

success

 SMTPS: postmas...@domain.tld<mailto:postmas...@domain.tld> -->

success





If Dovecot does not work, check the log file /var/log/dovecot.log. You may need 
to put advanced logging in the config file. Does that log file presently give 
you any errors?


Eric



On 4/7/2024 8:12 PM, Eric Broch wrote:

The *ONLY* thing that should have changed for a DKIM upgrade is qmail-remote. 
This has absolutely *NOTHING* to do with logging in.


What else changed on your system besides qmail-remote? The *ONLY* thing needed 
to restore the system (outgoing mail) was to cp qmail-remote.orig back to 
qmail-remote.


Again, what else changed!




On 4/7/2024 7:55 PM, Biju Jose wrote:
No, I can login to newly created domain, but not to the existing domains.
How can I fix  this?

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 08 April 2024 07:23
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:
# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:15
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:01
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: 

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

Here are what entries in the assign file look like, below. You'll need to check 
the domains in /home/vpopmail/domains and add them in the assign file then run 
qmailctl cdb. Then you'll need to add domains to the rcpthosts file.


+qmailtoaster.org-:qmailtoaster.org:89:89:/home/vpopmail/domains/qmailtoaster.org:-::
.




On Apr 7, 2024, 9:57 PM, at 9:57 PM, Eric Broch  wrote:
># cat /var/qmail/users/assign
>
>If there is nothing in it it's going to have to be rebuilt.
>
>
>
>On Apr 7, 2024, 9:48 PM, at 9:48 PM, Biju Jose 
>wrote:
>>doveadm auth test postmas...@xx.in '*7YOBpkeE3ybN'
>>passdb: postmas...@xx.in auth succeeded
>>extra fields:
>>  user=postmas...@xx.in
>>
>># conntest
>>Enter a valid remote email account to which QMT will send mail via
>>Submission & SMTPS: bijuko...@outlook.com
>>
>>Error. Domain domain1.co.in was not found in the assign file
>>Error. Domain domain2.co.in was not found in the assign file
>>
>>IMAPS: postmas...@domain1.co.in [failed]
>>Submission: postmas...@domain1.co.in --> bijuko...@outlook.com
>[failed]
>>SMTPS: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
>>
>>
>>
>>From: Eric Broch 
>>Sent: 08 April 2024 07:57
>>To: qmailtoaster-list@qmailtoaster.com
>>
>>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>>
>>
>>Biju,
>>
>>
>>The first thing to do is to check dovecot.
>>
>>
>>doveadm auth test
>>usern...@somedomain.com<mailto:usern...@somedomain.com> 'password'
>>
>>
>>To check
>>
>>
>>Submission & SMTPS
>>
>>
>>download conntest
>>
>>
>># wget -P /usr/local/bin
>>https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest
>># conntest
>>Enter a valid remote email account to which QMT will send mail: 'your
>>outlook account'
>>IMAPS: postmas...@domain.tld<mailto:postmas...@domain.tld> --> success
>>Submission: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
>>success
>>SMTPS: postmas...@domain.tld<mailto:postmas...@domain.tld> --> success
>>
>>
>>
>>
>>If Dovecot does not work, check the log file /var/log/dovecot.log. You
>>may need to put advanced logging in the config file. Does that log
>file
>>presently give you any errors?
>>
>>
>>Eric
>>
>>
>>
>>On 4/7/2024 8:12 PM, Eric Broch wrote:
>>
>>The *ONLY* thing that should have changed for a DKIM upgrade is
>>qmail-remote. This has absolutely *NOTHING* to do with logging in.
>>
>>
>>What else changed on your system besides qmail-remote? The *ONLY*
>thing
>>needed to restore the system (outgoing mail) was to cp
>>qmail-remote.orig back to qmail-remote.
>>
>>
>>Again, what else changed!
>>
>>
>>
>>
>>On 4/7/2024 7:55 PM, Biju Jose wrote:
>>No, I can login to newly created domain, but not to the existing
>>domains.
>>How can I fix  this?
>>
>>From: Eric Broch
>><mailto:ebr...@whitehorsetc.com>
>>Sent: 08 April 2024 07:23
>>To:
>>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
>><mailto:qmailtoaster-list@qmailtoaster.com>
>>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>>
>>
>>Does it work now?
>>
>>
>>On 4/7/2024 6:57 PM, Biju Jose wrote:
>># qmailctl stat
>>send: up (pid 1761) 126 seconds
>>smtp: up (pid 1760) 126 seconds
>>submission: up (pid 1774) 126 seconds
>>send/log: up (pid 1770) 126 seconds
>>smtp/log: up (pid 1762) 126 seconds
>>submission/log: up (pid 1759) 126 seconds
>>________
>>From: Biju Jose <mailto:bijuko...@outlook.com>
>>Sent: 08 April 2024 00:15
>>To:
>>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
>><mailto:qmailtoaster-list@qmailtoaster.com>
>>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>>
>># qmailctl stat
>>send: up (pid 44308) 13 seconds
>>smtp: up (pid 44504) 0 seconds
>>submission: up (pid 44505) 0 seconds
>>send/log: up (pid 44309) 13 seconds
>>smtp/log: up (pid 44310) 13 seconds
>>submission/log: up (pid 44312) 13 seconds
>>
>>From: Biju Jose <mailto:bijuko...@outlook.com>
>>Sent: 08 April 2024 00:01
>>To:
>>qmailtoaster-lis

Re: Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

 cat /var/qmail/users/assign
+domain1.in-:domain1.in:89:89:/home/vpopmail/domains/domain1.in:-::
+domain2.in-:domain2.in:89:89:/home/vpopmail/domains/domain2.in:-::

I have /var/qmail/assign.rpmsave , how do I add the domains therin to assign  
file and rebuild it?



From: Eric Broch 
Sent: 08 April 2024 09:27
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

# cat /var/qmail/users/assign

If there is nothing in it it's going to have to be rebuilt.

On Apr 7, 2024, at 9:48 PM, Biju Jose 
mailto:bijuko...@outlook.com>> wrote:
doveadm auth test postmas...@xx.in '*7YOBpkeE3ybN'
passdb: postmaster@ xx .in auth succeeded
extra fields:
  user=postmaster@ xx .in

# conntest
Enter a valid remote email account to which QMT will send mail via Submission & 
SMTPS: bijuko...@outlook.com

Error. Domain domain1.co.in was not found in the assign file
Error. Domain domain2.co.in was not found in the assign file

IMAPS: postmas...@domain1.co.in [failed]
Submission: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
SMTPS: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]



From: Eric Broch 
Sent: 08 April 2024 07:57
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Biju,


The first thing to do is to check dovecot.


doveadm auth test usern...@somedomain.com<mailto:usern...@somedomain.com> 
'password'


To check


Submission & SMTPS


download conntest




  # wget -P /usr/local/bin 
https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest # conntest 
Enter a valid remote email account to which QMT will send mail: 'your outlook 
account' IMAPS: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
  success
   Submission: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
  success
   SMTPS: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
  success



If Dovecot does not work, check the log file /var/log/dovecot.log. You may need 
to put advanced logging in the config file. Does that log file presently give 
you any errors?


Eric



On 4/7/2024 8:12 PM, Eric Broch wrote:

The *ONLY* thing that should have changed for a DKIM upgrade is qmail-remote. 
This has absolutely *NOTHING* to do with logging in.


What else changed on your system besides qmail-remote? The *ONLY* thing needed 
to restore the system (outgoing mail) was to cp qmail-remote.orig back to 
qmail-remote.


Again, what else changed!




On 4/7/2024 7:55 PM, Biju Jose wrote:
No, I can login to newly created domain, but not to the existing domains.
How can I fix  this?

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 08 April 2024 07:23
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:
# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:15
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:01
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 21:44
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmai

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

# cat /var/qmail/users/assign

If there is nothing in it it's going to have to be rebuilt.



On Apr 7, 2024, 9:48 PM, at 9:48 PM, Biju Jose  wrote:
>doveadm auth test postmas...@xx.in '*7YOBpkeE3ybN'
>passdb: postmas...@xx.in auth succeeded
>extra fields:
>  user=postmas...@xx.in
>
># conntest
>Enter a valid remote email account to which QMT will send mail via
>Submission & SMTPS: bijuko...@outlook.com
>
>Error. Domain domain1.co.in was not found in the assign file
>Error. Domain domain2.co.in was not found in the assign file
>
>IMAPS: postmas...@domain1.co.in [failed]
>Submission: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
>SMTPS: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
>
>
>
>From: Eric Broch 
>Sent: 08 April 2024 07:57
>To: qmailtoaster-list@qmailtoaster.com
>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>
>Biju,
>
>
>The first thing to do is to check dovecot.
>
>
>doveadm auth test
>usern...@somedomain.com<mailto:usern...@somedomain.com> 'password'
>
>
>To check
>
>
>Submission & SMTPS
>
>
>download conntest
>
>
># wget -P /usr/local/bin
>https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest
># conntest
>Enter a valid remote email account to which QMT will send mail: 'your
>outlook account'
>IMAPS: postmas...@domain.tld<mailto:postmas...@domain.tld> --> success
>Submission: postmas...@domain.tld<mailto:postmas...@domain.tld> -->
>success
>SMTPS: postmas...@domain.tld<mailto:postmas...@domain.tld> --> success
>
>
>
>
>If Dovecot does not work, check the log file /var/log/dovecot.log. You
>may need to put advanced logging in the config file. Does that log file
>presently give you any errors?
>
>
>Eric
>
>
>
>On 4/7/2024 8:12 PM, Eric Broch wrote:
>
>The *ONLY* thing that should have changed for a DKIM upgrade is
>qmail-remote. This has absolutely *NOTHING* to do with logging in.
>
>
>What else changed on your system besides qmail-remote? The *ONLY* thing
>needed to restore the system (outgoing mail) was to cp
>qmail-remote.orig back to qmail-remote.
>
>
>Again, what else changed!
>
>
>
>
>On 4/7/2024 7:55 PM, Biju Jose wrote:
>No, I can login to newly created domain, but not to the existing
>domains.
>How can I fix  this?
>
>From: Eric Broch
><mailto:ebr...@whitehorsetc.com>
>Sent: 08 April 2024 07:23
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>
>Does it work now?
>
>
>On 4/7/2024 6:57 PM, Biju Jose wrote:
># qmailctl stat
>send: up (pid 1761) 126 seconds
>smtp: up (pid 1760) 126 seconds
>submission: up (pid 1774) 126 seconds
>send/log: up (pid 1770) 126 seconds
>smtp/log: up (pid 1762) 126 seconds
>submission/log: up (pid 1759) 126 seconds
>
>From: Biju Jose <mailto:bijuko...@outlook.com>
>Sent: 08 April 2024 00:15
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
># qmailctl stat
>send: up (pid 44308) 13 seconds
>smtp: up (pid 44504) 0 seconds
>submission: up (pid 44505) 0 seconds
>send/log: up (pid 44309) 13 seconds
>smtp/log: up (pid 44310) 13 seconds
>submission/log: up (pid 44312) 13 seconds
>
>From: Biju Jose <mailto:bijuko...@outlook.com>
>Sent: 08 April 2024 00:01
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>I have done
>
>  1.
>rpm -e --nodeps qmail
>  2.
>yum install qmail
>  3.
> restored .rpmsave files in /var/qmail/control
>
>Now I am unable to login to existing domains . But I can create and
>login to a test domain. How do I connect to existing domains?
>
>Need some urgent help please.
>
>Biju Jose
>
>From: Biju Jose <mailto:bijuko...@outlook.com>
>Sent: 07 April 2024 21:44
>To:
>qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com>
><mailto:qmailtoaster-list@qmailtoaster.com>
>Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
>
>#ls -l /var/qmail/bin
>total 1512
>-rwxr-xr-x 1 root   qmail

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

doveadm auth test postmas...@xx.in '*7YOBpkeE3ybN'
passdb: postmas...@xx.in auth succeeded
extra fields:
  user=postmas...@xx.in

# conntest
Enter a valid remote email account to which QMT will send mail via Submission & 
SMTPS: bijuko...@outlook.com

Error. Domain domain1.co.in was not found in the assign file
Error. Domain domain2.co.in was not found in the assign file

IMAPS: postmas...@domain1.co.in [failed]
Submission: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]
SMTPS: postmas...@domain1.co.in --> bijuko...@outlook.com [failed]



From: Eric Broch 
Sent: 08 April 2024 07:57
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Biju,


The first thing to do is to check dovecot.


doveadm auth test usern...@somedomain.com<mailto:usern...@somedomain.com> 
'password'


To check


Submission & SMTPS


download conntest


# wget -P /usr/local/bin 
https://raw.githubusercontent.com/qmtoaster/scripts/master/conntest
# conntest
Enter a valid remote email account to which QMT will send mail: 'your outlook 
account'
IMAPS: postmas...@domain.tld<mailto:postmas...@domain.tld> --> success
Submission: postmas...@domain.tld<mailto:postmas...@domain.tld> --> success
SMTPS: postmas...@domain.tld<mailto:postmas...@domain.tld> --> success




If Dovecot does not work, check the log file /var/log/dovecot.log. You may need 
to put advanced logging in the config file. Does that log file presently give 
you any errors?


Eric



On 4/7/2024 8:12 PM, Eric Broch wrote:

The *ONLY* thing that should have changed for a DKIM upgrade is qmail-remote. 
This has absolutely *NOTHING* to do with logging in.


What else changed on your system besides qmail-remote? The *ONLY* thing needed 
to restore the system (outgoing mail) was to cp qmail-remote.orig back to 
qmail-remote.


Again, what else changed!




On 4/7/2024 7:55 PM, Biju Jose wrote:
No, I can login to newly created domain, but not to the existing domains.
How can I fix  this?

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 08 April 2024 07:23
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:
# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:15
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:01
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 21:44
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rw

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

Update:

created a new domain. I am able to send and receive using email ids from this 
domain.

Now, how do I restore the other domains already existed on the server?  Please 
help.

Biju

From: Biju Jose 
Sent: 08 April 2024 08:22
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

DKIM install messed up
qmail-remote.orig lost in the mess

rpm -e --nodeps qmail
yum install qmail
copied the contents from .rpmsave in /var/qmail/control to the respective files 
including virtualdomains

restarted the machine

toaststat and qmailctl stat shows everything up.

virtual domain tables are in the database
/home/vpopmail/domains directory is intact

unable to login to existing domains.




From: Eric Broch 
Sent: 08 April 2024 07:42
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


The *ONLY* thing that should have changed for a DKIM upgrade is qmail-remote. 
This has absolutely *NOTHING* to do with logging in.


What else changed on your system besides qmail-remote? The *ONLY* thing needed 
to restore the system (outgoing mail) was to cp qmail-remote.orig back to 
qmail-remote.


Again, what else changed!




On 4/7/2024 7:55 PM, Biju Jose wrote:
No, I can login to newly created domain, but not to the existing domains.
How can I fix  this?

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 08 April 2024 07:23
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:
# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:15
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:01
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 21:44
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 1

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

DKIM install messed up
qmail-remote.orig lost in the mess

rpm -e --nodeps qmail
yum install qmail
copied the contents from .rpmsave in /var/qmail/control to the respective files 
including virtualdomains

restarted the machine

toaststat and qmailctl stat shows everything up.

virtual domain tables are in the database
/home/vpopmail/domains directory is intact

unable to login to existing domains.




From: Eric Broch 
Sent: 08 April 2024 07:42
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


The *ONLY* thing that should have changed for a DKIM upgrade is qmail-remote. 
This has absolutely *NOTHING* to do with logging in.


What else changed on your system besides qmail-remote? The *ONLY* thing needed 
to restore the system (outgoing mail) was to cp qmail-remote.orig back to 
qmail-remote.


Again, what else changed!




On 4/7/2024 7:55 PM, Biju Jose wrote:
No, I can login to newly created domain, but not to the existing domains.
How can I fix  this?

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 08 April 2024 07:23
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:
# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:15
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:01
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 21:44
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qma

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

Biju,


The first thing to do is to check dovecot.


doveadm auth test usern...@somedomain.com 'password'


To check


Submission & SMTPS


download conntest


# wget -P 
/usr/local/binhttps://raw.githubusercontent.com/qmtoaster/scripts/master/conntest
# conntest
Enter a valid remote email account to which QMT will send mail: 'your outlook 
account'
IMAPS:postmas...@domain.tld  -->success
Submission:postmas...@domain.tld  -->success
SMTPS:postmas...@domain.tld  -->success

If Dovecot does not work, check the log file /var/log/dovecot.log. You 
may need to put advanced logging in the config file. Does that log file 
presently give you any errors?



Eric



On 4/7/2024 8:12 PM, Eric Broch wrote:


The *ONLY* thing that should have changed for a DKIM upgrade is 
qmail-remote. This has absolutely *NOTHING* to do with logging in.



What else changed on your system besides qmail-remote? The *ONLY* 
thing needed to restore the system (outgoing mail) was to cp 
qmail-remote.orig back to qmail-remote.



Again, what else changed!




On 4/7/2024 7:55 PM, Biju Jose wrote:
No, I can login to newly created domain, but not to the existing 
domains.

How can I fix  this?

*From:* Eric Broch 
*Sent:* 08 April 2024 07:23
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:

# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 08 April 2024 00:15
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 08 April 2024 00:01
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
I have done

1.
rpm -e --nodeps qmail
2.
yum install qmail
3.
 restored .rpmsave files in /var/qmail/control


Now I am unable to login to existing domains . But I can create and 
login to a test domain. How do I connect to existing domains?


Need some urgent help please.

Biju Jose

*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 07 April 2024 21:44
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail    126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail    928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root    2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail    114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail    179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Se

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

The *ONLY* thing that should have changed for a DKIM upgrade is 
qmail-remote. This has absolutely *NOTHING* to do with logging in.



What else changed on your system besides qmail-remote? The *ONLY* thing 
needed to restore the system (outgoing mail) was to cp qmail-remote.orig 
back to qmail-remote.



Again, what else changed!




On 4/7/2024 7:55 PM, Biju Jose wrote:

No, I can login to newly created domain, but not to the existing domains.
How can I fix  this?

*From:* Eric Broch 
*Sent:* 08 April 2024 07:23
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:

# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 08 April 2024 00:15
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 08 April 2024 00:01
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
I have done

1.
rpm -e --nodeps qmail
2.
yum install qmail
3.
 restored .rpmsave files in /var/qmail/control


Now I am unable to login to existing domains . But I can create and 
login to a test domain. How do I connect to existing domains?


Need some urgent help please.

Biju Jose

*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 07 April 2024 21:44
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail    126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail    928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root    2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail    114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail    179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail    371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root      26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qm                ail-queue

-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmai

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

No, I can login to newly created domain, but not to the existing domains.
How can I fix  this?

From: Eric Broch 
Sent: 08 April 2024 07:23
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:
# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:15
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:01
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 21:44
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root  26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qmail-queue
-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmail488 Jul 18  2018 qmail-queue.pl.sh
-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote
-rw-r--r-- 1 root   root7545 Apr  7 20:59 qmail-remote~
-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0
-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org
-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric
-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn
-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send
-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl
-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd
-rwx--

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

Does it work now?


On 4/7/2024 6:57 PM, Biju Jose wrote:

# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

*From:* Biju Jose 
*Sent:* 08 April 2024 00:15
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

*From:* Biju Jose 
*Sent:* 08 April 2024 00:01
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
I have done

1.
rpm -e --nodeps qmail
2.
yum install qmail
3.
 restored .rpmsave files in /var/qmail/control


Now I am unable to login to existing domains . But I can create and 
login to a test domain. How do I connect to existing domains?


Need some urgent help please.

Biju Jose

*From:* Biju Jose 
*Sent:* 07 April 2024 21:44
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail    126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail    928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root    2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail    114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail    179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail    371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root      26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qm            ail-queue

-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmail    488 Jul 18  2018 qmail-queue.pl.sh
-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote
-rw-r--r-- 1 root   root    7545 Apr  7 20:59 qmail-remote~
-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0
-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org
-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric
-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn
-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send
-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl
-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd
-rwx-- 1 root   qmail  10488 Sep 10  2019 qmail-start
-rwxr-xr-x 1 root   qmail  14584 Sep 10  2019 qmail-tcpok
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 qmail-tcpto
-rwxr-xr-x 1 root   qmail  31192 Sep 10  2019 qreceipt
-rwxr-xr-x 1 root   qmail  14632 Sep 10  2019 qsmhook
-rwxr-xr-x 1 root   root    3820 May  6  2019 rcptcheck-overlimit.sh
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 sendmail
-rws--x--x 1 clamav root   34774 Apr  7  2016 simscan
-rwsr-xr-x 1 root   root   24461 Apr  7  2016 simscanmk
-rwxr-xr-x 1 root   qmail  35

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

# qmailctl stat
send: up (pid 1761) 126 seconds
smtp: up (pid 1760) 126 seconds
submission: up (pid 1774) 126 seconds
send/log: up (pid 1770) 126 seconds
smtp/log: up (pid 1762) 126 seconds
submission/log: up (pid 1759) 126 seconds

From: Biju Jose 
Sent: 08 April 2024 00:15
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose 
Sent: 08 April 2024 00:01
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose 
Sent: 07 April 2024 21:44
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root  26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qmail-queue
-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmail488 Jul 18  2018 qmail-queue.pl.sh
-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote
-rw-r--r-- 1 root   root7545 Apr  7 20:59 qmail-remote~
-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0
-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org
-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric
-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn
-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send
-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl
-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd
-rwx-- 1 root   qmail  10488 Sep 10  2019 qmail-start
-rwxr-xr-x 1 root   qmail  14584 Sep 10  2019 qmail-tcpok
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 qmail-tcpto
-rwxr-xr-x 1 root   qmail  31192 Sep 10  2019 qreceipt
-rwxr-xr-x 1 root   qmail  14632 Sep 10  2019 qsmhook
-rwxr-xr-x 1 root   root3820 May  6  2019 rcptcheck-overlimit.sh
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 sendmail
-rws--x--x 1 clamav root   34774 Apr  7  2016 simscan
-rwsr-xr-x 1 root   root   24461 Apr  7  2016 simscanmk
-rwxr-xr-x 1 root   qmail  35560 Sep 10  2019 spfquery
-rwx--x--x 1 root   qmail  10536 Sep 10  2019 splogger
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 srsfilter
-rwxr-xr-x 1 root   qmail  26920 Sep 10  2019 tcp-env
-rwxr

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

send and submission is not running, unable to login to existing domains.

From: Eric Broch 
Sent: 08 April 2024 04:07
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


All you had to do was...


yum -y reinstall qmail


What is the status now?



On 4/7/2024 12:45 PM, Biju Jose wrote:
# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 08 April 2024 00:01
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 21:44
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root  26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qmail-queue
-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmail488 Jul 18  2018 qmail-queue.pl.sh
-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote
-rw-r--r-- 1 root   root7545 Apr  7 20:59 qmail-remote~
-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0
-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org
-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric
-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn
-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send
-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl
-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd
-rwx-- 1 root   qmail  10488 Sep 10  2019 qmail-start
-rwxr-xr-x 1 root   qmail  14584 Sep 10  2019 qmail-tcpok
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 qmail-tcpto
-rwxr-xr-x 1 root   qmail  31192 Sep 10  2019 qreceipt
-rwxr-xr-x 1 root   qmail  14632 Sep 10  2019 qsmhook
-rwxr-xr-x 1 root   root3820 May  6  2019 rcptcheck-overlimit.sh
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 sendmail
-rws--x--x 1 clamav root   34774 Apr  7  2016 simscan
-rwsr-xr-x 1 root   root   24461 Apr  7  2

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

All you had to do was...


yum -y reinstall qmail


What is the status now?



On 4/7/2024 12:45 PM, Biju Jose wrote:

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

*From:* Biju Jose 
*Sent:* 08 April 2024 00:01
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
I have done

1.
rpm -e --nodeps qmail
2.
yum install qmail
3.
 restored .rpmsave files in /var/qmail/control


Now I am unable to login to existing domains . But I can create and 
login to a test domain. How do I connect to existing domains?


Need some urgent help please.

Biju Jose

*From:* Biju Jose 
*Sent:* 07 April 2024 21:44
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail    126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail    928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root    2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail    114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail    179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail    371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root      26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qm  ail-queue

-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmail    488 Jul 18  2018 qmail-queue.pl.sh
-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote
-rw-r--r-- 1 root   root    7545 Apr  7 20:59 qmail-remote~
-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0
-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org
-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric
-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn
-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send
-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl
-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd
-rwx-- 1 root   qmail  10488 Sep 10  2019 qmail-start
-rwxr-xr-x 1 root   qmail  14584 Sep 10  2019 qmail-tcpok
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 qmail-tcpto
-rwxr-xr-x 1 root   qmail  31192 Sep 10  2019 qreceipt
-rwxr-xr-x 1 root   qmail  14632 Sep 10  2019 qsmhook
-rwxr-xr-x 1 root   root    3820 May  6  2019 rcptcheck-overlimit.sh
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 sendmail
-rws--x--x 1 clamav root   34774 Apr  7  2016 simscan
-rwsr-xr-x 1 root   root   24461 Apr  7  2016 simscanmk
-rwxr-xr-x 1 root   qmail  35560 Sep 10  2019 spfquery
-rwx--x--x 1 root   qmail  10536 Sep 10  2019 splogger
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 srsfilter
-rwxr-xr-x 1 root   qmail  26920 Sep 10  2019 tcp-env
-rwxr-xr-x 1 root   root     618 Dec 24  2013 update-simscan

*From:* Eric Broch 
*Sent:* 07 April 2024 21:40
*To:* qmailtoaster-l

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

# qmailctl stat
send: up (pid 44308) 13 seconds
smtp: up (pid 44504) 0 seconds
submission: up (pid 44505) 0 seconds
send/log: up (pid 44309) 13 seconds
smtp/log: up (pid 44310) 13 seconds
submission/log: up (pid 44312) 13 seconds

From: Biju Jose 
Sent: 08 April 2024 00:01
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose 
Sent: 07 April 2024 21:44
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root  26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qmail-queue
-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmail488 Jul 18  2018 qmail-queue.pl.sh
-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote
-rw-r--r-- 1 root   root7545 Apr  7 20:59 qmail-remote~
-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0
-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org
-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric
-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn
-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send
-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl
-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd
-rwx-- 1 root   qmail  10488 Sep 10  2019 qmail-start
-rwxr-xr-x 1 root   qmail  14584 Sep 10  2019 qmail-tcpok
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 qmail-tcpto
-rwxr-xr-x 1 root   qmail  31192 Sep 10  2019 qreceipt
-rwxr-xr-x 1 root   qmail  14632 Sep 10  2019 qsmhook
-rwxr-xr-x 1 root   root3820 May  6  2019 rcptcheck-overlimit.sh
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 sendmail
-rws--x--x 1 clamav root   34774 Apr  7  2016 simscan
-rwsr-xr-x 1 root   root   24461 Apr  7  2016 simscanmk
-rwxr-xr-x 1 root   qmail  35560 Sep 10  2019 spfquery
-rwx--x--x 1 root   qmail  10536 Sep 10  2019 splogger
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 srsfilter
-rwxr-xr-x 1 root   qmail  26920 Sep 10  2019 tcp-env
-rwxr-xr-x 1 root   root 618 Dec 24  2013 update-simscan

From: Eric Broch 
Sent: 07 April 2024 21:40
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


All you should have to do is move qmail-remote (original) back to qmail-remote


What's in /var/qmail/bin


# ls -l  /var/qmail/bin


If there is a symbolic link to qmai

Re: [qmailtoaster] Re: I messed up DKIM setup

[Remo Mattei]

Wow did you backup the /var/qmail? Not sure why you removed it you could in case reinstall on top but without a backup I would have not run those commands My 2 cents. Inviato da iPhoneIl giorno 7 apr 2024, alle ore 11:32, Biju Jose  ha scritto:






I have done 



rpm -e --nodeps qmail


yum install qmail


 restored .rpmsave files in /var/qmail/control 





Now I am unable to login to existing domains . But I can create and login to a test domain. How do I connect to existing domains? 

Need some urgent help please.




Biju Jose


From: Biju Jose 
Sent: 07 April 2024 21:44
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
 




#ls -l /var/qmail/bin

total 1512

-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying

-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect

-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast

-rwxr-xr-x 1 root   qmail    126 Sep 10  2019 datemail

-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE

-rwxr-xr-x 1 root   qmail    928 Sep 10  2019 dh_key

-rwxr-xr-x 1 root   root    2777 Apr 30  2018 dkimverify.pl

-rwxr-xr-x 1 root   qmail    114 Sep 10  2019 elq

-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except

-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward

-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck

-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox

-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake

-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch

-rwxr-xr-x 1 root   qmail    179 Sep 10  2019 mailsubj

-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh

-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 pinq

-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate

-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline

-rwxr-xr-x 1 root   qmail    115 Sep 10  2019 qail

-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff

-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes

-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes

-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean

-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk

-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw

-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject

-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local

-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn

-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh

-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu

-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u

-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc

-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd

-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd

-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread

-rwxr-xr-x 1 root   qmail    371 Sep 10  2019 qmail-qstat

-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue

lrwxrwxrwx 1 root   root      26 Apr  7 18:58 qmail-queue.1 -> /var/qmail/bin/qm                                ail-queue

-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig

-rwsrwxrwx 1 qmailq qmail    488 Jul 18  2018 qmail-queue.pl.sh

-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote

-rw-r--r-- 1 root   root    7545 Apr  7 20:59 qmail-remote~

-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0

-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org

-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric

-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn

-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send

-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl

-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd

-rwx-- 1 root   qmail  10488 Sep 10  2019 qmail-start

-rwxr-xr-x 1 root   qmail  14584 Sep 10  2019 qmail-tcpok

-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 qmail-tcpto

-rwxr-xr-x 1 root   qmail  31192 Sep 10  2019 qreceipt

-rwxr-xr-x 1 root   qmail  14632 Sep 10  2019 qsmhook

-rwxr-xr-x 1 root   root    3820 May  6  2019 rcptcheck-overlimit.sh

-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 sendmail

-rws--x--x 1 clamav root   34774 Apr  7  2016 simscan

-rwsr-xr-x 1 root   root   24461 Apr  7  2016 simscanmk

-rwxr-xr-x 1 root   qmail  35560 Sep 10  2019 spfquery

-rwx--x--x 1 root   qmail  10536 Sep 10  2019 splogger

-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 srsfilter

-rwxr-xr-x 1 root   qmail  26920 Sep 10  2019 tcp-env

-rwxr-xr-x 1 root   root     618 Dec 24  2013 update-simscan


From: Eric Broch 
Sent: 07 April 2024 21:40
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup
 


All you should have to do is move qmail-remote (original) back to qmail-remote


What's in /var/qmail/bin


# ls -l  /var/qmail/bin


If there is a symbolic link to qmail-remote (unlink qmail-remote).
do you have qmail-remote.orig ???



On 4/7/2024 9:47 AM, Biju Jose wrote:



How do I reverse  steps 1

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

I have done

  1.
rpm -e --nodeps qmail
  2.
yum install qmail
  3.
 restored .rpmsave files in /var/qmail/control

Now I am unable to login to existing domains . But I can create and login to a 
test domain. How do I connect to existing domains?

Need some urgent help please.

Biju Jose

From: Biju Jose 
Sent: 07 April 2024 21:44
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root  26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qmail-queue
-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmail488 Jul 18  2018 qmail-queue.pl.sh
-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote
-rw-r--r-- 1 root   root7545 Apr  7 20:59 qmail-remote~
-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0
-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org
-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric
-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn
-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send
-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl
-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd
-rwx-- 1 root   qmail  10488 Sep 10  2019 qmail-start
-rwxr-xr-x 1 root   qmail  14584 Sep 10  2019 qmail-tcpok
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 qmail-tcpto
-rwxr-xr-x 1 root   qmail  31192 Sep 10  2019 qreceipt
-rwxr-xr-x 1 root   qmail  14632 Sep 10  2019 qsmhook
-rwxr-xr-x 1 root   root3820 May  6  2019 rcptcheck-overlimit.sh
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 sendmail
-rws--x--x 1 clamav root   34774 Apr  7  2016 simscan
-rwsr-xr-x 1 root   root   24461 Apr  7  2016 simscanmk
-rwxr-xr-x 1 root   qmail  35560 Sep 10  2019 spfquery
-rwx--x--x 1 root   qmail  10536 Sep 10  2019 splogger
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 srsfilter
-rwxr-xr-x 1 root   qmail  26920 Sep 10  2019 tcp-env
-rwxr-xr-x 1 root   root 618 Dec 24  2013 update-simscan

From: Eric Broch 
Sent: 07 April 2024 21:40
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


All you should have to do is move qmail-remote (original) back to qmail-remote


What's in /var/qmail/bin


# ls -l  /var/qmail/bin


If there is a symbolic link to qmail-remote (unlink qmail-remote).

do you have qmail-remote.orig ???


On 4/7/2024 9:47 AM, Biju Jose wrote:
How do I reverse  steps 11 and 12?


  1.  DKIM verification (no patch):
 *   Assumes 'QMAILQUEUE="/var/qmail/bin/simscan"' defined in 
/etc/tcprules.d/tcp.smtp
&& /var/qmail/bin/qmail-queue is a link.
Note: Spamassassin has DKIM verification making this unne

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

#ls -l /var/qmail/bin
total 1512
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 bouncesaying
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 condredirect
-rwxr-xr-x 1 root   qmail   1087 Sep 10  2019 config-fast
-rwxr-xr-x 1 root   qmail126 Sep 10  2019 datemail
-rw--- 1 root   root   11430 Apr  7 20:20 DEADJOE
-rwxr-xr-x 1 root   qmail928 Sep 10  2019 dh_key
-rwxr-xr-x 1 root   root2777 Apr 30  2018 dkimverify.pl
-rwxr-xr-x 1 root   qmail114 Sep 10  2019 elq
-rwxr-xr-x 1 root   qmail  14552 Sep 10  2019 except
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 forward
-rwxr-xr-x 1 root   qmail  26888 Sep 10  2019 instcheck
-rwxr-xr-x 1 root   qmail  26952 Sep 10  2019 maildir2mbox
-rwxr-xr-x 1 root   qmail  14568 Sep 10  2019 maildirmake
-rwxr-xr-x 1 root   qmail  22888 Sep 10  2019 maildirwatch
-rwxr-xr-x 1 root   qmail179 Sep 10  2019 mailsubj
-rwxr-xr-x 1 root   qmail   8259 Sep 10  2019 makecert.sh
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 pinq
-rwxr-xr-x 1 root   qmail  18856 Sep 10  2019 predate
-rwxr-xr-x 1 root   qmail  18792 Sep 10  2019 preline
-rwxr-xr-x 1 root   qmail115 Sep 10  2019 qail
-rwxr-xr-x 1 root   qmail  18760 Sep 10  2019 qbiff
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badloadertypes
-rwxr-xr-x 1 root   qmail  18744 Sep 10  2019 qmail-badmimetypes
-rwx--x--x 1 root   qmail  14712 Sep 10  2019 qmail-clean
-rws--x--x 1 qmailq qmail  52144 Sep 10  2019 qmail-dk
-rwx--x--x 1 root   qmail  10480 Sep 10  2019 qmail-getpw
-rwxr-xr-x 1 root   qmail  51768 Sep 10  2019 qmail-inject
-rwx--x--x 1 root   qmail  64184 Sep 10  2019 qmail-local
-rwx-- 1 root   qmail  22904 Sep 10  2019 qmail-lspawn
-rwx-- 1 root   qmail  18744 Sep 10  2019 qmail-newmrh
-rwx-- 1 root   qmail  14648 Sep 10  2019 qmail-newu
-rwx--x--x 1 root   qmail  22976 Sep 10  2019 qmail-pw2u
-rwxr-xr-x 1 root   qmail  18816 Sep 10  2019 qmail-qmqpc
-rwxr-xr-x 1 root   qmail  22904 Sep 10  2019 qmail-qmqpd
-rwxr-xr-x 1 root   qmail  31096 Sep 10  2019 qmail-qmtpd
-rwxr-xr-x 1 root   qmail  22840 Sep 10  2019 qmail-qread
-rwxr-xr-x 1 root   qmail371 Sep 10  2019 qmail-qstat
-rwx--x--x 1 root   root   27104 Apr  7 21:25 qmail-queue
lrwxrwxrwx 1 root   root  26 Apr  7 18:58 qmail-queue.1 -> 
/var/qmail/bin/qmail-queue
-rws--x--x 1 qmailq qmail  27104 Sep 10  2019 qmail-queue.orig
-rwsrwxrwx 1 qmailq qmail488 Jul 18  2018 qmail-queue.pl.sh
-rwx--x--x 1 root   qmail  52056 Apr  7 21:10 qmail-remote
-rw-r--r-- 1 root   root7545 Apr  7 20:59 qmail-remote~
-rwx--x--x 1 root   qmail   7554 Apr  7 20:51 qmail-remote.0
-rwx--x--x 1 root   qmail  52056 Sep 10  2019 qmail-remote.org
-rwxrwxrwx 1 root   qmail   7545 Apr  7 19:28 qmail-remove.eric
-rwx--x--x 1 root   qmail  18768 Sep 10  2019 qmail-rspawn
-rwx--x--x 1 root   qmail  6 Sep 10  2019 qmail-send
-rwxr-xr-x 1 root   qmail  22856 Sep 10  2019 qmail-showctl
-rwxr-xr-x 1 root   qmail 205752 Sep 10  2019 qmail-smtpd
-rwx-- 1 root   qmail  10488 Sep 10  2019 qmail-start
-rwxr-xr-x 1 root   qmail  14584 Sep 10  2019 qmail-tcpok
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 qmail-tcpto
-rwxr-xr-x 1 root   qmail  31192 Sep 10  2019 qreceipt
-rwxr-xr-x 1 root   qmail  14632 Sep 10  2019 qsmhook
-rwxr-xr-x 1 root   root3820 May  6  2019 rcptcheck-overlimit.sh
-rwxr-xr-x 1 root   qmail  14616 Sep 10  2019 sendmail
-rws--x--x 1 clamav root   34774 Apr  7  2016 simscan
-rwsr-xr-x 1 root   root   24461 Apr  7  2016 simscanmk
-rwxr-xr-x 1 root   qmail  35560 Sep 10  2019 spfquery
-rwx--x--x 1 root   qmail  10536 Sep 10  2019 splogger
-rwxr-xr-x 1 root   qmail  31224 Sep 10  2019 srsfilter
-rwxr-xr-x 1 root   qmail  26920 Sep 10  2019 tcp-env
-rwxr-xr-x 1 root   root 618 Dec 24  2013 update-simscan

From: Eric Broch 
Sent: 07 April 2024 21:40
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


All you should have to do is move qmail-remote (original) back to qmail-remote


What's in /var/qmail/bin


# ls -l  /var/qmail/bin


If there is a symbolic link to qmail-remote (unlink qmail-remote).

do you have qmail-remote.orig ???


On 4/7/2024 9:47 AM, Biju Jose wrote:
How do I reverse  steps 11 and 12?


  1.  DKIM verification (no patch):
 *   Assumes 'QMAILQUEUE="/var/qmail/bin/simscan"' defined in 
/etc/tcprules.d/tcp.smtp
&& /var/qmail/bin/qmail-queue is a link.
Note: Spamassassin has DKIM verification making this unnecessary.
*   # qmailctl stop
*   Add 'export DKVERIFY=1' to /var/qmail/supervise/smtp/run
*   Increase softlimit to 12800 in /var/qmail/supervise/smtp/run
*   # cd /var/qmail/bin
*   # wget http://www.qmailtoaster.org/dkimverify.pl
*   # wget http://www.qmailtoaster.org/qmail-queue.pl.sh
*   # chown root:root dkimverify.pl
*   # chown qmailq:qmail qmail-queue.pl.sh
*  

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

All you should have to do is move qmail-remote (original) back to 
qmail-remote



What's in /var/qmail/bin


# ls -l  /var/qmail/bin


If there is a symbolic link to qmail-remote (unlink qmail-remote).

do you have qmail-remote.orig ???


On 4/7/2024 9:47 AM, Biju Jose wrote:

How do I reverse  steps 11 and 12?

 1. DKIM verification (no patch):
 1. Assumes 'QMAILQUEUE="/var/qmail/bin/simscan"' defined in
/etc/tcprules.d/tcp.smtp
&& /var/qmail/bin/qmail-queue is a link.
Note: Spamassassin has DKIM verification making this unnecessary.
 1. # qmailctl stop
 2. Add 'export DKVERIFY=1' to /var/qmail/supervise/smtp/run
 3. Increase softlimit to 12800 in
/var/qmail/supervise/smtp/run
 4. # cd /var/qmail/bin
 5. # wget http://www.qmailtoaster.org/dkimverify.pl
 6. # wget http://www.qmailtoaster.org/qmail-queue.pl.sh
 7. # chown root:root dkimverify.pl
 8. # chown qmailq:qmail qmail-queue.pl.sh
 9. # chmod 755 dkimverify.pl
10. # chmod 4777 qmail-queue.pl.sh
11. # unlink qmail-queue
12. # ln -s qmail-queue.pl.sh qmail-queue
13. # qmailctl start
14. Send email to user on the host
15. Check email header dkim verification




*From:* Biju Jose 
*Sent:* 07 April 2024 21:14
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup
the qmail-remote.orig file I have is 52,056 bytes root:qmail -rwx—x—x

This is not working. Can I get the file please ?

*From:* Eric Broch 
*Sent:* 07 April 2024 21:01
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Then


mv /var/qmail/bin/qmail-remote.orig /var/qmail/bin/qmail-remote


check permissions


-rwx--x--x 1 root qmail 69864 Mar 30  2022 /var/qmail/bin/qmail-remote



On 4/7/2024 9:18 AM, Biju Jose wrote:

 qmailctl queue
messages in queue: 937
messages in queue but not yet preprocessed: 935
7 Apr 2024 13:15:35 GMT  #269010074  45155  
<mailto:b...@home-trendz.in>  bouncing
7 Apr 2024 13:16:12 GMT  #269010075  63818  
<mailto:b...@whitesindia.com>  bouncing


Priority is to bring it back to send and receive state, DKIM can be 
setup next weekend.


*From:* Eric Broch  
<mailto:ebr...@whitehorsetc.com>

*Sent:* 07 April 2024 20:46
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

And while your at it, can you check the queue?

#qmailctl queue


I might ask, do you want to debug this now, or do you want mail to 
start flowing again?



On 4/7/2024 9:14 AM, Eric Broch wrote:



That won't work because you'll have


#my $debugfile  = undef;

my $debugfile    = '/tmp/dkim.debug';
.
.
. (A bunch of code)
.
.
my $debugfile  = undef;

remove what you've put in that file.

Find the line
my $debugfile  = undef;

comment it

#my $debugfile  = undef;

create an new line under it

my $debugfile    = '/tmp/dkim.debug';

save the file



On 4/7/2024 9:01 AM, Biju Jose wrote:

I added this to the top of qmail-remote
#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';

Tried send/receive, but nothing in  cat /tmp/dkim.debug

*From:* Eric Broch  
<mailto:ebr...@whitehorsetc.com>

*Sent:* 07 April 2024 20:06
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce 
message, will try later
@40006612abd814d79434 warning: trouble injecting bounce 
message, will try later
@40006612ac5419dfcd5c warning: trouble injecting bounce 
message, will try later
@40006612ac5419eda83c warning: trouble injecting bounce 
message, will try later
@40006612acd01e97e2e4 warning: trouble injecting bounce 
message, will try later
@40006612acd01ea413fc warning: trouble injecting bounce 
message, will try later
@40006612ad4c21f3b044 warning: trouble injecting bounce 
message, will try later
@40006612ad4c2202a07c warning: trouble injecting bounce 
message, will try later
@40006612adc825609c74 warning: trouble injecting bounce 
message, will try later
@40006612adc82

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

How do I reverse  steps 11 and 12?


  1.  DKIM verification (no patch):
 *   Assumes 'QMAILQUEUE="/var/qmail/bin/simscan"' defined in 
/etc/tcprules.d/tcp.smtp
&& /var/qmail/bin/qmail-queue is a link.
Note: Spamassassin has DKIM verification making this unnecessary.
*   # qmailctl stop
*   Add 'export DKVERIFY=1' to /var/qmail/supervise/smtp/run
*   Increase softlimit to 12800 in /var/qmail/supervise/smtp/run
*   # cd /var/qmail/bin
*   # wget http://www.qmailtoaster.org/dkimverify.pl
*   # wget http://www.qmailtoaster.org/qmail-queue.pl.sh
*   # chown root:root dkimverify.pl
*   # chown qmailq:qmail qmail-queue.pl.sh
*   # chmod 755 dkimverify.pl
*   # chmod 4777 qmail-queue.pl.sh
*   # unlink qmail-queue
*   # ln -s qmail-queue.pl.sh qmail-queue
*   # qmailctl start
*   Send email to user on the host
*   Check email header dkim verification



From: Biju Jose 
Sent: 07 April 2024 21:14
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup

the qmail-remote.orig file I have is 52,056 bytes root:qmail -rwx—x—x

This is not working. Can I get the file please ?

From: Eric Broch 
Sent: 07 April 2024 21:01
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Then


mv /var/qmail/bin/qmail-remote.orig  /var/qmail/bin/qmail-remote


check permissions


-rwx--x--x 1 root qmail 69864 Mar 30  2022 /var/qmail/bin/qmail-remote



On 4/7/2024 9:18 AM, Biju Jose wrote:
 qmailctl queue
messages in queue: 937
messages in queue but not yet preprocessed: 935
7 Apr 2024 13:15:35 GMT  #269010074  45155  
<mailto:b...@home-trendz.in>  bouncing
7 Apr 2024 13:16:12 GMT  #269010075  63818  
<mailto:b...@whitesindia.com>  bouncing

Priority is to bring it back to send and receive state, DKIM can be setup next 
weekend.

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 20:46
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


And while your at it, can you check the queue?

#qmailctl queue


I might ask, do you want to debug this now, or do you want mail to start 
flowing again?


On 4/7/2024 9:14 AM, Eric Broch wrote:


That won't work because you'll have


#my $debugfile  = undef;

my $debugfile= '/tmp/dkim.debug';
.
.
. (A bunch of code)
.
.
my $debugfile  = undef;

remove what you've put in that file.

Find the line
my $debugfile  = undef;

comment it

#my $debugfile  = undef;

create an new line under it

my $debugfile= '/tmp/dkim.debug';

save the file




On 4/7/2024 9:01 AM, Biju Jose wrote:
I added this to the top of qmail-remote
#my $debugfile  = undef;
my $debugfile= '/tmp/dkim.debug';

Tried send/receive, but nothing in  cat /tmp/dkim.debug

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 20:06
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile= '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce message, will try 
later
@40006612abd814d79434 warning: trouble injecting bounce message, will try 
later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, will try 
later
@40006612ac5419eda83c warning: trouble injecting bounce message, will try 
later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, will try 
later
@40006612acd01ea413fc warning: trouble injecting bounce message, will try 
later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, will try 
later
@40006612ad4c2202a07c warning: trouble injecting bounce message, will try 
later
@40006612adc825609c74 warning: trouble injecting bounce message, will try 
later
@40006612adc8256ce114 warning: trouble injecting bounce message, will try 
later

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 19:59
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

the qmail-remote.orig file I have is 52,056 bytes root:qmail -rwx—x—x

This is not working. Can I get the file please ?

From: Eric Broch 
Sent: 07 April 2024 21:01
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Then


mv /var/qmail/bin/qmail-remote.orig  /var/qmail/bin/qmail-remote


check permissions


-rwx--x--x 1 root qmail 69864 Mar 30  2022 /var/qmail/bin/qmail-remote



On 4/7/2024 9:18 AM, Biju Jose wrote:
 qmailctl queue
messages in queue: 937
messages in queue but not yet preprocessed: 935
7 Apr 2024 13:15:35 GMT  #269010074  45155  
<mailto:b...@home-trendz.in>  bouncing
7 Apr 2024 13:16:12 GMT  #269010075  63818  
<mailto:b...@whitesindia.com>  bouncing

Priority is to bring it back to send and receive state, DKIM can be setup next 
weekend.

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 20:46
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


And while your at it, can you check the queue?

#qmailctl queue


I might ask, do you want to debug this now, or do you want mail to start 
flowing again?


On 4/7/2024 9:14 AM, Eric Broch wrote:


That won't work because you'll have


#my $debugfile  = undef;

my $debugfile= '/tmp/dkim.debug';
.
.
. (A bunch of code)
.
.
my $debugfile  = undef;

remove what you've put in that file.

Find the line
my $debugfile  = undef;

comment it

#my $debugfile  = undef;

create an new line under it

my $debugfile= '/tmp/dkim.debug';

save the file




On 4/7/2024 9:01 AM, Biju Jose wrote:
I added this to the top of qmail-remote
#my $debugfile  = undef;
my $debugfile= '/tmp/dkim.debug';

Tried send/receive, but nothing in  cat /tmp/dkim.debug

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 20:06
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile= '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce message, will try 
later
@40006612abd814d79434 warning: trouble injecting bounce message, will try 
later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, will try 
later
@40006612ac5419eda83c warning: trouble injecting bounce message, will try 
later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, will try 
later
@40006612acd01ea413fc warning: trouble injecting bounce message, will try 
later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, will try 
later
@40006612ad4c2202a07c warning: trouble injecting bounce message, will try 
later
@40006612adc825609c74 warning: trouble injecting bounce message, will try 
later
@40006612adc8256ce114 warning: trouble injecting bounce message, will try 
later

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 19:59
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 19:56
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: [qmailtoaster] I messed up DKIM setup

Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a mistake and 
now emails are not going out. Request help to solve the issue.

Thanks
Biju Jose

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

Then


mv /var/qmail/bin/qmail-remote.orig  /var/qmail/bin/qmail-remote


check permissions


-rwx--x--x 1 root qmail 69864 Mar 30  2022 /var/qmail/bin/qmail-remote



On 4/7/2024 9:18 AM, Biju Jose wrote:

 qmailctl queue
messages in queue: 937
messages in queue but not yet preprocessed: 935
7 Apr 2024 13:15:35 GMT  #269010074  45155   bouncing
7 Apr 2024 13:16:12 GMT  #269010075  63818  
 bouncing


Priority is to bring it back to send and receive state, DKIM can be 
setup next weekend.


*From:* Eric Broch 
*Sent:* 07 April 2024 20:46
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

And while your at it, can you check the queue?

#qmailctl queue


I might ask, do you want to debug this now, or do you want mail to 
start flowing again?



On 4/7/2024 9:14 AM, Eric Broch wrote:



That won't work because you'll have


#my $debugfile  = undef;

my $debugfile    = '/tmp/dkim.debug';
.
.
. (A bunch of code)
.
.
my $debugfile  = undef;

remove what you've put in that file.

Find the line
my $debugfile  = undef;

comment it

#my $debugfile  = undef;

create an new line under it

my $debugfile    = '/tmp/dkim.debug';

save the file



On 4/7/2024 9:01 AM, Biju Jose wrote:

I added this to the top of qmail-remote
#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';

Tried send/receive, but nothing in  cat /tmp/dkim.debug

*From:* Eric Broch  
<mailto:ebr...@whitehorsetc.com>

*Sent:* 07 April 2024 20:06
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce 
message, will try later
@40006612abd814d79434 warning: trouble injecting bounce 
message, will try later
@40006612ac5419dfcd5c warning: trouble injecting bounce 
message, will try later
@40006612ac5419eda83c warning: trouble injecting bounce 
message, will try later
@40006612acd01e97e2e4 warning: trouble injecting bounce 
message, will try later
@40006612acd01ea413fc warning: trouble injecting bounce 
message, will try later
@40006612ad4c21f3b044 warning: trouble injecting bounce 
message, will try later
@40006612ad4c2202a07c warning: trouble injecting bounce 
message, will try later
@40006612adc825609c74 warning: trouble injecting bounce 
message, will try later
@40006612adc8256ce114 warning: trouble injecting bounce 
message, will try later


*From:* Eric Broch  
<mailto:ebr...@whitehorsetc.com>

*Sent:* 07 April 2024 19:59
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html 
<http://www.qmailtoaster.com/dkim.html>


*From:* Biju Jose  
<mailto:bijuko...@outlook.com>

*Sent:* 07 April 2024 19:56
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* [qmailtoaster] I messed up DKIM setup
Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made 
a mistake and now emails are not going out. Request help to solve 
the issue.


Thanks
Biju Jose

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

 qmailctl queue
messages in queue: 937
messages in queue but not yet preprocessed: 935
7 Apr 2024 13:15:35 GMT  #269010074  45155bouncing
7 Apr 2024 13:16:12 GMT  #269010075  63818bouncing

Priority is to bring it back to send and receive state, DKIM can be setup next 
weekend.

From: Eric Broch 
Sent: 07 April 2024 20:46
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


And while your at it, can you check the queue?

#qmailctl queue


I might ask, do you want to debug this now, or do you want mail to start 
flowing again?


On 4/7/2024 9:14 AM, Eric Broch wrote:


That won't work because you'll have


#my $debugfile  = undef;

my $debugfile= '/tmp/dkim.debug';
.
.
. (A bunch of code)
.
.
my $debugfile  = undef;

remove what you've put in that file.

Find the line
my $debugfile  = undef;

comment it

#my $debugfile  = undef;

create an new line under it

my $debugfile= '/tmp/dkim.debug';

save the file




On 4/7/2024 9:01 AM, Biju Jose wrote:
I added this to the top of qmail-remote
#my $debugfile  = undef;
my $debugfile= '/tmp/dkim.debug';

Tried send/receive, but nothing in  cat /tmp/dkim.debug

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 20:06
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile= '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce message, will try 
later
@40006612abd814d79434 warning: trouble injecting bounce message, will try 
later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, will try 
later
@40006612ac5419eda83c warning: trouble injecting bounce message, will try 
later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, will try 
later
@40006612acd01ea413fc warning: trouble injecting bounce message, will try 
later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, will try 
later
@40006612ad4c2202a07c warning: trouble injecting bounce message, will try 
later
@40006612adc825609c74 warning: trouble injecting bounce message, will try 
later
@40006612adc8256ce114 warning: trouble injecting bounce message, will try 
later

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 19:59
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 19:56
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: [qmailtoaster] I messed up DKIM setup

Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a mistake and 
now emails are not going out. Request help to solve the issue.

Thanks
Biju Jose

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

And while your at it, can you check the queue?

#qmailctl queue


I might ask, do you want to debug this now, or do you want mail to start 
flowing again?



On 4/7/2024 9:14 AM, Eric Broch wrote:



That won't work because you'll have


#my $debugfile  = undef;

my $debugfile    = '/tmp/dkim.debug';
.
.
. (A bunch of code)
.
.
my $debugfile  = undef;

remove what you've put in that file.

Find the line
my $debugfile  = undef;

comment it

#my $debugfile  = undef;

create an new line under it

my $debugfile    = '/tmp/dkim.debug';

save the file



On 4/7/2024 9:01 AM, Biju Jose wrote:

I added this to the top of qmail-remote
#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';

Tried send/receive, but nothing in  cat /tmp/dkim.debug

*From:* Eric Broch 
*Sent:* 07 April 2024 20:06
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce message, 
will try later
@40006612abd814d79434 warning: trouble injecting bounce message, 
will try later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, 
will try later
@40006612ac5419eda83c warning: trouble injecting bounce message, 
will try later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, 
will try later
@40006612acd01ea413fc warning: trouble injecting bounce message, 
will try later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, 
will try later
@40006612ad4c2202a07c warning: trouble injecting bounce message, 
will try later
@40006612adc825609c74 warning: trouble injecting bounce message, 
will try later
@40006612adc8256ce114 warning: trouble injecting bounce message, 
will try later


*From:* Eric Broch  
<mailto:ebr...@whitehorsetc.com>

*Sent:* 07 April 2024 19:59
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html 
<http://www.qmailtoaster.com/dkim.html>


*From:* Biju Jose  
<mailto:bijuko...@outlook.com>

*Sent:* 07 April 2024 19:56
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* [qmailtoaster] I messed up DKIM setup
Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a 
mistake and now emails are not going out. Request help to solve the 
issue.


Thanks
Biju Jose

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

That won't work because you'll have


#my $debugfile  = undef;

my $debugfile    = '/tmp/dkim.debug';
.
.
. (A bunch of code)
.
.
my $debugfile  = undef;

remove what you've put in that file.

Find the line
my $debugfile  = undef;

comment it

#my $debugfile  = undef;

create an new line under it

my $debugfile    = '/tmp/dkim.debug';

save the file



On 4/7/2024 9:01 AM, Biju Jose wrote:

I added this to the top of qmail-remote
#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';

Tried send/receive, but nothing in  cat /tmp/dkim.debug

*From:* Eric Broch 
*Sent:* 07 April 2024 20:06
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce message, 
will try later
@40006612abd814d79434 warning: trouble injecting bounce message, 
will try later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, 
will try later
@40006612ac5419eda83c warning: trouble injecting bounce message, 
will try later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, 
will try later
@40006612acd01ea413fc warning: trouble injecting bounce message, 
will try later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, 
will try later
@40006612ad4c2202a07c warning: trouble injecting bounce message, 
will try later
@40006612adc825609c74 warning: trouble injecting bounce message, 
will try later
@40006612adc8256ce114 warning: trouble injecting bounce message, 
will try later


*From:* Eric Broch  
<mailto:ebr...@whitehorsetc.com>

*Sent:* 07 April 2024 19:59
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html 
<http://www.qmailtoaster.com/dkim.html>


*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 07 April 2024 19:56
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* [qmailtoaster] I messed up DKIM setup
Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a 
mistake and now emails are not going out. Request help to solve the 
issue.


Thanks
Biju Jose

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

I added this to the top of qmail-remote
#my $debugfile  = undef;
my $debugfile= '/tmp/dkim.debug';

Tried send/receive, but nothing in  cat /tmp/dkim.debug

From: Eric Broch 
Sent: 07 April 2024 20:06
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile= '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce message, will try 
later
@40006612abd814d79434 warning: trouble injecting bounce message, will try 
later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, will try 
later
@40006612ac5419eda83c warning: trouble injecting bounce message, will try 
later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, will try 
later
@40006612acd01ea413fc warning: trouble injecting bounce message, will try 
later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, will try 
later
@40006612ad4c2202a07c warning: trouble injecting bounce message, will try 
later
@40006612adc825609c74 warning: trouble injecting bounce message, will try 
later
@40006612adc8256ce114 warning: trouble injecting bounce message, will try 
later

From: Eric Broch <mailto:ebr...@whitehorsetc.com>
Sent: 07 April 2024 19:59
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 19:56
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: [qmailtoaster] I messed up DKIM setup

Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a mistake and 
now emails are not going out. Request help to solve the issue.

Thanks
Biju Jose

Re: [qmailtoaster] Re: I messed up DKIM setup

[Qmail]

Hi.

Wouldn't it be to just stop qmail and move the qmail-remote.orig to 
qmail-remote and start qmail.


And then start from scratch with Dkim ?

/Finn

Den 07-04-2024 kl. 16:31 skrev Biju Jose:
@40006612abd814cc842c warning: trouble injecting bounce message, 
will try later
@40006612abd814d79434 warning: trouble injecting bounce message, 
will try later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, 
will try later
@40006612ac5419eda83c warning: trouble injecting bounce message, 
will try later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, 
will try later
@40006612acd01ea413fc warning: trouble injecting bounce message, 
will try later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, 
will try later
@40006612ad4c2202a07c warning: trouble injecting bounce message, 
will try later
@40006612adc825609c74 warning: trouble injecting bounce message, 
will try later
@40006612adc8256ce114 warning: trouble injecting bounce message, 
will try later


*From:* Eric Broch 
*Sent:* 07 April 2024 19:59
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html 
<http://www.qmailtoaster.com/dkim.html>


*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 07 April 2024 19:56
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* [qmailtoaster] I messed up DKIM setup
Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a 
mistake and now emails are not going out. Request help to solve the issue.


Thanks
Biju Jose


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

Change qmail-remote to look like this


#my $debugfile  = undef;
my $debugfile    = '/tmp/dkim.debug';


send an email


cat /tmp/dkim.debug


post output.



On 4/7/2024 8:31 AM, Biju Jose wrote:
@40006612abd814cc842c warning: trouble injecting bounce message, 
will try later
@40006612abd814d79434 warning: trouble injecting bounce message, 
will try later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, 
will try later
@40006612ac5419eda83c warning: trouble injecting bounce message, 
will try later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, 
will try later
@40006612acd01ea413fc warning: trouble injecting bounce message, 
will try later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, 
will try later
@40006612ad4c2202a07c warning: trouble injecting bounce message, 
will try later
@40006612adc825609c74 warning: trouble injecting bounce message, 
will try later
@40006612adc8256ce114 warning: trouble injecting bounce message, 
will try later


*From:* Eric Broch 
*Sent:* 07 April 2024 19:59
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* Re: [qmailtoaster] Re: I messed up DKIM setup

Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html 
<http://www.qmailtoaster.com/dkim.html>


*From:* Biju Jose  <mailto:bijuko...@outlook.com>
*Sent:* 07 April 2024 19:56
*To:* qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
 
<mailto:qmailtoaster-list@qmailtoaster.com>

*Subject:* [qmailtoaster] I messed up DKIM setup
Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a 
mistake and now emails are not going out. Request help to solve the 
issue.


Thanks
Biju Jose

Re: [qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

@40006612abd814cc842c warning: trouble injecting bounce message, will try 
later
@40006612abd814d79434 warning: trouble injecting bounce message, will try 
later
@40006612ac5419dfcd5c warning: trouble injecting bounce message, will try 
later
@40006612ac5419eda83c warning: trouble injecting bounce message, will try 
later
@40006612acd01e97e2e4 warning: trouble injecting bounce message, will try 
later
@40006612acd01ea413fc warning: trouble injecting bounce message, will try 
later
@40006612ad4c21f3b044 warning: trouble injecting bounce message, will try 
later
@40006612ad4c2202a07c warning: trouble injecting bounce message, will try 
later
@40006612adc825609c74 warning: trouble injecting bounce message, will try 
later
@40006612adc8256ce114 warning: trouble injecting bounce message, will try 
later

From: Eric Broch 
Sent: 07 April 2024 19:59
To: qmailtoaster-list@qmailtoaster.com 
Subject: Re: [qmailtoaster] Re: I messed up DKIM setup


Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:
The guide was at http://www.qmailtoaster.com/dkim.html

From: Biju Jose <mailto:bijuko...@outlook.com>
Sent: 07 April 2024 19:56
To: 
qmailtoaster-list@qmailtoaster.com<mailto:qmailtoaster-list@qmailtoaster.com> 
<mailto:qmailtoaster-list@qmailtoaster.com>
Subject: [qmailtoaster] I messed up DKIM setup

Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a mistake and 
now emails are not going out. Request help to solve the issue.

Thanks
Biju Jose

Re: [qmailtoaster] Re: I messed up DKIM setup

[Eric Broch]

Is there anything in /var/log/qmail/send/current log?


On 4/7/2024 8:27 AM, Biju Jose wrote:

The guide was at http://www.qmailtoaster.com/dkim.html

*From:* Biju Jose 
*Sent:* 07 April 2024 19:56
*To:* qmailtoaster-list@qmailtoaster.com 


*Subject:* [qmailtoaster] I messed up DKIM setup
Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a 
mistake and now emails are not going out. Request help to solve the issue.


Thanks
Biju Jose

[qmailtoaster] Re: I messed up DKIM setup

[Biju Jose]

The guide was at http://www.qmailtoaster.com/dkim.html

From: Biju Jose 
Sent: 07 April 2024 19:56
To: qmailtoaster-list@qmailtoaster.com 
Subject: [qmailtoaster] I messed up DKIM setup

Hi,

I need some urgent help.

I messed up a qmail server running on centos 7

I was trying to setup DKIM using this guide. But somewhere I made a mistake and 
now emails are not going out. Request help to solve the issue.

Thanks
Biju Jose

Re: [qmailtoaster] Re: Search from webmail: ERROR: Connection interrupted by the IMAP server

[Giuseppe Perna]

I use vmware and I can assign up to 20 GB re ram and 10/12 vcpu, but the vm
always uses only 1 GB of ram.

thanks

Il giorno mar 4 ott 2022 alle ore 21:16 Eric Broch 
ha scritto:

> What VE are you using? Can't you assign a hard amount of memory to a VM?
>
>
> On 10/4/2022 10:10 AM, Giuseppe Perna wrote:
>
> Hello Eric,
> Thanks for your replay.
> I have in total 7GB of RAM, but the vm alloched only 1gb in all condition.
>
> Please help me
> Thanks
>
>
> Il giorno martedì 4 ottobre 2022, Eric Broch  ha
> scritto:
>
>> I did a brief internet search and I did not find anything indicating how
>> to allow more memory to programs.
>>
>> I will investigate further.
>>
>> On 10/4/2022 6:59 AM, Giuseppe Perna wrote:
>>
>>> Hello,
>>> please help me.
>>> thanks
>>>
>>> ERROR: Connection interrupted by the IMAP server
>>> Query: SEARCH CHARSET UTF-8 ALL FROM "pippo"
>>>
>>> I have this old version CentOS release 5.8 (Final):
>>>
>>> ucspi-tcp-toaster-0.88-1.3.9
>>> maildrop-toaster-2.0.3-1.3.8
>>> control-panel-toaster-0.5-1.4.0
>>> libdomainkeys-toaster-0.68-1.3.6
>>> qmail-pop3d-toaster-1.03-1.3.22
>>> squirrelmail-toaster-1.4.20-1.3.17
>>> qmailtoaster-plus.repo-0.2-2
>>> vpopmail-toaster-5.4.33-1.4.0
>>> daemontools-toaster-0.76-1.3.6
>>> libsrs2-toaster-1.0.18-1.3.6
>>> courier-authlib-toaster-0.59.2-1.3.10
>>> ripmime-toaster-1.4.0.6-1.3.6
>>> autorespond-toaster-2.0.5-1.4.0
>>> courier-imap-toaster-4.1.2-1.3.10
>>> isoqlog-toaster-2.1-1.3.7
>>> maildrop-toaster-devel-2.0.3-1.3.8
>>> qmailmrtg-toaster-4.2-1.3.7
>>> send-emails-toaster-0.5-1.4.0
>>> spamassassin-toaster-3.3.2-1.4.3
>>> vqadmin-toaster-2.3.7-1.4.1
>>> qmailtoaster-plus-0.3.2-1.4.19
>>> ezmlm-toaster-0.53.324-1.3.6
>>> qmail-toaster-1.03-1.3.22
>>> ezmlm-cgi-toaster-0.53.324-1.3.6
>>> qmailadmin-toaster-1.2.16-1.4.0
>>> simscan-toaster-1.4.0-1.4.0
>>> clamav-toaster-0.97.6-1.4.2
>>>
>>>
>>> please help me
>>>
>>> thanks
>>>
>>
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>
>>

Re: [qmailtoaster] Re: Search from webmail: ERROR: Connection interrupted by the IMAP server

[Eric Broch]

What VE are you using? Can't you assign a hard amount of memory to a VM?


On 10/4/2022 10:10 AM, Giuseppe Perna wrote:

Hello Eric,
Thanks for your replay.
I have in total 7GB of RAM, but the vm alloched only 1gb in all condition.

Please help me
Thanks


Il giorno martedì 4 ottobre 2022, Eric Broch  
ha scritto:


I did a brief internet search and I did not find anything
indicating how to allow more memory to programs.

I will investigate further.

On 10/4/2022 6:59 AM, Giuseppe Perna wrote:

Hello,
please help me.
thanks

ERROR: Connection interrupted by the IMAP server
Query: SEARCH CHARSET UTF-8 ALL FROM "pippo"

I have this old version CentOS release 5.8 (Final):

ucspi-tcp-toaster-0.88-1.3.9
maildrop-toaster-2.0.3-1.3.8
control-panel-toaster-0.5-1.4.0
libdomainkeys-toaster-0.68-1.3.6
qmail-pop3d-toaster-1.03-1.3.22
squirrelmail-toaster-1.4.20-1.3.17
qmailtoaster-plus.repo-0.2-2
vpopmail-toaster-5.4.33-1.4.0
daemontools-toaster-0.76-1.3.6
libsrs2-toaster-1.0.18-1.3.6
courier-authlib-toaster-0.59.2-1.3.10
ripmime-toaster-1.4.0.6-1.3.6
autorespond-toaster-2.0.5-1.4.0
courier-imap-toaster-4.1.2-1.3.10
isoqlog-toaster-2.1-1.3.7
maildrop-toaster-devel-2.0.3-1.3.8
qmailmrtg-toaster-4.2-1.3.7
send-emails-toaster-0.5-1.4.0
spamassassin-toaster-3.3.2-1.4.3
vqadmin-toaster-2.3.7-1.4.1
qmailtoaster-plus-0.3.2-1.4.19
ezmlm-toaster-0.53.324-1.3.6
qmail-toaster-1.03-1.3.22
ezmlm-cgi-toaster-0.53.324-1.3.6
qmailadmin-toaster-1.2.16-1.4.0
simscan-toaster-1.4.0-1.4.0
clamav-toaster-0.97.6-1.4.2


please help me

thanks


-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Re: Search from webmail: ERROR: Connection interrupted by the IMAP server

[Giuseppe Perna]

Hello Eric,
Thanks for your replay.
I have in total 7GB of RAM, but the vm alloched only 1gb in all condition.

Please help me
Thanks


Il giorno martedì 4 ottobre 2022, Eric Broch  ha
scritto:

> I did a brief internet search and I did not find anything indicating how
> to allow more memory to programs.
>
> I will investigate further.
>
> On 10/4/2022 6:59 AM, Giuseppe Perna wrote:
>
>> Hello,
>> please help me.
>> thanks
>>
>> ERROR: Connection interrupted by the IMAP server
>> Query: SEARCH CHARSET UTF-8 ALL FROM "pippo"
>>
>> I have this old version CentOS release 5.8 (Final):
>>
>> ucspi-tcp-toaster-0.88-1.3.9
>> maildrop-toaster-2.0.3-1.3.8
>> control-panel-toaster-0.5-1.4.0
>> libdomainkeys-toaster-0.68-1.3.6
>> qmail-pop3d-toaster-1.03-1.3.22
>> squirrelmail-toaster-1.4.20-1.3.17
>> qmailtoaster-plus.repo-0.2-2
>> vpopmail-toaster-5.4.33-1.4.0
>> daemontools-toaster-0.76-1.3.6
>> libsrs2-toaster-1.0.18-1.3.6
>> courier-authlib-toaster-0.59.2-1.3.10
>> ripmime-toaster-1.4.0.6-1.3.6
>> autorespond-toaster-2.0.5-1.4.0
>> courier-imap-toaster-4.1.2-1.3.10
>> isoqlog-toaster-2.1-1.3.7
>> maildrop-toaster-devel-2.0.3-1.3.8
>> qmailmrtg-toaster-4.2-1.3.7
>> send-emails-toaster-0.5-1.4.0
>> spamassassin-toaster-3.3.2-1.4.3
>> vqadmin-toaster-2.3.7-1.4.1
>> qmailtoaster-plus-0.3.2-1.4.19
>> ezmlm-toaster-0.53.324-1.3.6
>> qmail-toaster-1.03-1.3.22
>> ezmlm-cgi-toaster-0.53.324-1.3.6
>> qmailadmin-toaster-1.2.16-1.4.0
>> simscan-toaster-1.4.0-1.4.0
>> clamav-toaster-0.97.6-1.4.2
>>
>>
>> please help me
>>
>> thanks
>>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>

[qmailtoaster] Re: **SPAM** Re: [qmailtoaster] qmail toaster support for BDAT

[Remo Mattei]

I just tested my two mail servers with qmt and both work just fine and sent 
email from outlook web. 

So not sure what is your config and which patch you have used. 

Remo 

> On Aug 28, 2022, at 13:25, Jaime Lerner  wrote:
> 
> I read that if you’re running ESMTP, that includes BDAT support. QMT has 
> ESMTP via a patch. I know my server’s banner includes ESMTP during an SMTP 
> handshake ... so wouldn’t that mean QMT has BDAT support?
>  
> From: Jeff Koch  >
> Reply-To:  >
> Date: Sunday, August 28, 2022 at 4:20 PM
> To:  >
> Subject: Re: [qmailtoaster] qmail toaster support for BDAT
>  
> Thanks Tonix - so the result is that messages from email clients (like 
> Outlook) that add multiple bare line feeds in their messages and use O365 
> will now get rejected by the qmail toaster.  How nice of Microsoft. 
> 
> Jeff
> 
> On 8/28/2022 2:27 PM, to...@interazioni.it  
> wrote:
>> This document explains the problem: 
>> https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/non-delivery-reports-in-exchange-online/fix-error-code-550-5-6-11-in-exchange-online
>>  
>> 
>> 
>> I will omit my thought on remote admins. 
>> A very simple rule in communication is: be strict when sending, be tolerant 
>> when receiving.
>> 
>> Regards,
>> Tonino
>> 
>> 
>> Il 28 agosto 2022 19:24:13 CEST, Jeff Koch  
>>  ha scritto:
>> >Further information:
>> >
>> >The sender also got the following message from his exchange mailserver when 
>> >trying to send to our mailserver:
>> >
>> >Your message contains invalid characters (bare line feed characters) which 
>> >the email servers at ..com don't support
>> >
>> >Jeff
>> >
>> >
>> >On 8/28/2022 12:45 PM, Jeff Koch wrote:
>> >> 
>> >> Never heard of this before but an email sender to our mailserver got the 
>> >> following error message:
>> >> 
>> >> 550 5.6.11 SMTPSEND.BareLinefeedsAreIllegal; message contains bare 
>> >> linefeeds, which cannot be sent via DATA and receiving system does not 
>> >> support BDAT
>> >> 
>> >> Does anyone know whether the qmail toaster supports the SMTP protocol 
>> >> BDAT command ?
>> >> 
>> >> Thanks,
>> >> 
>> >> Jeff

[qmailtoaster] Re: **SPAM** [qmailtoaster] SSL/TLS issue

[Remo Mattei]

I am running rocky latest as well I did not notice anything about this but I 
can check my system and share. 

> Il giorno 4 lug 2022, alle ore 08:30, Qmail  ha scritto:
> 
> Hi all
> 
> I'm Running Rocky - latest and greatest release.
> 
> After updating my Qmail to Rel. 1.03-3.3.7.qt.md.el8  (@qmt-md-testing) and  
> spamdyke to Rel. 5.0.1-3.qt.el8 (@qmt-testing)  I receive this in my maillog 
> file :
> 
> Jul  4 16:40:42 post spamdyke[4240]: ERROR(tls_init_inner()@tls.c:345): 
> unable to set SSL/TLS cipher list: DEFAULT: A protocol or library failure 
> occurred, error:1426E0B9:SSL routines:ciphersuite_cb:no cipher match
> Jul  4 16:40:42 post spamdyke[4240]: ERROR(tls_init_inner()@tls.c:355): 
> unable to initialize SSL/TLS library
> Jul  4 16:40:42 post spamdyke[4240]: TLS_ENCRYPTED from: (unknown) to: 
> (unknown) origin_ip: 91.123.194.221 origin_rdns: mta-56.gansend2.com auth: 
> (unknown) encryption: TLS_PASSTHROUGH reason: (empty)
> 
> 
> I have checked against my prevoius running qmail 1.03-3.3.5.qt.md.el8 
> instance and there is no changes to the tlsserverciphers.
> 
> update-crypto-policies=LEGACY
> opensslcnf.config  having  CipherString = @SECLEVEL=1
> 
> In my /var/log/qmail/smtp file all is fine
> 
> 
> All mails seems to pass through anyway but ...
> 
> 
> What am I missing ?  what's changed in spamdyke ?
> 
> 
> Thanks,
> Finn
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Re: Alias-Login

[Eric Broch]

Hi Andreas,

For Dovecot alias login you could try a new password query in your 
'/etc/dovecot/dovecot-sql.conf.ext' file (save original):


password_query = SELECT CONCAT( pw_name ,'@', pw_domain ) AS user, \
  pw_passwd AS password, \
  pw_dir as userdb_home, \
  89 AS userdb_uid, \
  89 AS userdb_gid \
  FROM vpopmail vp \
  LEFT JOIN valias va ON concat(vp.pw_name,'@',vp.pw_domain) = 
va.valias_line \

  WHERE ( vp.pw_name = '%n' OR va.alias = '%n' ) AND vp.pw_domain = '%d'

Reload dovecot

# systemctl reload dovecot.

Add alias

# /home/vpopmail/bin/valias -i u...@testdom.com us...@testdom.com

Test with doveadm

# doveadm auth test u...@testdom.com pass1
passdb: u...@testdom.com auth succeeded
extra fields:
  user=u...@testdom.com

# doveadm auth test us...@testdom.com pass2
passdb: us...@testdom.com auth succeeded
extra fields:
  user=u...@testdom.com

  original_user=us...@testdom.com


Hope it goes well.

Over on 'Roberto's qmail notes he does this with alias domains as well 
which includes a vpopmail patch and a new alias domain table in the database


Eric


On 2/18/2022 8:25 AM, Andreas wrote:

Hi Eric,

i just saw in my logs and tested afterwards: Submission works with an 
alias-login, It is just imap and pop that doesn't work.


Andreas

Am 10.02.22 um 15:55 schrieb Eric Broch:

Is this an issue with IMAP?

On 2/10/2022 7:33 AM, Andreas wrote:
I am glad if you do, just saw in my dkim-reports that there where 
some Mails from you not reaching my account.


Take your time, we could resolve the cient-issues for the time beeing

Andreas

Am 10.02.22 um 14:02 schrieb Eric Broch:

Andreas,

I haven't had a chance to look into this yet...will get to it today 
or tomorrow.


Eric

On 2/10/2022 12:09 AM, Andreas wrote:

Hi Eric,

I think you tried to respond for my issue with login with an 
alias-users?


My account was blocked for ~1 day, I didn't get the list-emails.

Did you find anything about this issue?

Thanks again for your work on the toaster

Andreas







-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Email account sync issue in email clients

[ChandranManikandan]

Hi Eric,

I have tried the following procedure and the issue has been resolved.

cd /home/vpopmail/domains/domain.com/email/Maildir/cur

ls 1648520179.28619.mail.domain.com,S=6322:2, -lh

mv 1648520179.28619.mail.domain.com,S=6322:2,  /home/vpopmail/domains/
domain.com/email/Maildir/

systemctl restart dovecot

Thanks for your support.



On Tue, Mar 29, 2022 at 10:01 PM Eric Broch  wrote:

> Yes, I've removed the offending email to solve this issue.
> On 3/29/2022 7:57 AM, Mani Kandan wrote:
>
> Hi Eric,
> I have rename the index.cache file and restarted dovecot but still the
> same sync issue while try from thunderbird or outlook, not download any
> email after that. But in squirrelmail and round cube webmail can see the
> new emails except that particular mail page.
>
> I have checked dovecot list, they said to use the below command for
> resyncing but still not fixed.
> doveadm force-resync -A or doveadm force-resync -A “*”
>
> Can I try to found this particular mail home/vpopmail/domains/
> xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,)  and
> remove or move from cur folder.
> Can you advise on this
>
> Sent from my iPhone
>
> On 29 Mar 2022, at 9:30 PM, Eric Broch 
>  wrote:
>
> 
>
> It's most likely a server side issue, specifically the
> dovecot.index.cache? file records a different size than the message name
> with S='size'. You could delete the cache file and see if it repairs itself
> or you could ask on the dovecot list.
>
> Eric
> On 3/29/2022 2:53 AM, ChandranManikandan wrote:
>
> Hi Friends,
>
> Anyone having the same issue, some users' email clients
> (Outlook,Thunderbird) have not synced any emails in Inbox since morning.
> I tried to repair it myself but received the same message
> Is it server side issue or email client side issue.
> I removed that email account and re-configure it but received the same
> message.
> I would Appreciate anyone who could help me.
>
> On Tue, Mar 29, 2022 at 1:59 PM ChandranManikandan 
> wrote:
>
>> Hi Friends,
>>
>> Some few email accounts are sync issue come in
>> outlook,thunderbird,roundcube and squirrelmail after power shutdown
>> suddenly.
>> The dovecot mail log is showing below for those email accounts.
>> can anyone help me to fix it.
>>
>>
>> imap(em...@xxx.com)<19758>: Error: Mailbox INBOX:
>> UID=502283: read(/home/vpopmail/domains/
>> xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,)
>> failed: Cached message size larger than expected (13720 > 0, box=INBOX,
>> UID=502283) (read reason=mail stream)
>> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Error:
>> Corrupted record in index cache file /home/vpopmail/domains/
>> xxx.com/email/Maildir/dovecot.index.cache:  Broken physical size in
>> mailbox INBOX: read(/home/vpopmail/domains/
>> xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,)
>> failed: Cached message size larger than expected (13720 > 0, box=INBOX,
>> UID=502283)
>> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Error:
>> Mailbox INBOX: UID=502283: read(/home/vpopmail/domains/
>> xxx.com/email/Maildir/cur/1648520174.28570..mail.xxx.com,S=13720:2,)
>> failed: Cached message size larger than expected (13720 > 0, box=INBOX,
>> UID=502283) (read reason=)
>> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Info:
>> FETCH failed: Internal error occurred. Refer to server log for more
>> information. [2022-03-29 13:40:48] in=323 out=589163 deleted=0 expunged=0
>> trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
>>
>>
>> --
>>
>>
>> *Regards, Manikandan.C *
>>
>
>
> --
>
>
> *Regards, Manikandan.C *
>
>

-- 


*Regards,Manikandan.C*

Re: [qmailtoaster] Re: Email account sync issue in email clients

[Eric Broch]

Yes, I've removed the offending email to solve this issue.

On 3/29/2022 7:57 AM, Mani Kandan wrote:

Hi Eric,
I have rename the index.cache file and restarted dovecot but still the 
same sync issue while try from thunderbird or outlook, not download 
any email after that. But in squirrelmail and round cube webmail can 
see the new emails except that particular mail page.


I have checked dovecot list, they said to use the below command for 
resyncing but still not fixed.

doveadm force-resync -A or doveadm force-resync -A “*”

Can I try to found this particular mail 
home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2, 
) 
 and remove or move from cur folder.

Can you advise on this

Sent from my iPhone


On 29 Mar 2022, at 9:30 PM, Eric Broch  wrote:



It's most likely a server side issue, specifically the 
dovecot.index.cache? file records a different size than the message 
name with S='size'. You could delete the cache file and see if it 
repairs itself or you could ask on the dovecot list.


Eric

On 3/29/2022 2:53 AM, ChandranManikandan wrote:

Hi Friends,

Anyone having the same issue, some users' email clients 
(Outlook,Thunderbird) have not synced any emails in Inbox since morning.

I tried to repair it myself but received the same message
Is it server side issue or email client side issue.
I removed that email account and re-configure it but received the 
same message.

I would Appreciate anyone who could help me.

On Tue, Mar 29, 2022 at 1:59 PM ChandranManikandan 
 wrote:


Hi Friends,

Some few email accounts are sync issue come in
outlook,thunderbird,roundcube and squirrelmail after power
shutdown suddenly.
The dovecot mail log is showing below for those email accounts.
can anyone help me to fix it.


imap(em...@xxx.com)<19758>: Error: Mailbox
INBOX: UID=502283:

read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,
)
failed: Cached message size larger than expected (13720 > 0,
box=INBOX, UID=502283) (read reason=mail stream)
Mar 29 13:40:48 imap(em...@xxx.com)<19758>:
Error: Corrupted record in index cache file
/home/vpopmail/domains/xxx.com/email/Maildir/dovecot.index.cache
:  Broken
physical size in mailbox INBOX:

read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,
)
failed: Cached message size larger than expected (13720 > 0,
box=INBOX, UID=502283)
Mar 29 13:40:48 imap(em...@xxx.com)<19758>:
Error: Mailbox INBOX: UID=502283:

read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570..mail.xxx.com,S=13720:2,

)
failed: Cached message size larger than expected (13720 > 0,
box=INBOX, UID=502283) (read reason=)
Mar 29 13:40:48 imap(em...@xxx.com)<19758>:
Info: FETCH failed: Internal error occurred. Refer to server log
for more information. [2022-03-29 13:40:48] in=323 out=589163
deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0
body_count=0 body_bytes=0


-- 
*/Regards,

Manikandan.C
/*



--
*/Regards,
Manikandan.C
/*

Re: [qmailtoaster] Re: Email account sync issue in email clients

[Mani Kandan]

Hi Eric, 
I have rename the index.cache file and restarted dovecot but still the same 
sync issue while try from thunderbird or outlook, not download any email after 
that. But in squirrelmail and round cube webmail can see the new emails except 
that particular mail page.

I have checked dovecot list, they said to use the below command for resyncing 
but still not fixed.
doveadm force-resync -A or doveadm force-resync -A “*”

Can I try to found this particular mail 
home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,)
  and remove or move from cur folder.
Can you advise on this

Sent from my iPhone

> On 29 Mar 2022, at 9:30 PM, Eric Broch  wrote:
> 
> 
> It's most likely a server side issue, specifically the dovecot.index.cache? 
> file records a different size than the message name with S='size'. You could 
> delete the cache file and see if it repairs itself or you could ask on the 
> dovecot list.
> 
> Eric
> 
> On 3/29/2022 2:53 AM, ChandranManikandan wrote:
>> Hi Friends,
>> 
>> Anyone having the same issue, some users' email clients 
>> (Outlook,Thunderbird) have not synced any emails in Inbox since morning.
>> I tried to repair it myself but received the same message
>> Is it server side issue or email client side issue.
>> I removed that email account and re-configure it but received the same 
>> message.
>> I would Appreciate anyone who could help me.
>> 
>> On Tue, Mar 29, 2022 at 1:59 PM ChandranManikandan  wrote:
>>> Hi Friends,
>>> 
>>> Some few email accounts are sync issue come in 
>>> outlook,thunderbird,roundcube and squirrelmail after power shutdown 
>>> suddenly.
>>> The dovecot mail log is showing below for those email accounts.
>>> can anyone help me to fix it.
>>> 
>>> 
>>> imap(em...@xxx.com)<19758>: Error: Mailbox INBOX: 
>>> UID=502283: 
>>> read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,)
>>>  failed: Cached message size larger than expected (13720 > 0, box=INBOX, 
>>> UID=502283) (read reason=mail stream)
>>> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Error: 
>>> Corrupted record in index cache file 
>>> /home/vpopmail/domains/xxx.com/email/Maildir/dovecot.index.cache:  Broken 
>>> physical size in mailbox INBOX: 
>>> read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,)
>>>  failed: Cached message size larger than expected (13720 > 0, box=INBOX, 
>>> UID=502283)
>>> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Error: 
>>> Mailbox INBOX: UID=502283: 
>>> read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570..mail.xxx.com,S=13720:2,)
>>>  failed: Cached message size larger than expected (13720 > 0, box=INBOX, 
>>> UID=502283) (read reason=)
>>> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Info: FETCH 
>>> failed: Internal error occurred. Refer to server log for more information. 
>>> [2022-03-29 13:40:48] in=323 out=589163 deleted=0 expunged=0 trashed=0 
>>> hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
>>> 
>>> 
>>> -- 
>>> Regards,
>>> Manikandan.C
>> 
>> 
>> -- 
>> Regards,
>> Manikandan.C

Re: [qmailtoaster] Re: Email account sync issue in email clients

[Eric Broch]

It's most likely a server side issue, specifically the 
dovecot.index.cache? file records a different size than the message name 
with S='size'. You could delete the cache file and see if it repairs 
itself or you could ask on the dovecot list.


Eric

On 3/29/2022 2:53 AM, ChandranManikandan wrote:

Hi Friends,

Anyone having the same issue, some users' email clients 
(Outlook,Thunderbird) have not synced any emails in Inbox since morning.

I tried to repair it myself but received the same message
Is it server side issue or email client side issue.
I removed that email account and re-configure it but received the same 
message.

I would Appreciate anyone who could help me.

On Tue, Mar 29, 2022 at 1:59 PM ChandranManikandan  
wrote:


Hi Friends,

Some few email accounts are sync issue come in
outlook,thunderbird,roundcube and squirrelmail after power
shutdown suddenly.
The dovecot mail log is showing below for those email accounts.
can anyone help me to fix it.


imap(em...@xxx.com)<19758>: Error: Mailbox
INBOX: UID=502283:

read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,
)
failed: Cached message size larger than expected (13720 > 0,
box=INBOX, UID=502283) (read reason=mail stream)
Mar 29 13:40:48 imap(em...@xxx.com)<19758>:
Error: Corrupted record in index cache file
/home/vpopmail/domains/xxx.com/email/Maildir/dovecot.index.cache
:  Broken
physical size in mailbox INBOX:

read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,
)
failed: Cached message size larger than expected (13720 > 0,
box=INBOX, UID=502283)
Mar 29 13:40:48 imap(em...@xxx.com)<19758>:
Error: Mailbox INBOX: UID=502283:

read(/home/vpopmail/domains/xxx.com/email/Maildir/cur/1648520174.28570..mail.xxx.com,S=13720:2,

)
failed: Cached message size larger than expected (13720 > 0,
box=INBOX, UID=502283) (read reason=)
Mar 29 13:40:48 imap(em...@xxx.com)<19758>:
Info: FETCH failed: Internal error occurred. Refer to server log
for more information. [2022-03-29 13:40:48] in=323 out=589163
deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0
body_count=0 body_bytes=0


-- 
*/Regards,

Manikandan.C
/*



--
*/Regards,
Manikandan.C
/*

[qmailtoaster] Re: Email account sync issue in email clients

[ChandranManikandan]

Hi Friends,

Anyone having the same issue, some users' email clients
(Outlook,Thunderbird) have not synced any emails in Inbox since morning.
I tried to repair it myself but received the same message
Is it server side issue or email client side issue.
I removed that email account and re-configure it but received the same
message.
I would Appreciate anyone who could help me.

On Tue, Mar 29, 2022 at 1:59 PM ChandranManikandan 
wrote:

> Hi Friends,
>
> Some few email accounts are sync issue come in
> outlook,thunderbird,roundcube and squirrelmail after power shutdown
> suddenly.
> The dovecot mail log is showing below for those email accounts.
> can anyone help me to fix it.
>
>
> imap(em...@xxx.com)<19758>: Error: Mailbox INBOX:
> UID=502283: read(/home/vpopmail/domains/
> xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,)
> failed: Cached message size larger than expected (13720 > 0, box=INBOX,
> UID=502283) (read reason=mail stream)
> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Error:
> Corrupted record in index cache file /home/vpopmail/domains/
> xxx.com/email/Maildir/dovecot.index.cache:  Broken physical size in
> mailbox INBOX: read(/home/vpopmail/domains/
> xxx.com/email/Maildir/cur/1648520174.28570.mail.xxx.com,S=13720:2,)
> failed: Cached message size larger than expected (13720 > 0, box=INBOX,
> UID=502283)
> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Error:
> Mailbox INBOX: UID=502283: read(/home/vpopmail/domains/
> xxx.com/email/Maildir/cur/1648520174.28570..mail.xxx.com,S=13720:2,)
> failed: Cached message size larger than expected (13720 > 0, box=INBOX,
> UID=502283) (read reason=)
> Mar 29 13:40:48 imap(em...@xxx.com)<19758>: Info: FETCH
> failed: Internal error occurred. Refer to server log for more information.
> [2022-03-29 13:40:48] in=323 out=589163 deleted=0 expunged=0 trashed=0
> hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
>
>
> --
>
>
> *Regards,Manikandan.C*
>


-- 


*Regards,Manikandan.C*

Re: [qmailtoaster] Re: Setup quota for large-scale email accounts

[ChandranManikandan]

Hi Eric,

I have done as you advised and it's working fine now.

I tried the following procedure.
Check the mailbox usage

cd /home/vpopmail/domains/domain.com
du -h user
/home/vpopmail/bin/vmoduser -q 69793218560  us...@domain.com


On Thu, Mar 10, 2022 at 9:27 PM Eric Broch  wrote:

> Convert GB to Bytes
>
> 65GB = 69793218560 bytes
>
> /home/vpopmail/bin/vmoduser -q 69793218560  us...@domain.com
>
> echo "select pw_shell  from domain_com where pw_name='user1'" | mysql -u
> root -p vpopmail
>
> pw_shell
> 69793218560S
>
> 55GB = 59055800320 bytes
>
> /home/vpopmail/bin/vmoduser -q 59055800320  us...@domain.com
>
> echo "select pw_shell  from domain_com where pw_name='user2'" | mysql -u
> root -p vpopmail
>
> pw_shell
> 59055800320S
>
>
>
> On 3/9/2022 11:26 PM, ChandranManikandan wrote:
>
> Hi Friends,
>
> Could anyone help me,
> how to check the NOQUOTA mailbox size and how to setup quota for the
> mailbox quota (MB or GB)
>
>
> On Wed, Mar 9, 2022 at 4:35 PM ChandranManikandan 
> wrote:
>
>> Hi Folks,
>>
>> I've run two large-scale email accounts with NOQUOTA, how to apply for
>> the reservation of these email accounts without affecting the existing
>> emails through qmailadmin or commands.
>> one email account is more than 60 GB and another one is more than 50 GB.
>> I want to restrict these accounts not crossing 65 and 55 GB.
>>
>> Note: I am running in COS 7 with QMT
>> Appreciate anyone who supports me.
>>
>> --
>>
>>
>> *Regards, Manikandan.C *
>>
>
>
> --
>
>
> *Regards, Manikandan.C *
>
>

-- 


*Regards,Manikandan.C*

[qmailtoaster] Re: Increasing local delivery

[Eric Broch]

https://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg43593.html

On 3/9/2022 10:42 PM, Tahnan Al Anas wrote:

Hi Eric,

May be I have reported this before, How can I increase local delivery 
queue for local delivery, I have found concurrency remote fle increase 
outgoing delivery but local delivery remain 10/10.


status: local 10/10 remote 0/60


--
--

Best Regards
Muhammad Tahnan Al Anas

Re: [qmailtoaster] Re: Setup quota for large-scale email accounts

[Eric Broch]

Convert GB to Bytes

65GB = 69793218560 bytes

/home/vpopmail/bin/vmoduser -q 69793218560 us...@domain.com

echo "select pw_shell  from domain_com where pw_name='user1'" | mysql -u 
root -p vpopmail


pw_shell
69793218560S

55GB = 59055800320 bytes

/home/vpopmail/bin/vmoduser -q 59055800320 us...@domain.com

echo "select pw_shell  from domain_com where pw_name='user2'" | mysql -u 
root -p vpopmail


pw_shell
59055800320S



On 3/9/2022 11:26 PM, ChandranManikandan wrote:

Hi Friends,

Could anyone help me,
how to check the NOQUOTA mailbox size and how to setup quota for the 
mailbox quota (MB or GB)



On Wed, Mar 9, 2022 at 4:35 PM ChandranManikandan  
wrote:


Hi Folks,

I've run two large-scale email accounts with NOQUOTA, how to apply
for the reservation of these email accounts without affecting the
existing emails through qmailadmin or commands.
one email account is more than 60 GB and another one is more than
50 GB.
I want to restrict these accounts not crossing 65 and 55 GB.

Note: I am running in COS 7 with QMT
Appreciate anyone who supports me.

-- 
*/Regards,

Manikandan.C
/*



--
*/Regards,
Manikandan.C
/*

Re: [qmailtoaster] Re: Setup quota for large-scale email accounts

[Tahnan Al Anas]

I think you can set quota from qmailadmin


--
--

Best Regards
Muhammad Tahnan Al Anas


On Thu, Mar 10, 2022 at 12:27 PM ChandranManikandan 
wrote:

> Hi Friends,
>
> Could anyone help me,
> how to check the NOQUOTA mailbox size and how to setup quota for the
> mailbox quota (MB or GB)
>
>
> On Wed, Mar 9, 2022 at 4:35 PM ChandranManikandan 
> wrote:
>
>> Hi Folks,
>>
>> I've run two large-scale email accounts with NOQUOTA, how to apply for
>> the reservation of these email accounts without affecting the existing
>> emails through qmailadmin or commands.
>> one email account is more than 60 GB and another one is more than 50 GB.
>> I want to restrict these accounts not crossing 65 and 55 GB.
>>
>> Note: I am running in COS 7 with QMT
>> Appreciate anyone who supports me.
>>
>> --
>>
>>
>> *Regards,Manikandan.C*
>>
>
>
> --
>
>
> *Regards,Manikandan.C*
>

[qmailtoaster] Re: Setup quota for large-scale email accounts

[ChandranManikandan]

Hi Friends,

Could anyone help me,
how to check the NOQUOTA mailbox size and how to setup quota for the
mailbox quota (MB or GB)


On Wed, Mar 9, 2022 at 4:35 PM ChandranManikandan  wrote:

> Hi Folks,
>
> I've run two large-scale email accounts with NOQUOTA, how to apply for the
> reservation of these email accounts without affecting the existing emails
> through qmailadmin or commands.
> one email account is more than 60 GB and another one is more than 50 GB.
> I want to restrict these accounts not crossing 65 and 55 GB.
>
> Note: I am running in COS 7 with QMT
> Appreciate anyone who supports me.
>
> --
>
>
> *Regards,Manikandan.C*
>


-- 


*Regards,Manikandan.C*

Re: [qmailtoaster] Re: EZMLM list management issues

[Eric Broch]

Same as mine

On 3/3/2022 4:43 PM, Chris wrote:

[root@mail ~]# rpm -qa |grep ezmlm
ezmlm-0.53.324-0.qt.el7.x86_64
ezmlm-cgi-0.53.324-0.qt.el7.x86_64

On Fri, Mar 4, 2022 at 5:30 AM Eric Broch  wrote:

Sorry, it is actually working on mine from the command line. I was
using
.org instead of .com mailing list.

What version of ezmlm are you using?

# rpm -qa |grep ezmlm

On 3/3/2022 8:25 AM, Eric Broch wrote:
> I removed a subscriber through the qmailadmin interface, but
couldn't
> at the command line.
>
> On 3/3/2022 3:36 AM, qmailtoas...@dukat.dk wrote:
>> I was hoping that Apache/qmailadmin would have given a clue
when you
>> hit the trash.
>>
>> Are there illegal chars in the mailaddress?
>>
>> cd ~vpopmail/domains///subscribers
>> strings * | cat -vte
>>
>> Regards,
>>
>> Allan
>>
>> On 2022-03-03 01:44, Boheme wrote:
>>> But I can’t unsubscribe using the CLI tools, and there is no
error
>>> output.
>>>
>>> -Sent from my Pip-Boy 3000
>>>
 On 3/03/2022, at 1:40 AM, qmailtoas...@dukat.dk wrote:

 Hi Chris

 Have you looked carefully for relevant information in web
servers
 log files?

 - Allan

> On 2022-03-02 10:01, Chris Knight wrote:
> I’m still having ezmlm issues.  I can’t delete users from
the command
> line, from qmailadmin, or via email commands.  Permissions
on all
> files in the list directory are vpopmail:vchkpw
> Has anyone else encountered this?
> -Chris
>>> On Feb 6, 2022, at 7:45 AM, Chris Knight
 wrote:
>> I’ve got a toaster that has been running fine for a long
while.
>> One of my friends who I host email for reported that they are
>> unable to unsubscribe someone from a mailing list they run.  I
>> logged in, and tried to manually use the ezmlm-unsub
command, and
>> yet the email address refuses to be removed from the mailing
>> list. I’ve checked permission in the [list]/subscribers/
>> directory, and all files are owned by vpopmail:vchkpw
>> Has anyone else had problems with list management?
>> My package version is ezmlm-0.53.324-0.qt.el7.x86_64
>> -Chris
>>
>>
>>
-
>> To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
>>
>
>
-
> To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
>

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: EZMLM list management issues

[Chris]

[root@mail ~]# rpm -qa |grep ezmlm
ezmlm-0.53.324-0.qt.el7.x86_64
ezmlm-cgi-0.53.324-0.qt.el7.x86_64

On Fri, Mar 4, 2022 at 5:30 AM Eric Broch  wrote:

> Sorry, it is actually working on mine from the command line. I was using
> .org instead of .com mailing list.
>
> What version of ezmlm are you using?
>
> # rpm -qa |grep ezmlm
>
> On 3/3/2022 8:25 AM, Eric Broch wrote:
> > I removed a subscriber through the qmailadmin interface, but couldn't
> > at the command line.
> >
> > On 3/3/2022 3:36 AM, qmailtoas...@dukat.dk wrote:
> >> I was hoping that Apache/qmailadmin would have given a clue when you
> >> hit the trash.
> >>
> >> Are there illegal chars in the mailaddress?
> >>
> >> cd ~vpopmail/domains///subscribers
> >> strings * | cat -vte
> >>
> >> Regards,
> >>
> >> Allan
> >>
> >> On 2022-03-03 01:44, Boheme wrote:
> >>> But I can’t unsubscribe using the CLI tools, and there is no error
> >>> output.
> >>>
> >>> -Sent from my Pip-Boy 3000
> >>>
>  On 3/03/2022, at 1:40 AM, qmailtoas...@dukat.dk wrote:
> 
>  Hi Chris
> 
>  Have you looked carefully for relevant information in web servers
>  log files?
> 
>  - Allan
> 
> > On 2022-03-02 10:01, Chris Knight wrote:
> > I’m still having ezmlm issues.  I can’t delete users from the command
> > line, from qmailadmin, or via email commands.  Permissions on all
> > files in the list directory are vpopmail:vchkpw
> > Has anyone else encountered this?
> > -Chris
> >>> On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:
> >> I’ve got a toaster that has been running fine for a long while.
> >> One of my friends who I host email for reported that they are
> >> unable to unsubscribe someone from a mailing list they run.  I
> >> logged in, and tried to manually use the ezmlm-unsub command, and
> >> yet the email address refuses to be removed from the mailing
> >> list. I’ve checked permission in the [list]/subscribers/
> >> directory, and all files are owned by vpopmail:vchkpw
> >> Has anyone else had problems with list management?
> >> My package version is ezmlm-0.53.324-0.qt.el7.x86_64
> >> -Chris
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> >> For additional commands, e-mail:
> qmailtoaster-list-h...@qmailtoaster.com
> >>
> >
> > -
> > To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> > For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> >
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>

Re: [qmailtoaster] Re: EZMLM list management issues

[Chris]

I think I found the problem.  Maybe.

Last night I created a new list, and then I added and removed subscribers
via the web interface and the command line (fixing the directory/file
ownership after using the CLI as root) and I had no issues.

I suspect the issue is that all of the lists in question are old, and were
migrated via rsync from an older toaster.  I suspect there is an
incompatibility between the way the subscribers were stored with an older
version of ezmlm vs the version I am running now.  I plan to work with one
of my friends, who owns several of the broken lists in question, to delete
and re-create them.  They'll lose any archived messages, but from my
testing it seems the user lists will become manageable again.

-Chris

On Fri, Mar 4, 2022 at 5:30 AM Eric Broch  wrote:

> Sorry, it is actually working on mine from the command line. I was using
> .org instead of .com mailing list.
>
> What version of ezmlm are you using?
>
> # rpm -qa |grep ezmlm
>
> On 3/3/2022 8:25 AM, Eric Broch wrote:
> > I removed a subscriber through the qmailadmin interface, but couldn't
> > at the command line.
> >
> > On 3/3/2022 3:36 AM, qmailtoas...@dukat.dk wrote:
> >> I was hoping that Apache/qmailadmin would have given a clue when you
> >> hit the trash.
> >>
> >> Are there illegal chars in the mailaddress?
> >>
> >> cd ~vpopmail/domains///subscribers
> >> strings * | cat -vte
> >>
> >> Regards,
> >>
> >> Allan
> >>
> >> On 2022-03-03 01:44, Boheme wrote:
> >>> But I can’t unsubscribe using the CLI tools, and there is no error
> >>> output.
> >>>
> >>> -Sent from my Pip-Boy 3000
> >>>
>  On 3/03/2022, at 1:40 AM, qmailtoas...@dukat.dk wrote:
> 
>  Hi Chris
> 
>  Have you looked carefully for relevant information in web servers
>  log files?
> 
>  - Allan
> 
> > On 2022-03-02 10:01, Chris Knight wrote:
> > I’m still having ezmlm issues.  I can’t delete users from the command
> > line, from qmailadmin, or via email commands.  Permissions on all
> > files in the list directory are vpopmail:vchkpw
> > Has anyone else encountered this?
> > -Chris
> >>> On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:
> >> I’ve got a toaster that has been running fine for a long while.
> >> One of my friends who I host email for reported that they are
> >> unable to unsubscribe someone from a mailing list they run.  I
> >> logged in, and tried to manually use the ezmlm-unsub command, and
> >> yet the email address refuses to be removed from the mailing
> >> list. I’ve checked permission in the [list]/subscribers/
> >> directory, and all files are owned by vpopmail:vchkpw
> >> Has anyone else had problems with list management?
> >> My package version is ezmlm-0.53.324-0.qt.el7.x86_64
> >> -Chris
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> >> For additional commands, e-mail:
> qmailtoaster-list-h...@qmailtoaster.com
> >>
> >
> > -
> > To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> > For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> >
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>

Re: [qmailtoaster] Re: EZMLM list management issues

[Eric Broch]

Sorry, it is actually working on mine from the command line. I was using 
.org instead of .com mailing list.


What version of ezmlm are you using?

# rpm -qa |grep ezmlm

On 3/3/2022 8:25 AM, Eric Broch wrote:
I removed a subscriber through the qmailadmin interface, but couldn't 
at the command line.


On 3/3/2022 3:36 AM, qmailtoas...@dukat.dk wrote:
I was hoping that Apache/qmailadmin would have given a clue when you 
hit the trash.


Are there illegal chars in the mailaddress?

cd ~vpopmail/domains///subscribers
strings * | cat -vte

Regards,

Allan

On 2022-03-03 01:44, Boheme wrote:
But I can’t unsubscribe using the CLI tools, and there is no error 
output.


-Sent from my Pip-Boy 3000


On 3/03/2022, at 1:40 AM, qmailtoas...@dukat.dk wrote:

Hi Chris

Have you looked carefully for relevant information in web servers 
log files?


- Allan


On 2022-03-02 10:01, Chris Knight wrote:
I’m still having ezmlm issues.  I can’t delete users from the command
line, from qmailadmin, or via email commands.  Permissions on all
files in the list directory are vpopmail:vchkpw
Has anyone else encountered this?
-Chris

On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:
I’ve got a toaster that has been running fine for a long while.  
One of my friends who I host email for reported that they are 
unable to unsubscribe someone from a mailing list they run.  I 
logged in, and tried to manually use the ezmlm-unsub command, and 
yet the email address refuses to be removed from the mailing 
list. I’ve checked permission in the [list]/subscribers/ 
directory, and all files are owned by vpopmail:vchkpw

Has anyone else had problems with list management?
My package version is ezmlm-0.53.324-0.qt.el7.x86_64
-Chris



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: EZMLM list management issues

[Eric Broch]

I removed a subscriber through the qmailadmin interface, but couldn't at 
the command line.


On 3/3/2022 3:36 AM, qmailtoas...@dukat.dk wrote:
I was hoping that Apache/qmailadmin would have given a clue when you 
hit the trash.


Are there illegal chars in the mailaddress?

cd ~vpopmail/domains///subscribers
strings * | cat -vte

Regards,

Allan

On 2022-03-03 01:44, Boheme wrote:
But I can’t unsubscribe using the CLI tools, and there is no error 
output.


-Sent from my Pip-Boy 3000


On 3/03/2022, at 1:40 AM, qmailtoas...@dukat.dk wrote:

Hi Chris

Have you looked carefully for relevant information in web servers 
log files?


- Allan


On 2022-03-02 10:01, Chris Knight wrote:
I’m still having ezmlm issues.  I can’t delete users from the command
line, from qmailadmin, or via email commands.  Permissions on all
files in the list directory are vpopmail:vchkpw
Has anyone else encountered this?
-Chris

On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:
I’ve got a toaster that has been running fine for a long while.  
One of my friends who I host email for reported that they are 
unable to unsubscribe someone from a mailing list they run.  I 
logged in, and tried to manually use the ezmlm-unsub command, and 
yet the email address refuses to be removed from the mailing 
list.  I’ve checked permission in the [list]/subscribers/ 
directory, and all files are owned by vpopmail:vchkpw

Has anyone else had problems with list management?
My package version is ezmlm-0.53.324-0.qt.el7.x86_64
-Chris



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: EZMLM list management issues

[qmailtoaster]

I was hoping that Apache/qmailadmin would have given a clue when you hit 
the trash.


Are there illegal chars in the mailaddress?

cd ~vpopmail/domains///subscribers
strings * | cat -vte

Regards,

Allan

On 2022-03-03 01:44, Boheme wrote:
But I can’t unsubscribe using the CLI tools, and there is no error 
output.


-Sent from my Pip-Boy 3000


On 3/03/2022, at 1:40 AM, qmailtoas...@dukat.dk wrote:

Hi Chris

Have you looked carefully for relevant information in web servers log 
files?


- Allan


On 2022-03-02 10:01, Chris Knight wrote:
I’m still having ezmlm issues.  I can’t delete users from the command
line, from qmailadmin, or via email commands.  Permissions on all
files in the list directory are vpopmail:vchkpw
Has anyone else encountered this?
-Chris

On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:
I’ve got a toaster that has been running fine for a long while.  One 
of my friends who I host email for reported that they are unable to 
unsubscribe someone from a mailing list they run.  I logged in, and 
tried to manually use the ezmlm-unsub command, and yet the email 
address refuses to be removed from the mailing list.  I’ve checked 
permission in the [list]/subscribers/ directory, and all files are 
owned by vpopmail:vchkpw

Has anyone else had problems with list management?
My package version is ezmlm-0.53.324-0.qt.el7.x86_64
-Chris



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: EZMLM list management issues

[Boheme]

But I can’t unsubscribe using the CLI tools, and there is no error output. 

-Sent from my Pip-Boy 3000

> On 3/03/2022, at 1:40 AM, qmailtoas...@dukat.dk wrote:
> 
> Hi Chris
> 
> Have you looked carefully for relevant information in web servers log files?
> 
> - Allan
> 
>> On 2022-03-02 10:01, Chris Knight wrote:
>> I’m still having ezmlm issues.  I can’t delete users from the command
>> line, from qmailadmin, or via email commands.  Permissions on all
>> files in the list directory are vpopmail:vchkpw
>> Has anyone else encountered this?
>> -Chris
 On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:
>>> I’ve got a toaster that has been running fine for a long while.  One of my 
>>> friends who I host email for reported that they are unable to unsubscribe 
>>> someone from a mailing list they run.  I logged in, and tried to manually 
>>> use the ezmlm-unsub command, and yet the email address refuses to be 
>>> removed from the mailing list.  I’ve checked permission in the 
>>> [list]/subscribers/ directory, and all files are owned by vpopmail:vchkpw
>>> Has anyone else had problems with list management?
>>> My package version is ezmlm-0.53.324-0.qt.el7.x86_64
>>> -Chris
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: EZMLM list management issues

[qmailtoaster]

Hi Chris

Have you looked carefully for relevant information in web servers log 
files?


- Allan

On 2022-03-02 10:01, Chris Knight wrote:

I’m still having ezmlm issues.  I can’t delete users from the command
line, from qmailadmin, or via email commands.  Permissions on all
files in the list directory are vpopmail:vchkpw

Has anyone else encountered this?

-Chris


On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:

I’ve got a toaster that has been running fine for a long while.  One 
of my friends who I host email for reported that they are unable to 
unsubscribe someone from a mailing list they run.  I logged in, and 
tried to manually use the ezmlm-unsub command, and yet the email 
address refuses to be removed from the mailing list.  I’ve checked 
permission in the [list]/subscribers/ directory, and all files are 
owned by vpopmail:vchkpw


Has anyone else had problems with list management?

My package version is ezmlm-0.53.324-0.qt.el7.x86_64

-Chris



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Re: EZMLM list management issues

[Chris Knight]

I’m still having ezmlm issues.  I can’t delete users from the command line, 
from qmailadmin, or via email commands.  Permissions on all files in the list 
directory are vpopmail:vchkpw

Has anyone else encountered this?

-Chris

> On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:
> 
> I’ve got a toaster that has been running fine for a long while.  One of my 
> friends who I host email for reported that they are unable to unsubscribe 
> someone from a mailing list they run.  I logged in, and tried to manually use 
> the ezmlm-unsub command, and yet the email address refuses to be removed from 
> the mailing list.  I’ve checked permission in the [list]/subscribers/ 
> directory, and all files are owned by vpopmail:vchkpw
> 
> Has anyone else had problems with list management?
> 
> My package version is ezmlm-0.53.324-0.qt.el7.x86_64
> 
> -Chris


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Error on greeting

[Andreas Galatis]

Hi Eric,

they told me they couldn't delist my IP because on the website unet.de 
was no legal information of the owner.


They need:
1. Servername indicating purpose of the server (mail.unet.de should be ok)
2. ip-address resolving to servername (ptr-record = mail.unet.de)
3. legal  info about owner (fixed)

and then it takes time to get it on the whitelist.
The address to contact them is: postmas...@rx.t-online.de

I did the same for microsoft (outlook...)



Am 07.02.22 um 15:16 schrieb Eric Broch:

Did you contact rx.t-online.de ? I'd be interested in what they say.

On 2/7/2022 12:29 AM, Andreas Galatis wrote:

Hi,

when sending out mails to t-online I get the following message:

Connected to 194.25.134.8 but greeting failed.
Remote host said: 554 IP=85.10.201.91 - A problem occurred. (Ask your 
postmaster for help or to contactt...@rx.t-online.de  to clarify.)


Does anybody have an idea?

Andreas



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com





OpenPGP_signature
Description: OpenPGP digital signature

[qmailtoaster] Re: Error on greeting

[Eric Broch]

Did you contact rx.t-online.de ? I'd be interested in what they say.

On 2/7/2022 12:29 AM, Andreas Galatis wrote:

Hi,

when sending out mails to t-online I get the following message:

Connected to 194.25.134.8 but greeting failed.
Remote host said: 554 IP=85.10.201.91 - A problem occurred. (Ask your 
postmaster for help or to contactt...@rx.t-online.de  to clarify.)


Does anybody have an idea?

Andreas



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Re: Login with alias

[Eric Broch]

I'll take a look.

On 2/6/2022 3:07 PM, Andreas Galatis wrote:

Hi,

I just migrated from an old Qmailtoaster to
qmail-1.03-3.3.5.qt.md.el8.x86_64

I have clients login in with alis domainnames or users. It worked 
always but with the new toaster stopped working

Is there a way to reenable login with aliasdomains or alias accounts?


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Re: Redirection of Links on qmailtoaster.com

[Eric Broch]

what are you typing in your browser and/or what links are you clicking on?

On 2/1/2022 1:45 AM, Andreas Galatis wrote:

Hello,

when trying to get infos on qmailtoaster.com I get redirected from 
https://www.qmailtoaster.com/apache.html to 
https://albertchubakpolitician.ca/apache.html.


This server is not resolvable and I doubt is not the server with the 
correct documents.


Iodok


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Re: Best Config for new server

[Eric Broch]

I'd personally go with Springdale and ECC.

On 1/20/2022 4:06 AM, Andreas Galatis wrote:

Hi all,

I use the qmail-toaster since many years and are very glad with it. 
The system is very stable, secure and configurable with the features 
we need.


I need to install a new Server for qmail and migrate the installation 
from CentOS7.


What is the preferred OS, (Rocky or Springdale)

Is there a big advantage of ECC-Ram (with XEON) over Standard Ram 
(with Core7)?


Thanks in advance

Iodok



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: how to use ssl for individual domain

[xaf]

Remo a écrit le 25/10/2021 à 05:52 :
> Well smtp on port 25 is not dovecot that’s what I was looking for. 

Dovecot act as MSA or SMTP relay, Qmail is the MTA.
You can put anything in the relay port, but Qmail must listen to it.
Using port 25 simplifies local conf.

xaf



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: how to use ssl for individual domain

[xaf]

Remo a écrit le 23/10/2021 à 22:33 :
> I would be interested too but I see postfix and not qmail Eric do you happen 
> to have the steps for qmail? 

As Eric says, it's Dovecot specific.
My notes in attachment.

xaf



#  #
#Dovecot SSL certificates per domain + MSA #
#  #


Let's Encrypt SAN certificate per domain, imap.* pop3.* smtp.* with acme.sh
(to adapt for other scripts).

One file per domain, easier for bash scripting.

mkdir /etc/dovecot/domaincerts/

/etc/dovecot/domaincerts/example.org.conf
local_name imap.example.org {
ssl_cert = https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/

issue 1 - per domain / per IP conflict

Dovecot log
imap-login: Fatal: Error reading configuration
config: Error: Conflict in setting ssl_cert found

issue 2 - Outlook workarounds

remove digest-md5 mechanism
https://www.google.com/search?gl=us&hl=en&gws_rd=cr&q=digest-md5+outlook

submission_client_workarounds = whitespace-before-path
Dovecot log
command MAIL: 501 reply: Sent: 501 5.5.4 Invalid FROM: Unexpected whitespace 
before path

Dovecot TLS SNI Client Support

https://wiki.dovecot.org/SSL/SNIClientSupport (quite old)


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: how to use ssl for individual domain

[Remo]

Well smtp on port 25 is not dovecot that’s what I was looking for. 

> Il giorno 24 ott 2021, alle ore 20:40, xaf  ha scritto:
> 
> Remo a écrit le 23/10/2021 à 22:33 :
>> I would be interested too but I see postfix and not qmail Eric do you happen 
>> to have the steps for qmail? 
> 
> As Eric says, it's Dovecot specific.
> My notes in attachment.
> 
> xaf
> 


#  #
#Dovecot SSL certificates per domain + MSA #
#  #


Let's Encrypt SAN certificate per domain, imap.* pop3.* smtp.* with acme.sh
(to adapt for other scripts).

One file per domain, easier for bash scripting.

mkdir /etc/dovecot/domaincerts/

/etc/dovecot/domaincerts/example.org.conf
local_name imap.example.org {
ssl_cert = https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/

issue 1 - per domain / per IP conflict

Dovecot log
imap-login: Fatal: Error reading configuration
config: Error: Conflict in setting ssl_cert found

issue 2 - Outlook workarounds

remove digest-md5 mechanism
https://www.google.com/search?gl=us&hl=en&gws_rd=cr&q=digest-md5+outlook

submission_client_workarounds = whitespace-before-path
Dovecot log
command MAIL: 501 reply: Sent: 501 5.5.4 Invalid FROM: Unexpected whitespace 
before path

Dovecot TLS SNI Client Support

https://wiki.dovecot.org/SSL/SNIClientSupport (quite old)


> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: how to use ssl for individual domain

[Eric Broch]

The question (I think) was for dovecot.

Qmail cannot do this...yet

On 10/23/2021 2:33 PM, Remo wrote:
I would be interested too but I see postfix and not qmail Eric do you 
happen to have the steps for qmail?


Thanks

Il giorno 23 ott 2021, alle ore 08:49, Eric Broch 
 ha scritto:




https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/

https://serverfault.com/questions/920436/set-up-certs-for-multiple-domains-in-postfix-and-dovecot

On 10/22/2021 11:52 PM, Tahnan Al Anas wrote:

Hello All,

Anyone using ssl on dovecot for individual domain? For example, 
Iamusing server's hostname ssl for all domain currently, but some of 
my user do not want to use server hostname at their outlook, rather 
they want to use their domain name as incoming outgoing. When they 
do that, they get error as domain name do not match with 
certificate's domain. I tried below settings but it not working as 
email client software try to use first one.


ssl_cert = ssl_cert = 
ssl_key = 



--
--

Best Regards
Muhammad Tahnan Al Anas

Re: [qmailtoaster] Re: how to use ssl for individual domain

[Remo]

I would be interested too but I see postfix and not qmail Eric do you happen to 
have the steps for qmail? 

Thanks 

> Il giorno 23 ott 2021, alle ore 08:49, Eric Broch  
> ha scritto:
> 
> 
> https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/
> 
> https://serverfault.com/questions/920436/set-up-certs-for-multiple-domains-in-postfix-and-dovecot
> 
> On 10/22/2021 11:52 PM, Tahnan Al Anas wrote:
>> Hello All,
>> 
>> Anyone using ssl on dovecot for individual domain? For example, Iamusing 
>> server's hostname ssl for all domain currently, but some of my user do not 
>> want to use server hostname at their outlook, rather they want to use their 
>> domain name as incoming outgoing. When they do that, they get error as 
>> domain name do not match with certificate's domain. I tried below settings 
>> but it not working as email client software try to use first one.
>> 
>> ssl_cert = > ssl_key = > 
>> 
>> ssl_cert = > ssl_key = > 
>> 
>> --
>> --
>> 
>> Best Regards
>> Muhammad Tahnan Al Anas

[qmailtoaster] Re: how to use ssl for individual domain

[Eric Broch]

https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/

https://serverfault.com/questions/920436/set-up-certs-for-multiple-domains-in-postfix-and-dovecot

On 10/22/2021 11:52 PM, Tahnan Al Anas wrote:

Hello All,

Anyone using ssl on dovecot for individual domain? For example, 
Iamusing server's hostname ssl for all domain currently, but some of 
my user do not want to use server hostname at their outlook, rather 
they want to use their domain name as incoming outgoing. When they do 
that, they get error as domain name do not match with certificate's 
domain. I tried below settings but it not working as email 
client software try to use first one.


ssl_cert = ssl_cert = 
ssl_key = 



--
--

Best Regards
Muhammad Tahnan Al Anas

Re: [qmailtoaster] Re: Qmail local delivery limit

[Tahnan Al Anas]

Xaf, this worked! Thank you so much.


--
--

Best Regards
Muhammad Tahnan Al Anas


On Tue, Sep 7, 2021 at 6:35 PM Eric Broch  wrote:

> Thanks, xaf, that worked...not sure where concurrencyincoming came from.
>
> On 9/7/2021 1:30 AM, xaf wrote:
> > Tahnan Al Anas a écrit le 07/09/2021 à 05:09 :
> >> I did increased concorencyincoming to 100 then rebooted the server but
> still local is not getting increased. it stays 10/10
> > concurrencyincoming limits incoming SMTP sessions (qmail-smtpd logs).
> > concurrencylocal limits simultaneous local deliveries (qmail-send logs).
> >
> > /var/qmail/bin/qmail-showctl | grep concurrency
> > concurrencylocal: (Default.) Local concurrency is 10.
> >
> > echo "100" >/var/qmail/control/concurrencylocal
> > chmod 644 /var/qmail/control/concurrencylocal
> > chown root:qmail /var/qmail/control/concurrencylocal
> >
> > restart qmail
> >
> > /var/qmail/bin/qmail-showctl | grep concurrency
> > concurrencylocal: Local concurrency is 100.
> >
> > check qmail-send logs.
> >
> > xaf
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> > For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> >
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>

Re: [qmailtoaster] Re: Qmail local delivery limit

[Eric Broch]

Thanks, xaf, that worked...not sure where concurrencyincoming came from.

On 9/7/2021 1:30 AM, xaf wrote:

Tahnan Al Anas a écrit le 07/09/2021 à 05:09 :

I did increased concorencyincoming to 100 then rebooted the server but still 
local is not getting increased. it stays 10/10

concurrencyincoming limits incoming SMTP sessions (qmail-smtpd logs).
concurrencylocal limits simultaneous local deliveries (qmail-send logs).

/var/qmail/bin/qmail-showctl | grep concurrency
concurrencylocal: (Default.) Local concurrency is 10.

echo "100" >/var/qmail/control/concurrencylocal
chmod 644 /var/qmail/control/concurrencylocal
chown root:qmail /var/qmail/control/concurrencylocal

restart qmail

/var/qmail/bin/qmail-showctl | grep concurrency
concurrencylocal: Local concurrency is 100.

check qmail-send logs.

xaf





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Qmail local delivery limit

[xaf]

Tahnan Al Anas a écrit le 07/09/2021 à 05:09 :
> I did increased concorencyincoming to 100 then rebooted the server but still 
> local is not getting increased. it stays 10/10

concurrencyincoming limits incoming SMTP sessions (qmail-smtpd logs).
concurrencylocal limits simultaneous local deliveries (qmail-send logs).

/var/qmail/bin/qmail-showctl | grep concurrency
concurrencylocal: (Default.) Local concurrency is 10.

echo "100" >/var/qmail/control/concurrencylocal
chmod 644 /var/qmail/control/concurrencylocal
chown root:qmail /var/qmail/control/concurrencylocal

restart qmail

/var/qmail/bin/qmail-showctl | grep concurrency
concurrencylocal: Local concurrency is 100.

check qmail-send logs.

xaf





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Qmail local delivery limit

[Qmail]

Hi.

Just a guess..

I recall an issue (many many years ago) with the CHKUSER limit's in 
TCP.SMTP that they could not exceed 200 ? maybe they default to 10 ?

(mine are 50 and 10)

/Finn



Den 07-09-2021 kl. 07:26 skrev Tahnan Al Anas:
I have checked there too before posting, tcp.smtp is set as below: still 
hacing limit of 10


:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="5000",CHKUSER_WRONGRCPTLIMIT="5000",NOP0FCHECK="1",QMAILQUEUE="/var/qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-queue.orig",DKVERIFY="DEGIJKfh",DKSIGN="/var/qmail/control/domainkeys/%/private"


--
--

Best Regards
Muhammad Tahnan Al Anas


On Tue, Sep 7, 2021 at 9:12 AM Remo Mattei > wrote:


It’s on the chkuser limit.  You need to check your tcpsmtp file.
Default is 10. I am not in front of my computer but I share it later.


Il giorno 6 set 2021, alle ore 20:10, Tahnan Al Anas
mailto:tah...@gmail.com>> ha scritto:


Hi Ericm,

I did increased concorencyincoming to 100 then rebooted the server
but still local is not getting increased. it stays 10/10


--
--

Best Regards
Muhammad Tahnan Al Anas


On Sat, Sep 4, 2021 at 4:18 PM Eric Broch mailto:ebr...@whitehorsetc.com>> wrote:

/var/qmail/control/concurrencyincoming

On 9/4/2021 12:41 AM, Tahnan Al Anas wrote:

Dear Eriq,

Can you please share which file we can edit to increase local
delivery limit? I have foundlocal delivery limit isset to
"status: local 0/10 remote 0/509"

How can I increase it to 100 instead of 10


--
--

Best Regards
Muhammad Tahnan Al Anas




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Qmail local delivery limit

[Tahnan Al Anas]

I have checked there too before posting, tcp.smtp is set as below: still
hacing limit of 10

:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="5000",CHKUSER_WRONGRCPTLIMIT="5000",NOP0FCHECK="1",QMAILQUEUE="/var/qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-queue.orig",DKVERIFY="DEGIJKfh",DKSIGN="/var/qmail/control/domainkeys/%/private"


--
--

Best Regards
Muhammad Tahnan Al Anas


On Tue, Sep 7, 2021 at 9:12 AM Remo Mattei  wrote:

> It’s on the chkuser limit.  You need to check your tcpsmtp file. Default
> is 10. I am not in front of my computer but I share it later.
>
> Il giorno 6 set 2021, alle ore 20:10, Tahnan Al Anas 
> ha scritto:
>
> 
> Hi Ericm,
>
> I did increased concorencyincoming to 100 then rebooted the server but
> still local is not getting increased. it stays 10/10
>
>
> --
> --
>
> Best Regards
> Muhammad Tahnan Al Anas
>
>
> On Sat, Sep 4, 2021 at 4:18 PM Eric Broch  wrote:
>
>> /var/qmail/control/concurrencyincoming
>> On 9/4/2021 12:41 AM, Tahnan Al Anas wrote:
>>
>> Dear Eriq,
>>
>> Can you please share which file we can edit to increase local delivery
>> limit? I have foundlocal delivery limit isset to "status: local 0/10 remote
>> 0/509"
>>
>> How can I increase it to 100 instead of 10
>>
>>
>> --
>> --
>>
>> Best Regards
>> Muhammad Tahnan Al Anas
>>
>>

Re: [qmailtoaster] Re: Qmail local delivery limit

[Remo Mattei]

It’s on the chkuser limit.  You need to check your tcpsmtp file. Default is 10. 
I am not in front of my computer but I share it later. 

> Il giorno 6 set 2021, alle ore 20:10, Tahnan Al Anas  ha 
> scritto:
> 
> 
> Hi Ericm, 
> 
> I did increased concorencyincoming to 100 then rebooted the server but still 
> local is not getting increased. it stays 10/10
> 
> 
> --
> --
> 
> Best Regards
> Muhammad Tahnan Al Anas
> 
> 
>> On Sat, Sep 4, 2021 at 4:18 PM Eric Broch  wrote:
>> /var/qmail/control/concurrencyincoming
>> 
>> On 9/4/2021 12:41 AM, Tahnan Al Anas wrote:
>>> Dear Eriq,
>>> 
>>> Can you please share which file we can edit to increase local delivery 
>>> limit? I have foundlocal delivery limit isset to "status: local 0/10 remote 
>>> 0/509" 
>>> 
>>> How can I increase it to 100 instead of 10
>>> 
>>> 
>>> --
>>> --
>>> 
>>> Best Regards
>>> Muhammad Tahnan Al Anas

[qmailtoaster] Re: Qmail local delivery limit

[Tahnan Al Anas]

Hi Ericm,

I did increased concorencyincoming to 100 then rebooted the server but
still local is not getting increased. it stays 10/10


--
--

Best Regards
Muhammad Tahnan Al Anas


On Sat, Sep 4, 2021 at 4:18 PM Eric Broch  wrote:

> /var/qmail/control/concurrencyincoming
> On 9/4/2021 12:41 AM, Tahnan Al Anas wrote:
>
> Dear Eriq,
>
> Can you please share which file we can edit to increase local delivery
> limit? I have foundlocal delivery limit isset to "status: local 0/10 remote
> 0/509"
>
> How can I increase it to 100 instead of 10
>
>
> --
> --
>
> Best Regards
> Muhammad Tahnan Al Anas
>
>

[qmailtoaster] Re: Qmail local delivery limit

[Eric Broch]

/var/qmail/control/concurrencyincoming

On 9/4/2021 12:41 AM, Tahnan Al Anas wrote:

Dear Eriq,

Can you please share which file we can edit to increase local delivery 
limit? I have foundlocal delivery limit isset to "status: local 0/10 
remote 0/509"


How can I increase it to 100 instead of 10


--
--

Best Regards
Muhammad Tahnan Al Anas

Re: [qmailtoaster] Re: QM7 - Issues connecting with Outlook for Android

[Jeff Koch]

Hi Eric - just added auth_debug=yes to the end of 
/etc/dovecot/toaster.conf. The dovecot log is showing auth: Debug


Let me know when you test - thanks - Jeff




On 9/3/2021 10:25 AM, Eric Broch wrote:


When you get advanced logging for dovecot done let me know I'll test 
again.


Here are my settings for squirrelmail in 
/etc/squirrelmail/config_local.php


# imap server options
$imapServerAddress  = 'localhost';
$imap_server_type   = 'dovecot';
# SM doesn't support starttls until v1.5.1, so we'll use digest-md5 
til then

$imap_auth_mech = 'login';

On 9/2/2021 5:47 PM, Eric Broch wrote:

You can change squirrelmail config
On Sep 2, 2021, at 5:11 PM, Jeff Koch > wrote:


Hi Eric - tried removing digest-md5 and cram-md5. Found out
squirrelmail webmail won't work unless digest-md5 is in the
auth_mechanisms

Jeff

On 9/2/2021 10:31 AM, Eric Broch wrote:


both have

auth_mechanisms = plain login

On 9/2/2021 8:29 AM, Eric Broch wrote:


I have a 2 QMT 7 servers and they both work with
dovecot-2.3.11.3-12.qt.el7.x86_64


On 9/2/2021 7:55 AM, Jeff Koch wrote:

Hi Eric:

We'll try doing that but is this a problem with only our
mailserver or all QMT 7 mailservers?

Jeff

On 9/2/2021 9:44 AM, Eric Broch wrote:


Next to the check when entering the settings there is a
question mark circled to the left. Clicking that gives a menu
with 'Collect Diagnostics' & 'Contact Support'

On 9/2/2021 7:42 AM, Eric Broch wrote:


When the popup indicates a connection issue I push 'support'
button and error suggests a certificate issue. Two options
appear at this point: 'Talk to Agent' & 'OK'. If you 'talk
to an agent' you can do more advanced troublshooting like
sending an Outlook error log file to them. You might try this.

Eric

On 9/2/2021 7:11 AM, Jeff Koch wrote:

I could be wrong but I think Outlook for Android must be
very sensitive to the encryption ciphers being used and the
SSL/TLS versions. We use Let's Encrypt certificates - I
wonder if it's anything to do with that.

Jeff

On 9/2/2021 1:16 AM, Remo Mattei wrote:

I just found out to have the same issue from one of my
client.


Il giorno 2 set 2021, alle ore 02:49, Eric Broch
 ha scritto:



Try this script (replace with relevant user, password, &
host) from the command line of the server. It will yield
what version of TLS you're running.



#!/bin/bash

function imapscript () {
echo "a login $1 $2"
echo 'a logout'
sleep 1
echo 'quit'
}

user=some...@mydomain.com
pass=***
host=mail.mydomain.com

imapscript "$user" $pass  | openssl s_client -crlf
-connect $host:993



On 9/1/2021 6:29 PM, Eric Broch wrote:

Does your web mail work?
On Sep 1, 2021, at 5:12 PM, Jeff Koch <
jeffk...@intersessions.com
> wrote:

Neither IMAP or IMAPS will connect - Jeff

On 9/1/2021 6:16 PM, Eric Broch wrote:


What protocol, IMAP, IMAPS, SMTPS...?

On 9/1/2021 2:36 PM, Jeff Koch wrote:


We have a customer trying to connect to his
qmail-toaster email account using the MicroSoft
Outlook app on an Android phone. He keeps getting
bounced off with the message 'can't connect to
server' or 'can't login'.  I did some research on
the MS forums and apparently this Outlook app only
connects with SSL (no STARTTLS) and TLS 1.2 or
higher.  If the mailserver tries anything else
first the connection is dropped.

Is there any known work-around or configuration
adjustment needed to get this Android Outlook app
to work with the toaster.

We're running qmail-1.03-2.2.qt.cdb.el7.x86_64.rpm

Thanks, Jeff

Re: [qmailtoaster] Re: QM7 - Issues connecting with Outlook for Android

[Eric Broch]

When you get advanced logging for dovecot done let me know I'll test again.

Here are my settings for squirrelmail in /etc/squirrelmail/config_local.php

# imap server options
$imapServerAddress  = 'localhost';
$imap_server_type   = 'dovecot';
# SM doesn't support starttls until v1.5.1, so we'll use digest-md5 til then
$imap_auth_mech = 'login';

On 9/2/2021 5:47 PM, Eric Broch wrote:

You can change squirrelmail config
On Sep 2, 2021, at 5:11 PM, Jeff Koch > wrote:


Hi Eric - tried removing digest-md5 and cram-md5. Found out
squirrelmail webmail won't work unless digest-md5 is in the
auth_mechanisms

Jeff

On 9/2/2021 10:31 AM, Eric Broch wrote:


both have

auth_mechanisms = plain login

On 9/2/2021 8:29 AM, Eric Broch wrote:


I have a 2 QMT 7 servers and they both work with
dovecot-2.3.11.3-12.qt.el7.x86_64


On 9/2/2021 7:55 AM, Jeff Koch wrote:

Hi Eric:

We'll try doing that but is this a problem with only our
mailserver or all QMT 7 mailservers?

Jeff

On 9/2/2021 9:44 AM, Eric Broch wrote:


Next to the check when entering the settings there is a
question mark circled to the left. Clicking that gives a menu
with 'Collect Diagnostics' & 'Contact Support'

On 9/2/2021 7:42 AM, Eric Broch wrote:


When the popup indicates a connection issue I push 'support'
button and error suggests a certificate issue. Two options
appear at this point: 'Talk to Agent' & 'OK'. If you 'talk to
an agent' you can do more advanced troublshooting like
sending an Outlook error log file to them. You might try this.

Eric

On 9/2/2021 7:11 AM, Jeff Koch wrote:

I could be wrong but I think Outlook for Android must be
very sensitive to the encryption ciphers being used and the
SSL/TLS versions. We use Let's Encrypt certificates - I
wonder if it's anything to do with that.

Jeff

On 9/2/2021 1:16 AM, Remo Mattei wrote:

I just found out to have the same issue from one of my client.


Il giorno 2 set 2021, alle ore 02:49, Eric Broch
 ha scritto:



Try this script (replace with relevant user, password, &
host) from the command line of the server. It will yield
what version of TLS you're running.



#!/bin/bash

function imapscript () {
echo "a login $1 $2"
echo 'a logout'
sleep 1
echo 'quit'
}

user=some...@mydomain.com
pass=***
host=mail.mydomain.com

imapscript "$user" $pass  | openssl s_client -crlf
-connect $host:993



On 9/1/2021 6:29 PM, Eric Broch wrote:

Does your web mail work?
On Sep 1, 2021, at 5:12 PM, Jeff Koch <
jeffk...@intersessions.com
> wrote:

Neither IMAP or IMAPS will connect - Jeff

On 9/1/2021 6:16 PM, Eric Broch wrote:


What protocol, IMAP, IMAPS, SMTPS...?

On 9/1/2021 2:36 PM, Jeff Koch wrote:


We have a customer trying to connect to his
qmail-toaster email account using the MicroSoft
Outlook app on an Android phone. He keeps getting
bounced off with the message 'can't connect to
server' or 'can't login'.  I did some research on
the MS forums and apparently this Outlook app only
connects with SSL (no STARTTLS) and TLS 1.2 or
higher.  If the mailserver tries anything else
first the connection is dropped.

Is there any known work-around or configuration
adjustment needed to get this Android Outlook app
to work with the toaster.

We're running qmail-1.03-2.2.qt.cdb.el7.x86_64.rpm

Thanks, Jeff