Re: [qmailtoaster] qmail upgrade

[Eric Broch]

If you have no send and receive issues I'd leave it alone.


On 1/31/2018 11:25 PM, Chandran Manikandan wrote:

Hi Eric,

Am currently using COS 6 with domainkeys and tcp file like 
that QMAILQUEUE="/var/qmail/bin/simscan"


There is no issue for send and receive.

Do i need to use to update of your above email steps?



On Thu, Feb 1, 2018 at 1:43 PM, Eric Broch > wrote:


Hello list,

If anyone has upgraded qmail lately, especially those of you who
DO NOT use domainkeys and those who DO use dkim, remember that an
upgrade overwrites the qmail binaries (/var/qmail/bin). This could
affect domainkeys, which you really shouldn't use anymore IMHO,
and DKIM signing.

1) Domainkeys: If you DON'T use domainkeys and you've upgrade you
might have to unlink qmail-queue from qmail-dk and link (ln -s) it
to qmail-queue.orig. Another approach is to simply change
QMAILQUEUE in /etc/tcprules.d/tcp.smtp (below).

QMAILQUEUE="/var/qmail/bin/qmail-queue.orig"


2) DKIM: On upgrade the perl script 'qmail-remote' which calls
'qmail-remote.orig', will be overwritten...run the following commands

#   wget -O /var/qmail/bin/qmail-remote
https://raw.githubusercontent.com/qmtoaster/dkim/master/qmail-remote


# chown root:qmail /var/qmail/bin/qmail-remote

# chmod 777 /var/qmail/bin/qmail-remote

Sorry about the inconvenience.

Comments and suggestions please!

-- 
Eric Broch

White Horse Technical Consulting (WHTC)


-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

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





--
*Thanks,*
*Manikandan.C*
*System Administrator*


--
Eric Broch
White Horse Technical Consulting (WHTC)

Re: [qmailtoaster] qmail upgrade

[Gary Bowling]

  
  
I moved from a CentOS-5 box to a CentOS-7 box last year, so I did
  a full migration/upgrade. It works, but I just want to make sure I
  did things the right way. 



In my /etc/tcprules.d/tcp.smtp file I have
  QMAILQUEUE="/var/qmail/bin/simscan"
I do NOT use domainkeys or DKIM and still have my qmail-queue
  -> /var/qmail/bin/qmail-dk


Maybe I had a problem with that link and muddled around and
  changed it to "simscan" but I don't remember. 



Here are some versions on my machine. 



qmt-release-1-4.qt.el7.noarch
  qmt-plus-1-0.qt.el7.noarch
  qmailmrtg-4.2-3.qt.el7.x86_64
  qmailadmin-1.2.16-2.qt.el7.x86_64
  qmail-1.03-2.1.qt.el7.x86_64


systemd service:    clamav-daemon.service:   [  OK  ]
  systemd service: clamav-daemon.socket:   [  OK  ]
  systemd service: clamav-freshclam:   [  OK  ]
  systemd service:    spamd:   [  OK  ]
  systemd service:  dovecot:   [  OK  ]
  systemd service:  mariadb:   [  OK  ]
  systemd service:    httpd:   [  OK  ]
  systemd service: ntpd:   [  OK  ]
  systemd service: sshd:   [  OK  ]
  systemd service:  network:   [  OK  ]
  systemd service:    crond:   [  OK  ]
  systemd service:    acpid:   [  OK  ]
  systemd service:  atd:   [  OK  ]
  systemd service:   autofs:   [  OK  ]
  systemd service:   smartd:   [  OK  ]
  systemd service:   irqbalance:   [  OK  ]
  



Please advise as to the right way to do this. 



Thanks, Gary 

On 2/1/2018 12:43 AM, Eric Broch wrote:

Hello
  list,
  
  
  If anyone has upgraded qmail lately, especially those of you who
  DO NOT use domainkeys and those who DO use dkim, remember that an
  upgrade overwrites the qmail binaries (/var/qmail/bin). This could
  affect domainkeys, which you really shouldn't use anymore IMHO,
  and DKIM signing.
  
  
  1) Domainkeys: If you DON'T use domainkeys and you've upgrade you
  might have to unlink qmail-queue from qmail-dk and link (ln -s) it
  to qmail-queue.orig. Another approach is to simply change
  QMAILQUEUE in /etc/tcprules.d/tcp.smtp (below).
  
  
  QMAILQUEUE="/var/qmail/bin/qmail-queue.orig"
  
  
  
  2) DKIM: On upgrade the perl script 'qmail-remote' which calls
  'qmail-remote.orig', will be overwritten...run the following
  commands
  
  
  #   wget -O /var/qmail/bin/qmail-remote
  https://raw.githubusercontent.com/qmtoaster/dkim/master/qmail-remote
  
  
  # chown root:qmail /var/qmail/bin/qmail-remote
  
  
  # chmod 777 /var/qmail/bin/qmail-remote
  
  
  Sorry about the inconvenience.
  
  
  Comments and suggestions please!
  
  


  


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

Re: [qmailtoaster] qmail upgrade

[Havrla]

Hello

I have 6 server with QT.
All work well. However, I had to turn off DK on one.

The server sometimes had an email for multiple recipients had a problem.

"qmail-dk: Cannot sign message due to invalid message syntax. (#5.3.0)"

I do not know where the problem is, I do not care.

Version package:
[root@mail ~]# rpm -qa  | grep qt
maildrop-2.9.1-2.qt.el7.x86_64
dovecot-2.2.29.1-19.qt.el7.x86_64
libsrs2-1.0.18-0.qt.el7.x86_64
vpopmail-5.4.33-1.qt.el7.x86_64
control-panel-0.5.1-1.qt.el7.x86_64
squirrelmail-1.4.22-1.qt.el7.x86_64
ezmlm-cgi-0.53.324-0.qt.el7.x86_64
qmailmrtg-4.2-3.qt.el7.x86_64
clamav-0.99.3-2.qt.el7.x86_64
qmt-release-1-4.qt.el7.noarch
mailman-2.1.12-20.qt.el7.x86_64
mailman-debuginfo-2.1.12-20.qt.el7.x86_64
qmail-1.03-2.1.qt.el7.x86_64
qmailadmin-1.2.16-2.qt.el7.x86_64
libsrs2-devel-1.0.18-0.qt.el7.x86_64
daemontools-0.76-0.qt.el7.x86_64
autorespond-2.0.5-0.qt.el7.x86_64
vqadmin-2.3.7-1.qt.el7.x86_64
ezmlm-0.53.324-0.qt.el7.x86_64
maildrop-devel-2.9.1-2.qt.el7.x86_64
spamdyke-5.0.1-0.qt.el7.x86_64
ucspi-tcp-0.88-0.qt.el7.x86_64
ripmime-1.4.0.10-0.qt.el7.x86_64
spamassassin-3.4.1-1.qt.el7.x86_64
simscan-1.4.0-1.qt.el7.x86_64
isoqlog-2.2.1-2.qt.el7.x86_64
[root@mail ~]#


