Install Qmail Toaster Plus and try newmodel upgrade, it's one of the
BEST!
On 2007.02.18, at 20:04, Eric Shubes wrote:
The wiki is the best source of documentation and such.
See http://wiki.qmailtoaster.com/index.php/Upgrading
Robert S Galloway wrote:
Howdy everyone.
First, thanks to all
On 2/16/07, Erik A. Espinoza [EMAIL PROTECTED] wrote:
Greetings,
The following packages (qmail-toaster, ucspi-tcp-toaster,
clamav-toaster, courier-authlib-toaster) have been moved from the
devel site to the main site.
http://www.qmailtoaster.com/
All but ucspi-tcp-toaster are security
On 2/22/07, Natalio Gatti [EMAIL PROTECTED] wrote:
Anyone else had troubles with clamav 0.90?
I just tried to upgrade with rpm -Uvh and this is what I got:
package clamav-toaster-0.90rc2-1.3.8 (which is newer than
clamav-toaster-0.90-1.3.10) is already installed. Removing the
packaage
I keep having problems with domainkeys, I've followed the instructions to
the letter at http://www.qmailtoaster.com/qt-doc/QT-README.domainkeys and it
still is failing almost 24 hours later. I got it working before but I had
updated qmailtoaster with the newer rpms released on the 16th and it
@400045ddacaa0c7eb13c delivery 65: deferral: qmail-
inject:_fatal:_unable_to_parse_this_line:/To:_undisclosed-recipients:/
write_to_qmail-inject_failed:_32/system_error/
this is from /var/log/qmail/send/current
bottom line is when i send from same client but different outgoing
mail
Brian Trudeau wrote:
I keep having problems with domainkeys, I’ve followed the instructions
to the letter at http://www.qmailtoaster.com/qt-doc/QT-README.domainkeys
and it still is failing almost 24 hours later. I got it working before
but I had updated qmailtoaster with the newer rpms
Igor Vukotic' wrote:
@400045ddacaa0c7eb13c delivery 65: deferral:
qmail-inject:_fatal:_unable_to_parse_this_line:/To:_undisclosed-recipients:/write_to_qmail-inject_failed:_32/system_error/
this is from /var/log/qmail/send/current
bottom line is when i send from same client but
Well my TTL is set for 3600 so it should've been updated by now, I think it
might be failing for some other reason. How can I test it locally?
--
Brian Trudeau, Network Administrator
Eastek International Corporation
330 Hastings Drive, Buffalo Grove, IL 60089
Tel: (847) 353-8300 Ext. 213
Brian Trudeau wrote:
Well my TTL is set for 3600 so it should've been updated by now, I think it
might be failing for some other reason. How can I test it locally?
dig it?
--
-Eric 'shubes'
-
QmailToaster hosted by:
No I mean to see if it's using the right private and public keys... Like how
do you use dktest?
--
Brian Trudeau, Network Administrator
Eastek International Corporation
330 Hastings Drive, Buffalo Grove, IL 60089
Tel: (847) 353-8300 Ext. 213 Fax: (847) 353-8900
Web:
Peter Peltonen wrote:
On 2/22/07, Natalio Gatti [EMAIL PROTECTED] wrote:
Anyone else had troubles with clamav 0.90?
I just tried to upgrade with rpm -Uvh and this is what I got:
package clamav-toaster-0.90rc2-1.3.8 (which is newer than
clamav-toaster-0.90-1.3.10) is already
Brian Trudeau wrote:
No I mean to see if it's using the right private and public keys... Like how
do you use dktest?
I haven't done that. Check the list archives. I think Alexey posted
something a little while ago on how to do that.
--
-Eric 'shubes'
ClamAV upgrades should always take place as follows:
rpmbuild --rebuild --with $DIST clamav-new.src.rpm
rpm -e --nodeps clamav-toaster
rpm -Uhv /path/to/clamav-new.$ARCH.rpm
service qmail cdb
I am looking to make this work with rpm -Uhv, but currently this is
the procedure.
As far as 0.90rc2
Would clamav-toaster-0.88.7-1.3.7 need to be removed, or only *rc* versions?
Erik A. Espinoza wrote:
ClamAV upgrades should always take place as follows:
rpmbuild --rebuild --with $DIST clamav-new.src.rpm
rpm -e --nodeps clamav-toaster
rpm -Uhv /path/to/clamav-new.$ARCH.rpm
service qmail
Tihis is only one client of many, and this work on Apple OSX 10.4.8
(current) and system mail application.
Only this mail give this error, any other works fine from that
client..
On 2007.02.22, at 17:53, Eric Shubes wrote:
Igor Vukotic' wrote:
@400045ddacaa0c7eb13c delivery 65:
On 2/22/07, Erik A. Espinoza [EMAIL PROTECTED] wrote:
ClamAV upgrades should always take place as follows:
rpmbuild --rebuild --with $DIST clamav-new.src.rpm
rpm -e --nodeps clamav-toaster
rpm -Uhv /path/to/clamav-new.$ARCH.rpm
service qmail cdb
I am looking to make this work with rpm -Uhv,
I have a Mac Mini with current OSX that's working fine with the toaster,
smtp and imap.
What are the Mac's configuration parameters for smtp (outgoing)? I'm using
port 587, but I don't see why port 25 wouldn't work. I don't know much about
the Mac, but it sounds to me like it's trying to do
Indeed.
On 2/22/07, Eric Shubes [EMAIL PROTECTED] wrote:
Would clamav-toaster-0.88.7-1.3.7 need to be removed, or only *rc* versions?
Erik A. Espinoza wrote:
ClamAV upgrades should always take place as follows:
rpmbuild --rebuild --with $DIST clamav-new.src.rpm
rpm -e --nodeps
Indeed which?
Erik A. Espinoza wrote:
Indeed.
On 2/22/07, Eric Shubes [EMAIL PROTECTED] wrote:
Would clamav-toaster-0.88.7-1.3.7 need to be removed, or only *rc*
versions?
Erik A. Espinoza wrote:
ClamAV upgrades should always take place as follows:
rpmbuild --rebuild --with $DIST
On Thursday 22 February 2007, Erik A. Espinoza wrote:
ClamAV upgrades should always take place as follows:
rpmbuild --rebuild --with $DIST clamav-new.src.rpm
rpm -e --nodeps clamav-toaster
rpm -Uhv /path/to/clamav-new.$ARCH.rpm
service qmail cdb
I am looking to make this work with rpm
Obsoletes wouldn't do it. I think the correct thing would be setting the Epoch.
Erik
On 2/22/07, Scott Jones [EMAIL PROTECTED] wrote:
On Thursday 22 February 2007, Erik A. Espinoza wrote:
ClamAV upgrades should always take place as follows:
rpmbuild --rebuild --with $DIST
Dear All,,
In my QT I see a weird kind of logs like .
tail -f /var/log/qmail/smtp/current
@400045ddfa711ffc2dd4 CHKUSER accepted rcpt: from
[EMAIL PROTECTED]:: remote
mail3.bigpixelnet.com:unknown:69.6.1.135 rcpt [EMAIL PROTECTED] : found
existing recipient
@400045ddfa7526838134
Hi list!
I've upgraded with -Uvh from 0.88.7 to 0.90 and what happened was that it did
not remove 0.88.7 and in fact it kept using that version until I did an rpm -e
--no-deps... After that everything is working fine...
Best regards,
Fernando
De: Eric
On 2/22/07, Erik A. Espinoza [EMAIL PROTECTED] wrote:
ClamAV upgrades should always take place as follows:
I just did the actual upgrade, restarted all services but I still see
this in my Received headers:
Received: by simscan 1.3.1 ppid: 25926, pid: 25928, t: 0.2803s
scanners:
Did you run service qmail cdb?
Erik
On 2/22/07, Peter Peltonen [EMAIL PROTECTED] wrote:
On 2/22/07, Erik A. Espinoza [EMAIL PROTECTED] wrote:
ClamAV upgrades should always take place as follows:
I just did the actual upgrade, restarted all services but I still see
this in my Received
On 2/6/07, Jake Vickers [EMAIL PROTECTED] wrote:
I wrote a script that's on my site that will monitor BLs for you and
remove the slow ones. v2gnu.com
I've just tried your script and it works great, thanks. I am running
it now once per hour (how often do you run it yourself?).
One thing came
On 2/22/07, Erik A. Espinoza [EMAIL PROTECTED] wrote:
Did you run service qmail cdb?
No I did not, that did the trick, thanks! I thought that it was only
required if one does changes in
/etc/tcprules.d/tcp.smtp.cdb
/var/qmail/control/badmimetypes.cdb
/var/qmail/control/badloadertypes.cdb
Hi list,
I keep getting a simscan: connect error 2 in my log files... aparently the
e-mail still gets processed and delivered (if not filtered) but I do not
understand what this means.
I've googled for info but without any success.
Can anyone explain or point the direction I should follow?
The /var/qmail/control/simversions.cdb file tells Qmail which versions
of the different scanners are running.
I prefer not to have rpm's running service commands, which is why it
is not done automatically. It doesn't change the version you are
scanning with, just the header in the e-mail.
Erik
Peter Peltonen wrote:
On 2/22/07, Erik A. Espinoza [EMAIL PROTECTED] wrote:
Did you run service qmail cdb?
No I did not, that did the trick, thanks! I thought that it was only
required if one does changes in
/etc/tcprules.d/tcp.smtp.cdb
/var/qmail/control/badmimetypes.cdb
Peter Peltonen wrote:
On 2/6/07, Jake Vickers [EMAIL PROTECTED] wrote:
I wrote a script that's on my site that will monitor BLs for you and
remove the slow ones. v2gnu.com
I've just tried your script and it works great, thanks. I am running
it now once per hour (how often do you run it
Fernando Azevedo wrote:
Hi list,
I keep getting a simscan: connect error 2 in my log files... aparently
the e-mail still gets processed and delivered (if not filtered) but I do
not understand what this means.
I've googled for info but without any success.
Can anyone explain or point
ashok wrote:
Dear All,,
In my QT I see a weird kind of logs like …
tail -f /var/log/qmail/smtp/current
@400045ddfa711ffc2dd4 CHKUSER accepted rcpt: from
[EMAIL PROTECTED]:: remote
mail3.bigpixelnet.com:unknown:69.6.1.135 rcpt [EMAIL PROTECTED] : found
existing recipient
On Thursday 22 February 2007, Erik A. Espinoza wrote:
Obsoletes wouldn't do it. I think the correct thing would be setting the
Epoch.
Epoch probably would be the better way when dealing with a version number
change, and in the case of clamav wouldn't be a problem since there are no
34 matches
Mail list logo
