Re: [qmailtoaster] Private IP causes POP3 timeout

2007-08-28 Thread Janno Sannik
it seems more like network/routing/nat problem than qmail toaster problem. Andrew Niemantsverdriet wrote: I have a few customers that have a private IP and are getting timeouts when they try to check their POP3 account. What can I do to stop this from happening?

Re: [qmailtoaster] automtically forward emails from Primary Server to Secondary Server

2007-08-28 Thread Gabriel Lai
Hi, seems like smtproutes is not the function that I required, or probably I don't fully understand the help file. Recap: 2 Servers. Site A Site B have the same Domain Email Address eg: abc.com.my then when Primary server receives the emails, it will copy/forward a copy of the email to Site

Re: [qmailtoaster] Private IP causes POP3 timeout

2007-08-28 Thread PakOgah
or perhaps DNS server. because DNS play important role on mail server Janno Sannik wrote: it seems more like network/routing/nat problem than qmail toaster problem. Andrew Niemantsverdriet wrote: I have a few customers that have a private IP and are getting timeouts when they try to check

Re: [qmailtoaster] Location of spamassasin db? (+)

2007-08-28 Thread L. A.
hmm, systems identical, but only spamassasin different branch. from machine with 3.1 branch: root 2482 0.0 0.0 1424 304 ?SAug27 0:00 supervise spamd qmaill2504 0.0 0.0 1572 368 ?SAug27 0:04 /usr/bin/multilog t s100 n100

Re: [qmailtoaster] Location of spamassasin db? (+)

2007-08-28 Thread Lucian Cristian
L. A. wrote: In 3.1 branch i saw that directory .spamassasin (with some data inside) was placed in /home/vpopmail (and it looks like /home/vpopmail/.spamassasin) But i reinstall on old server spamassasin upto 3.2.3 and today was builded new one . And after i send mail on this machines, in

Re: [qmailtoaster] automtically forward emails from Primary Server to Secondary Server

2007-08-28 Thread Natalio Gatti
Sorry, my mistake ;-) smtproutes will function in case you don't have the domain locally created. I had a similar situation and i solved it by creating a second domain and alias/forwards. The users that use the second domain sent mail using there primary address. Maybe this fits you, but if you

RE: [qmailtoaster] automtically forward emails from Primary Server to Secondary Server

2007-08-28 Thread Mark Burlingame
Ok, So you want people at Site B to be checking their mail on Server B, right? This can be done with DNS entries. I'd set it up like this mail.abc.com.my 10.10.5.10 mail2.abc.com.my 192.168.0.10 And then for the email settings at Site 2, have them use the 2nd

[qmailtoaster] clamd spawns

2007-08-28 Thread Eric Pierce
I've noticed over the last few days we have clients sending some relatively large attachments that causes clamd to get busy (up to 100% cpu) for up to 30-45 seconds. It appears to be normal behavior, so I'm not concerned about that. I'd like to know if it's possible to configure toaster to

[qmailtoaster] users maildir

2007-08-28 Thread Ayesha
Hi all, I made an install and everything ran well. I did access admin-toaster, then qmailadmin and create with success an user. But when I try to send a message, I received an error that !28/8/2007, 11:19:06: SEND - Message has not been sent. Server reply - sorry, no mailbox here by that

Re: [qmailtoaster] automtically forward emails from Primary Server to Secondary Server

2007-08-28 Thread Gabriel Lai
Yes, Phil got me right. However, creating an alias domain name is not a very solution, because users are non-IT knowledge. it will be a mass asking them to change their email address, and might get fired :D Yes, that's what I'm trying to achieve. However, Mark Burlingame gave a very good

RE: [qmailtoaster] automtically forward emails from Primary Server to Secondary Server

2007-08-28 Thread Phil Leinhauser
I think he's asking about the server side not the client side. I think what he is asking is he has 2 locations and as an example, use 2 users, Fred and Mary. Fred works in location 1 and Mary is in location 2. He only has one domain for mail: abc.com.my He wants Fred to check his pop account

RE: [qmailtoaster] automtically forward emails from Primary Server to Secondary Server

2007-08-28 Thread Mark Burlingame
What are you goals? To reduce network usage between site 1 and site 2. correct? Do you also _need_ to have a backup email server? So, if this is true, then you need both servers to have all copies of all mails. By changing DNS to the 2nd server IP, you can stop the extra traffic

Re: [qmailtoaster] automtically forward emails from Primary Server to Secondary Server

2007-08-28 Thread Gabriel Lai
hi mark, With this setup, the Site A users will be checking the mails from Site B server already, right? site B server will becoming a primary server already, right? Correct me if I'm wrong. TQ - Original Message From: Mark Burlingame [EMAIL PROTECTED] To:

RE: [qmailtoaster] users maildir

2007-08-28 Thread Helmut Fritz
look in the domains directory... you did create a (virtual) domain, correct (with vadddomain)? you have to do that to create a user...unless it is a local user. _ From: Ayesha [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 28, 2007 7:25 AM To: qmailtoaster-list@qmailtoaster.com

Re[2]: [qmailtoaster] users maildir

2007-08-28 Thread Ayesha
Hi Helmut, Yep, I use for that vadddomain and vadduser - both were created with success and I found the directory, but I can not send any email, as I received the message that its maibox wasn't found :( I delete it through admin-toaster, and recreate without succeed. Any idea why? Ayesha

Re: [qmailtoaster] Private IP causes POP3 timeout

2007-08-28 Thread Andrew Niemantsverdriet
Ok it was not POP3 timing out it was SMTP giving an error. Outlook express needs some serious help with reporting it's errors. The problem was with dksign and private IP address space not sure what the exact problem was but once I removed all traces of it things started working. On 8/28/07,

RE: [qmailtoaster] automtically forward emails from Primary Server to Secondary Server

2007-08-28 Thread Mark Burlingame
Hello, I'm assuming a few things here. Let me state them now. 1. I assume you have two email servers. Site A receives everything and is then synced to Site B. 2. Both email servers have the same set of data. 3. You don't want to have separate email servers for both.