Havrla



Dne 1.2.2018 v 10:33 Remo Mattei napsal(a):
I just tested mine yum upgrade no new pkg and sent an email out it 
works ok.


Inviato da iPhone

Il giorno 01 feb 2018, alle ore 07:25, Chandran Manikandan 
mailto:tech2m...@gmail.com>> ha scritto:



Hi Eric,

Am currently using COS 6 with domainkeys and tcp file like 
that QMAILQUEUE="/var/qmail/bin/simscan"


There is no issue for send and receive.

Do i need to use to update of your above email steps?



On Thu, Feb 1, 2018 at 1:43 PM, Eric Broch > wrote:


Hello list,

If anyone has upgraded qmail lately, especially those of you who
DO NOT use domainkeys and those who DO use dkim, remember that an
upgrade overwrites the qmail binaries (/var/qmail/bin). This
could affect domainkeys, which you really shouldn't use anymore
IMHO, and DKIM signing.

1) Domainkeys: If you DON'T use domainkeys and you've upgrade you
might have to unlink qmail-queue from qmail-dk and link (ln -s)
it to qmail-queue.orig. Another approach is to simply change
QMAILQUEUE in /etc/tcprules.d/tcp.smtp (below).

QMAILQUEUE="/var/qmail/bin/qmail-queue.orig"


2) DKIM: On upgrade the perl script 'qmail-remote' which calls
'qmail-remote.orig', will be overwritten...run the following commands

#   wget -O /var/qmail/bin/qmail-remote
https://raw.githubusercontent.com/qmtoaster/dkim/master/qmail-remote


# chown root:qmail /var/qmail/bin/qmail-remote

# chmod 777 /var/qmail/bin/qmail-remote

Sorry about the inconvenience.

Comments and suggestions please!

-- 
Eric Broch

White Horse Technical Consulting (WHTC)


-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

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





--
*Thanks,*
*Manikandan.C*
*System Administrator*

Re: [qmailtoaster] qmail upgrade

[Remo Mattei]

I just tested mine yum upgrade no new pkg and sent an email out it works ok. 

Inviato da iPhone

> Il giorno 01 feb 2018, alle ore 07:25, Chandran Manikandan 
>  ha scritto:
> 
> Hi Eric,
> 
> Am currently using COS 6 with domainkeys and tcp file like that 
> QMAILQUEUE="/var/qmail/bin/simscan"
> 
> There is no issue for send and receive.
> 
> Do i need to use to update of your above email steps?
> 
> 
> 
>> On Thu, Feb 1, 2018 at 1:43 PM, Eric Broch  wrote:
>> Hello list,
>> 
>> If anyone has upgraded qmail lately, especially those of you who DO NOT use 
>> domainkeys and those who DO use dkim, remember that an upgrade overwrites 
>> the qmail binaries (/var/qmail/bin). This could affect domainkeys, which you 
>> really shouldn't use anymore IMHO, and DKIM signing.
>> 
>> 1) Domainkeys: If you DON'T use domainkeys and you've upgrade you might have 
>> to unlink qmail-queue from qmail-dk and link (ln -s) it to qmail-queue.orig. 
>> Another approach is to simply change QMAILQUEUE in /etc/tcprules.d/tcp.smtp 
>> (below).
>> 
>> QMAILQUEUE="/var/qmail/bin/qmail-queue.orig"
>> 
>> 
>> 2) DKIM: On upgrade the perl script 'qmail-remote' which calls 
>> 'qmail-remote.orig', will be overwritten...run the following commands
>> 
>> #   wget -O /var/qmail/bin/qmail-remote 
>> https://raw.githubusercontent.com/qmtoaster/dkim/master/qmail-remote
>> 
>> # chown root:qmail /var/qmail/bin/qmail-remote
>> 
>> # chmod 777 /var/qmail/bin/qmail-remote
>> 
>> Sorry about the inconvenience.
>> 
>> Comments and suggestions please!
>> 
>> -- 
>> Eric Broch
>> White Horse Technical Consulting (WHTC)
>> 
>> 
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>> 
> 
> 
> 
> -- 
> Thanks,
> Manikandan.C
> System Administrator

Re: [qmailtoaster] qmail upgrade

[Chandran Manikandan]

Hi Eric,

Am currently using COS 6 with domainkeys and tcp file like
that QMAILQUEUE="/var/qmail/bin/simscan"

There is no issue for send and receive.

Do i need to use to update of your above email steps?



On Thu, Feb 1, 2018 at 1:43 PM, Eric Broch  wrote:

> Hello list,
>
> If anyone has upgraded qmail lately, especially those of you who DO NOT
> use domainkeys and those who DO use dkim, remember that an upgrade
> overwrites the qmail binaries (/var/qmail/bin). This could affect
> domainkeys, which you really shouldn't use anymore IMHO, and DKIM signing.
>
> 1) Domainkeys: If you DON'T use domainkeys and you've upgrade you might
> have to unlink qmail-queue from qmail-dk and link (ln -s) it to
> qmail-queue.orig. Another approach is to simply change QMAILQUEUE in
> /etc/tcprules.d/tcp.smtp (below).
>
> QMAILQUEUE="/var/qmail/bin/qmail-queue.orig"
>
>
> 2) DKIM: On upgrade the perl script 'qmail-remote' which calls
> 'qmail-remote.orig', will be overwritten...run the following commands
>
> #   wget -O /var/qmail/bin/qmail-remote https://raw.githubusercontent.
> com/qmtoaster/dkim/master/qmail-remote
>
> # chown root:qmail /var/qmail/bin/qmail-remote
>
> # chmod 777 /var/qmail/bin/qmail-remote
>
> Sorry about the inconvenience.
>
> Comments and suggestions please!
>
> --
> Eric Broch
> White Horse Technical Consulting (WHTC)
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>


