Re: [vchkpw] vpopmail and postfix

2007-08-24 Thread Rick Widmer



Quey wrote:

[taken out of order...]

> If you feel a reply is warranted (even off list is fine), else this
> my last word on the matter.

Sorry you got caught up in this...  Here is the answer I wish I would 
have posted long ago.  I've been busy with other things...


[from the first message in this thread]


> has anyone actually got postfix to work with vpopmail using the 
current stable release?


Not that I know of.  Vpopmail is tightly integrated with qmail, and 
making it work with another mail server is probably easiest if you just 
start from scratch.


If you have any vpopmail related questions, please start a new thread...


I did not bother to read the guys second post once I got as far as 
outblaze as that said enough, however,  


I did.  It is the message I replied to.


> how can anything to do with vpopmail be OT ?
> I would have thought would be on topic, are you saying we can only
> discuss vpopmail and qmail related issues?

No, but I expect to see more vpopmail content than argument about 
sendmail or postfix.  Vpopmail does not support either of them.


Postfix - used 20 times

Sendmail - used 17 times

vpopmail - used 8 times

qmail - used 2 times

This thread looks more like a sendmail vs. postfix rant to me...  It 
does not belong here.




I am fully aware of your alliances with qmail, is this the reason?


I have no alliance with qmail, but I do subscribe to its list.  Vpopmail 
was written as a virtual domain system for qmail long before I started 
using it.  It is tightly integrated with qmail from top to bottom.  If 
you, or anyone else, want to submit patches to make it work with another 
mail system, they will be considered.  Do not underestimate the effort 
this will take.


Rick


Re: [vchkpw] vpopmail and postfix

2007-08-24 Thread Quey

Rick,
I did not bother to read the guys second post once I got as far as 
outblaze as that said enough, however,  how can anything to do with 
vpopmail be OT ? I had a private email from Wietse  overnight showing me 
a work around, my only concern about postfix using mysql to auth user 
and get the dir for maildir how was it knowing/creating the users dir if 
not using any vpopmails utils adding users, since we do by direct INSERT 
into mysql where initially P/F would have no clue to its name where to 
put the mail, I have my answer so I don't need to carry on with this 
thread, however the point is vpopmail is a powerful pop3d, therefor 
getting "any" MTA to co-operate with it, I would have thought would be 
on topic, are you saying we can only discuss vpopmail and qmail related 
issues? Not being sarcastic,  just inquiring as why you are limiting 
discussions, I am fully aware of your alliances with qmail, is this the 
reason? As I would have thought the wider available usage the better, 
perhaps this is why google shows no help.


If you feel a reply is warranted (even off list is fine), else this was 
my last word on the matter.


Q


Rick Widmer wrote:

And this has what to do with vpopmail?

This is a VPOPMAIL list, not a sendmail list, or a postfix list.  I 
don't mind qmail questions here, but this is way too far off topic to 
continue.


Rick




[vchkpw] Clear Password DB Field Size

2007-08-24 Thread Joshua Megerman
Because of my looking at my DB layout just now to check the UPGRADE
script, I just realized that there's another field that should probably be
changed: pw_clear_passwd is only 16 characters long, and while that's more
than sufficient for crypt (only the first 8 are significant anyway), it's
insufficient for MD5.  After digging the code, there's 2 places that this
would need to change: 1) MAX_PW_CLEAR_PASSWD is currently set to 16,
meaning that attmpts to set a larger password fail.  2) The column
pw_clear_passwd is CHAR(16), so larger passwords won't fit.  vgetpasswd()
uses 128 character buffers, so we should be able to increase the clear
password field to at least 64 without a problem.  I'm not sure it really
needs to go beyond 32, but I actually have been know to use passwords
larger than 16 characters...

Just a thought - feel free to overrule me on this one :)

Josh

Joshua Megerman
SJGames MIB #5273 - OGRE AI Testing Division
You can't win; You can't break even; You can't even quit the game.
  - Layman's translation of the Laws of Thermodynamics
[EMAIL PROTECTED]



Re: [vchkpw] vpopmail 5.4.20 released

2007-08-24 Thread Joshua Megerman

> On Wednesday 22 August 2007, Rick Widmer wrote:
>> http://vpopmail.sf.net/
>>
>> 5.4.20 - released 21-Aug-07
>
> Feels odd to ask this, but in the UPGRADE document, it lists the
> "pw_domain"
> columns as requiring updates, but my databases have just "domain" in them
> except for the vpopmail table.
>
> I've upgraded them manually, but should I be re-naming the columns
> manually?
> I'd prefer not to take the plunge and ask instead. :)
>
> Moving from 5.4.17.
>
Looks like there was a bit of a disconnect early in the coding process
(well before I ever heard of vpopmail, which was in the 5.3.x era), and
only the vpopmail table has a 'pw_domain' column (to match the rest of the
password structure naming, I assume).  All of the other tables have a
'domain' column, instead.  So I made an error when I wrote the fix and
updated the UPGRADE document for 5.4.18 (I think it was that), and
incorrectly labelled the column name for vpopmail 'domain' instead of
'pw_domain'.

Thus, the relevant section of UPGRADE should really be:

ALTER TABLE `dir_control` CHANGE `domain` `domain` CHAR(96) NOT NULL;
ALTER TABLE `ip_alias_map` CHANGE domain domain CHAR(96) NOT NULL;
ALTER TABLE `lastauth` CHANGE domain domain CHAR(96) NOT NULL;
ALTER TABLE `valias` CHANGE domain domain CHAR(96) NOT NULL;
ALTER TABLE `vlog` CHANGE domain domain CHAR(96) NOT NULL;
ALTER TABLE `vpopmail` CHANGE pw_domain pw_domain CHAR(96) NOT NULL;

