Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: alex_rhys-hurn on January 09, 2008, 07:18:20 PM
-
Hey folks....
I know I shouldnt be using multidrop, but I have to because the client was using it with mdaemon on windows and we are now upgrading them and transfering over to SMTP delivery on SME. Problem is that some mails have been spooled on the POP account.
The SME server is all ready to go apart from downloading these few remaining mails and changing to SMTP delivery.
My Configuration:
I have set multidrop / fetchmail as follows:
[root@server ~]# config show fetchmail
fetchmail=service
FreqOffice=every5min
FreqOutside=every5min
FreqWeekend=every5min
Method=multidrop
SecondaryMailAccount=xxx@hotgossip.co.ke
SecondaryMailPassword=xxx
SecondaryMailServer=mail.hotgossip.co.ke
status=enabled
[root@server ~]#
My problems is this:
Jan 9 11:45:02 server fetchmail[5367]: Authorization failure on domainpop@hotgossip.co.ke@mail.hotgossip.co.ke
Jan 9 11:45:02 server fetchmail[5367]: Query status=3 (AUTHFAIL)
Jan 9 12:00:01 server fetchmail[5684]: Authorization failure on domainpop@hotgossip.co.ke@mail.hotgossip.co.ke
Jan 9 12:00:01 server fetchmail[5684]: Query status=3 (AUTHFAIL)
Jan 9 12:15:01 server fetchmail[5985]: Authorization failure on domainpop@hotgossip.co.ke@mail.hotgossip.co.ke
Jan 9 12:15:01 server fetchmail[5985]: Query status=3 (AUTHFAIL)
Jan 9 12:30:02 server fetchmail[6244]: Authorization failure on domainpop@hotgossip.co.ke@mail.hotgossip.co.ke
Jan 9 12:30:02 server fetchmail[6244]: Query status=3 (AUTHFAIL)
As you can see it is an authentication failure, and looking at the return I can see why: it has not formatted my username properly.
It seems that SME presumes that my username for multidrop will just be a plain username and so it appends the mail server address to the end with an @ sign.
My Hosting service requires that the username be the whole email address.
Can any body help me to tweak the fetchmail configuration to allow this?
Help appreciated.
Thanks.
Alex
-
Since it is only a one only time solution if I understand you correctly... what is wrong with opening your mailclient and creating a new account with the POP mail server as well as the accounts you need to deliver the mail to. If you create the latter as IMAP accounts, you might be able the mail from your POP server and drag them to the proper IMAP mailbox...
-
Thanks for the quick reply.
The reason for this is that, i have 60 addresses and there are 800 messages to do. :shock:
Perhaps that is me being lazy.....
-
Thanks for the quick reply.
The reason for this is that, i have 60 addresses and there are 800 messages to do. :shock:
Perhaps that is me being lazy.....
You said some mails... I assumed only a a hand full not 800! :-)
-
Ok, I have thought of a way.
Well I still have the original mdaemon mail server which was doing multi drop properly.
I am going to commission it again, get it to collect the mail and drop it to all the correct mail boxes.
Then I will use ImapCopy to poll those imap boxes and copy them over to the new SME server.... Whaddya reckon? 10 mins work? Grin...
Wish me luck and thanks for the moral support!
-
It seems that SME presumes that my username for multidrop will just be a plain username and so it appends the mail server address to the end with an @ sign.
No, it does not. It uses exactly the username which you provide.
The failure message shows that the remote mailserver is already appending the domainname (so that you see domainpop@hotgossip.co.ke@mail.hotgossip.co.ke) - you should try just 'domainpop'.
-
I have tried domainpop on its own. The problem is that the MSP specifies that the username MUST be domainpop@hotgossip.co.ke and the mail server is mail.hotgossip.co.ke.
So, in this case why does fetchmail place the @ between the two?
Are there any tags I can use to tell fetchmail to do this differently?
Rgds
Alex
-
I have tried domainpop on its own. The problem is that the MSP specifies that the username MUST be domainpop@hotgossip.co.ke and the mail server is mail.hotgossip.co.ke.
So, in this case why does fetchmail place the @ between the two?
Fetchmail doesn't, as I've already told you. The error message provided by your ISP's POP server has put the two together.
Are you certain you are using the correct password?
-
I have set multidrop / fetchmail as follows:
[root@server ~]# config show fetchmail
fetchmail=service
FreqOffice=every5min
FreqOutside=every5min
FreqWeekend=every5min
Method=multidrop
SecondaryMailAccount=xxx@hotgossip.co.ke
SecondaryMailPassword=xxx
SecondaryMailServer=mail.hotgossip.co.ke
status=enabled
[root@server ~]#
Shouldn't that read:
...
SecondaryMailAccount=xxx (only account name no @domain)
...This is the only way I can imagine the appearance of the double concatenation of the domain name.
-
I have tried domainpop on its own.
And what happens when you try that?
-
when I try that I get error 2 Socket failure.
Jan 9 12:40:02 server fetchmail[6765]: Query status=2 (SOCKET)
Jan 9 12:45:02 server fetchmail[7114]: Query status=2 (SOCKET)
Jan 9 12:50:02 server fetchmail[7230]: Query status=2 (SOCKET)
the reason for this is the my mail service provider REQUIRES the following:
username MUST be domapinpop@hotgossip.co.ke
host name MUST be mail.hotgossip.co.ke
So, in the case of entering only domainpop as username and the host as mail.hotgossip.co.ke then the login details fetchmail submits are domainpop@mail.hotgossip.co.ke which is incorrect, also if I put domainpop as username and hotgossip.co.ke as hotname then also mail fails as that is incorrect.
I have also used my evolution client to try all combinations of this, and also liased with my MSP who insist that the credentials be insterted as such.
My MSP is Dreamhost.com
I still havent resolved this issue and would like to know how it could be done.
Thanks for your help and interest.
Regards,
Alex
-
when I try that I get error 2 Socket failure.
Which means I think that the POP server closed the connection without providing an error message.
So, in the case of entering only domainpop as username and the host as mail.hotgossip.co.ke then the login details fetchmail submits are domainpop@mail.hotgossip.co.ke ...
As I've told you twice already, that is not the case.
-
I apologise if I am not being clear, and thank you for your patience.
Scenario 1:
As per my providers settings requirements:
username: domainpop@hotgossip.co.ke
host: mail.hotgossip.co.ke
Result:
Jan 9 12:15:01 server fetchmail[5985]: Authorization failure on domainpop@hotgossip.co.ke@mail.hotgossip.co.ke
Jan 9 12:15:01 server fetchmail[5985]: Query status=3 (AUTHFAIL)
Jan 9 12:30:02 server fetchmail[6244]: Authorization failure on domainpop@hotgossip.co.ke@mail.hotgossip.co.ke
Jan 9 12:30:02 server fetchmail[6244]: Query status=3 (AUTHFAIL)
Scenario 2:
Adjusted settings:
username: domainpop
host: mail.hotgossip.co.ke
Result:
Jan 9 13:30:02 server fetchmail[8391]: Query status=2 (SOCKET)
Scenario 3:
username: domainpop
host: hostgossip.co.ke
Jan 9 13:30:02 server fetchmail[8391]: Query status=2 (SOCKET)
Now the reason this is occuring according to my mail host is because they are running some sort of mail cluster feature, and that the host mail.hotgossip.co.ke is in fact some sort of alias for another host. They therefore need the full email address as the username in order to forward the request to the proper host.
Now I dont pretend to understand this stuff, but it explains the socket error that occurs when incorrect credentials are given, because a connection is made, but because they are wrong the connection just fails without specifics.
Perhaps I should give up at this point....