-- 
*Thanks,*
*Manikandan.C*
*System Administrator*

[qmailtoaster] qmail upgrade

[Eric Broch]

Hello list,

If anyone has upgraded qmail lately, especially those of you who DO NOT 
use domainkeys and those who DO use dkim, remember that an upgrade 
overwrites the qmail binaries (/var/qmail/bin). This could affect 
domainkeys, which you really shouldn't use anymore IMHO, and DKIM signing.


1) Domainkeys: If you DON'T use domainkeys and you've upgrade you might 
have to unlink qmail-queue from qmail-dk and link (ln -s) it to 
qmail-queue.orig. Another approach is to simply change QMAILQUEUE in 
/etc/tcprules.d/tcp.smtp (below).


QMAILQUEUE="/var/qmail/bin/qmail-queue.orig"


2) DKIM: On upgrade the perl script 'qmail-remote' which calls 
'qmail-remote.orig', will be overwritten...run the following commands


#   wget -O /var/qmail/bin/qmail-remote 
https://raw.githubusercontent.com/qmtoaster/dkim/master/qmail-remote


# chown root:qmail /var/qmail/bin/qmail-remote

# chmod 777 /var/qmail/bin/qmail-remote

Sorry about the inconvenience.

Comments and suggestions please!

--
Eric Broch
White Horse Technical Consulting (WHTC)


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

Re: [qmailtoaster] qmail upgrade

[PakOgah]

from http://wiki.qmailtoaster.com/index.php/CentOS_4.4_QmailToaster_Install

   * note: the new SpamAssasin also required newer perl-module which
 may not satisfy by just running the script above. so here easy way
 to updates perl modules. Visit
 http://dag.wieers.com/rpm/packages/rpmforge-release/ and make sure
 you choose the latest, and correct version for your distro and
 architecture.

# rpm -ivh 
http://dag.wieers.com/rpm/packages/rpmforge-release/rpmforge-release-0.3.6-1.el4.rf.i386.rpm
# yum install perl-HTML-Parser
# yum install perl-IO-Zlib
# yum install perl-Archive-Tar

If SpamAssassin required other perl module (say: Mail::SPF) you can 
easily type


# yum install perl-Mail-SPF

Failing to satisfy perl module needed by SpamAssassin, SpamAssassin not 
installed and also broke Simscan and ClamAV installation


sami's strat wrote:


I recently started a new job and was tasked to upgrade an instance of 
gmail toaster on centos 4.6.  Needless to say I had a few problems.  
The new-model script stated the upgrade wouldn't work hinting out O/S 
would require an upgrade.  Yet I am not able to upgrade the O/S on the 
mail server at this time.


[EMAIL PROTECTED] ~]$ uname -a
Linux qmail 2.6.9-67.0.15.ELsmp #1 SMP Thu May 8 10:52:19 EDT 2008 
i686 athlon i386 GNU/Linux

[EMAIL PROTECTED] ~]$ more /etc/redhat-release
CentOS release 4.6 (Final)

The qmail rpm's we're running are as follows:

[EMAIL PROTECTED] ~]$ rpm -qa | grep -i qmail
qmail-pop3d-toaster-1.03-1.3.15
qmailmrtg-toaster-4.2-1.3.3
qmail-toaster-1.03-1.3.15
qmailadmin-toaster-1.2.11-1.3.4
qmailtoaster-plus-0.3.0-1.4.0
qmailtoaster-plus.repo-0.1-1
[EMAIL PROTECTED] ~]$

Problem is when we select new-model upgrade script from the qtp-menu, 
it complains that HTML parser is out of date.



REQUIRED module out of date: HTML::Parser
optional module missing: Mail::SPF
optional module missing: Mail::SPF::Query
optional module missing: IP::Country
optional module missing: Razor2
optional module missing: Net::Ident
optional module missing: IO::Socket::INET6
optional module missing: IO::Socket::SSL
optional module missing: Mail::DKIM
optional module missing: Encode::Detect

Yet, the html parser is the latest we have available for the version 
of the O/S we are running on.


[EMAIL PROTECTED] ~]# rpm -qa | grep -i perl-HTML-Parser
perl-HTML-Parser-3.35-6

There are newer RPM's out there but is downloading a newer 
perl-HTML-Parser going to allow us to successfully upgrade? I don't 
want to down a path that may require a complete server restore if I 
can avoid it.


Please advice, thanks in advance!!

 




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] qmail upgrade

[sami's strat]

I recently started a new job and was tasked to upgrade an instance of gmail
toaster on centos 4.6.  Needless to say I had a few problems.  The new-model
script stated the upgrade wouldn't work hinting out O/S would require an
upgrade.  Yet I am not able to upgrade the O/S on the mail server at this
time.

[EMAIL PROTECTED] ~]$ uname -a
Linux qmail 2.6.9-67.0.15.ELsmp #1 SMP Thu May 8 10:52:19 EDT 2008 i686
athlon i386 GNU/Linux
[EMAIL PROTECTED] ~]$ more /etc/redhat-release
CentOS release 4.6 (Final)

The qmail rpm's we're running are as follows:

[EMAIL PROTECTED] ~]$ rpm -qa | grep -i qmail
qmail-pop3d-toaster-1.03-1.3.15
qmailmrtg-toaster-4.2-1.3.3
qmail-toaster-1.03-1.3.15
qmailadmin-toaster-1.2.11-1.3.4
qmailtoaster-plus-0.3.0-1.4.0
qmailtoaster-plus.repo-0.1-1
[EMAIL PROTECTED] ~]$

Problem is when we select new-model upgrade script from the qtp-menu, it
complains that HTML parser is out of date.