ALTER TABLE `limits` CHANGE domain domain CHAR(96) NOT NULL,
  ADD `disable_spamassassin` TINYINT(1) DEFAULT '0' NOT NULL AFTER
`disable_smtp`,
  ADD `delete_spam` TINYINT(1) DEFAULT '0' NOT NULL AFTER
`disable_spamassassin`;

Note that this is mostly what it said before, with the vpopmail table line
changed to pw_domain instead of domain.  Sorry I didn't catch this before
it was released...

Ideally I would think that the column names should be consistent across
the tables, but that would cause mandatory breakage, and probably should
be held back for a more major release (redo 5.5 or go to 5.6?).  At least
people will have a greater expectation of needing to read the docs
carefully on somethign bigger than a point upgrade :)

Josh

Joshua Megerman
SJGames MIB #5273 - OGRE AI Testing Division
You can't win; You can't break even; You can't even quit the game.
  - Layman's translation of the Laws of Thermodynamics
[EMAIL PROTECTED]



Re: [vchkpw] vpopmail and postfix

2007-08-24 Thread Rick Widmer

And this has what to do with vpopmail?

This is a VPOPMAIL list, not a sendmail list, or a postfix list.  I 
don't mind qmail questions here, but this is way too far off topic to 
continue.


Rick



Christopher Chan wrote:

Quey wrote:

Christopher Chan wrote:


I think it is your subconscious dislike of postfix that is preventing 
you from exploring postfix and really make full use of its capabilities.




possibly,  it may have a lot to do with all the postfix spammers, " oh 
why use sendmail piss it off use postfix its better", kind of like the 
rest of the spam we all been getting for years "mines bigger than 
yours" ... well sorry, I disagree I have run it before and i find 
sendmail just as or more flexible, but I admit it is each to our own, 
I only wish sendmail natively supported maildir without messy use of 
maildrop.


You are free to hit Spam-L and call Outblaze spammers. I do not work for 
them any more but I dare say you will be run of the list. It is really 
strange that you start off with 'postfix spammers'. In my over three 
years of fighting bounce floods from joe-jobs, fighting scripters and 
419 scammers, I have never seen postfix as part of the problem. There 
has not been one remotely exploitable root hole in postfix but as for 
sendmail, I have had to patch, recompile and reinstall sendmail at least 
4 occasions in my first year with Outblaze before I had to rip it out 
and replace it with postfix. I ripped sendmail out, not because of the 
need to patch security holes, but because the mysql patch was hammering 
our mysql servers into the ground so I guess I cannot blame sendmail 
itself on that score but I do believe I can lay part of the spam blame 
at sendmail for its insecure code since not all 'admins' out there 
maintain their servers properly. Just recently I had to tell one 'admin' 
to seriously reconsider not using Redhat 9 and the sendmail that comes 
on disk.


Unless you use milter, there is no way sendmail is more flexible than 
postfix. As an example, if you can come up with a sendmail ruleset that 
incorporates both sender and recipient into its consideration, I take 
that back. I will accept and I did say that sendmail gives you more 
control due to its rulesets but I disagree on flexibility. Of course, 
one would now just pass on all this stuff to a milter and forget about 
driving yourself crazy with sendmail rulesets.


procmail supports maildir...but yes, it is hard to get a virtual mail 
solution ala vpopmail.




incidently I also have manage large networks, one recently a top 5 
national telco in my country so your 30 million email blah blah doesnt 
astound me or shock me, it is however rather typical of the snotty 
nosed postfix spammers. I'll use cyrus with sendmail over postfix 
anyday,  and since you have contributed nothing of consequence to this 
thread your opinion means as much to me as the kid who lives next door 
that runs his works 3 person exchange server.


OH, you do not want to know how to get postfix to check for mailbox 
existence at smtp time? Okay.




My interest was in not having to change the current setup where I am 
now, which as I said is fed by bunch of sendmail servers that handle 
the job well, I was just exploring other possibilities, where I am now 
we certainly will not move from vpopmail because all that data on 
those FAS6000's would be a nightmare if something went wrong, and I'm 
very happy with vpopmail, its very effcient and fast.




No way did I imply moving away from vpopmail. Why build your own when 
vpopmail does such an excellent job of it?


In both setups, use of vpopmail tools is basically all that needs 
running to configure postfix after the main postfix configuration is 
done. If vpopmail does not have that domain or that user, it is get lost 
at RCPT TO.


What are you using for your backend? mysql or cdb? Did your sendmail 
bigot of a mind prevent you from seeing that postfix can directly use 
vpopmail user databases for user existence checking? I have done a cdb 
patch for sendmail if you want to continue to use sendmail but it was 
done for sendmail 8.12.7 so I guess it probably needs updating...





Re: [vchkpw] change Log_ service

2007-08-24 Thread John Simpson

On 2007-08-23, at 2043, Quey wrote:


Is there an easy  way to have logging go to another service like  
local1, local3 etc without having to massively edit all LOG_'s ?


logging of what? pop3? smtp auth? vpopmaild? onchange?

and how is the logging being done right now?


| John M. Simpson---   KG4ZOW   ---Programmer At Large |
| http://www.jms1.net/ <[EMAIL PROTECTED]> |

| http://video.google.com/videoplay?docid=-1656880303867390173 |





PGP.sig
Description: This is a digitally signed message part