REQUIRED module out of date: HTML::Parser
optional module missing: Mail::SPF
optional module missing: Mail::SPF::Query
optional module missing: IP::Country
optional module missing: Razor2
optional module missing: Net::Ident
optional module missing: IO::Socket::INET6
optional module missing: IO::Socket::SSL
optional module missing: Mail::DKIM
optional module missing: Encode::Detect

Yet, the html parser is the latest we have available for the version of the
O/S we are running on.

[EMAIL PROTECTED] ~]# rpm -qa | grep -i perl-HTML-Parser
perl-HTML-Parser-3.35-6

There are newer RPM's out there but is downloading a newer perl-HTML-Parser
going to allow us to successfully upgrade? I don't want to down a path that
may require a complete server restore if I can avoid it.

Please advice, thanks in advance!!

Re: [qmailtoaster] qmail upgrade to qmail plus

[Jake Vickers]

Jim Shupert, Jr. wrote:

and would qmail plus be an aternative to
Jake's QMail Stuff  Toaster Upgrade Script http://v2gnu.com/qmail/
 
That's a really old script. It was used as the base for the new upgrade 
scripts, and I just keep it around for history purposes. Matter of fact, 
the whole v2gnu.com/qmail site is around for history purposes. The 
current things being worked on are in the download section of v2gnu.com.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qmailtoaster] qmail upgrade to qmail plus

[Eric \"Shubes\"]

Jim Shupert, Jr. wrote:
> 
> - Original Message - From: "Eric "Shubes"" <[EMAIL PROTECTED]>
> To: 
> Sent: Wednesday, March 07, 2007 3:46 PM
> Subject: Re: [qmailtoaster] qmail upgrade to qmail plus
> 
> 
>> Jim Shupert, Jr. wrote:
>>> Friends,
>>>
>>> i have been reading about qmail-plus   (
>>> http://qtp.qmailtoaster.com/wiki  )
>>> would the upgrade be as easy as the 1,2,3 that is seen at the website?
>>> ( I think i have vers 1.05 )
>>
>> The upgrade is only that easy if you're upgrading from a previous
>> *qmail-toaster* version. And then, you might have some manual
>> migration of
>> domains/accounts to do if the toaster was very old (1.2 versions or
>> previous).
>>
>>> would updating to qmail-plus be an alternative to a manual update
>>> such as:
>>>
>>> *To update manually*, you must remove libdomainkeys,
>>> control-panel-toaster and spamassassin-toaster with "rpm -e --nodeps"
>>> just prior to updating to ensure a clean build on all the packages. So,
>>> remove these three packages and use the install script for your distro
>>> found in the "Utilities" section above".
>>
>> The qtp-newmodel script takes care of this for you.
>>
>>> You will also find a file named "qmailmrtg-upgrade-fix.sh in your
>>> support directory. The new version of qmailmrtg-toaster fixes the web
>>> file location so the mrtg info displays properly on all distros. After
>>> an update to the current version, qmailmrtg-upgrade-fix.sh will move
>>> your historical mrtg files to the new location for you.
>>
>> qtp-newmodel takes care of this too.
>>
>>> and would qmail plus be an aternative to
>>> Jake's QMail Stuff  Toaster Upgrade Script http://v2gnu.com/qmail/
>>
>> That's an older script, which was used as the starting point for writing
>> qtp-newmodel. Other scripts from Jakes site such as backup, restore, and
>> qmail-spam are included in the qmailtoaster-plus package.
>>
>>> 
>>> Here is my bottom line: I have installed qmail and I have it working ( i
>>> think my version is netQmail 1.05 )
>>> and before put the company on it - I would like to see if I can update
>>> it , update the anti - Spam & Virus parts.
>>
>> Since you're starting with a non-toaster implementation of qmail (if I'm
>> reading you right), you'll be essentially building a new toaster and
>> migrating off of your existing server to the toaster. I don't think
>> I'd try
>> upgrading an existing netQmail server that is in production.
>>
>>> I have not done something like this before - I admire the work and
>>> expertise that has gone into it's creation.
>>
>> Thanks. We're here to help.
>>
>> I'd consider building a server from scratch, then migrating over your
>> domain(s) and users.
>>
>> How many domains/users are you talking about?
>>
>> You don't need much of a computer to run the toaster for a home/small
>> office. An old PII-266 or so with 160M+ of ram would do nicely. HDD
>> should
>> be several Gigs, 10 or so would be comfortable (depending on your IMAP
>> requirements). You can bring an old desktop computer out of
>> retirement, and
>> it'd work well as a toaster.
>>
>> Don't hesitate to ask any questions you might have.
> 
> jim respond:
> 
> maybe I mislead you  I do have qmailToaster
> I installed it from the instructions known as
> EZ QmailToaster Fresh Install on CentOS 4.3
> Nick Hemmesch <[EMAIL PROTECTED]> June 08, 2006
> 
> and since I do  have qmail toaster I can do the qmail-plus upgrade
> (   http://qtp.qmailtoaster.com/wiki  )
> and the upgrade be as easy as the 1,2,3 that is seen at the website?
> 

You should be just fine then using qmailtoaster-plus. Many have used it
successfully since nearly as long ago as you installed your toaster.

Be sure to let us know if you have any difficulty with it so we might make
improvements. We like to hear of successes too. ;)

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] qmail upgrade to qmail plus

[Jim Shupert, Jr.]

- Original Message - 
From: "Eric "Shubes"" <[EMAIL PROTECTED]>

To: 
Sent: Wednesday, March 07, 2007 3:46 PM
Subject: Re: [qmailtoaster] qmail upgrade to qmail plus



Jim Shupert, Jr. wrote:

Friends,

i have been reading about qmail-plus   (
http://qtp.qmailtoaster.com/wiki  )
would the upgrade be as easy as the 1,2,3 that is seen at the website?
( I think i have vers 1.05 )


The upgrade is only that easy if you're upgrading from a previous
*qmail-toaster* version. And then, you might have some manual migration of
domains/accounts to do if the toaster was very old (1.2 versions or 
previous).


would updating to qmail-plus be an alternative to a manual update such 
as:


*To update manually*, you must remove libdomainkeys,
control-panel-toaster and spamassassin-toaster with "rpm -e --nodeps"
just prior to updating to ensure a clean build on all the packages. So,
remove these three packages and use the install script for your distro
found in the "Utilities" section above".


The qtp-newmodel script takes care of this for you.


You will also find a file named "qmailmrtg-upgrade-fix.sh in your
support directory. The new version of qmailmrtg-toaster fixes the web
file location so the mrtg info displays properly on all distros. After
an update to the current version, qmailmrtg-upgrade-fix.sh will move
your historical mrtg files to the new location for you.


qtp-newmodel takes care of this too.


and would qmail plus be an aternative to
Jake's QMail Stuff  Toaster Upgrade Script http://v2gnu.com/qmail/


That's an older script, which was used as the starting point for writing
qtp-newmodel. Other scripts from Jakes site such as backup, restore, and
qmail-spam are included in the qmailtoaster-plus package.



Here is my bottom line: I have installed qmail and I have it working ( i
think my version is netQmail 1.05 )
and before put the company on it - I would like to see if I can update
it , update the anti - Spam & Virus parts.


Since you're starting with a non-toaster implementation of qmail (if I'm
reading you right), you'll be essentially building a new toaster and
migrating off of your existing server to the toaster. I don't think I'd 
try

upgrading an existing netQmail server that is in production.


I have not done something like this before - I admire the work and
expertise that has gone into it's creation.


Thanks. We're here to help.

I'd consider building a server from scratch, then migrating over your
domain(s) and users.

How many domains/users are you talking about?

You don't need much of a computer to run the toaster for a home/small
office. An old PII-266 or so with 160M+ of ram would do nicely. HDD should
be several Gigs, 10 or so would be comfortable (depending on your IMAP
requirements). You can bring an old desktop computer out of retirement, 
and

it'd work well as a toaster.

Don't hesitate to ask any questions you might have.


jim respond:

maybe I mislead you  I do have qmailToaster
I installed it from the instructions known as
EZ QmailToaster Fresh Install on CentOS 4.3
Nick Hemmesch <[EMAIL PROTECTED]> June 08, 2006

and since I do  have qmail toaster I can do the qmail-plus upgrade
(   http://qtp.qmailtoaster.com/wiki  )
and the upgrade be as easy as the 1,2,3 that is seen at the website?




-
QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] qmail upgrade to qmail plus

[Eric \"Shubes\"]

Jim Shupert, Jr. wrote:
> Friends,
>  
> here is likely an easy one...
> i have been reading about qmail-plus   (  
> http://qtp.qmailtoaster.com/wiki  )
> would the upgrade be as easy as the 1,2,3 that is seen at the website?
> ( I think i have vers 1.05 )

The upgrade is only that easy if you're upgrading from a previous
*qmail-toaster* version. And then, you might have some manual migration of
domains/accounts to do if the toaster was very old (1.2 versions or previous).

> would updating to qmail-plus be an alternative to a manual update such as:
>  
> *To update manually*, you must remove libdomainkeys,
> control-panel-toaster and spamassassin-toaster with "rpm -e --nodeps"
> just prior to updating to ensure a clean build on all the packages. So,
> remove these three packages and use the install script for your distro
> found in the "Utilities" section above".

The qtp-newmodel script takes care of this for you.

> You will also find a file named "qmailmrtg-upgrade-fix.sh in your
> support directory. The new version of qmailmrtg-toaster fixes the web
> file location so the mrtg info displays properly on all distros. After
> an update to the current version, qmailmrtg-upgrade-fix.sh will move
> your historical mrtg files to the new location for you.

qtp-newmodel takes care of this too.

> and would qmail plus be an aternative to
> Jake's QMail Stuff  Toaster Upgrade Script http://v2gnu.com/qmail/

That's an older script, which was used as the starting point for writing
qtp-newmodel. Other scripts from Jakes site such as backup, restore, and
qmail-spam are included in the qmailtoaster-plus package.

> 
> Here is my bottom line: I have installed qmail and I have it working ( i
> think my version is netQmail 1.05 )
> and before put the company on it - I would like to see if I can update
> it , update the anti - Spam & Virus parts.

Since you're starting with a non-toaster implementation of qmail (if I'm
reading you right), you'll be essentially building a new toaster and
migrating off of your existing server to the toaster. I don't think I'd try
upgrading an existing netQmail server that is in production.

> I have not done something like this before - I admire the work and
> expertise that has gone into it's creation.

Thanks. We're here to help.

I'd consider building a server from scratch, then migrating over your
domain(s) and users.

How many domains/users are you talking about?

You don't need much of a computer to run the toaster for a home/small
office. An old PII-266 or so with 160M+ of ram would do nicely. HDD should
be several Gigs, 10 or so would be comfortable (depending on your IMAP
requirements). You can bring an old desktop computer out of retirement, and
it'd work well as a toaster.

Don't hesitate to ask any questions you might have.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] qmail upgrade to qmail plus

[Jim Shupert, Jr.]

Friends,

here is likely an easy one...
i have been reading about qmail-plus   (   http://qtp.qmailtoaster.com/wiki  )
would the upgrade be as easy as the 1,2,3 that is seen at the website?
( I think i have vers 1.05 )

would updating to qmail-plus be an alternative to a manual update such as: 

To update manually, you must remove libdomainkeys, control-panel-toaster and 
spamassassin-toaster with "rpm -e --nodeps" just prior to updating to ensure a 
clean build on all the packages. So, remove these three packages and use the 
install script for your distro found in the "Utilities" section above".

You will also find a file named "qmailmrtg-upgrade-fix.sh in your support 
directory. The new version of qmailmrtg-toaster fixes the web file location so 
the mrtg info displays properly on all distros. After an update to the current 
version, qmailmrtg-upgrade-fix.sh will move your historical mrtg files to the 
new location for you.

and would qmail plus be an aternative to 
Jake's QMail Stuff  Toaster Upgrade Script http://v2gnu.com/qmail/


Here is my bottom line: I have installed qmail and I have it working ( i think 
my version is netQmail 1.05 )
and before put the company on it - I would like to see if I can update it , 
update the anti - Spam & Virus parts.

I have not done something like this before - I admire the work and expertise 
that has gone into it's creation.

Re: [qmailtoaster] Qmail upgrade - Domainkeys

[Vesko Nedev]

Nick Hemmesch wrote:

Hi Jason,

Here is a quick explanation.
1 - Make dir for ndstorm.com:
  mkdir /var/qmail/control/domainkeys/ndstorm.com
2 - Make domainkey:
dknewkey /var/qmail/control/domainkeys/ndstorm.com/private > ndstorm-dk,txt
3 - Make dns entry:
BIND - in the ndstorm.com zone file (see ndstorm-dk.txt):
private._domainkey  IN  TXT  "k=rsa; p=MEwwDQY . . . to end of key"
   (NOTE QUOTATION MARKS MUST BE THERE)
...
I hope this is of help to you.

Regards,

Nick



Hi Nick,

That "quick explanation" helped me get working domainkeys on 
qmailtoaster and BIND9.

Mail send to yahoo & gmail validated the domain key.
This is how the TXT entries in the zone file look:
---
$ORIGIN orbinet.bg.
_domainkey  86400   IN  TXT "t=y; o=~"
private._domainkey  86400  IN  TXT "k=rsa; 
p=MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxAN/X/xn9g6mTGLBxO5OwLifwQohYzXaFUuAnAwliyp6JAT+gulDR01cD40liyhhYewIDAQAB"

...
---

Thans for the support

Vesko Nedev


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Qmail upgrade - Domainkeys

[Erik Espinoza]

Oh I see it now. I've been racking my brain trying to figure it out,
and I already have working DomainKeys.

Erik

On 5/23/06, Jean-Paul van de Plasse <[EMAIL PROTECTED]> wrote:

Just a very small typo the , before txt


- Original Message -
From: "Erik Espinoza" <[EMAIL PROTECTED]>
To: 
Sent: Wednesday, May 24, 2006 2:35 AM
Subject: Re: [qmailtoaster] Qmail upgrade - Domainkeys


I'm sorry but I don't see a difference in those two lines.

On 5/23/06, Nick Hemmesch <[EMAIL PROTECTED]> wrote:
> Please note:
>
> dknewkey /var/qmail/control/domainkeys/ndstorm.com/private >
> ndstorm-dk,txt
>
>   SHOULD BE:
>
> dknewkey /var/qmail/control/domainkeys/ndstorm.com/private >
> ndstorm-dk.txt
>
> Regards,
>
> Nick
>
> > Hi Jason,
> >
> > Here is a quick explanation.
> >
> > 1 - Make dir for ndstorm.com:
> >
> >   mkdir /var/qmail/control/domainkeys/ndstorm.com
> >
> > 2 - Make domainkey:
> >
> > dknewkey /var/qmail/control/domainkeys/ndstorm.com/private >
> > ndstorm-dk,txt
> >
> > 3 - Make dns entry:
> >
> > BIND - in the ndstorm.com zone file (see ndstorm-dk.txt):
> >
> > private._domainkey  IN  TXT  "k=rsa; p=MEwwDQY . . . to end of key"
> >(NOTE QUOTATION MARKS MUST BE THERE)
> >
> > DJBDNS - in /var/djbdns/tinydns/root/data (make from ndstorm-dk.txt):
> >
> > '_domainkey.ndstorm.com:o=-; [EMAIL PROTECTED]
> > 'private._domainkey.ndstorm.com:k=rsa; p=MEwwDQY . . . to end of key
> >
> >
> > I hope this is of help to you.
> >
> > Regards,
> >
> > Nick
> >
> >
> >
> >> Jason - I don't think domainkeys will have any effect on mail getting
> >> delivered or recieved. domainkeys are a form of authentication that is
> >> used by some mail servers (yahoo.com), but i personally didn't have any
> >> mail bounce back before i got them working. i sent test emails so
> >> hotmail, gmail and yahoo with no problems. hope this helps, if anyone
> >> else would like to chime in with their experience it would be helpful.
> >>
> >> Dewain
> >>
> >> jason p wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I haven't upgraded my toaster to the most recent version, I'm still a
> >>> little confused with the domain keys. What I'm wondering is, if I
> >>> upgrade my toaster before my domain keys are published in my DNS
> >>> records, will this cause problems? Or, if my domainkeys are published
> >>> before I start using them with the new version, would that cause
> >>> problems?
> >>>
> >>> Also, what should the first part of my domainkey in my dns record be?
> >>> I've seen:
> >>>
> >>> _domainkey.domain.tld
> >>>
> >>> private._domainkey.domain.tld
> >>>
> >>> mail._domainkey.domain.tld
> >>>
> >>> I thought it should be:
> >>>
> >>> _domainkey.domain.tld IN TXT "k=rsa; p=MEww……"
> >>>
> >>> Is that right? I don't directly control my DNS records, and I have to
> >>> tell those who do control them exactly what to put in the records…
> >>>
> >>> Thanks in advance,
> >>>
> >>> Jason
> >>>
> >>
> >> -
> >>  QmailToaster hosted by: VR Hosted <http://www.vr.org>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail:
> >> [EMAIL PROTECTED]
> >>
> >>
> >
> >
> >
> > -
> >  QmailToaster hosted by: VR Hosted <http://www.vr.org>
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
>
> -
>  QmailToaster hosted by: VR Hosted <http://www.vr.org>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Qmail upgrade - Domainkeys

[Jean-Paul van de Plasse]

Just a very small typo the , before txt


- Original Message - 
From: "Erik Espinoza" <[EMAIL PROTECTED]>

To: 
Sent: Wednesday, May 24, 2006 2:35 AM
Subject: Re: [qmailtoaster] Qmail upgrade - Domainkeys


I'm sorry but I don't see a difference in those two lines.

On 5/23/06, Nick Hemmesch <[EMAIL PROTECTED]> wrote:

Please note:

dknewkey /var/qmail/control/domainkeys/ndstorm.com/private > 
ndstorm-dk,txt


  SHOULD BE:

dknewkey /var/qmail/control/domainkeys/ndstorm.com/private > 
ndstorm-dk.txt


Regards,

Nick

> Hi Jason,
>
> Here is a quick explanation.
>
> 1 - Make dir for ndstorm.com:
>
>   mkdir /var/qmail/control/domainkeys/ndstorm.com
>
> 2 - Make domainkey:
>
> dknewkey /var/qmail/control/domainkeys/ndstorm.com/private >
> ndstorm-dk,txt
>
> 3 - Make dns entry:
>
> BIND - in the ndstorm.com zone file (see ndstorm-dk.txt):
>
> private._domainkey  IN  TXT  "k=rsa; p=MEwwDQY . . . to end of key"
>(NOTE QUOTATION MARKS MUST BE THERE)
>
> DJBDNS - in /var/djbdns/tinydns/root/data (make from ndstorm-dk.txt):
>
> '_domainkey.ndstorm.com:o=-; [EMAIL PROTECTED]
> 'private._domainkey.ndstorm.com:k=rsa; p=MEwwDQY . . . to end of key
>
>
> I hope this is of help to you.
>
> Regards,
>
> Nick
>
>
>
>> Jason - I don't think domainkeys will have any effect on mail getting
>> delivered or recieved. domainkeys are a form of authentication that is
>> used by some mail servers (yahoo.com), but i personally didn't have any
>> mail bounce back before i got them working. i sent test emails so
>> hotmail, gmail and yahoo with no problems. hope this helps, if anyone
>> else would like to chime in with their experience it would be helpful.
>>
>> Dewain
>>
>> jason p wrote:
>>>
>>> Hi all,
>>>
>>> I haven't upgraded my toaster to the most recent version, I'm still a
>>> little confused with the domain keys. What I'm wondering is, if I
>>> upgrade my toaster before my domain keys are published in my DNS
>>> records, will this cause problems? Or, if my domainkeys are published
>>> before I start using them with the new version, would that cause
>>> problems?
>>>
>>> Also, what should the first part of my domainkey in my dns record be?
>>> I've seen:
>>>
>>> _domainkey.domain.tld
>>>
>>> private._domainkey.domain.tld
>>>
>>> mail._domainkey.domain.tld
>>>
>>> I thought it should be:
>>>
>>> _domainkey.domain.tld IN TXT "k=rsa; p=MEww……"
>>>
>>> Is that right? I don't directly control my DNS records, and I have to
>>> tell those who do control them exactly what to put in the records…
>>>
>>> Thanks in advance,
>>>
>>> Jason
>>>
>>
>> -
>>  QmailToaster hosted by: VR Hosted <http://www.vr.org>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: 
>> [EMAIL PROTECTED]

>>
>>
>
>
>
> -
>  QmailToaster hosted by: VR Hosted <http://www.vr.org>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Qmail upgrade - Domainkeys

[Erik Espinoza]

I'm sorry but I don't see a difference in those two lines.

On 5/23/06, Nick Hemmesch <[EMAIL PROTECTED]> wrote:

Please note:

dknewkey /var/qmail/control/domainkeys/ndstorm.com/private > ndstorm-dk,txt

  SHOULD BE:

dknewkey /var/qmail/control/domainkeys/ndstorm.com/private > ndstorm-dk.txt

Regards,

Nick

> Hi Jason,
>
> Here is a quick explanation.
>
> 1 - Make dir for ndstorm.com:
>
>   mkdir /var/qmail/control/domainkeys/ndstorm.com
>
> 2 - Make domainkey:
>
> dknewkey /var/qmail/control/domainkeys/ndstorm.com/private >
> ndstorm-dk,txt
>
> 3 - Make dns entry:
>
> BIND - in the ndstorm.com zone file (see ndstorm-dk.txt):
>
> private._domainkey  IN  TXT  "k=rsa; p=MEwwDQY . . . to end of key"
>(NOTE QUOTATION MARKS MUST BE THERE)
>
> DJBDNS - in /var/djbdns/tinydns/root/data (make from ndstorm-dk.txt):
>
> '_domainkey.ndstorm.com:o=-; [EMAIL PROTECTED]
> 'private._domainkey.ndstorm.com:k=rsa; p=MEwwDQY . . . to end of key
>
>
> I hope this is of help to you.
>
> Regards,
>
> Nick
>
>
>
>> Jason - I don't think domainkeys will have any effect on mail getting
>> delivered or recieved. domainkeys are a form of authentication that is
>> used by some mail servers (yahoo.com), but i personally didn't have any
>> mail bounce back before i got them working. i sent test emails so
>> hotmail, gmail and yahoo with no problems. hope this helps, if anyone
>> else would like to chime in with their experience it would be helpful.
>>
>> Dewain
>>
>> jason p wrote:
>>>
>>> Hi all,
>>>
>>> I haven't upgraded my toaster to the most recent version, I'm still a
>>> little confused with the domain keys. What I'm wondering is, if I
>>> upgrade my toaster before my domain keys are published in my DNS
>>> records, will this cause problems? Or, if my domainkeys are published
>>> before I start using them with the new version, would that cause
>>> problems?
>>>
>>> Also, what should the first part of my domainkey in my dns record be?
>>> I've seen:
>>>
>>> _domainkey.domain.tld
>>>
>>> private._domainkey.domain.tld
>>>
>>> mail._domainkey.domain.tld
>>>
>>> I thought it should be:
>>>
>>> _domainkey.domain.tld IN TXT "k=rsa; p=MEww……"
>>>
>>> Is that right? I don't directly control my DNS records, and I have to
>>> tell those who do control them exactly what to put in the records…
>>>
>>> Thanks in advance,
>>>
>>> Jason
>>>
>>
>> -
>>  QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Qmail upgrade - Domainkeys

[Nick Hemmesch]

Please note:

dknewkey /var/qmail/control/domainkeys/ndstorm.com/private > ndstorm-dk,txt

  SHOULD BE:

dknewkey /var/qmail/control/domainkeys/ndstorm.com/private > ndstorm-dk.txt

Regards,

Nick

> Hi Jason,
>
> Here is a quick explanation.
>
> 1 - Make dir for ndstorm.com:
>
>   mkdir /var/qmail/control/domainkeys/ndstorm.com
>
> 2 - Make domainkey:
>
> dknewkey /var/qmail/control/domainkeys/ndstorm.com/private >
> ndstorm-dk,txt
>
> 3 - Make dns entry:
>
> BIND - in the ndstorm.com zone file (see ndstorm-dk.txt):
>
> private._domainkey  IN  TXT  "k=rsa; p=MEwwDQY . . . to end of key"
>(NOTE QUOTATION MARKS MUST BE THERE)
>
> DJBDNS - in /var/djbdns/tinydns/root/data (make from ndstorm-dk.txt):
>
> '_domainkey.ndstorm.com:o=-; [EMAIL PROTECTED]
> 'private._domainkey.ndstorm.com:k=rsa; p=MEwwDQY . . . to end of key
>
>
> I hope this is of help to you.
>
> Regards,
>
> Nick
>
>
>
>> Jason - I don't think domainkeys will have any effect on mail getting
>> delivered or recieved. domainkeys are a form of authentication that is
>> used by some mail servers (yahoo.com), but i personally didn't have any
>> mail bounce back before i got them working. i sent test emails so
>> hotmail, gmail and yahoo with no problems. hope this helps, if anyone
>> else would like to chime in with their experience it would be helpful.
>>
>> Dewain
>>
>> jason p wrote:
>>>
>>> Hi all,
>>>
>>> I haven’t upgraded my toaster to the most recent version, I’m still a
>>> little confused with the domain keys. What I’m wondering is, if I
>>> upgrade my toaster before my domain keys are published in my DNS
>>> records, will this cause problems? Or, if my domainkeys are published
>>> before I start using them with the new version, would that cause
>>> problems?
>>>
>>> Also, what should the first part of my domainkey in my dns record be?
>>> I’ve seen:
>>>
>>> _domainkey.domain.tld
>>>
>>> private._domainkey.domain.tld
>>>
>>> mail._domainkey.domain.tld
>>>
>>> I thought it should be:
>>>
>>> _domainkey.domain.tld IN TXT "k=rsa; p=MEww……"
>>>
>>> Is that right? I don’t directly control my DNS records, and I have to
>>> tell those who do control them exactly what to put in the records…
>>>
>>> Thanks in advance,
>>>
>>> Jason
>>>
>>
>> -
>>  QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Qmail upgrade - Domainkeys

[Nick Hemmesch]

Hi Jason,

Here is a quick explanation.

1 - Make dir for ndstorm.com:

  mkdir /var/qmail/control/domainkeys/ndstorm.com

2 - Make domainkey:

dknewkey /var/qmail/control/domainkeys/ndstorm.com/private > ndstorm-dk,txt

3 - Make dns entry:

BIND - in the ndstorm.com zone file (see ndstorm-dk.txt):

private._domainkey  IN  TXT  "k=rsa; p=MEwwDQY . . . to end of key"
   (NOTE QUOTATION MARKS MUST BE THERE)

DJBDNS - in /var/djbdns/tinydns/root/data (make from ndstorm-dk.txt):

'_domainkey.ndstorm.com:o=-; [EMAIL PROTECTED]
'private._domainkey.ndstorm.com:k=rsa; p=MEwwDQY . . . to end of key


I hope this is of help to you.

Regards,

Nick



> Jason - I don't think domainkeys will have any effect on mail getting
> delivered or recieved. domainkeys are a form of authentication that is
> used by some mail servers (yahoo.com), but i personally didn't have any
> mail bounce back before i got them working. i sent test emails so
> hotmail, gmail and yahoo with no problems. hope this helps, if anyone
> else would like to chime in with their experience it would be helpful.
>
> Dewain
>
> jason p wrote:
>>
>> Hi all,
>>
>> I haven’t upgraded my toaster to the most recent version, I’m still a
>> little confused with the domain keys. What I’m wondering is, if I
>> upgrade my toaster before my domain keys are published in my DNS
>> records, will this cause problems? Or, if my domainkeys are published
>> before I start using them with the new version, would that cause
>> problems?
>>
>> Also, what should the first part of my domainkey in my dns record be?
>> I’ve seen:
>>
>> _domainkey.domain.tld
>>
>> private._domainkey.domain.tld
>>
>> mail._domainkey.domain.tld
>>
>> I thought it should be:
>>
>> _domainkey.domain.tld IN TXT "k=rsa; p=MEww……"
>>
>> Is that right? I don’t directly control my DNS records, and I have to
>> tell those who do control them exactly what to put in the records…
>>
>> Thanks in advance,
>>
>> Jason
>>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Qmail upgrade - Domainkeys

[Dewain Riddle]

Jason - I don't think domainkeys will have any effect on mail getting 
delivered or recieved. domainkeys are a form of authentication that is 
used by some mail servers (yahoo.com), but i personally didn't have any 
mail bounce back before i got them working. i sent test emails so 
hotmail, gmail and yahoo with no problems. hope this helps, if anyone 
else would like to chime in with their experience it would be helpful.


Dewain

jason p wrote:


Hi all,

I haven’t upgraded my toaster to the most recent version, I’m still a 
little confused with the domain keys. What I’m wondering is, if I 
upgrade my toaster before my domain keys are published in my DNS 
records, will this cause problems? Or, if my domainkeys are published 
before I start using them with the new version, would that cause problems?


Also, what should the first part of my domainkey in my dns record be? 
I’ve seen:


_domainkey.domain.tld

private._domainkey.domain.tld

mail._domainkey.domain.tld

I thought it should be:

_domainkey.domain.tld IN TXT "k=rsa; p=MEww……"

Is that right? I don’t directly control my DNS records, and I have to 
tell those who do control them exactly what to put in the records…


Thanks in advance,

Jason



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] Qmail upgrade - Domainkeys

[jason p]

Hi all,

 

I haven’t upgraded my toaster to the most recent
version, I’m still a little confused with the domain keys.  What I’m
wondering is, if I upgrade my toaster before my domain keys are published in my
DNS records, will this cause problems?  Or, if my domainkeys are published
before I start using them with the new version, would that cause problems?

 

Also, what should the first part of my domainkey in my dns
record be?  I’ve seen:

_domainkey.domain.tld

private._domainkey.domain.tld

mail._domainkey.domain.tld

 

I thought it should be:

_domainkey.domain.tld       IN  TXT
"k=rsa; p=MEww……"

 

Is that right?  I don’t directly control my DNS records,
and I have to tell those who do control them exactly what to put in the records…

 

Thanks in advance,

Jason